Sometimes shutdown immediate is issued when the database is closed, and the command has not been closed. View alert logs. There are hints in the log after waiting for a while:
Shutdown:waiting for active calls to complete.
The reason is that some processes cannot be cleaned up by the Pmon process. Causes shutdown to shut down and hang.
= = "according to observation, in oracle10g and above version number. Will be for example the following prompt:(2015/11/24 the latest validation ORACLE9206 will also prompt for the process number)
Active call to process 12345 user ' Oracle ' program ' [email protected] '
Shutdown:waiting for active calls to complete.
That is, which process causes the wait. At this point the kill-9 12345 process is available.
= = "However, in the Oracle 8I version number, it is not prompted which process active caused the shutdown process hang. The demo sample is as follows:
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.
Such a case. Only good to find Ps-ef|grep Local=no related processes are killed and other processing ideas.
= = "Assuming the Windows platform, no process can kill, the best way is to stop the Oracle database service."
This information is available in the MOS documentation:
Alert Log:shutdown waiting for Active Calls to complete (document ID 1039389.6)
How to shut down the database in the quickest way? (Document ID 1577321.1)
A recent shutdown of the Oracle 8.1.7.4.0 database was encountered before it was shut down. Check and process according to the normal shutdown database process:
Turn off monitoring to see if there are Ps-ef|grep ora_j, see if there is a transaction in progress, if there is a large transaction that needs to be rolled back at another start, the archive is switched multiple times, the checkpoint is completed multiple times, and then the library is closed.
In the above check, Local=no's session has been processed, also confirmed that no transaction execution;
However, the shutdown immediate command runs. Still hang and report shutdown:waiting for active calls to complete.
After a long wait, do a review just for example the following process, try the kill arc0 process. Pmon process terminates the instance (equivalent to shutdown ABORT), fortunately is the shutdown before the completion of the confirmation transaction, switching redo/checkpoint, and so on, all normal startup.
= = "In such cases, it is recommended to switch logfile several times before shutdown immediate, and to perform checkpoints to ensure that the application is closed at the same time and that the data has been written to disk at the same time without transaction execution. Assuming that helplessness can only shutdown abort or other kill processes that cause shutdown abort, there are very few instances of data corruption (such as data files, REDO log corruption) that result in an instance start exception.
Logs such as the following:
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
Processes such as the following
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
When you close the database shutdown:waiting for active calls to complete. Processing
