ORA-00445: Background Process “xxxx” Did Not Start After 120 Seconds (文档 ID 1345364.1)
In this Document
Symptoms
Changes
Cause
Solution
APPLIES TO:
Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.1 [Release 11.2 to 12.1] SaaS Operations - Version N/A to N/A IBM: Linux on System z Linux x86-64 Linux x86
SYMPTOMS
Errors are seen in the alert log relating to spawning of processes such as:
@ Checked for relevance on 17th Jan 2012 ORA-00445: background process “m001” did not start after 120 seconds Incident details in: /opt/u01/app/oracle/diag/rdbms/incident/incdir_3721/db1_mmon_7417_i3721.trc ERROR: Unable to normalize symbol name for the following short stack (at offset 2): Tue Jun 21 03:03:06 2011 ORA-00445: background process “J003” did not start after 120 seconds
or
Waited for process W002 to initialize for 60 seconds
The system appears to be running very slowly and defunct processes can appear.
CHANGES
REDHAT 5 kernel 2.6.18-194.el5 #1 SMP Tue Mar 16 Oracle 11.2.0.2 Single Instance IBM: Linux on System z
CAUSE
Recent linux kernels have a feature called Address Space Layout Randomization (ASLR). ASLR is a feature that is activated by default on some of the newer linux distributions. It is designed to load shared memory objects in random addresses. In Oracle, multiple processes map a shared memory object at the same address across the processes.
With ASLR turned on Oracle cannot guarantee the availability of this shared memory address. This conflict in the address space means that a process trying to attach a shared memory object to a specific address may not be able to do so, resulting in a failure in shmat subroutine.
页码 ， 1/1文 档显示
2015/9/2https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl -state=1a86egh1dt_9
文档显示
or
ORA-00445: Background Process “xxxx” Did Not Start After 120 Seconds (文档 ID 1345364.1)
In this Document
Symptoms Changes Cause Solution
APPLIES TO:
Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.1 [Release 11.2 to 12.1] SaaS Operations - Version N/A to N/A IBM: Linux on System z Linux x86-64 Linux x86
SYMPTOMS
Errors are seen in the alert log relating to spawning of processes such as:
@ Checked for relevance on 17th Jan 2012 ORA-00445: background process “m001” did not start after 120 seconds Incident details in: /opt/u01/app/oracle/diag/rdbms/incident/incdir_3721/db1_mmon_7417_i3721.trc ERROR: Unable to normalize symbol name for the following short stack (at offset 2): Tue Jun 21 03:03:06 2011 ORA-00445: background process “J003” did not start after 120 seconds
Waited for process W002 to initialize for 60 seconds
The system appears to be running very slowly and defunct processes can appear.
CHANGES
REDHAT 5 kernel 2.6.18-194.el5 #1 SMP Tue Mar 16 Oracle 11.2.0.2 Single Instance IBM: Linux on System z
CAUSE
Recent linux kernels have a feature called Address Space Layout Randomization (ASLR). ASLR is a feature that is activated by default on some of the newer linux distributions. It is designed to load shared memory objects in random addresses. In Oracle, multiple processes map a shared memory object at the same address across the processes.
With ASLR turned on Oracle cannot guarantee the availability of this shared memory address. This conflict in the address space means that a process trying to attach a shared memory object to a specific address may not be able to do so, resulting in a failure in shmat subroutine.
