OpenVMS: Listener Process Occasionally Fails And Requires Manual Restart
(Doc ID 390597.1)
Last updated on DECEMBER 18, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 7.0.16.0 to 10.2.0.5 [Release 7.0 to 10.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
HP OpenVMS Itanium
HP OpenVMS Alpha
***Checked for relevance on 21-Jun-2013***
Symptoms
The SQL*Net Listener process dies and needs to be restarted.
The Alert log may contain additional information that suggests problems with OpenVMS processes.
For example:
skgpspawn failed:category = 27142, depinfo = 924, op = skgpspawn_error, loc = skgpspawn3
ksbsrv: No startup acknowledgement from forked process after 30 seconds
The first error shows a 'depinfo' value of 924.
This translates to the following OpenVMS error ($ exit 924):
%SYSTEM-F-NOSLOT, no PCB available
The OpenVMS help for this error is :
The maximum number of processes that can be created at one
time has been exceeded.
The second error suggests that we (Oracle) have requested that a new process to be started and,
after waiting for 30 seconds, find the process has not been successfully started.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |