Database does not start after a Windows server reboot and clients are still attempting to connect because of a SID_LIST section in the listener.ora
(Doc ID 3003149.1)
Last updated on FEBRUARY 07, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 19.3.1.0.0 and laterOracle Net Services - Version 19.3.0.0.0 and later
Microsoft Windows x64 (64-bit)
Symptoms
When the Windows Server is restarted, the database intermittently does not OPEN.
Connections will fail with:
ORA-1034: ORACLE not available
ORA-27101: Shared Memory Realm Does Not Exist
etc.
Changes
The Windows Server was restarted but you have Clients (such as Applications like W3WP.EXE) that try and continue to connect while the DB is opening.
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 |