Instance crashes With ORA-00469
(Doc ID 1526119.1)
Last updated on MARCH 09, 2022
Applies to:
Oracle Database Cloud Exadata Service - Version N/A and laterOracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 10.2.0.4 and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
HP-UX Itanium
Symptoms
Instance crashes with the following error reported in the alert.log file
Errors in file /oracle/admin/XXX/bdump/XXX_pmon_10162.trc:
ORA-00469: CKPT process terminated with error
PMON: terminating instance due to error 469
Instance terminated by PMON, pid = 10162
pmon trace only says CKPT found dead
*** 2013-01-17 19:16:50.277
Background process CKPT found dead
Oracle pid = 7
OS pid (from detached process) = 10173
OS pid (from process state) = 10173
dtp = c000000100e17e40, proc = c00000057d4ad1d8
no CKPT trace files generated. However, there might be an <sid>_ora_xxx.trc trace file under udump.
ora trace file says
*** SESSION ID:(1920.29004) 2013-01-17 19:11:33.377
Waited for detached process: CKPT for 300 seconds:
.........
bt" | /opt/langtools/bin/gdb -quiet /oracle/produce/10.2.0/db/bin/oracle 10173 2>&1 timed out after 60 seconds
Or as mentioned in Bug 10008092, you may see below if gdb is called successfully.
@ 0xc00000000043af70:0 in _write_sys+0x30 () from /usr/lib/hpux64/libc.so.1
@ (gdb) (gdb)
@ #0 0xc00000000043af70:0 in _write_sys+0x30 () from /usr/lib/hpux64/libc.so.1
@ #1 0xc0000000004521b0:0 in write+0xb0 () from /usr/lib/hpux64/libc.so.1
@ #2 0x4000000002b951f0:0 in skgfqio () at skgfr.c:4264
@ #3 0x4000000002b05b40:0 in ksfdgo () at ksfd.c:10865
@ #4 0x4000000002a907a0:0 in ksfdbio () at ksfd.c:9507
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 |