Re: PMon Interval

You could also increase CLEANUP_ROLLBACK_ENTRIES to force PMON to do more cleanup work when it activates...and reduce the number of cycles it takes to clean up disconnected session transactions.

It defaults to 20, try incrementing it slowly in increments of 20 until you get desired results...

"Nevin Hahn" <nevin.hahn_at_born.com> wrote in message news:39B48EC9.769B4843_at_born.com...
> Hi Daniel,
>
> You may have a lock problem. If the session that became disconnected was
> somehow locking rows, or tables, it may be involved in a locking/blocking
> relationship with another
> session. The easiest way to resolve these problems is usually to identify
 the
> SID,SERIAL#
> of the session and issue the alter system kill session 'SID,SERIAL#'; to
 remove
> the
> dead session. If the server only marks the session for kill then you'll
 have to
> wait for
> PMON to wake up and kill the session off otherwise it should happen
> immediately.
>
> Nevin Hahn
> nhahn_at_evoke.com
>
> Daniel Dai wrote:
>
> > My computer suddently disconnect from the database server when I am
 running
> > a SQL script, I think the current transaction will rollback after a
 while
> > when PMON notice this process is disconnect. But I re-check it two hours
> > later, I found the resource still occupied, I can not update the rows it
> > involved. The script is not commited nor rollbacked. I wonder how many
 time
> > PMON needed to notice the process is disconnected and release the
 resource.
>
Received on Wed Sep 06 2000 - 18:52:30 CDT