we will be seeing below error when the Oraagent is re-spawning.
ORA-27300: OS system dependent operation:fork failed with status: 12
ORA-27301:OS failure message: Not enough space
ORA-27302: failure occurred at: skgpspawn3
Recently we were getting this error in the alert log. when did a little research i found oracle recommending couple of work arounds to fix this problem..
1) to monitor the Oraagent usage continously and kill it when it is using more swap space as it re-spawn the process again..
2)crsctl modify resource ora.asm -attr START_DEPENDENCIES="hard(ora.cssd) weak(ora.LISTENER_DEV.lsnr)"
Before trying given oracle work arounds i did something different which fixed my issue too...
1) At first i made sure the listener is not dynamic registered. need to be OFF it if it is ON. even if it is ON leave it now and do below steps and validate after last step again.
2) stop the listener that got created and quickly unregister the listener from crs.
crs_unregister ora.listener.lsnr
3) Re- add the listener using srvctl command with appropriate listener name and Port.
srvctl add listener -l LISTENER -p "TCP:1521"
4) shutdown db and asm and remove asm from crs.
srvctl remove asm –f
5) add asm again with appropriate values..
srvctl add asm -l LISTENER -p $ORACLE_HOMEdbs/spfile+ASM.ora
6) bring everything up one by one and monitor oraagent swap usage.
This fixed my above oracle error from coming....
Hope this helps.....
Regards,
ORA-27300: OS system dependent operation:fork failed with status: 12
ORA-27301:OS failure message: Not enough space
ORA-27302: failure occurred at: skgpspawn3
Recently we were getting this error in the alert log. when did a little research i found oracle recommending couple of work arounds to fix this problem..
1) to monitor the Oraagent usage continously and kill it when it is using more swap space as it re-spawn the process again..
2)crsctl modify resource ora.asm -attr START_DEPENDENCIES="hard(ora.cssd) weak(ora.LISTENER_DEV.lsnr)"
Before trying given oracle work arounds i did something different which fixed my issue too...
1) At first i made sure the listener is not dynamic registered. need to be OFF it if it is ON. even if it is ON leave it now and do below steps and validate after last step again.
2) stop the listener that got created and quickly unregister the listener from crs.
crs_unregister ora.listener.lsnr
3) Re- add the listener using srvctl command with appropriate listener name and Port.
srvctl add listener -l LISTENER -p "TCP:1521"
4) shutdown db and asm and remove asm from crs.
srvctl remove asm –f
5) add asm again with appropriate values..
srvctl add asm -l LISTENER -p $ORACLE_HOMEdbs/spfile+ASM.ora
6) bring everything up one by one and monitor oraagent swap usage.
This fixed my above oracle error from coming....
Hope this helps.....
Regards,
No comments:
Post a Comment