Operating System - HP-UX
1752812 Members
6138 Online
108789 Solutions
New Discussion юеВ

Re: oracle not shuting down as expected

 
SOLVED
Go to solution
Michael Fairclough
New Member

Re: oracle not shuting down as expected

The key is "SHUTDOWN: waiting for active calls to complete." There should be a process id listed in the alert log just after this message. That's the process that needs to be killed. Here's one of mine:

Fri Jul 23 00:10:14 2004
Active call for process 24050 user 'oraprd' program 'oracle@drerpdb01 (TNS V1-V3)'
SHUTDOWN: waiting for active calls to complete.

In this case the process 24050 needs to be killed. Once it's killed the database will shutdown normally.
Yogeeraj_1
Honored Contributor

Re: oracle not shuting down as expected

hi Rick,

The database is waiting for pmon to clean up processes, but pmon is unable to clean them. The client connections to the server are causing the shutdown immediate or normal to hang. Killing them allows pmon to clean up and release the associated Oracle processes and resources.

You can write a script to locate and kill any client connections to the database at the Unix level, as follows:

a. Locate any client connections to the database using ps, and grep for any processes belonging to this .

Example: ps -ef | grep YD

b. Look for processes that include a 'LOCAL=NO' designation.

Example: ora816 235 1 0 Sep 22 1:01 oracleYD (LOCAL=NO)

c. Kill the Unix process(es) with the 'LOCAL=NO' designation.

Example: kill -9 235

hope this helps!

regards
Yogeeraj
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
Jean-Luc Oudart
Honored Contributor

Re: oracle not shuting down as expected

Rick,

The normal procedure would be to shutdown or shutdown immeiate, but as mentioned it could hang if you have session still running (lon op ?) or a (very) long backout transaction in progress.

shutdown abort will avoid that but the database would be in a status I don't think you can use for cloning.
shutdown abort + startup + shutdown
You may still have to replay (rollback) the aborted transaction and this too can take sometimes.

The alternative is to use a watchdog for your shutdown immediate.
The watchdog process will check for the shutdown script still running after a while (!) , kill it and run a shutdown abort instead.
Not the nicest solution I agree. but the abort means you could start your backup.

Regards,
Jean-Luc

PS : if this is just a DEV database, you may just stick to shutdown abort + startup + shutdown as mentioned in an other post
fiat lux
Rick Garland
Honored Contributor

Re: oracle not shuting down as expected

Many thanks for the extra info.
Rick Garland
Honored Contributor

Re: oracle not shuting down as expected

Close up