Shutdown is busy updating waiting for lock

Wait Time: The session will wait 1 / 100 of a second and check to see if the new dispatchers have started else the session will wait again Parameters: A session is waiting on another process to allocate a system change number (SCN).

If the foreground timed out waiting on a process to get the SCN, the foreground will get the SCN.

This means that after the wait, the DBWR will scan the whole buffer cache again.

This could happen, for example, during a close database or a local checkpoint./home/oracle/sqlplus ' / as sysdba ' @/export/home/mysid/&1 # Or, manually set the environment . If you want a full set of Oracle shutdown and startup scripts, get the Oracle script collection.Debugging a hung database In these cases, the DBA had few options other than to force-down the instance and warmstart it.Still, you can't really hurt the database using the shutdown abort command. For more, get the book "Oracle shell Scripting": # ************************** # Shutdown crontab entry # ************************** 00 7 * * * /u01/app/oracle/bin/prodb1 /home/tmp/# ************************** # Shutdown script # ************************** #! ORACLE_SID=mon1 export ORACLE_SID ORACLE_HOME=`cat /etc/oratab|grep ^$ORACLE_SID:|cut -f2 -d':'` export ORACLE_HOME PATH=$ORACLE_HOME/bin:$PATH export PATH -- ************************** -- Shutdown script -- ************************** shutdown abort; startup restrict; shutdown immediate; While this uses the "shutdown abort" (meaning to abort in-flight transactions, it's necessary to re-start and allow Oracle to rollback the in-flight work./bin/ksh # Source the to set the Oracle environment . Right after this normal restricted startup, Oracle will safely shutdown with shutdown immediate.

Search for shutdown is busy updating waiting for lock:

shutdown is busy updating waiting for lock-47shutdown is busy updating waiting for lock-19

This event happens because a buffer is either being read into the buffer cache by another session (and the session is waiting for that read to complete) or the buffer is the buffer cache, but in a incompatible mode (that is, some other session is changing the buffer). If the session was waiting for a buffer during the last wait, then the next wait will be 3 seconds.

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “shutdown is busy updating waiting for lock”

  1. Wait Time: The session will wait 1 / 100 of a second and check to see if the new dispatchers have started else the session will wait again Parameters: A session is waiting on another process to allocate a system change number (SCN).