njzh24 发表于 2013-08-12 19:07

老大们~help! Invalid column length: 18 at offset: 7. Value must be bet

10:00000:00218:2013/08/12 09:29:04.67 serverInvalid column length: 18 at offset: 7. Value must be between 0 and 201 for 'data-only' row with minimum row length of 60.
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x0000000100281668 pcstkwalk+0x84()
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x0000000100281ee4 ucstkgentrace+0x238()
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x0000000100280680 ucbacktrace+0xe4()
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x00000001003fafc8 collocate__fdpr_6+0x1cc()
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x00000001000093e4 setkeys+0x98()
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x00000001000c023c dol__form_btleafrow+0x40()
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x000000010058ab2c dol__ncinsert+0x11c()
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x000000010058b520 dol_insert__fdpr_2+0x110()
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x00000001000be3d8 ins_insert__fdpr_9+0x20()
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x0000000100059344 insert_all__fdpr_1+0x10()
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x00000001000593bc run__fdpr_11+0x38()
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x000000010002e508 exec_eop__fdpr_2+0x40()
10:00000:00218:2013/08/12 09:29:04.67 kernel
10:00000:00218:2013/08/12 09:29:04.67 kernel
10:00000:00218:2013/08/12 09:29:04.67 kernel
10:00000:00218:2013/08/12 09:29:04.67 kernel
10:00000:00218:2013/08/12 09:29:04.67 kernel
10:00000:00218:2013/08/12 09:29:04.67 kernel
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x000000010002983c execute+0x308()
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x0000000100060050 s_execute__fdpr_12+0x94()
10:00000:00218:2013/08/12 09:29:04.67 kernel
10:00000:00218:2013/08/12 09:29:04.67 kernel
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x000000010003f810 sequencer__fdpr_1+0x2e8()
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x0000000100077fd8 execproc+0x31c()
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x0000000100077c18 s_execute__fdpr_19+0x11c()
10:00000:00218:2013/08/12 09:29:04.67 kernel
10:00000:00218:2013/08/12 09:29:04.67 kernel
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x000000010003f810 sequencer__fdpr_1+0x2e8()
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x000000010005c820 tdsrecv_language__fdpr_1+0x44()
10:00000:00218:2013/08/12 09:29:04.67 kernel
10:00000:00218:2013/08/12 09:29:04.67 kernel
10:00000:00218:2013/08/12 09:29:04.67 kernel
10:00000:00218:2013/08/12 09:29:04.67 kernelpc: 0x000000010005c07c conn_hdlr__fdpr_1+0x1c4()
10:00000:00218:2013/08/12 09:29:04.67 kernelend of stack trace, spid 218, kpid 964428229, suid 11
10:00000:00218:2013/08/12 09:29:04.67 serverSET SWITCH SERVERWIDE ON 3605, SPID 218.
SDES: (at 0x18f440938) sdes_next=0x18f440e80 sdesp=0x18090cf00 objuid=1 objid=231668842 objname=IV_ORD_DETAIL_MIS
SDES: (at 0x18f431fa8) sdes_next=0x18f4324f0 sdesp=0x1819a8ad0 objuid=1 objid=8 objname=syslogs

ESTMT (0x200759b38) STATEMENT NUMBER 31 AT LINE 126:

e_next=0x1c5570ca0 e_estep=0x200759c50 e_goto=0x1c5570ca0 e_xdes=0x1a4002790 e_mpcr=0x20074ff28
e_offset=5613 e_lineno=126 e_stmtno=31 e_stmttype=195 (INSERT) e_open_varct=1 e_open_workct=0 e_open_ri_cnt = 0 e_locks=0x200755268 e_nlocks=1 e_mode=1 (XMOD_DIRECT) e_isolation
=0 (NOT_SPECIFIED), e_complevel=1 (LEVEL_1), e_estcost=0 e_status=(0x0010 (LEGALINXACT)) e_status2=(0x0000) e_updcol=0x0 ( )

LOCK STRATEGY FOR INSERT
      db=5 obj=231668842 lock=exclusive intent stat=0x0
e_css=0x0 e_resconst_list=0x0e_tempdb_cid=0
e_dseg_cnt=0, e_dseg_firsttbl=0x0, e_dseg_curtbl=0x0,
e_dseg_curtblcnt=0;
e_pre_dseg_alloc=0x0,
e_plansize=0u e_pmemcnt=0u, e_pmemhwm=0u e_ptempdb_hwm=0

e_runvars=0x0 {}

E_PLL:
e_plldeg=0

MAIN ESTEP (0x200759c50) NUMBER 0:
e_stnext=0x0 e_stsubor=0x0 e_stfirst=0x200754150 e_stbegrow=0x1c5570000
e_strowsz=3231 e_stendrow=0x1c5570c9e e_stresdom=0x200754568 e_stdefcol=0x0
e_ststat=(0x00000001 (USER)) e_st2stat=(0x00200000 (LASTQUERY), 0x00100000 (FIRSTQUERY)) e_st3stat=(0x00000000) e_st4stat=(0x00000000)
e_st5stat=(0x00000040 (OJ_PROCESSED), 0x00000020 (AGG_PROCESSED))
e_st7stat=(0x0000)
e_stepstat=(0x00000000)
e_toplimit=0 e_stvarct=1 e_stworkct=0 e_stresvar=0 ( IV_ORD_DETAIL_MIS )
e_streadvar=-1 (), e_stquerytype=195 (INSERT)
e_stname=0x0 () e_staggbuf=0x0 e_stvirtrg=0x2007550d8 e_strange=0x200759d20

Virtual Range Table:
# 0: 0x200759f20, # 1: 0x0, # 2: 0x0, # 3 0x0
# 4: 0x0, # 5: 0x0, # 6: 0x0, # 7 0x0
# 8: 0x0, # 9: 0x0, #10: 0x0, #11 0x0
#12: 0x0, #13: 0x0, #14: 0x0, #15 0x0
#16: 0x0, #17: 0x0, #18: 0x0, #19 0x0
#20: 0x0, #21: 0x0, #22: 0x0, #23 0x0
#24: 0x0, #25: 0x0, #26: 0x0, #27 0x0
#28: 0x0, #29: 0x0, #30: 0x0, #31 0x0
#32: 0x0, #33: 0x0, #34: 0x0, #35 0x0
#36: 0x0, #37: 0x0, #38: 0x0, #39 0x0
#40: 0x0, #41: 0x0, #42: 0x0, #43 0x0
#44: 0x0, #45: 0x0, #46: 0x0, #47 0x0
#48: 0x0, #49: 0x0

E_STPLL:
e_stpll=0x0

RANGE (0):(0x200759f20) rgstat:(0x00000800 (MADEPROT))rgstat2:(0x0000)    rgstat3:(0x0010 (ROWLOCK), 0x0004 (LOCK_DATAROWS))    rgstat4:(0x00)rgnondiskres=0x200754000    rgp
arent=0x200759f20 rgconstrl=0x0 rglastconstr=0x0
rgencrkey=0x0 rglastencrkey=0x0
    rgdes=0x18090cf00 rgndreop=0x0 rgtextoff=0x0
    rgdefaultcol=0x0, rgtabstatp=0x0
    Updated colids=(0x0 ( ))
    rgdepends: ( )
    rgndrstat:(0x00000020 (VARCOL))
    rgdcacheid=0 rgselfjoin=-1 rgnumpart=0 rgmaxpartsize=0
    rgadmlob=0x0
rgname(0x200754138)=IV_ORD_DETAIL_MIS rgtabid=231668842 rgdbid=5 rgschema2=14 rgschema=35 rgcoldel=1 rgsubq=0 rglevel=0 rglock=3 (exclusive intent)
rgcol:0x0 rgjoin:0x0 rgsclause:0x0 rgor=0x0 rgcorr=0x0 rgcursor=-1 rgcrtime=1160501 rgprefetch=0 rgdepends=( )

RESDOM LIST:

=======
日志中大量堆栈信息,导致日志文件大小剧增。。
dbcc checktable(IV_ORD_DETAIL_MIS) 无异常。
该表正常增删。

njzh24 发表于 2013-08-12 19:20

最烦这些堆栈信息, 无从下手啊。。。。

ceozenliu 发表于 2013-08-13 08:41

試試 dbcc checkcatalog(<database name>)

njzh24 发表于 2013-08-13 09:38

回复 3# ceozenliu

dbcc checkcatalog 是检查索引的一致性吧。
生产库,暂时还没敢试~
要是索引问题就好办赖~重建索引

ceozenliu 发表于 2013-08-13 11:07

dbcc checkcatalog
是在系统表中和系统表之间检查一致性,也包含索引

njzh24 发表于 2013-08-13 16:12

回复 5# ceozenliu


    check 过了,日志中的那张表有报错

Internal index error: Table id 231668842, indid 2, colid 20 length in Syscolumns 50 does not match value 7 in Sysindexes.
Msg 15052, Level 16, State 1:                                                                                             
Server 'mkt17', Line 1:                                                                                                   
Index error: Table id 231668842, indid 2 calculated maxirow 129 does not match value 86 in Sysindexes.                  
Msg 15052, Level 16, State 1:                                                                                             
Server 'mkt17', Line 1:                                                                                                   
Index error: Table id 231668842, indid 2 calculated maxlen 129 does not match value 86 in Sysindexes.                     
Found 3 errors in index 2 for table 231668842, run DBCC CHECKCATALOG(<db>, fix) or recreate the index to correct it.      


重建了索引,再check一遍, 无异常。
再观察一段时间吧。

andkylee 发表于 2013-08-13 19:53

用dbcc reindex重建Table id 231668842, indid 2

njzh24 发表于 2013-08-14 09:52

回复 7# andkylee
重建了索引,问题解决,不再堆栈信息。
什么情况会造成这种系统表间不一致呢。。。。
页: [1]
查看完整版本: 老大们~help! Invalid column length: 18 at offset: 7. Value must be bet