ora-600 ktbdchk1: bad dscn
大批量dml操作时报错如下:
ora-600 ktbdchk1: bad dscn
metlink上有如下描述:
ORA-600 on UPDATE statement
========= Dump for incident 932331 (ORA 600 [ktbdchk1: bad dscn]) ========
----- Beginning of Customized Incident Dump(s) -----
[ktbdchk] -- ktbgcl4 -- bad dscn
dependent scn: 0x0013.dc0691c4 recent scn: 0x0013.a7fdc08a current scn: 0x0013.a7fdc08a
----- End of Customized Incident Dump(s) -----
*** 2012-10-08 00:55:43.199
dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0)
----- Current SQL Statement for this session (sql_id=9m8qjhtu2vj4r) -----
UPDATE SIEBEL.S_ORG_EXT BT
SET (ACTIVE_FLG,
CONTRACT_VIS_FLG,
DISA_CLEANSE_FLG,
EVT_LOC_FLG,
FCST_ORG_FLG,
FUND_ELIG_FLG,
INCL_FLG,
INT_ORG_FLG,
PROSPECT_FLG,
PRTNR_FLG,
...
----- Call Stack Trace -----
skdstdst <- ksedst1 <- ksedst <- dbkedDefDump <- ksedmp
<- ksfdmp <- dbgexPhaseII <- dbgexExplicitEndInc <- dbgeEndDDEInvocatio <- nImpl
<- dbgeEndDDEInvocatio <- ktbValidateDependen <- tScn <- ktbgcl1 <- tScn
<- ktbgtl0 <- kdiins0 <- kdiinsp <- kauupd <- updrow
<- qerupFetch <- updaul <- updThreePhaseExe <- 319 <- updexe
<- opiexe <- kpoal8 <- opiodr <- ttcpip <- opitsk
<- opiino <- opiodr <- opidrv <- sou2o <- opimai_real
<- ssthrdmain <- main <- libc_start_main <- start
一般解决方式就是:
1 打psu;
2 修改隐含参数: "_ktb_debug_flags"=8(oracle建议 patch for bug 8895202 打后,再修改)
来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/13750068/viewspace-1086858/ ,如需转载,请注明出处,否则将追究法律责任。