Re: onlog -n hung, online (CKPT REQD)
Running onlog on the log, puts a lock on the log. Hence if it is the
current log then no process can update it. It means that no activity can
happen on the system.
To examine the current log, switch logs 'onmode -l' and then run onlog
on the log. The next log is now the current one and onlog does not lock
out any users.
Dilip Kikla
Art S. Kagel wrote:
>
> Peter Groarke wrote:
> >
> > Hi,
> > I wanted to examine the current logical log file, (I was not logged
> > in as informix).
>
> > so I typed:
> > onlog -n 24596 > ./blah> >
> > The onlog session just seems to be hung. When I do onstat - it gives:
> >
> > INFORMIX-OnLine Version 7.13.UC4 -- On-Line (CKPT REQ) -- Up 8 days
> > 04:42:30 -- 14832 Kbytes
>
> > Blocked:CKPT
>
> > The status of the onlog session seems to be sleeping(Forever)
>
> > What state is online in? , would an onmode -c clear the problem ?
>
> > Im using 7.13 on Solaris 2.6
>
> Known bug that coincidently bit me Monday. Onlog frequently hangs and
> blocks the next checkpoint. Killing the process will not stop the
> session. Fortunately, unlike a similar problem with killed UPDATE
> STATISTICS processes, the session can be killed. As root do an onmode
> -z <sessid> on the session THEN kill the onlog process, it will not die
> on it's own when the session is killed. This should even work if the
> process is already dead. The bug was fixed in 7.23 or 7.24 (I did not
> ask). Run onlog at your own risk in earlier versions.
>
> Art S. Kagel