Error while starting db with srvctl:
$srvctl start database -d poc01
PRCR-1079 : Failed to start resource ora.poc01.db
CRS-5017: The resource action "ora.poc01.db start" encountered the following error:
ORA-00445: background process "PMON" did not start after 120 seconds
. For details refer to "(:CLSN00107:)" in "/app/grid/diag/crs/node02/crs/trace/crsd_oraagent_oracle.trc".
CRS-2674: Start of 'ora.poc01.db' on 'node02' failed
CRS-2632: There are no more servers to try to place resource 'ora.poc01.db' on that would satisfy its placement policy
CRS-5017: The resource action "ora.poc01.db start" encountered the following error:
ORA-00445: background process "PMON" did not start after 120 seconds
. For details refer to "(:CLSN00107:)" in
"/app/grid/diag/crs/node01/crs/trace/crsd_oraagent_oracle.trc".
CRS-2674: Start of 'ora.poc01.db' on 'node01' failed
Cause:
System not able to allocate required memory for oracle instance within time limit
Troubleshoot:
1. Check parameter file if instance fails at PMON startup
If db starting with high sga_target value and pre_page_sga=TRUE parameters,
pre_page_sga will read entire SGA to Memory during instance start up and it also increases the startup duration, because every process that starts must access every page in the SGA — it may be reason for failure
set pre_page_sga=FALSE and start instance
2. If it fails on other then PMON process start time
Check ASLR related setting in sysctl.conf file
# /sbin/sysctl -a | grep randomize
kernel.randomize_va_space = 1
If the parameter is set to any value other than 0 then ASLR is in use.
To permanently disable ASLR, add/modify this parameter in /etc/sysctl.conf:
kernel.randomize_va_space=0
kernel.exec-shield=0
reboot the node to take effect
No comments:
Post a Comment