ORA-00600[ktspNextL1:4]_bug59098_11.1.0.7之后已修复
今天看了一下alert log发现如下报错： 查看alert log：
Fri Aug 2 07:13:33 2013
Errors in file /u01/Oracle/admin/eptdb/bdump/eptdb1_j002_9624.trc:
ORA-00600: internal error code, arguments: [ktspNextL1:4], [], [], [], [], [], [], []
Fri Aug 2 07:13:36 2013
Errors in file /u01/oracle/admin/eptdb/bdump/eptdb1_j002_9624.trc:
ORA-00600: internal error code, arguments: [ORA-00600: internal error code, arguments: [ktspNextL1:4], [], [], [], [], [], [], []
ORA-06512: at "SYS.PRVT_ADVISOR", line 1624
ORA-06512: at "SYS.DBMS_ADVISOR", line 186
ORA-06512: at "SYS.DBMS_SPACE", line 1500
ORA-06512: at "SYS.DBMS_SPACE", line 1566
], [], [], [], [], [], [], []
Fri Aug 2 07:13:36 2013
Trace dumping is performing id=[cdmp_20130802071336]
查看trace文件：
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [ktspNextL1:4], [], [], [], [], [], [], []
Current SQL statement for this session:
insert into wri$_adv_objspace_trend_data select timepoint, space_usage, space_alloc, quality from table(dbms_space.object_growth_t
rend(:1, :2, :3, :4, NULL, NULL, NULL, 'FALSE', :5, 'FALSE'))
----- PL/SQL Call Stack -----
object line object
handle number name
7000002e5a5d398 1834 package body SYS.DBMS_SPACE
7000002e5a5d398 3922 package body SYS.DBMS_SPACE
7000002e5a5d398 4233 package body SYS.DBMS_SPACE
70000030cded6d0 1 anonymous block
700000320ec2178 344 SYS.WRI$_ADV_OBJSPACE_TREND_T
700000320ec2178 1485 SYS.WRI$_ADV_OBJSPACE_TREND_T
70000031d9e48a8 1535 package body SYS.PRVT_ADVISOR
70000031d9e48a8 1618 package body SYS.PRVT_ADVISOR
70000031bb80860 186 package body SYS.DBMS_ADVISOR
7000002e5a5d398 1500 package body SYS.DBMS_SPACE
7000002e5a5d398 1566 package body SYS.DBMS_SPACE
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedst+001c bl ksedst1 700000344A7DF80 ? 100000001 ?
ksedmp+0290 bl ksedst 10454B728 ?
ksfdmp+0018 bl 03F49CB0
kgerinv+00dc bl _ptrgl
kgeasnmierr+004c bl kgerinv 000000000 ? 000000001 ?
000000001 ? 7000002684E40CC ?
7000002684E4014 ?
ktspGetNextL1ForSca bl kgeasnmierr 110173D18 ? 110400040 ?
n+0104 10487FADC ? 000000000 ?
000000002 ? 000000000 ?
...............
MOS中解释： CAUSE
Unpublished bug 6746222 ORA-00600 [KTSPNEXTL1:4] DURING WORKLOAD
Closed as a potential duplicate of unpublished Bug 59098
Unpublished bug 59098 ORA 600 [KTSPNEXTL1:4] WHILE SEGMENT SHRINK
Closed as not reproducible in 11.1.0.7, but a fix was never identified
--是由于bug 6746222、bug 59098 导致的。
SOLUTION
To implement the solution, please execute one of the following steps:
1. Ignore the error.
2. Upgrade to 11.1.0.7.
3. Rerun the job.
Unpublished bug 59098 was found during the 11g beta testing and was determined as being fixed in the 11.1.0.7 version. The bug was closed as not reproducible.
Reports of the same problem exist in 10.2 and those have been either suspended (because the problem only happened once) or marked as potential duplicate of unpublished bug 59098.
--我的数据库是10.2的，所以因为bug 59098而该报错。
This error happens when the advisor job runs continuously concurrent with other heavy segment operations. This bug does not cause any data corruption or instance crash. The workaround is to run the job again.
--这个bug不会导致数据损坏或者实例崩溃，因此不用管它，，只要重新启动job即可。
推荐阅读：
Oracle基础教程之通过RMAN复制数据库
RMAN备份策略制定参考内容
RMAN备份学习笔记
Oracle数据库备份加密 RMAN加密
