ORA-00600 [qosdExpStatRead: expcnt mismatch] Still Happens Even After Applied both Patch 28681153 and Patch 31143146 (Doc ID 2803002.1)

Last updated on SEPTEMBER 27, 2023

Applies to:

Symptoms

• ORA-00600 [qosdExpStatRead: expcnt mismatch] error still happens even after applying merge patch 33206421 including the fix of 28681153 and 31143146.
  
  
  ORA-00600: internal error code, arguments: [qosdExpStatRead: expcnt mismatch], [0], [47], [91560], [1], [], [], [], [], [], [], []
  
       qosdExpStatRead <- 380 <- kglslod <- qosdExpObjLoad <- kglobld
          <- kglobpn <- kglpim <- kglpin <- qosdGetKglObj <- qosdUpdExprStat
           <- 096 <- ksxmfchk <- ksxmftim <- ksxmfallOneObj <- qosdFlushSlave
            <- kebm_slave_cb <- kpdbSwitch <- kebm_slave_main <- 174 <- ksvrdp_int
             <- opirip <- opidrv <- sou2o <- opimai_real <- ssthrdmain
              <- main <- libc_start_main
  
  
  
• Customer tried the workaround of MOS Note 28681153.8 at both CDB and PDB, but it does not help to solve the problem.
  
  
  With b as (
  select count(*) cnt,objn,snapshot_id from sys.exp_stat$ es group by
  objn,snapshot_id)
  select * from sys.exp_obj$ a, b where a.objn=b.objn and
  a.snapshot_id=b.snapshot_id
  and a.EXP_CNT<>b.CNT;
  
  
  delete from sys.exp_stat$ b
  where b.snapshot_id = <snapshot_id> and b.objn = <objn> ;
  
  update sys.exp_obj$  a
  set a.EXP_CNT=0
  where a.SNAPSHOT_ID= <snapshot_id>
     and a.objn = <objn>;
  
  commit;
• After the ORA-00600: [qosdExpStatRead: expcnt mismatch] customer check the query result, but didn't return any row.
  
  
  With b as (
  select count(*) cnt,objn,snapshot_id from sys.exp_stat$ es group by
  objn,snapshot_id)
  select * from sys.exp_obj$ a, b where a.objn=b.objn and
  a.snapshot_id=b.snapshot_id
  and a.EXP_CNT<>b.CNT;

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.