Thanks for the question, Calibre DJ.
Asked: January 25, 2018 - 4:42 pm UTC
Last updated: January 25, 2018 - 4:51 pm UTC
Version: Oracle9i Enterprise Edition Release 9.2.0.6.0
Viewed 1000+ times
You Asked
Hello, I am receiving the following error in the alert log of my DB:
Errors in file /u01/app/oracle/admin/oraprod/udump/oraprod_ora_239365.trc:
ORA-07445: exception encountered: core dump [unknown] [SIGILL] [Illegal opcode] [0x000000000] [] []
I have read that it may be caused by several factors, but what I need is to detect which of these factors is causing it, it occurs mostly during working hours, I would like you to help me to see what steps or what steps to follow to capture the problem in question.
I use TOAD for administration, and I do not really understand the .trc file:
...
Oracle process number: 31
Unix process pid: 222418, image: oracle @ gs1280prod (TNS V1-V3)
*** 2018-01-25 10: 02: 42.862
*** SESSION ID: (40.24245) 2018-01-25 10: 02: 42.862
Exception signal: 4 (SIGILL), code: 1 (Illegal opcode), addr: 0x0
sc_onstack: 0000000000000000, sc_mask 0000000000000000
pc: 000000012037fbe4, ps: 0000000000000008, ownedfp: 0000000000000001
r00: 00000000000003f2
r01: 00000001403da2a0
r02: 000000011fffa078
r03: 0000000120e37260
r04: 0000000000000004
r05: 0000000000000000
r06: 0000000000000000
r07: 0000000000000006
r08: 0000000000000006
r09: 0000000000000000
r10: 0000000000000001
r11: 00000000000003f2
r12: 00000001400c5540
r13: 00000001400c3e48
r14: 0000000038008af0
r15: 000000014030c130
r16: 0000000038008af0
r17: 0000000000000093
r18: 000000011fffa190
r19: 0000000000000000
r20: 0000000000000000
r21: 000000011fffa098
r22: 0000000000000001
r23: 0000000000000000
r24: 0000000000000000
r25: 0000000038010000
r26: 0000000120e39ef4
r27: 000000012037fbd0
r28: ffffffffffffffff
r29: 00000001402aa340
r30: 000000011fffa000
r31: 0000000000000000
fpcr: 8900000000000000, fp_control: 0000000000000000
trap_a0: 0000000000000004, trap_a1: 0000000000000093, trap_a2: 000000011fffa190
fp_trap_pc: 0000000000000000, fp_trigger_sum: 00000001403d9440, fp_trigger_inst 000000000040002d
*** 2018-01-25 10: 02: 44.120
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [unknown] [SIGILL] [Illegal opcode] [0x000000000] [] []
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- - --------------------------
ksedmp: 2049 [kse.c] ??? ksedst: 2638 [kse.c] 120D418C0? 000000004?
000000002? 11FFF9D78?
000000000? 11FFF9BD0?
ssexhd: 289 [ssexhd.c ??? ksedmp: 2049 [kse.c] 12028B9D0? 000000001?
] 00000000E? 12028B538?
000000002? 000000000?
__sigtramp [<strippe ??? ssexhd: 289 [ssexhd.c 11FFF9D78? 000000000?
d>]] 000000040? 000000004?
C00000001? 000000000?
[] JSR __sigtramp [<strippe 000000040? 000000004?
d>] C00000001? 000000000?
000000003?
FFFFFFFF00000000?
--------------------- Binary Stack Dump ---------------------
========== FRAME [1] (ksedmp: 2049 [kse.c] -> ksedst: 2638 [kse.c]) ==========
Dump of memory from 0x0000000140313D10 to 0x0000000140313DB0
140313D10 1FFF7EB0 00000001 00000003 00000000 [. ~ ..............]
140313D20 20D4015C 00000001 00000001 00000000 [\ .. ............]
140313D30 40313DB0 00000001 20D418C0 00000001 [. = 1 @ ....... ....]
140313D40 00000004 00000000 00000002 00000000 [................]
... etc
and Chris said...
ORA-07445s are internal errors. There's a lookup tool at MOS note 153788.1 to help you understand it.
In any case, you should work with support to resolve it.
Who will probably tell you to upgrade from 9i ;)
Is this answer out of date? If it is, please let us know via a Comment