Applies to:Oracle Server - Enterprise Edition - Version: 10.2.0.4 and later [Release: 10.2 and later ]
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_trend(:1, :2, :3, :4, NULL, NULL, NULL, 'FALSE', :5, 'FALSE'))
----- PL/SQL Call Stack -----
object line object
handle number name
0xa7b85db8 1834 package body SYS.DBMS_SPACE
0xa7b85db8 3922 package body SYS.DBMS_SPACE
0xa7b85db8 4233 package body SYS.DBMS_SPACE
0xa89eff668 1 anonymous block
0xa82a0BB8 344 SYS.RI$_ADV_OBJSPACE_TREND_T
0xa82a0BB8 1485 SYS.RI$_ADV_OBJSPACE_TREND_T
0xa79b07c8 1535 package body SYS.PRVT_ADVISOR
0xa79b07c8 1618 package body SYS.PRVT_ADVISOR
0xa88e9790 186 package body SYS.DBMS_ADVISOR
0xa7b85db8 1500 package body SYS.DBMS_SPACE
0xa7b85db8 1566 package body SYS.DBMS_SPACE
2. The alert.log reports:
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
], , , , , , , 
3. Part of the call stack contains:
kgeasnmierr <- ktspGetNextL1ForSca <- ktspGenExtentMap1 <- kteinmap1 <- kteinmap <- kdglfp <- kdgbp <- kdg_block_auto <- ktsa_object_space_u <- sage <- ktsaps_object_space <- usage <- pevm_icd_call_commo <- pfrinstr_ICAL <- pfrrun_no_tool <- pfrrun <- plsql_run <- peicnt <- kkxuexe <- kkxmpsexe <- kgmexwi <- kgmexec <- evapls <- evaopn2 <- qerocnFetch <- qerocFetch
Closed as a potential duplicate of Bug 5649098
Unpublished bug 5649098 ORA 600 [KTSPNEXTL1:4] WHILE SEGMENT SHRINK
Closed as not reproducible in 188.8.131.52, but a fix was never identified
1. Ignore the error.
2. Upgrade to 184.108.40.206.
3. Rerun the job.
Unpublished bug 5649098 was found during the 11g beta testing and was determined as being fixed in the 220.127.116.11 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.
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.