ORA-27302: failure occurred at: skgpspawn3

ORA-27302: failure occurred at: skgpspawn3 Applies to: OracleServer-Enterprise Edition-Version: 10.2.0.1 to 10.2.0.3This problem can occur on any platform. symptomsThe database can not start up due to the following errors: Errors in file ....... Trc :...... ORA-27300: OS system dependent operation: fork failed with status: 12ORA-27301: OS failure message: Not enough spaceORA-27302: failure occurred at: skgpspawn3 ...... CauseThis issue is mainly caused by lack of memory/swap. checking the memory configuration on the server, we have found the following: Total Physical Memory 38912 MBSwap: Max Size 17664 MiBSo, RAM is 38 GB, SWAP space is only 17 GB Solution-We shocould increase the server swap space (paging space ). the general rule of thumb is that swap space shoshould be: RAM SWAP1GB to 2 GB 1.5 times RAM> 2 GB and <= 8 GB 1 times RAM> 8 GB. 75 times RAM So in our case, the recommended swap space is @ 28 GB. we can also try to increase physical memory, if possible. we shoshould also check the ulimits for Oracle user.: memory-unlimiteddata-unlimitedcpu-unlimitedstack-at least 32768 nofile-OS dependent We shoshould also check memory parameters in the pfile/spfile that add more load to the memory consumption on the server. in our issue, we found these settings which added more pressure to the memory:-lock_sga = true-large db_keep_cache_size = 14000 m. f. Check the Physical Memory Total Physical Memory 8 GBSwap: 8 GB on the server 10.10.10.100. Check the swap space lsps-asize 8 GB used % 69% h and use the smitty chps command to add 4 GB swap space, now, the client can connect to the database normally.