Resolves the shutdown:waiting for active calls to complete when the Oracle database is closed.

When the Oracle database is closed, the shutdown immediate is not closed after the command, the alert log is viewed, and the log is prompted after the wait period:

Shutdown:waiting for active calls to complete.

The reason is that some processes cannot be cleaned by the Pmon process, causing shutdown to shut down while hang live.

= = "according to observation, in oracle10g and above version, will be the following tips:
Active call for Process 12345 user ' Oracle ' ORACLE@ABCD '
Shutdown:waiting for active calls to complete.
That is to say which process caused the wait, at this time kill-9 12345 process can.


= = But in the Oracle 8I release, it is not prompted which process active caused the shutdown process to hang, prompted as follows:
Sun June 26 21:42:38 2015
Arc0:beginning to archive log# 6 seq# 393635
arc0:completed Archiving log# 6 seq# 393635
Sun June 26 21:42:54 2015
Shutting down instance (immediate)
License High Water mark = 235
Sun June 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 services.

This information can be referenced in MOS documentation:
Alert Log:shutdown waiting for Active Calls to Complete (document ID 1039389.6)
How do I shut down the database in the quickest way, cleanly? (Document ID 1577321.1)



When you recently encountered a shutdown of an Oracle 8.1.7.4.0 database, check and process the database process normally before shutting down:
Turn off listening to see if there are any ps-ef|grep ora_j, see if there is a transaction running, whether there are large transactions that need to be rolled back on reboot, multiple switches archived, multiple execution checkpoint completed, and then shut down the library.
In the above inspection, the LOCAL=NO session has been processed, also confirmed that no transaction operation;
However, when the shutdown immediate command executes, it still hang and reports shutdown:waiting for active calls to complete.
Wait for a long time, to see only the following process, try to kill arc0 process, Pmon process termination instance (equivalent to shutdown ABORT), the lucky is shutdown before the confirmation of transaction completion, 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; no transaction running at the same time the data has been written to disk; If you can only shutdown ABORT or other kill processes cause shutdown ABORT and rarely cause an instance startup exception caused by data corruption (such as data files, REDO log corruption).


The log is as follows:
Sun June 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 June 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