Database Instance crashes with ORA-15064
(Doc ID 1359441.1)
Last updated on MAY 22, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.2 to 11.2.0.2 [Release 11.2]Information in this document applies to any platform.
Symptoms
Database instance can terminate intermittently with the following messages in the alert log file:
NOTE: Deferred communication with ASM instance
Errors in file <Database Trace Directory>/db_arc1_13467.trc:
ORA-03113: end-of-file on communication channel
Process ID:
Session ID: 41 Serial number: 55245
NOTE: deferred map free for map id 41582
System state dump requested by (instance=1, osid=12401 (ASMB)), summary=[abnormal instance termination].
System State dumped to trace file <Database Trace Directory>/db_diag_12361.trc
Instance terminated by ASMB, pid = 12401
Errors in file <Database Trace Directory>/db_arc1_13467.trc:
ORA-03113: end-of-file on communication channel
Process ID:
Session ID: 41 Serial number: 55245
NOTE: deferred map free for map id 41582
System state dump requested by (instance=1, osid=12401 (ASMB)), summary=[abnormal instance termination].
System State dumped to trace file <Database Trace Directory>/db_diag_12361.trc
Instance terminated by ASMB, pid = 12401
The ASM instance alert log file show that the DB instance was unresponsive and terminating it.
Thu Sep 01 00:02:25 2011
System state dump requested by (instance=2, osid=14572), summary=[SYSTEMSTATE_GLOBAL: global system state dump request (kjdgdss_g)].
System State dumped to trace file <ASM Trace Directory>/+ASM2_diag_22981.trc
Thu Sep 01 00:04:17 2011
WARNING: client [DB:DB] not responsive for 237s; state=0x1. killing pid 12407
Thu Sep 01 00:05:02 2011
System state dump requested by (instance=2, osid=14572), summary=[SYSTEMSTATE_GLOBAL: global system state dump request (kjdgdss_g)].
System State dumped to trace file <ASM Trace Directory>/+ASM2_diag_22981.trc
Thu Sep 01 00:04:17 2011
WARNING: client [DB:DB] not responsive for 237s; state=0x1. killing pid 12407
Thu Sep 01 00:05:02 2011
The systemstate dump generated at the DB instance at the time of the crash would indicate that the there was a shared pool latch contention at the DB side and ASMB and other processes is intermittently stuck due to that.
PROCESS 17: ASMB
--------------------------------
Process Group: DEFAULT, pseudo proc: 0x97ce33298
O/S info: user: oracle, term: UNKNOWN, ospid: 12401
OSD pid info: Unix process pid: 12401, image: oracle@sdb-04p (ASMB)
service name: SYS$BACKGROUND
Current Wait Stack:
Not in wait; last wait ended 1.622120 sec ago
There are 35 sessions blocked by this session.
Dumping one waiter:
inst: 1, sid: 969, ser: 35769
wait event: 'latch: shared pool'
p1: 'address'=0x3800f7978
p2: 'number'=0x131
p3: 'tries'=0x0
--------------------------------
Process Group: DEFAULT, pseudo proc: 0x97ce33298
O/S info: user: oracle, term: UNKNOWN, ospid: 12401
OSD pid info: Unix process pid: 12401, image: oracle@sdb-04p (ASMB)
service name: SYS$BACKGROUND
Current Wait Stack:
Not in wait; last wait ended 1.622120 sec ago
There are 35 sessions blocked by this session.
Dumping one waiter:
inst: 1, sid: 969, ser: 35769
wait event: 'latch: shared pool'
p1: 'address'=0x3800f7978
p2: 'number'=0x131
p3: 'tries'=0x0
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 |
| Cause |
| Solution |
| References |