Instance Locked after Multiple ORA-7445 errors Including; _memset _pollsys kglgob kjcsmba and _ndoprnt

(Doc ID 888451.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.4 and later
Oracle Solaris on SPARC (64-bit)
Sun Solaris SPARC (64-bit)

Symptoms

You are unable to access the instance. Accounts are locked and various ORA-07445 errors are generated in alertlog.

ORA-07445: exception encountered: core dump [_memset()+120] [SIGSEGV] [Address not mapped to
object] [0xFFFFFFFF7FFF7A40] [] []
ORA-07445: exception encountered: core dump [__pollsys()+8] [SIGSEGV] [Address not mapped to
object] [0xFFFFFFFF7FFEFFE0] [] []
ORA-07445: exception encountered: core dump [kglgob()+60] [SIGSEGV] [Address not mapped to object]
ORA-07445: exception encountered: core dump [kjcsmba()+24] [SIGSEGV] [Address not mapped to
object] [0xFFFFFFFF7FFE1F70] [] []
ORA-07445: exception encountered: core dump [_ndoprnt()+4] [SIGSEGV] [Address not mapped to
object] [0xFFFFFFFF7FFEFE30] [] []
ORA-16146: standby destination control file enqueue unavailable
ORA-03135: connection lost contact


Changes

This can happen when the kernal parameter SHMMAX is set to over half the size of the physical memory on the machine,
for example; if SHMMAX was set to 800G and operating system memory is only 16G.

Oracle is using the SYSTEM project files. They are owned by SYSTEM because the CRS installation is made using root.

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