数据库版本:oracle 9.2.0.6.0
操作系统:Red Hat Enterprise Linux AS release 3 (Taroon Update 5)
例行检查的时候,发现后台报警日志有报错。
分别有三次报错,在最近
Thu May 1 00:20:49 2008
Errors in file /home/oracle/admin/md126/udump/md126_ora_4468.trc:
ORA-07445: exception encountered: core dump [lxmspax()+46] [SIGSEGV] [Address not mapped to object] [0x16E] [] []
Thu May 1 00:21:23 2008
Fri May 16 01:43:16 2008
Errors in file /home/oracle/admin/md126/bdump/md126_d002_9354.trc:
ORA-07445: exception encountered: core dump [nstimset()+224] [SIGSEGV] [Address not mapped to object] [0x0] [] []
Fri May 16 01:43:24 2008
Tue Jun 17 12:26:40 2008
Errors in file /home/oracle/admin/md126/bdump/md126_d000_9340.trc:
ORA-07445: exception encountered: core dump [nstimset()+224] [SIGSEGV] [Address not mapped to object] [0x0] [] []
Tue Jun 17 12:27:40 2008
因为我是月初接手的这个库,所以,今天才发现问题又报了。
/home/oracle/admin/md126/bdump/md126_d000_9340.trc的节选部分:
Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0x0, PC: [0xa0a1e72, nstimset()+224]
Registers:
%eax: 0x00000000 %ebx: 0x0aea8824 %ecx: 0x00007530
%edx: 0x0aec71a0 %edi: 0x00000005 %esi: 0x0c153420
%esp: 0xbfff99a0 %ebp: 0xbfff99d8 %eip: 0x0a0a1e72
%efl: 0x00010206
nstimset()+204 (0xa0a1e5e) mov 0x158(%ecx),%eax
nstimset()+210 (0xa0a1e64) movzw 0x14c(%ecx),%edi
nstimset()+217 (0xa0a1e6b) imul $0x1770,%edi,%ecx
nstimset()+223 (0xa0a1e71) push %ecx
> nstimset()+224 (0xa0a1e72) push (%eax)
nstimset()+226 (0xa0a1e74) push 0xc4(%edx)
nstimset()+232 (0xa0a1e7a) call 0xa2bb564
nstimset()+237 (0xa0a1e7f) add $12,%esp
nstimset()+240 (0xa0a1e82) test %eax,%eax
*** 2008-06-17 12:26:40.312
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [nstimset()+224] [SIGSEGV] [Address not mapped to object] [0x0] [] []
Current SQL information unavailable - no session.
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedmp()+274 call ksedst() 1 ? 0 ? 0 ? 1 ? 65252C78 ?
7861 ?
ssexhd()+1113 call ksedmp() 3 ? 0 ? 0 ? 0 ? 0 ? 0 ?
__pthread_sighandle call 00000000 B ? B75CFC90 ? B75CFD10 ? 0 ?
r_rt()+122 0 ? 0 ?
nstimset()+224 signal 00000000 B ? B75CFC90 ? B75CFD10 ?
nstimexp()+650 call nstimset() C154DD0 ? C201450 ?
ltmdvp()+177 call 00000000 C16B4D0 ? C201450 ? C18F6E0 ?
1876A977 ? 1F9F9 ? C16B3A8 ?
C18F6E0 ?
ltmdrv()+89 call ltmdvp() C16B4D0 ? C16B3A8 ? 0 ? 0 ?
sltmdf()+32 call ltmdrv() C16B4D0 ? 0 ? 0 ?
sslsstehdlr()+560 call 00000000 E ? C16B4D0 ?
__pthread_sighandle call 00000000 E ? BFFF9C10 ? BFFF9C90 ? 0 ?
r_rt()+122 0 ? 0 ?
__GI___poll()+56 signal 00000000 E ? BFFF9C10 ? BFFF9C90 ?
__PGOSF27_ntevpque( call poll() C24D7B4 ? B8 ? EA60 ? 1 ?
)+225 50 ? 0 ?
ntevque()+162 call 00000000 C1551B8 ? EA60 ? BFFFA830 ?
AEA8824 ? 0 ? C154DD0 ?
nsevwait()+474 call ntevque() C1551B8 ? EA60 ? BFFFA830 ?
BFFFA930 ? C153420 ?
C154DD0 ?
ksnwait()+46 call nsevwait() C154DD0 ? AEB77A4 ? AEB77A8 ?
0 ? AEB77AC ?
ksliwat()+1772 call ksnwait() EA60 ? 0 ? AD3C717C ?
C194720 ? 0 ? 2 ?
kslwaitns()+29 call ksliwat() 1770 ? 1 ? 144 ? 0 ? 1770 ?
0 ? 0 ?
kskthbwt()+83 call kslwaitns() 1770 ? 1 ? 144 ? 0 ? 1770 ?
0 ? 0 ?
kslwait()+61 call kskthbwt() 1770 ? 1 ? 144 ? 0 ? 1770 ?
0 ?
kmdmai()+1431 call kslwait() 1770 ? 144 ? 0 ? 1770 ? 0 ?
kmmrdp()+472 call kmdmai() A135616C ? 299D24E3 ? 1C ?
A0FF027F ? BFFFABDC ? E7F ?
opirip()+729 call kmmrdp() AEB485C ? BFFFB588 ? 13A46C ?
BFFFB6F0 ? 1 ? 1 ?
opidrv()+865 call opirip() 32 ? 0 ? 0 ?
sou2o()+30 call opidrv() 32 ? 0 ? 0 ?
main()+440 call sou2o() BFFFB6F0 ? 32 ? 0 ? 0 ?
57E710 ? 0 ?
__libc_start_main() call 00000000 1 ? BFFFB774 ? BFFFB77C ?
+170 57E518 ? 1 ? 8213EC0 ?
metalink如下说:
-- Problem Statement:
On 10.2.0.3 in Production:
While attempting cloning a production, the following error occurs:
ERROR
RMAN-03015: error occurred in stored script Memory Script
RMAN-10038: database session for channel ORA_AUX_SBT_TAPE_3 terminated unexpectedly
by checking the alert.log for target database we noticed the following error cause the session
termination with RMAN :
Errors in file /oracle/admin/FSSIT/udump/fssit_ora_28003.trc:
ORA-07445: exception encountered: core dump [CleanUpShMforRestore()+164] [SIGSEGV] [Address not
mapped to object] [0x000000070] [] []
Tue Feb 19 13:28:10 2008
Errors in file /oracle/admin/FSSIT/udump/fssit_ora_28005.trc:
ORA-07445: exception encountered: core dump [CleanUpShMforRestore()+164] [SIGSEGV] [Address not
mapped to object] [0x000000040] [] []
Tue Feb 19 13:28:21 2008
Errors in file /oracle/admin/FSSIT/udump/fssit_ora_28007.trc:
ORA-07445: exception encountered: core dump [CleanUpShMforRestore()+164] [SIGSEGV] [Address not
mapped to object] [0x0000000D0] [] []
Tue Feb 19 13:28:37 2008
Errors in file /oracle/admin/FSSIT/udump/fssit_ora_28009.trc:
ORA-07445: exception encountered: core dump [CleanUpShMforRestore()+164] [SIGBUS] [Invalid address
alignment] [0x6F6E647320776879] [] []
Cause
Issue is caused by Media Manager
ORA-7445 shows that process crashes in function 'CleanUpShMforRestore' which is a Media Manager
function
Solution
This is not an Oracle issue but concerns the Media Manager
Since the 'CleanUpShMforRestore' is a Media Manager function.
As such, please contact your Media Manager vendor concerning this issue.
Keywords
CORE~DUMP; CLONING.RTF; INVALID~ADDRESS;
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/79499/viewspace-417661/,如需转载,请注明出处,否则将追究法律责任。