ORA-7445(koiogex)错误
上一篇 / 下一篇 2008-06-26 23:56:55 / 个人分类:Bug
在一个数据库的alert文件中发现了这个ORA-7445错误,这个错误应该是升级不完全造成的问题。
错误信息为:
Errors in file /opt/oracle/admin/data01/udump/data01_ora_7327.trc:ITPUB个人空间-G&E9UIb+~zq;u
ORA-07445: exception encountered: core dump [0000000101BFDCAC] [SIGSEGV] [Address not mapped to object] [0x
详细的trace文件内容:
Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0x
o2q N8m~5bM0ksedmp: internal or fatal error
cTC.R
k[7O0ORA-07445: exception encountered: core dump [0000000101BFDCAC] [SIGSEGV] [Address not mapped to object] [0x
+Dl#e(i1mE,by+Hu0Current SQL statement for this session:
.se [#Yk0BEGIN :1 := "SYS"."DBMS_AW_EXP".schema_info_exp(:2,:3,:4,:5,:6); END;
)zP9Y7s*_J1bx0----- PL/SQL Call Stack -----
l#{:h"~B.qrn,_0 object line object
u:rtIQ\6j0 handle number name
X3K&M'jY04012ff94020 106 package body SYS.DBMS_AWITPUB个人空间_'\B$W&o%M
4012ff94020 222 package body SYS.DBMS_AW
[!f#kcfcJ
bMNJ040143214ff8 264 package body SYS.DBMS_AW_EXP
C0Sg3z.x0401326627d8 1 anonymous blockITPUB个人空间(r~mY0^)B
~fl u@
----- Call Stack Trace -----
5v#x~R#d&S4~b-Q~0calling call entry argument values in hex
5S0OwTOYt0location type point (? means dubious value) ITPUB个人空间;x3uB4p~)Advs/O.z
-------------------- -------- -------------------- ----------------------------ITPUB个人空间].t~.~2X
ksedmp()+328 CALL ksedst()+0 FFFFFFFF7FFF
Ts;IR w)r*_
Q0 000000000 ? 000000000 ?
9\)W@E-}aF:l
_a0 00000003E ?ITPUB个人空间U'|-XNA?o$P-}
FFFFFFFF7FFF
huutj ^,B+Y0
ssexhd()+604 CALL ksedmp()+0 000000000 ? 000103400 ?
wj7M.NJ-S*mMj0 0001035CD ?
1035CD000 ? 1035CD328 ?ITPUB个人空间![N9H%]"P9NK@
sigacthandler()+44 PTR_CALL 0000000000000000 1035D5000 ?ITPUB个人空间%`^"S$s Us8F
z
FFFFFFFF7FFF7290 ?ITPUB个人空间;UBq,{4qP@a bK
000000000 ? 000000001 ?
]1}2a%f,i ?8u0 1035D24D8 ? 00000000B ?
9b ~IL'@vjA8gb7u0koiogex()+76 PTR_CALL 0000000000000000 00000000B ?ITPUB个人空间
VIc&I*u1I}bb b
FFFFFFFF7FFF7290 ?ITPUB个人空间$}1hK~ pr%fw'?9B#\
FFFFFFFF7FFF6FB0 ?ITPUB个人空间Z;_Mq%}ig'|B'{
00000000B ? 000000000 ?ITPUB个人空间1hQ(R8kCf
000000000 ?ITPUB个人空间pQTC{JQ7k
OCIObjectExists()+9 CALL koiogex()+0 1035CD588 ?
qm#Gj
N&d/N)Zm000 10358EB18 ?ITPUB个人空间R'v-F2s8S f
FFFFFFFF7FFF
00000000B ?
build_namelist()+48 CALL OCIObjectExists()+0 FFFFFFFF7D069698 ?
/d$k1se{8Y'\.i-f0 FFFFFFFF7CE0FA30 ?ITPUB个人空间p| ?R?B0xD(C1E
Z;@ g*y$gkx_ d0 FFFFFFFF7FFF
102BEC440 ? 000039400 ?ITPUB个人空间#Qx&y0xB&g
xseifExportTable()+ CALL build_namelist()+0 FFFFFFFF7FFF7988 ?ITPUB个人空间\+M!u~ Nz
236
000000001 ?ITPUB个人空间D5BPBU/N3d
FFFFFFFF7FFF7988 ?
.bo"j|}2hp"p0 000000000 ?
根据METALINK查询的结果:Doc ID: Note:416063.1,造成这个问题的原因是OLAP组件的状态不正常:
SQL> SELECT COMP_NAME, STATUS FROM DBA_REGISTRY;
COMP_NAME STATUSITPUB个人空间X;[}:X
BkPi'M
---------------------------------------- -----------
wFWch;fZuzG"Xb-L0Oracle OLAP API UPGRADEDITPUB个人空间:hZ`[`|&V!a
OLAP Analytic Workspace UPGRADED
+pU\/i P0Oracle Text VALID
(s7Py
z/d/g0?X[5@k0Oracle interMedia VALID
[)WiW5A'iF0Oracle9i Java Packages VALIDITPUB个人空间
w4X3_fM(^k&[0s7d
Oracle XDK for Java VALIDITPUB个人空间*e,f)r
}
@
JServer JAVA Virtual Machine VALIDITPUB个人空间JcX8E"m@
Oracle9i Packages and Types VALID
(Q"`*]"w%U_2g6lf,B#q5|0Oracle9i Catalog Views VALID
-hG~]n
A P"T$K0Oracle Workspace Manager VALIDITPUB个人空间"q7@d
N lunE5T8G
Spatial VALID
Zp3_xdM0Oracle XML Database VALID
1E,? oWT6vE
t!{3E:O0Oracle Ultra Search VALIDITPUB个人空间S&p~7U}0Wx
Oracle Data Mining VALID
l$BC @;cbI0OLAP Catalog VALID
15 rows selected.
由于OLAP的状态不正常,导致全库导出过程中,出现了这个错误。
Oracle给出的解决方法是STARTUP MIGRATE,然后运行?/rdbms/admin/catpatch.sql脚本。
这个方法需要重新启动数据库,且需要执行CATPATCH.SQL,代价相对较大。对于一些确认不使用OLAP的环境,可以通过避免全库导出,或者直接删除OLAP用户的方法来避免问题的产生。
导入论坛 引用链接 收藏 分享给好友 推荐到圈子 管理 举报
TAG: