【问题记录】ORA-00600[ktspNextL1:4]_bug5649098_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_962644.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_962644.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 5649098

Unpublished bug 5649098 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 5649098 导致的。


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 5649098 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 5649098.

--我的数据库是10.2的,所以因为bug 5649098而该报错。


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即可。



  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值