Shutdown On Solaris 11 Can Cause Shared Memory Segments Not Getting Cleaned Up
(Doc ID 1643012.1)
Last updated on FEBRUARY 20, 2019
Applies to:Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Solaris on SPARC (64-bit)
If your database is running on Solaris Operating System version 11 and if you see similar of following symptoms.
a) Shared Memory Segments are NOT getting cleaned up after shutdown (instance) command is executed.
b) Shutdown is taking considerable amount of time.
c) Core Files with following functions.
d) No error in Alert log but core file would be generated.
ORACLE instance shut down.
ORA-3113: end-of-file on communication channel
e) ON SuperCluster Environment (Background Process is crashing with core dump
Process DBW3 died, see its trace file
USER (ospid: 5326): terminating the instance due to error 443
Instance terminated by USER, pid
f) Internal Error like
g) PMON terminating due to ORA-00443
Process PMON died, see its trace file
USER (ospid: 13966): terminating the instance due to error 443
Instance terminated by USER, pid = 13966
h) You may see Shutdown is hanging sometimes.
It would happen only on Solaris
This issue is regression issue .
IDR that delivers CR 17437800 that has introduced this issue
The IDR ( 808 or 876 ) can cause this issue .
You can check the IDR with following commands.
# pkg info entire
# pkg info idr876
# pkg info idr876
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