告警日誌出現skgpspawn failed category 27142錯誤

客戶的資料庫告警日誌出現skgpspawn failed資訊。

詳細錯誤資訊如下：

Mon Nov 28 07:59:59 2011
skgpspawn failed:category = 27142, depinfo = 11, p = fork, loc = skgpspawn5
skgpspawn failed:category = 27142, depinfo = 11, p = fork, loc = skgpspawn3
skgpspawn failed:category = 27142, depinfo = 11, p = fork, loc = skgpspawn3
skgpspawn failed:category = 27142, depinfo = 11, p = fork, loc = skgpspawn3
skgpspawn failed:category = 27142, depinfo = 11, p = fork, loc = skgpspawn3
skgpspawn failed:category = 27142, depinfo = 11, p = fork, loc = skgpspawn3
Mon Nov 28 08:00:20 2011
skgpspawn failed:category = 27142, depinfo = 11, p = fork, loc = skgpspawn5
skgpspawn failed:category = 27142, depinfo = 11, p = fork, loc = skgpspawn3
skgpspawn failed:category = 27142, depinfo = 11, p = fork, loc = skgpspawn3

從資訊上看，問題應該發生在fork操作時，或者說spawn程式時報錯。

這個27142錯誤對應的實際上是ORA-27142錯誤。

ORA-27142 could not create new process
Cause: Operating system call error.
Action: Check errno and if possible increase the number of processes.

可以看到這個錯誤發生在作業系統呼叫的錯誤上，根據說明很可能是程式數受到了限制。

檢查MOS，發現有兩篇文件和當前的情況類似，其中之一是Skgpspawn Errors In Alert Log, New Connections to Database Fail [ID 435787.1]，這篇文章中記錄的錯誤和當前十分類似，唯一的差別在於depinfo為12。而導致這個錯誤的原因是SWAP空間不足。

另外一篇Bug 5141429 - "skgspawn 27142" errors and defunct Oracle processes [ID 5141429.8]記錄的問題是由於殭屍程式所致，不過這篇文章記錄錯誤資訊與當前的區別仍然在於depinfo上，這篇文章的depinfo為0。

最終查詢作業系統上的資訊發現，除了系統中存在殭屍程式外，也有作業系統限制上的不同，只不過不是SWAP空間的不足，而是系統引數maxuprc設定太低所致。