oracle database shutdown
SQL> shutdown immediate
In alert log file:
shutting down instance (immediate)
license high water mark = 7
sculkget : failed to lock $ORACLE_HOME/dbs/lkinstabc
sculkget : lock held by PID: 16191
shutdown : active processes prevent shutdown operation
Can you guys help me in shuttting down database gracefully as I dont want to corrupt the database
In alert log file:
shutting down instance (immediate)
license high water mark = 7
sculkget : failed to lock $ORACLE_HOME/dbs/lkinstabc
sculkget : lock held by PID: 16191
shutdown : active processes prevent shutdown operation
Can you guys help me in shuttting down database gracefully as I dont want to corrupt the database
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
no its the same page but not describing a "known Problem" but describing a workaround !!!!
ASKER
How to find that process I'd which need to be deleted. I heard in this case we can try. SQL> shutdown abort. SQL> startup restrict. SQL> shutdown immediate . But my question is if we issue shutdown abort won't it corrupt the database as it's not graceful shutdown
It is not a graceful shutdown but it will likely not corrupt the database per say. Oracle is pretty good about instance recovery after a 'system crash'. A shutdown abort basically simulates a crash.
You should be able to track down the session from v$session but since you are hitting a bug that seems to refer to a SYS process, killing it would also likely simulate a crash.
Read the Metalink note referenced in the link I posted above. It should have all the details. The note I'd is at the bottom of the discussion.
You should be able to track down the session from v$session but since you are hitting a bug that seems to refer to a SYS process, killing it would also likely simulate a crash.
Read the Metalink note referenced in the link I posted above. It should have all the details. The note I'd is at the bottom of the discussion.
The process id is nothing but it is showing in ur alert log file i.e PID:16191 through this trace the sid and check there is any active session are running.
As slightwv told the shutdown abort will not corrupt the database usually.
and also go through the metalink doc which will give u more inputs on it.
and also you can try enabling event trace on it as mention in the slightwv posted above.
As slightwv told the shutdown abort will not corrupt the database usually.
and also go through the metalink doc which will give u more inputs on it.
and also you can try enabling event trace on it as mention in the slightwv posted above.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I do agree that it isn't all that bad.
>>shutdown immediate does on the way down, shutdown abort does on the way back up
Like your post, going from old memory here: Shutdown immediate waits for all current transactions to either commit or rollback. Shutdown abort kills all current transactions. On the way back up Oracle will have to roll through the undo, replay the partial transactions then turn around and roll them all back.
>>shutdown immediate does on the way down, shutdown abort does on the way back up
Like your post, going from old memory here: Shutdown immediate waits for all current transactions to either commit or rollback. Shutdown abort kills all current transactions. On the way back up Oracle will have to roll through the undo, replay the partial transactions then turn around and roll them all back.
check the PID what exactly its doing if its not required kill that particular PID and try to shutdown the database.
kill -9 PID