DBCC Problems with syscolumns

Hi, I have run a DBCC CHECKDB and it found 2 Errors in syscolumns. I
have run a CHECKTABLE and found the following Error:
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 3, index ID 2: Page (1:266) could not be processed. See other
errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table Corrupt: Object ID 3, index ID 2, page (1:266), row 12. Test
(VarColOffsets + (int)(sizeof (class VarColOffset) * nVarCols) <=
(nextRec - pRec)) failed. Values are 178 and 72.
DBCC results for 'syscolumns'.
There are 6963 rows in 144 pages for object 'syscolumns'.
CHECKTABLE found 0 allocation errors and 2 consistency errors in table
'syscolumns' (object ID 3).
repair_allow_data_loss is the minimum repair level for the errors found
by DBCC CHECKTABLE (EMIS.dbo.syscolumns ).
Can anyone suggest the best way to proceed with this problem. I am a
little dubious about running REPAIR_ALLOW_DATALOSS on syscolumns, I am
unsure of what will happen if sections of syscolumns go missing. I have
run DBCC PAGE ('EMIS',1,266,1) but this has given me nothing to work
with.
Thanks in Advance,
Dave Shaw.
Normally i would suggest DBREINDEX but as this is a system table you're not
allowed.
Give SP_FixIndex a try. You will need the DB in single user mode 1st.
"Dave Shaw" <Dave.Shaw1584@.NTLWorld.com> wrote in message
news:1134990883.398840.145620@.z14g2000cwz.googlegr oups.com...
> Hi, I have run a DBCC CHECKDB and it found 2 Errors in syscolumns. I
> have run a CHECKTABLE and found the following Error:
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 3, index ID 2: Page (1:266) could not be processed. See other
> errors for details.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 3, index ID 2, page (1:266), row 12. Test
> (VarColOffsets + (int)(sizeof (class VarColOffset) * nVarCols) <=
> (nextRec - pRec)) failed. Values are 178 and 72.
> DBCC results for 'syscolumns'.
> There are 6963 rows in 144 pages for object 'syscolumns'.
> CHECKTABLE found 0 allocation errors and 2 consistency errors in table
> 'syscolumns' (object ID 3).
> repair_allow_data_loss is the minimum repair level for the errors found
> by DBCC CHECKTABLE (EMIS.dbo.syscolumns ).
> Can anyone suggest the best way to proceed with this problem. I am a
> little dubious about running REPAIR_ALLOW_DATALOSS on syscolumns, I am
> unsure of what will happen if sections of syscolumns go missing. I have
> run DBCC PAGE ('EMIS',1,266,1) but this has given me nothing to work
> with.
> Thanks in Advance,
> Dave Shaw.
>
|||This article may help ...
http://www.windows2000faq.com/Articl...rticleID=14051
"John Smith" <fsfsdf@.microsoft.com> wrote in message
news:enUNTKJBGHA.3872@.TK2MSFTNGP12.phx.gbl...
> Normally i would suggest DBREINDEX but as this is a system table you're
not
> allowed.
> Give SP_FixIndex a try. You will need the DB in single user mode 1st.
>
> "Dave Shaw" <Dave.Shaw1584@.NTLWorld.com> wrote in message
> news:1134990883.398840.145620@.z14g2000cwz.googlegr oups.com...
>
|||Thanks John Smith.
I shall give this a try.
Dave.