ksvcreate: Process(m000) creation failed
http://yangtingkun.itpub.net/post/468/512612
一個節點報如下錯誤﹕

Sat Jan 15 01:13:56 EAT 2011
Process startup failed, error stack:
Sat Jan 15 01:13:56 EAT 2011
Errors in file /opt/oracle/db/admin/orcl/bdump/orcl2_psp0_7231.trc:
ORA-27300: OS system dependent operation:fork failed with status: 11
ORA-27301: OS failure message: Resource temporarily unavailable
ORA-27302: failure occurred at: skgpspawn5
ORA-27303: additional information: skgpspawn5
Sat Jan 15 01:13:57 EAT 2011
Process m000 died, see its trace file
Sat Jan 15 01:13:57 EAT 2011
ksvcreate: Process(m000) creation failed
Sat Jan 15 01:34:00 EAT 2011
Process startup failed, error stack:
Sat Jan 15 01:34:00 EAT 2011
Errors in file /opt/oracle/db/admin/orcl/bdump/orcl2_psp0_7231.trc:
ORA-27300: OS system dependent operation:fork failed with status: 11
ORA-27301: OS failure message: Resource temporarily unavailable
ORA-27302: failure occurred at: skgpspawn5
ORA-27303: additional information: skgpspawn5
Sat Jan 15 01:34:01 EAT 2011
Process PZ99 died, see its trace file
Sat Jan 15 01:34:01 EAT 2011
Process startup failed, error stack:
Sat Jan 15 01:34:01 EAT 2011
Errors in file /opt/oracle/db/admin/orcl/bdump/orcl2_psp0_7231.trc:
ORA-27300: OS system dependent operation:fork failed with status: 11
ORA-27301: OS failure message: Resource temporarily unavailable
ORA-27302: failure occurred at: skgpspawn5
ORA-27303: additional information: skgpspawn5

另一個節點有類似錯誤﹕

Sat Jan 15 12:56:51 EAT 2011
Process startup failed, error stack:
Sat Jan 15 12:56:51 EAT 2011
Errors in file /opt/oracle/db/admin/orcl/bdump/orcl1_psp0_19417.trc:
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

從錯誤信息上看﹐似乎是操作系統上內存不足導致的問題
不過Oracle 的 SGA+PGA 也不過占用了一多半的內存﹐不應該導致這樣的錯誤才對。
查詢了metalink后﹐發現是操作系統上SWAP分區設置太小導致的

對于小于8G的內存﹐Oracle建議SWAP是內存的兩倍﹐如果是8G以上內存﹐則SWAP至少是內存的0.75倍﹐而當前系統配置了16G內存﹐而SWAP只分配了8G﹐因此導致了大量并發會話連接到數據庫后﹐導致了操作系統SWAP空間不足﹐從而導致上述的錯誤。

將操作系統SWAP分區調整到16G以后﹐這個問題沒有再次出現