Re: Table Locking Problem

From: Graeme Farmer <g_farmer_at_halas.com.au>
Date: 2000/04/20
Message-ID: <FLrL4.4733$E4.9891@newsfeeds.bigpond.com>#1/1

SC wrote in message <38FD6B74.A6174725_at_hotmail.com>...
>Graeme, Mark
>
>As per my understanding:- when you kill a process
>its status appear to be as killed but the process is
>actually cleaned by SMON. SMON cleans up processes at
>regular intervals (which is around 3 minutes).
>Cant remember the parameter that sets smon timings (if any).
>

SMON is responsable for instance recovery and coalescing. PMON is the ORACLE "janitor" responsible for wiping up after aborted user sessions.

Quote from ORACLE PRESS:

"When a user process fails, PMON is there to handle automatic process recovery for the database in several areas. Some of those areas are listed in the bullet list below:

- Rollback on the failed process
- Relase of locks on tables and internal latches the process acquired
- Removal of that process identifier from active processes in the V$

performance views"

>you can perhaps try to write some shell script in unix
>that will trigger smon process thereby clearing up the process.
>

from my original post:

    ordebug wakeup <pid of PMON>

Thanks all the same,

Graeme.

>s_c_99_at_hotmail.com
>
>Graeme Farmer wrote:
>>
>> Mark,
>>
>> It definately took a lot longer for Oracle to release the lock on the
 table
>> than it did to lock it. As for the user process I did check it and it was
>> still there as KILLED but I wouldn't know if the serial# was changing.
>>
>> Can you, or anyone else, answer the question as to what Oracle was doing
>> when I issued the shutdown immediate command and throughout 15 minutes
 there
>> was zero CPU/DISK activity? Surely if the db wasn't shutting down due to
 the
>> locks being removed there would be some CPU activity as the locks were
 being
>> removed.
>> Ta,
>> Graeme.
Received on Thu Apr 20 2000 - 00:00:00 CDT