ora_sa00_ process Consuming Huge Memory and System is Getting Hung During Instance Startup
(Doc ID 2496876.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterInformation in this document applies to any platform.
Symptoms
In Real Application Cluster environment, certain processes are going to D state and running out of memory during Instance startup.
Instance startup entries appear to be like below indicating processes not able to start, unable to spawn jobq slave process etc.
For example: alert_racdb1.log from <oracle base>/diag/rdbms/racdb/racdb1/trace location:
Fri Jan 18 14:58:44 2019
Decreasing number of real time LMS from 5 to 0
Process m000 died, see its trace file
Errors in file /u01/app/oracle/diag/rdbms/racdb/racdb1/trace/racdb1_cjq0_8703.trc (incident=58598):
ORA-00445: background process "J000" did not start after 30 seconds
Incident details in: /u01/app/oracle/diag/rdbms/racdb/racdb1/incident/incdir_58598/racdb1_cjq0_8703_i58598.trc
Process m000 died, see its trace file
Errors in file /u01/app/oracle/diag/rdbms/racdb/racdb1/trace/racdb1_mmon_7591.trc (incident=58030):
ORA-00445: background process "m001" did not start after 120 seconds
Fri Jan 18 15:13:05 2019
Dumping diagnostic data in directory=[cdmp_20190118151304], requested by (instance=1, osid=8703 (CJQ0)), summary=[incident=58598].
Incident details in: /u01/app/oracle/diag/rdbms/racdb/racdb1/incident/incdir_58030/racdb1_mmon_7591_i58030.trc
Fri Jan 18 15:15:19 2019
kkjcre1p: unable to spawn jobq slave process
.
.
From the top command during Instance startup time, ora_sa00_ process observe consuming huge memory and going to D state with Out of memory error. Subsequently causing system to be hung and other processes appear to be blocked.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| Community Discussions |
| References |