Database Hangs with ORA-7445 [kglic0()+1172], PMON Failed to Acquire Latch, ORA-29771
(Doc ID 2128960.1)
Last updated on AUGUST 25, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.3 to 11.2.0.4 [Release 11.2]Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Next error is reported in the alert log:
ORA-07445: exception encountered: core dump [kglic0()+1172] [SIGBUS] [ADDR:0xB38F0000000091] [PC:0x1085FB354] [Invalid address alignment] []
The call stack from the trace file shows functions like:
... kglic0 kksIterCursorStat kewrbtsq_build_topsql kewrftsq_flush_topsql kewrft_flush_table kewrftec_flush_table_ehdlcx kewrfat_flush_all_tables kewrfsr_flush_snapshot_r ...
In alert.log, also other errors are reported next to the ORA-7445 in the following order:
ORA-07445: exception encountered: core dump [kglic0()+1172] [SIGBUS] [ADDR:0xB38F0000000091] [PC:0x1085FB354] [Invalid address alignment] []
...
PMON failed to acquire latch, see PMON dump
...
LCK0 (ospid: 29766) waits for latch 'shared pool' for 92 secs.
...
ORA-29771: process USER (OSID 17702) blocks LCK0 (OSID 29766) for more than 70 seconds
...
PMON failed to acquire latch, see PMON dump
...
LCK0 (ospid: 29766) waits for latch 'shared pool' for 92 secs.
...
ORA-29771: process USER (OSID 17702) blocks LCK0 (OSID 29766) for more than 70 seconds
Changes
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 |