Instance Locked after Multiple ORA-7445 errors Including; _memset _pollsys kglgob kjcsmba and _ndoprnt
(Doc ID 888451.1)
Last updated on APRIL 06, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.4 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A 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]
ORA-07445: exception encountered: core dump [__pollsys()+8] [SIGSEGV]
ORA-07445: exception encountered: core dump [kglgob()+60] [SIGSEGV]
ORA-07445: exception encountered: core dump [kjcsmba()+24] [SIGSEGV]
ORA-07445: exception encountered: core dump [_ndoprnt()+4] [SIGSEGV]
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
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 |
| References |