Guardian Procedure Errors and Messages Manual

Recovery If insufficient PFS space was the cause of this error, either try to free up more PFS space
or wait for more PFS space to become available.
24 (%014000 + %nnn) UNKNOWN ERROR
Cause An error was received when an attempt was made to start a process on a remote system.
Your system does not know how to interpret the error.
Effect The call returns the PROCESS_CREATE_ error number %nnn, or 119 if the actual error
number is too large, in errinfo.<8:15>. No process is created.
Recovery For corrective action for the PROCESS_CREATE_ error received in bits <8:15> of the
errinfo parameter, see “Process Creation Errors” (page 158), and then perform a recovery action
based on this error. If the problem persists and the PROCESS_CREATE_ error number does not
give you enough information to diagnose the problem, contact your service provider.
25 (%014400) UNABLE TO ALLOCATE A PRIV STACK
FOR THE PROCESS
Cause There was no segment available for the priv stack of a TNS/R native process.
Effect No process is created.
Recovery Try a different processor or wait until the system load decreases and then retry the existing
call.
26 (%015000) UNABLE TO LOCK THE PRIV STACK
FOR THE PROCESS
Cause There was not enough physical memory free to lock the priv stack of a TNS/R native process.
Effect No process is created.
Recovery Try a different processor or wait until the system load decreases and then retry the existing
call.
27 (%015400) UNABLE TO ALLOCATE A MAIN STACK
FOR THE PROCESS
Cause There was no segment available for the main stack of a TNS/R native process.
Effect No process is created.
Recovery Try a different processor or wait until the system load decreases and then retry the existing
call.
28 (%016000) UNABLE TO LOCK THE MAINSTACK OF A
TNS/R NATIVE I/O PROCESS THAT IS
CREATED BY COUP
Cause There was not enough physical memory free to lock the main stack for a TNS/R native I/O
process. This error is only returned to some privileged callers.
Effect No process is created.
Recovery Try a different processor or wait until the system load decreases and then retry the existing
call.
29 (%016400 + %nnn) SECURITY INHERITANCE FAILURE
150 NEWPROCESS AND NEWPROCESSNOWAIT Errors