PMON TRYING TO START CJQ0 DURING DATABASE SHUTDOWN-ORA-443&ORA-450
環境：
Oracle 11g 11.2.0.3 on Linux 64bit
shutdown的時候出現ORA-00450/ORA-00443的錯誤。
alert及trace內容如下：
[oracle@bvh trace]$ vi alert_ora11203.log
Fri Oct 18 00:38:12 2013
Shutting down instance (immediate)
Shutting down instance: further logons disabled
Fri Oct 18 00:38:13 2013
Starting background process CJQ0
Errors in file /u01/11.2.0.3/diag/rdbms/ora11203/ora11203/trace/ora11203_pmon_2532.trc:
ORA-00443: background process "CJQ0" did not start
Errors in file /u01/11.2.0.3/diag/rdbms/ora11203/ora11203/trace/ora11203_pmon_2532.trc:
ORA-00450: background process 'CJQ0' did not start
ORA-00443: background process "CJQ0" did not start
Starting background process CJQ0
Errors in file /u01/11.2.0.3/diag/rdbms/ora11203/ora11203/trace/ora11203_pmon_2532.trc:
ORA-00443: background process "CJQ0" did not start
Errors in file /u01/11.2.0.3/diag/rdbms/ora11203/ora11203/trace/ora11203_pmon_2532.trc:
ORA-00450: background process 'CJQ0' did not start
ORA-00443: background process "CJQ0" did not start
Fri Oct 18 00:38:14 2013
db_recovery_file_dest_size of 4122 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Starting background process CJQ0
Errors in file /u01/11.2.0.3/diag/rdbms/ora11203/ora11203/trace/ora11203_pmon_2532.trc:
ORA-00443: background process "CJQ0" did not start
Errors in file /u01/11.2.0.3/diag/rdbms/ora11203/ora11203/trace/ora11203_pmon_2532.trc:
ORA-00450: background process 'CJQ0' did not start
ORA-00443: background process "CJQ0" did not start
Stopping background process MMNL
Stopping background process MMON
Fri Oct 18 00:38:41 2013
License high water mark = 1
All dispatchers and shared servers shutdown
ALTER DATABASE CLOSE NORMAL
Fri Oct 18 00:38:41 2013
SMON: disabling tx recovery
SMON: disabling cache recovery
Fri Oct 18 00:38:41 2013
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 16
Successful close of redo thread 1
Completed: ALTER DATABASE CLOSE NORMAL
ALTER DATABASE DISMOUNT
Shutting down archive processes
Archiving is disabled
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Fri Oct 18 00:38:42 2013
Stopping background process VKTM
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Fri Oct 18 00:38:44 2013
Instance shutdown complete
[oracle@bvh trace]$ cat /u01/11.2.0.3/diag/rdbms/ora11203/ora11203/trace/ora11203_pmon_2532.trc
Trace file /u01/11.2.0.3/diag/rdbms/ora11203/ora11203/trace/ora11203_pmon_2532.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/11.2.0.3/product/11.2.0/db_1
System name: Linux
Node name: bvh.dbinsight.com
Release: 2.6.39-400.17.1.el6uek.x86_64
Version: #1 SMP Fri Feb 22 18:16:18 PST 2013
Machine: x86_64
Instance name: ora11203
Redo thread mounted by this instance: 1
Oracle process number: 2
Unix process pid: 2532, image: oracle@bvh.dbinsight.com (PMON)
*** 2013-10-18 00:38:13.743
*** SESSION ID:(2.1) 2013-10-18 00:38:13.743
*** CLIENT ID:() 2013-10-18 00:38:13.743
*** SERVICE NAME:(SYS$BACKGROUND) 2013-10-18 00:38:13.743
*** MODULE NAME:() 2013-10-18 00:38:13.743
*** ACTION NAME:() 2013-10-18 00:38:13.743
-------------------------------------------------------------------------------
Trace Bucket Dump Begin: default bucket for process 2 (osid: 2532, PMON)
TIME(*=approx):SEQ:COMPONENT:FILE@LINE:FUNCTION:SECT/DUMP: [EVENT#:PID:SID] DATA
-------------------------------------------------------------------------------
*** 2013-10-18 00:38:13.931
2013-10-18 00:38:13.525506 :80000CED:db_trace:ksb.c@2342:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON trying to start background CJQ0
2013-10-18 00:38:13.525509 :80000CEE:db_trace:ksb.c@2405:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON obtained PR enqueue to start background CJQ0
2013-10-18 00:38:13.650594 :80000CFA:db_trace:ksb.c@2539:ksbs1p_real(): [10254:2:2] KSBS1P: creation error posted OER(1089)
2013-10-18 00:38:13.650617 :80000CFC:db_trace:ksb.c@2609:ksbs1p_real(): [10254:2:2] KSBS1P: out of loop: process did not start
-------------------------------------------------------------------------------
Trace Bucket Dump End: default bucket for process 2 (osid: 2532, PMON)
ORA-00443: background process "CJQ0" did not start
ORA-00450: background process 'CJQ0' did not start
ORA-00443: background process "CJQ0" did not start
-------------------------------------------------------------------------------
Trace Bucket Dump Begin: default bucket for process 2 (osid: 2532, PMON)
TIME(*=approx):SEQ:COMPONENT:FILE@LINE:FUNCTION:SECT/DUMP: [EVENT#:PID:SID] DATA
-------------------------------------------------------------------------------
2013-10-18 00:38:13.525506 :80000CED:db_trace:ksb.c@2342:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON trying to start background CJQ0
2013-10-18 00:38:13.525509 :80000CEE:db_trace:ksb.c@2405:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON obtained PR enqueue to start background CJQ0
2013-10-18 00:38:13.650594 :80000CFA:db_trace:ksb.c@2539:ksbs1p_real(): [10254:2:2] KSBS1P: creation error posted OER(1089)
2013-10-18 00:38:13.650617 :80000CFC:db_trace:ksb.c@2609:ksbs1p_real(): [10254:2:2] KSBS1P: out of loop: process did not start
2013-10-18 00:38:14.086277 :80000D33:db_trace:ksb.c@2342:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON trying to start background CJQ0
2013-10-18 00:38:14.086278 :80000D34:db_trace:ksb.c@2405:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON obtained PR enqueue to start background CJQ0
2013-10-18 00:38:14.187537 :80000D4D:db_trace:ksb.c@2539:ksbs1p_real(): [10254:2:2] KSBS1P: creation error posted OER(1089)
2013-10-18 00:38:14.187554 :80000D4F:db_trace:ksb.c@2609:ksbs1p_real(): [10254:2:2] KSBS1P: out of loop: process did not start
-------------------------------------------------------------------------------
Trace Bucket Dump End: default bucket for process 2 (osid: 2532, PMON)
ORA-00443: background process "CJQ0" did not start
ORA-00450: background process 'CJQ0' did not start
ORA-00443: background process "CJQ0" did not start
-------------------------------------------------------------------------------
Trace Bucket Dump Begin: default bucket for process 2 (osid: 2532, PMON)
TIME(*=approx):SEQ:COMPONENT:FILE@LINE:FUNCTION:SECT/DUMP: [EVENT#:PID:SID] DATA
-------------------------------------------------------------------------------
2013-10-18 00:38:13.525506 :80000CED:db_trace:ksb.c@2342:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON trying to start background CJQ0
2013-10-18 00:38:13.525509 :80000CEE:db_trace:ksb.c@2405:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON obtained PR enqueue to start background CJQ0
2013-10-18 00:38:13.650594 :80000CFA:db_trace:ksb.c@2539:ksbs1p_real(): [10254:2:2] KSBS1P: creation error posted OER(1089)
2013-10-18 00:38:13.650617 :80000CFC:db_trace:ksb.c@2609:ksbs1p_real(): [10254:2:2] KSBS1P: out of loop: process did not start
2013-10-18 00:38:14.086277 :80000D33:db_trace:ksb.c@2342:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON trying to start background CJQ0
2013-10-18 00:38:14.086278 :80000D34:db_trace:ksb.c@2405:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON obtained PR enqueue to start background CJQ0
2013-10-18 00:38:14.187537 :80000D4D:db_trace:ksb.c@2539:ksbs1p_real(): [10254:2:2] KSBS1P: creation error posted OER(1089)
2013-10-18 00:38:14.187554 :80000D4F:db_trace:ksb.c@2609:ksbs1p_real(): [10254:2:2] KSBS1P: out of loop: process did not start
2013-10-18 00:38:14.676610 :80000D58:db_trace:ksb.c@2342:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON trying to start background CJQ0
2013-10-18 00:38:14.676612 :80000D59:db_trace:ksb.c@2405:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON obtained PR enqueue to start background CJQ0
2013-10-18 00:38:14.676800 :80000D5C:db_trace:ksb.c@2539:ksbs1p_real(): [10254:2:2] KSBS1P: creation error posted OER(1089)
2013-10-18 00:38:14.676807 :80000D5E:db_trace:ksb.c@2609:ksbs1p_real(): [10254:2:2] KSBS1P: out of loop: process did not start
-------------------------------------------------------------------------------
Trace Bucket Dump End: default bucket for process 2 (osid: 2532, PMON)
ORA-00443: background process "CJQ0" did not start
ORA-00450: background process 'CJQ0' did not start
ORA-00443: background process "CJQ0" did not start
[oracle@bvh trace]$ oerr ora 1089
01089, 00000, "immediate shutdown in progress - no operations are permitted"
// *Cause: The SHUTDOWN IMMEDIATE command was used to shut down
// a running ORACLE instance, so your operations have been
// terminated.
// *Action: Wait for the instance to be restarted, or contact your DBA.
[oracle@bvh trace]$ oerr ora 00443
00443, 00000, "background process \"%s\" did not start"
// *Cause: The specified process did not start.
// *Action: Ensure that the executable image is in the correct place with
// the correct protections, and that there is enough memory.
[oracle@bvh trace]$ oerr ora 00450
00450, 00000, "background process '%s' did not start"
// *Cause: The specified process did not start.
// *Action: Consult the error code, and the trace file for the process.
[oracle@bvh trace]$
原因：
This problem is as described in
unpublished Bug 6865966 PMON TRYING TO START CJQ0 DURING DATABASE SHUTDOWN-ORA-443 & ORA-450
where development explained that the errors are misleading but are unharmful.
解決方案：
This is caused by scheduler autostart feature trying to start up the coordinator at the same time as database is shutting down. So you can safely ignore the errors.
The unpublished Bug 6865966 is still under investigation and you can apply the patch, once the fix is made available.
The Autostart feature will not be available in 12c and hence this issue wont be present in 12c version.
References
@ BUG:6865966 - PMON TRYING TO START CJQ0 DURING DATABASE SHUTDOWN-ORA-443 & ORA-450
參考連結：
http://appsdbastuff.blogspot.com/2012/09/ora-00450-ora-00443-background-process.html
Oracle 11g 11.2.0.3 on Linux 64bit
shutdown的時候出現ORA-00450/ORA-00443的錯誤。
alert及trace內容如下：
[oracle@bvh trace]$ vi alert_ora11203.log
Fri Oct 18 00:38:12 2013
Shutting down instance (immediate)
Shutting down instance: further logons disabled
Fri Oct 18 00:38:13 2013
Starting background process CJQ0
Errors in file /u01/11.2.0.3/diag/rdbms/ora11203/ora11203/trace/ora11203_pmon_2532.trc:
ORA-00443: background process "CJQ0" did not start
Errors in file /u01/11.2.0.3/diag/rdbms/ora11203/ora11203/trace/ora11203_pmon_2532.trc:
ORA-00450: background process 'CJQ0' did not start
ORA-00443: background process "CJQ0" did not start
Starting background process CJQ0
Errors in file /u01/11.2.0.3/diag/rdbms/ora11203/ora11203/trace/ora11203_pmon_2532.trc:
ORA-00443: background process "CJQ0" did not start
Errors in file /u01/11.2.0.3/diag/rdbms/ora11203/ora11203/trace/ora11203_pmon_2532.trc:
ORA-00450: background process 'CJQ0' did not start
ORA-00443: background process "CJQ0" did not start
Fri Oct 18 00:38:14 2013
db_recovery_file_dest_size of 4122 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Starting background process CJQ0
Errors in file /u01/11.2.0.3/diag/rdbms/ora11203/ora11203/trace/ora11203_pmon_2532.trc:
ORA-00443: background process "CJQ0" did not start
Errors in file /u01/11.2.0.3/diag/rdbms/ora11203/ora11203/trace/ora11203_pmon_2532.trc:
ORA-00450: background process 'CJQ0' did not start
ORA-00443: background process "CJQ0" did not start
Stopping background process MMNL
Stopping background process MMON
Fri Oct 18 00:38:41 2013
License high water mark = 1
All dispatchers and shared servers shutdown
ALTER DATABASE CLOSE NORMAL
Fri Oct 18 00:38:41 2013
SMON: disabling tx recovery
SMON: disabling cache recovery
Fri Oct 18 00:38:41 2013
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 16
Successful close of redo thread 1
Completed: ALTER DATABASE CLOSE NORMAL
ALTER DATABASE DISMOUNT
Shutting down archive processes
Archiving is disabled
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Fri Oct 18 00:38:42 2013
Stopping background process VKTM
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Fri Oct 18 00:38:44 2013
Instance shutdown complete
[oracle@bvh trace]$ cat /u01/11.2.0.3/diag/rdbms/ora11203/ora11203/trace/ora11203_pmon_2532.trc
Trace file /u01/11.2.0.3/diag/rdbms/ora11203/ora11203/trace/ora11203_pmon_2532.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/11.2.0.3/product/11.2.0/db_1
System name: Linux
Node name: bvh.dbinsight.com
Release: 2.6.39-400.17.1.el6uek.x86_64
Version: #1 SMP Fri Feb 22 18:16:18 PST 2013
Machine: x86_64
Instance name: ora11203
Redo thread mounted by this instance: 1
Oracle process number: 2
Unix process pid: 2532, image: oracle@bvh.dbinsight.com (PMON)
*** 2013-10-18 00:38:13.743
*** SESSION ID:(2.1) 2013-10-18 00:38:13.743
*** CLIENT ID:() 2013-10-18 00:38:13.743
*** SERVICE NAME:(SYS$BACKGROUND) 2013-10-18 00:38:13.743
*** MODULE NAME:() 2013-10-18 00:38:13.743
*** ACTION NAME:() 2013-10-18 00:38:13.743
-------------------------------------------------------------------------------
Trace Bucket Dump Begin: default bucket for process 2 (osid: 2532, PMON)
TIME(*=approx):SEQ:COMPONENT:FILE@LINE:FUNCTION:SECT/DUMP: [EVENT#:PID:SID] DATA
-------------------------------------------------------------------------------
*** 2013-10-18 00:38:13.931
2013-10-18 00:38:13.525506 :80000CED:db_trace:ksb.c@2342:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON trying to start background CJQ0
2013-10-18 00:38:13.525509 :80000CEE:db_trace:ksb.c@2405:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON obtained PR enqueue to start background CJQ0
2013-10-18 00:38:13.650594 :80000CFA:db_trace:ksb.c@2539:ksbs1p_real(): [10254:2:2] KSBS1P: creation error posted OER(1089)
2013-10-18 00:38:13.650617 :80000CFC:db_trace:ksb.c@2609:ksbs1p_real(): [10254:2:2] KSBS1P: out of loop: process did not start
-------------------------------------------------------------------------------
Trace Bucket Dump End: default bucket for process 2 (osid: 2532, PMON)
ORA-00443: background process "CJQ0" did not start
ORA-00450: background process 'CJQ0' did not start
ORA-00443: background process "CJQ0" did not start
-------------------------------------------------------------------------------
Trace Bucket Dump Begin: default bucket for process 2 (osid: 2532, PMON)
TIME(*=approx):SEQ:COMPONENT:FILE@LINE:FUNCTION:SECT/DUMP: [EVENT#:PID:SID] DATA
-------------------------------------------------------------------------------
2013-10-18 00:38:13.525506 :80000CED:db_trace:ksb.c@2342:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON trying to start background CJQ0
2013-10-18 00:38:13.525509 :80000CEE:db_trace:ksb.c@2405:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON obtained PR enqueue to start background CJQ0
2013-10-18 00:38:13.650594 :80000CFA:db_trace:ksb.c@2539:ksbs1p_real(): [10254:2:2] KSBS1P: creation error posted OER(1089)
2013-10-18 00:38:13.650617 :80000CFC:db_trace:ksb.c@2609:ksbs1p_real(): [10254:2:2] KSBS1P: out of loop: process did not start
2013-10-18 00:38:14.086277 :80000D33:db_trace:ksb.c@2342:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON trying to start background CJQ0
2013-10-18 00:38:14.086278 :80000D34:db_trace:ksb.c@2405:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON obtained PR enqueue to start background CJQ0
2013-10-18 00:38:14.187537 :80000D4D:db_trace:ksb.c@2539:ksbs1p_real(): [10254:2:2] KSBS1P: creation error posted OER(1089)
2013-10-18 00:38:14.187554 :80000D4F:db_trace:ksb.c@2609:ksbs1p_real(): [10254:2:2] KSBS1P: out of loop: process did not start
-------------------------------------------------------------------------------
Trace Bucket Dump End: default bucket for process 2 (osid: 2532, PMON)
ORA-00443: background process "CJQ0" did not start
ORA-00450: background process 'CJQ0' did not start
ORA-00443: background process "CJQ0" did not start
-------------------------------------------------------------------------------
Trace Bucket Dump Begin: default bucket for process 2 (osid: 2532, PMON)
TIME(*=approx):SEQ:COMPONENT:FILE@LINE:FUNCTION:SECT/DUMP: [EVENT#:PID:SID] DATA
-------------------------------------------------------------------------------
2013-10-18 00:38:13.525506 :80000CED:db_trace:ksb.c@2342:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON trying to start background CJQ0
2013-10-18 00:38:13.525509 :80000CEE:db_trace:ksb.c@2405:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON obtained PR enqueue to start background CJQ0
2013-10-18 00:38:13.650594 :80000CFA:db_trace:ksb.c@2539:ksbs1p_real(): [10254:2:2] KSBS1P: creation error posted OER(1089)
2013-10-18 00:38:13.650617 :80000CFC:db_trace:ksb.c@2609:ksbs1p_real(): [10254:2:2] KSBS1P: out of loop: process did not start
2013-10-18 00:38:14.086277 :80000D33:db_trace:ksb.c@2342:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON trying to start background CJQ0
2013-10-18 00:38:14.086278 :80000D34:db_trace:ksb.c@2405:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON obtained PR enqueue to start background CJQ0
2013-10-18 00:38:14.187537 :80000D4D:db_trace:ksb.c@2539:ksbs1p_real(): [10254:2:2] KSBS1P: creation error posted OER(1089)
2013-10-18 00:38:14.187554 :80000D4F:db_trace:ksb.c@2609:ksbs1p_real(): [10254:2:2] KSBS1P: out of loop: process did not start
2013-10-18 00:38:14.676610 :80000D58:db_trace:ksb.c@2342:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON trying to start background CJQ0
2013-10-18 00:38:14.676612 :80000D59:db_trace:ksb.c@2405:ksbs1p_real(): [10254:2:2] KSBS1P: process PMON obtained PR enqueue to start background CJQ0
2013-10-18 00:38:14.676800 :80000D5C:db_trace:ksb.c@2539:ksbs1p_real(): [10254:2:2] KSBS1P: creation error posted OER(1089)
2013-10-18 00:38:14.676807 :80000D5E:db_trace:ksb.c@2609:ksbs1p_real(): [10254:2:2] KSBS1P: out of loop: process did not start
-------------------------------------------------------------------------------
Trace Bucket Dump End: default bucket for process 2 (osid: 2532, PMON)
ORA-00443: background process "CJQ0" did not start
ORA-00450: background process 'CJQ0' did not start
ORA-00443: background process "CJQ0" did not start
[oracle@bvh trace]$ oerr ora 1089
01089, 00000, "immediate shutdown in progress - no operations are permitted"
// *Cause: The SHUTDOWN IMMEDIATE command was used to shut down
// a running ORACLE instance, so your operations have been
// terminated.
// *Action: Wait for the instance to be restarted, or contact your DBA.
[oracle@bvh trace]$ oerr ora 00443
00443, 00000, "background process \"%s\" did not start"
// *Cause: The specified process did not start.
// *Action: Ensure that the executable image is in the correct place with
// the correct protections, and that there is enough memory.
[oracle@bvh trace]$ oerr ora 00450
00450, 00000, "background process '%s' did not start"
// *Cause: The specified process did not start.
// *Action: Consult the error code, and the trace file for the process.
[oracle@bvh trace]$
原因：
This problem is as described in
unpublished Bug 6865966 PMON TRYING TO START CJQ0 DURING DATABASE SHUTDOWN-ORA-443 & ORA-450
where development explained that the errors are misleading but are unharmful.
解決方案：
This is caused by scheduler autostart feature trying to start up the coordinator at the same time as database is shutting down. So you can safely ignore the errors.
The unpublished Bug 6865966 is still under investigation and you can apply the patch, once the fix is made available.
The Autostart feature will not be available in 12c and hence this issue wont be present in 12c version.
References
@ BUG:6865966 - PMON TRYING TO START CJQ0 DURING DATABASE SHUTDOWN-ORA-443 & ORA-450
參考連結：
http://appsdbastuff.blogspot.com/2012/09/ora-00450-ora-00443-background-process.html
來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/29154652/viewspace-774598/，如需轉載，請註明出處，否則將追究法律責任。
相關文章
- Bug 4632780 - PMON "failed to acquire latch" during shutdownAIUI
- PMON "failed to acquire latch" during shutdown-4632780.8AIUI
- Oracle Database Cloud - Database as a Service Quick StartOracleDatabaseCloudUI
- 【tomcat報錯】A child container failed during startTomcatAI
- Fails to Start: PMON (ospid: nnnn): terminating the instance due to error 481AIError
- GET ORA-32700 WHEN TRYING TO CREATE DATABASE USING 9.2Database
- Supporting Bigfile Tablespaces During Database Creation (77)Database
- PMON failed to acquire latch, see PMON dumpAIUI
- ORA-279 signalled during: alter database recover logfileDatabase
- 【DataGuarad】ORA-1153 trying to turn on Flashback for Physical Standby DatabaseDatabase
- ORA-1113 signalled during: alter database open...Database
- PMON failed to acquire latch, see PMON dump in alert logAIUI
- Ora-12720 During Rman Duplication Of Database (文件 ID 341089.1)Database
- 'PMON failed to acquire latch, see PMON dump' in Alert Log-976714.1AIUI
- Killed Session Are Not Cleaned By PMONSession
- ORA-07445 [eomg_migrate_if_oldnew()+61] during upgrade 11.2.0.4 databaseDatabase
- RAC 例項不能啟動 ORA-1589 signalled during ALTER DATABASE OPENDatabase
- Process Monitor Process (PMON) (121)
- 資料庫關閉Hang住，出現錯誤PMON failed to acquire latch, see PMON dump資料庫AIUI
- Oracle Database Fails to Start with Error ORA-12547 [ID 1307075.1]OracleDatabaseAIError
- why app_start startAPP
- oracle 10g 中cjq0後臺程式的作用Oracle 10g
- [重慶思莊每日技術分享]-ORA-1142 signalled during: ALTER DATABASE END BACKUPDatabase
- Trying to hack Redis via HTTP requestsRedisHTTP
- oracle smon與pmon ckpt功能的作用(ZT)Oracle
- A New Start
- the new start
- oracle 11g pmon工作內容系列一Oracle
- oracle 11g pmon工作內容系列二Oracle
- oracle 11g pmon工作內容系列三Oracle
- fast_start_parallel_rollback與v$fast_start_servers和v$fast_start_transactionsASTParallelServer
- Extract or Replicat Fail to Start (Don't Start) With No Error MessagesAIError
- crsctl start/stop crs and crsctl start/stop cluster 區別
- 【HBase】start master 與 start master --backup 的區別AST
- An error occurred during bosboot verification processingErrorboot
- MyEclipse提示Errors occurred during the buildEclipseErrorUI
- Errors During Multilevel Price DeterminationError
- 【RAC】PMON: terminating the instance due to error 481Error