一个07445的错误

显示全部楼层 · 2008-1-2 17:35:53

今天在alert.log突然发现以下错误:
这个错误已经连续好几天了:
Errors in file f:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_4516.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__intel_fast_memcmp+36] [PC:0x2610984] [ADDR:0x0] [UNABLE_TO_READ] []
Thu Mar 23 16:58:03 2006
Errors in file f:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_3940.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__intel_fast_memcmp+36] [PC:0x2610984] [ADDR:0x0] [UNABLE_TO_READ] []
Thu Mar 23 17:04:10 2006
Errors in file f:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_4732.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__intel_fast_memcmp+36] [PC:0x2610984] [ADDR:0x0] [UNABLE_TO_READ] []
Thu Mar 23 17:04:25 2006
Errors in file f:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_884.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__intel_fast_memcmp+36] [PC:0x2610984] [ADDR:0x0] [UNABLE_TO_READ] []
Thu Mar 23 17:04:51 2006
Errors in file f:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_4732.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__intel_fast_memcmp+36] [PC:0x2610984] [ADDR:0x0] [UNABLE_TO_READ] []
Thu Mar 23 17:05:26 2006
Errors in file f:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_884.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__intel_fast_memcmp+36] [PC:0x2610984] [ADDR:0x0] [UNABLE_TO_READ] []
Thu Mar 23 17:05:41 2006
Errors in file f:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_4756.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__intel_fast_memcmp+36] [PC:0x2610984] [ADDR:0x0] [UNABLE_TO_READ] []
Thu Mar 23 17:06:36 2006
Errors in file f:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_4680.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__intel_fast_memcmp+36] [PC:0x2610984] [ADDR:0x0] [UNABLE_TO_READ] []
Thu Mar 23 17:08:58 2006
Errors in file f:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_4756.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__intel_fast_memcmp+36] [PC:0x2610984] [ADDR:0x0] [UNABLE_TO_READ] []
Thu Mar 23 17:09:21 2006
Errors in file f:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_4680.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__intel_fast_memcmp+36] [PC:0x2610984] [ADDR:0x0] [UNABLE_TO_READ] []
Thu Mar 23 17:09:35 2006
Errors in file f:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_4756.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__intel_fast_memcmp+36] [PC:0x2610984] [ADDR:0x0] [UNABLE_TO_READ] []
Thu Mar 23 17:16:03 2006
Errors in file f:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_4224.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__intel_fast_memcmp+36] [PC:0x2610984] [ADDR:0x0] [UNABLE_TO_READ] []
Thu Mar 23 17:16:19 2006
Errors in file f:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_4644.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__intel_fast_memcmp+36] [PC:0x2610984] [ADDR:0x0] [UNABLE_TO_READ] []
Thu Mar 23 17:16:50 2006
Errors in file f:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_4224.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__intel_fast_memcmp+36] [PC:0x2610984] [ADDR:0x0] [UNABLE_TO_READ] []
Thu Mar 23 17:18:14 2006
Errors in file f:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_4644.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__intel_fast_memcmp+36] [PC:0x2610984] [ADDR:0x0] [UNABLE_TO_READ] []
Sat Mar 25 12:28:24 2006
Errors in file f:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_2152.trc:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__intel_fast_memcmp+36] [PC:0x2610984] [ADDR:0x0] [UNABLE_TO_READ] []
...
...
...
截止到25号为止.这个错误信息就消失了.

千问 · 2008-1-2 17:35:53

以下是trace的内容.
*** SERVICE NAME

SYS$USERS) 2006-03-25 12:24:48.125
*** SESSION ID

117.5730) 2006-03-25 12:24:48.125
*** 2006-03-25 12:24:48.125
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [__intel_fast_memcmp+36] [PC:0x2610984] [ADDR:0x0] [UNABLE_TO_READ] []
Current SQL statement for this session:
update sms_info set gzzp=:"SYS_B_0" where rlrybh=:"SYS_B_1"
----- Call Stack Trace -----
calling
call entry
argument values in hex
location
type point
(? means dubious value)
-------------------- -------- -------------------- ----------------------------
__intel_fast_memcmp 00000000

+36

_kkscbt+287
CALLrel_kxscod+0
26905840 B17010C 263FF8C8

DD16D38 1
_kksfbc+13476CALLrel_kkscbt+0
FACD318 B17010C 0 102
_opiexe+1856 CALLrel_kksfbc+0
B17010C 3 102 0 0 FACD7EC

FACD824 0
_kpoal8+2172 CALLrel_opiexe+0
49 3 FACDB10
_opiodr+1099 CALLreg00000000
5E 17 FACF6F4
_ttcpip+1273 CALLreg00000000
5E 17 FACF6F4 0
_opitsk+1017 CALL???00000000

_opiino+1087 CALLrel_opitsk+0
0 0
_opiodr+1099 CALLreg00000000
3C 4 FACFC8C
_opidrv+819
CALLrel_opiodr+0
3C 4 FACFC8C 0
_sou2o+45
CALLrel_opidrv+0
3C 4 FACFC8C
_opimai_real+112 CALLrel_sou2o+0
FACFC80 3C 4 FACFC8C
_opimai+92 CALLrel_opimai_real+0 2 FACFCB8
_OracleThreadStart@CALLrel_opimai+0

4+708

77E6B385
CALLreg00000000

--------------------- Binary Stack Dump ---------------------
.....................

千问 · 2008-1-2 17:35:53

在大多数trace文件中的发生这个错误时的current sql都是:
update sms_info set gzzp=:"SYS_B_0" where rlrybh=:"SYS_B_1"
但是在我作单独测试的时候.未没有产生这个错误.
我的DB版本是10.2.0.1

cursor_sharing= SIMILAR

千问 · 2008-1-2 17:35:53

AIX5L,10201
我的数据库也是因为一个语句出现这个问题，在10202（WINDOWS 2003）上同一个语句，
则没有。

千问 · 2008-1-2 17:35:53

最初由 ZALBB 发布
[B]AIX5L,10201
我的数据库也是因为一个语句出现这个问题，在10202（WINDOWS 2003）上同一个语句，
则没有。 [/B]
不过现在已经没有这个错误了.metalink也说得不太清楚.

千问 · 2008-1-2 17:35:53

我的也是，好像说是10gR2的一个bug。

千问 · 2008-1-2 17:35:53

Bug 3315960是one-off patch，能够解决这个问题。但是有一点是您需要理解的，就是Oracle永远推荐客户使用最新的补丁集，这是因为补丁集都是经过递归测试的，而one-off patch只是为了某个问题而发出的，并没有经过回归测试。这个Bug在9.2.0.6往后版本的数据库中不会再出现，因此，您可以有两个选择：升级到 9.2.0.6，或者打这个one-off patch

千问 · 2008-1-2 17:35:53

最初由 lexus 发布
[B]Bug 3315960是one-off patch，能够解决这个问题。但是有一点是您需要理解的，就是Oracle永远推荐客户使用最新的补丁集，这是因为补丁集都是经过递归测试的，而one-off patch只是为了某个问题而发出的，并没有经过回归测试。这个Bug在9.2.0.6往后版本的数据库中不会再出现，因此，您可以有两个选择：升级到 9.2.0.6，或者打这个one-off patch [/B]

您可能弄错了.我的DB版本是10gR2
不过很感谢您的建议^_^