Error 605 - table corrupted - help!! 
Author Message
 Error 605 - table corrupted - help!!

I saw Russell Fields' reply (over 2 years old!!!) in Deja-News to Mike
Fulton who had a very similar problem to mine.  I hope Russell (or
anyone else!!) can help me also.

My client just received a message from an Automated Task (which runs at
midnight and is SQLMAINT.EXE -D ALAN -CkDB -CkAl -CkTxtAl -CkCat  -Rpt
D:\MSSQL\LOG\CREDSURE_maint.rpt) indicating it had failed.  Looking at
the Task History I saw that it has failed every night since October 6
(but my client had never noticed!!)  I would prefer not to have to
restore to then and so I am asking for your help.  The log file has the
following:

[1] Check Data and Index Linkage...
   The following errors were found:
Attempt to fetch logical page 841656 in database 'ALAN' belongs to
object  'Document', not to object 'Buyer'.

Data size mismatch occurred while checking TEXT/IMAGE values. The first
page for this value is: 685795. There were 1800 bytes found, which is
different from the expected data length of 755712 bytes.

Table Corrupt: Page linkage is not consistent; check the following
pages:
(current page#=811001;  page# pointing to this page=811000; previous
page# indicated in this page=814407)
   ** Execution Time: 0 hrs, 8 mins, 59 secs **

[2] Check Data and Index Allocation...
   The following errors were found:
Table Corrupt: Object id wrong; tables: alloc page 841472  extent
id=841656
l page#=841656 objid in ext=1754489329 (name = Document) objid in
page=1754489329 (name = Document)objid in sysindexes=265820059 (name =
Buyer)

Table Corrupt: Extent is linked in more than one chain.  Check the
following allocation page and extent: alloc pg#=841728 extent#=841728
status=194
   ** Execution Time: 0 hrs, 2 mins, 33 secs **

[3] Check Text/Image Data Allocation...
   The following errors were found:
Table Corrupt: Page linkage is not consistent; check the following
pages:
(current page#=811001;  page# pointing to this page=811000; previous
page# indicated in this page=814407)

Page 841671 was expected to be the first page of a TEXT/IMAGE value.
Page 841685 was expected to be the first page of a TEXT/IMAGE value.
Page 841697 was expected to be the first page of a TEXT/IMAGE value.
Page 841710 was expected to be the first page of a TEXT/IMAGE value.
Page 841722 was expected to be the first page of a TEXT/IMAGE value.
   ** Execution Time: 0 hrs, 9 mins, 31 secs **

When I ran DBCC NEWALLOC(ALAN) the result included
TABLE: Buyer OBJID = 265820059
INDID=1 FIRST=19328 ROOT=19339 DPAGES=511 SORT=0
Data level: 1.  511 Data  Pages in 65 extents.
Indid   : 1.  7 Index Pages in 1 extents.
INDID=2 FIRST=818960 ROOT=818971 DPAGES=168 SORT=0
Msg 2525, Level 16, State 1
Table Corrupt: Object id wrong; tables: alloc page 841472  extent
id=841656
l page#=841656 objid in ext=1754489329 (name = Document) objid in
page=1754489329 (name = Document)objid in sysindexes=265820059 (name =
Buyer)
INDID=3 FIRST=819096 ROOT=839453 DPAGES=79 SORT=0
Indid   : 3.  137 Index Pages in 18 extents.
TOTAL # of extents = 84
***************************************************************
TABLE: Document OBJID = 1754489329
INDID=1 FIRST=31752 ROOT=31763 DPAGES=395 SORT=0
Data level: 1.  393 Data  Pages in 50 extents.
Indid   : 1.  4 Index Pages in 1 extents.
INDID=2 FIRST=35448 ROOT=35529 DPAGES=38 SORT=1
Indid   : 2.  42 Index Pages in 7 extents.
INDID=255 FIRST=656 ROOT=866008 DPAGES=0 SORT=0
Msg 2542, Level 16, State 1
Table Corrupt: Extent is linked in more than one chain.  Check the
following allocation page and extent: alloc pg#=841728 extent#=841728
status=194
TOTAL # of extents = 58
***************************************************************
and finally
Processed 299 entries in the Sysindexes for dbid 6.
Found 2 bad entries in the Sysindexes.

I noticed in Russell's reply to Mike he said
"However, apparently the crosslink occurs on your clustered index --
not good.  (If it was on a non-clustered index, I would suggest just
dropping the index and recreating it.)"

How did he know the crosslink was on his clustered index?  Is this the
case with my client?  What can I do?  (My client also used
Backup/Transfer to transfer the database to a backup server machine on
26 October and running the same task and DBCC NEWALLOC against that
database doesn't give any errors (although the 'orginal' database has
apparently been failing since October 6).  Can I trust these results
and try to restore from the backup server machine?)  Are these two
affected tables definitely corrupt or can I rebuild them somehow?

I would be very grateful if anyone could help.

Sent via Deja.com http://www.***.com/
Before you buy.



Tue, 23 Apr 2002 03:00:00 GMT
 
 [ 1 post ] 

 Relevant Pages 

1. Corrupt Data Error 605

2. Help error 605 with affected tables user and syslogs

3. Error 605 on the sysprocedures table of master

4. Error 605 on temp table

5. Error 605 on temporary table

6. PRODUCTION EMERGENCY - Help with 605/1117 errors

7. HELP.. Error 605 on syscolumns on MSSQL 6.5

8. Error 605 - SQL Server 6.5 - Please Help me

9. Error code 605 help.

10. Need more help on error 605.

11. Error 605 - SQL Server 6.5 - Please Help

12. Help: sql 6.5 : Error : 605, Severity: 21, State: 1


 
Powered by phpBB® Forum Software