ORA-00130: invalid listener address and ORA-600 [ksfglt:no_proc] in alert log
(Doc ID 950172.1)
Last updated on JANUARY 20, 2025
Applies to:
Oracle Net Services - Version 11.1.0.6.0 to 11.1.0.7.0 [Release 11.1]Gen 2 Exadata Cloud at Customer - Version N/A and later
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Information in this document applies to any platform.
Symptoms
Alert Log
-----------
1. You find the following information in the alert log:
...
ORA-00130: invalid listener address '(ADDRESS=(PROTOCOL=TCP)(HOST=<hostname>)(PORT=1521))'
...
dispatcher 'D000' encountered error getting listening address
ORA-108 : opidrv aborting process D000 ospid (9269_1)
Errors in file /opt/app/hostname/diag/rdbms/instance/instance/instance_d000_9269.trc (incident=4904):
ORA-00600: internal error code, arguments: [ksfglt:no_proc], [], [], [], [], [], [], []
ORA-00108: failed to set up dispatcher to accept connection asynchronously
found dead dispatcher 'D000', pid = (23, 51)
2. This might be followed by numerous entries such as:
...
dispatcher 'D000' encountered error getting listening address
ORA-108 : opidrv aborting process D000 ospid (9854_1)
found dead dispatcher 'D000', pid = (23, 129)
...
dispatcher 'D000' encountered error getting listening address
ORA-108 : opidrv aborting process D000 ospid (9856_1)
...
found dead dispatcher 'D000', pid = (23, 130)
...
Dump Trace
-------------
In addition, you find the following in the dump trace specified above:
Unix process pid: 9269, image: oracle@curua02 (D000)
...
network error encountered getting listening address:
NS Primary Error: TNS-12533: TNS:illegal ADDRESS parameters
NS Secondary Error: TNS-12560: TNS:protocol adapter error
NT Generic Error: TNS-00503: Illegal ADDRESS parameters
OPIRIP: Uncaught error 108. Error stack:
ORA-00108: failed to set up dispatcher to accept connection asynchronously
...
DDE: Problem Key 'ORA 600 [ksfglt:no_proc]' was flood controlled (0x6) (incident: 4904)
ORA-00600: internal error code, arguments: [ksfglt:no_proc], [], [], [], [], [], [], []
ORA-00108: failed to set up dispatcher to accept connection asynchronously
kgepop: no error frame to pop to for error 600
Shadow_Core_Dump = PARTIAL
Changes
This may be a new install or some changes might have been made at the Network level, such as with hostnames.
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 |
| Changes |
| Cause |
| Solution |