Pmon process died

Question

Hi,
One of our database was crashed unexpectedly and it was due to shortage of space in swap as per OS logs but there is sufficient swap space available still it occurred. Please find the details of aler log below, whats the workaround for this to avoid.
Database crashes with the below given errors
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
ORA-00490: PSP process terminated with error
PMON: terminating instance due to error 490
Instance terminated by PMON, pid = 20094
error in Alert log file
ORA-04030: out of process memory when trying to allocate 8389144 bytes (pga heap,redo read buffer)
Doing block recovery for file 11 block 388042
Wed May 26 18:37:06 2010
Errors in file /oradata/dump/bdump/sid_pmon_1383.trc:
ORA-04030: out of process memory when trying to allocate 8389144 bytes (pga heap,redo read buffer)
Doing block recovery for file 1 block 999
Wed May 26 18:37:09 2010
Errors in file /oradata/dump/bdump/sid_pmon_1383.trc:
ORA-04030: out of process memory when trying to allocate 8389144 bytes (pga heap,redo read buffer)
Wed May 26 18:37:10 2010
Errors in file /oradata/dump/bdump/sid_pmon_1383.trc:
ORA-00490: PSP process terminated with error
Wed May 26 18:37:10 2010
PMON: terminating instance due to error 490
Wed May 26 18:37:11 2010
Error occured while spawning process J000; error = 490
Wed May 26 18:37:11 2010
Errors in file /oradata/dump/bdump/sid_pmon_1398:
ORA-00490: PSP process terminated with error
Wed May 26 18:37:16 2010
Termination issued to instance processes. Waiting for the processes to exit
Instance terminated by PMON, pid = 1383
Wed May 26 18:55:33 2010
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
Oracle 10.2.0.1.0 version on solaris box with 16 gb ram 44 Gb swap space.
OS logs
May 26 18:20:54 PMDSUNV49002 sendmail[4511]: [ID 801593 mail.crit] o4QCos06004508: SYSERR(ora10g): putbody: write error: File too large
May 26 18:20:54 PMDSUNV49002 sendmail[4512]: [ID 801593 mail.crit] o4QCose4004507: SYSERR(ora10g): putbody: write error: File too large
May 26 18:23:18 PMDSUNV49002 genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow stack for pid 3906 (oracle)
May 26 18:24:21 PMDSUNV49002 genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow stack for pid 4221 (oracle)
regards
Jaffy

Answer 1

Hi, Jaffy,error occur because this time there is not significant server resouce (swap space).How did you configure swap space for your server?.Configuring swap space is related RAM of server.First check this following links.
http://download.oracle.com/docs/cd/B19306_01/install.102/b15704/pre_install.htm#sthref100
There you will see how to related RAM and swap space.Also you can monitor usage of swap using "free" and "swap -s" OS commands.If this error occur then immediately run this commands then you will see usage of swap space.Finally check following metalink docs.
Database Crash With Error ORA-00490 [ID 465002.1]
Ora-04030 Ora-07445 Ora-27300 Ora-27301 Ora-27302 Crashed Database. [ID 580552.1]
Troubleshooting ORA-27300 ORA-27301 ORA-27302 errors [ID 579365.1]