首页 » ORACLE » skgpspawn failed:category = 27143 in alert log

skgpspawn failed:category = 27143 in alert log

A few days ago a friend asked me how to resolve this question if hit it from QQ. at that time I’m on vacation , sort out today.

This case with DB version 9.2.0.4, OS version He did not tell me.

[oracle@anbob ~]$ oerr ora 27143
27143, 0000, “OS system call failure”
// *Cause: OS system call failed
// *Action: check errno and contact Oracle support

Explanation:
============
This problem is occurring because you are running out of resources on your machine that are required for the servers to startup.

The error messages:

skgpspawn failed:category = 27143, depinfo = 24, op = pipe, loc = skgpspawn2

puts forward some ideas and methods for to solve this problem

1,Check free memory and swap on the server. 

2,Check the oracle account's process limits? 

$ ulimit -a

3,Is the executable large memory enabled?

4,alert log file ,listener.log size too big?

related bugs

bug 3980656 JOB QUEUE PROCESS START FAILS : SKGPSPAWN FAILED:CATEGORY = 27143
Fixed in Release 9.2.0.7

bug 4729565 ORA-600 [12235] AND SKGPSPAWN FAILED ERROR 27143 ORA-00600
Fixed in Release 10.2.0.3

Bug 4517854 : INITIALIZATION OF INTERNAL RECOVERY MANAGER PACKAGE FAILED ORA-01031
Fixed in Product Version 11.0
Hdr: 4517854 9.2.0.5.0 RDBMS 9.2.0.5.0 OSD PRODID-5 PORTID-46 ORA-7445
PROBLEM STATEMENT:
——————
skgpspawn failed:category = 27143, depinfo = 10, op = waitpid, loc =
skgpdparent1

Bug 3616023 Tru64: “skgpspawn failed:category = 27143” during process / instance startup
Versions confirmed as being affected
10.1.0.2
9.2.0.5

Platforms affected
HP Tru64

Process startup (as occurs during database startup or during
startup of any background process such as PQ slaves, extra
job queue processes etc..) can fail with an error of the form:

“skgpspawn failed:category = 27143, depinfo = 13, op = open, loc = skgpstime2”

bug 1003255

打赏

对不起,这篇文章暂时关闭评论。