Sometimes shutdown immediate is issued when the database is closed, the command has not been closed, view the alert log, after waiting for a period of time the log is prompted:
Shutdown:waiting for active calls to complete.
The reason is that some processes cannot be cleaned up by the Pmon process, causing the shutdown to shut down and hang.
= = "according to observation, in oracle10g and above, will be the following prompt:
Active call to process 12345 user ' Oracle ' program ' [email protected] '
Shutdown:waiting for active calls to complete.
That is to say which process caused the wait, at this time kill-9 12345 process can be.
= = "However, in the Oracle 8I version, it is not prompted which process active causes the shutdown process hang, the following prompt:
Sun Jul 26 21:42:38 2015
Arc0:beginning to archive log# 6 seq# 393635
arc0:completed Archiving log# 6 seq# 393635
Sun Jul 26 21:42:54 2015
Shutting down instance (immediate)
License High Water mark = 235
Sun Jul 26 21:48:02 2015
Shutdown:waiting for active calls to complete.
In this case, had to find Ps-ef|grep Local=no related processes are killed and other processing ideas.
= = "If it is a Windows platform, there is no process to kill, the best way is to stop the Oracle database service."
This information can be consulted in the MOS documentation:
Alert Log:shutdown waiting for Active Calls to complete (document ID 1039389.6)
How do I close a database cleanly in the quickest way? (Document ID 1577321.1)
When you recently encountered a shutdown of an Oracle 8.1.7.4.0 database, check and process the normal shutdown database process before shutting down:
Turn off monitoring to see if there are Ps-ef|grep ora_j, see if there is a transaction running, if there is a large transaction that needs to be rolled back at reboot, multiple switch archives, multiple executions checkpoint completed, and then close the library.
In the above check, Local=no's session has been processed, also confirmed that no transaction operation;
However, when the shutdown immediate command executes, it is still stuck and reported shutdown:waiting for active calls to complete.
After a long wait, to see only the following process, try to kill the ARC0 process, the Pmon process terminates the instance (equivalent to shutdown ABORT), fortunately, before shutting down the transaction to confirm the completion of transactions, switching redo/checkpoints and other operations are carried out, startup all normal.
= = "In this case, it is recommended to switch logfile several times before shutdown immediate, and to perform checkpoints, while ensuring that the application is closed, when no transaction is running and the data has been written to disk; if only shutdown Abort or other kill processes cause shutdown ABORT and rarely cause an instance initiation exception due to data corruption (such as data files, REDO log corruption).
The logs are as follows:
Sun Jul 11 21:50:57 2015
Errors in FILE/ORACLE/8.1.7/ADMIN/AAA/BDUMP/PMON_26680_AAA.TRC:
Ora-00473:arch process terminated with error
Sun Jul 11 21:50:57 2015
Pmon:terminating instance due to error 473
Instance terminated by Pmon, PID = 26680
The process is as follows
Oracle 17016 1 0 Feb 11-60:13 ora_arc0_aaa
Oracle 18346 1 0 Feb 11-1568:00 ora_lgwr_aaa
Oracle 18858 1 0 Feb 11-0:02 ora_reco_aaa
Oracle 22528 1 0 Feb 11-122:02 ora_dbw0_aaa
Oracle 26680 1 0 Feb 11-55:24 ora_pmon_aaa
Oracle 28856 1 0 Feb 11-6:02 ora_smon_aaa
Oracle 29776 1 0 Feb 11-67:07 ora_ckpt_aaa
Oracle 80566 67462 0 21:50:44 pts/0 0:00 grep ora_
Oracle 110824 1 0 may 28-18:18 ora_arc1_aaa
Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.
When you close the database shutdown:waiting for active calls to complete. Processing
