Shutdown On Solaris 11 Can Cause Shared Memory Segments Not Getting Cleaned Up (Doc ID 1643012.1)

Last updated on DECEMBER 25, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 to 12.1.0.1 [Release 11.2 to 12.1]
Information in this document applies to any platform.

Symptoms

 

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.

ssMemMalloc_shared

ksm_attach_sga

ksmlsge_phaseone

 

d) No error in Alert log but core file would be generated.

 

Database dismounted.

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

ORA-600 [QKSCEPARAMSTRTONUM2]

 

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

 

 

 

Changes

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

# /opt/SUNWexplo/bin/explorer 

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms