April 6, 2005 at 8:19 am
We received the 605 Error this morning...
DESCRIPTION: Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:528) in database 'CMSOPEN' belongs to object 'BLE_ACT_AUDIT', not to object 'GLT_JRNL'.
After running DBCC CHECKTABLE, this error was returned:
Server: Msg 8981, Level 16, State 1, Line 1
Table error: Object ID 510624862, index ID 1. The next pointer of (1:7002604) refers to page (1:528). Neither (1:528) nor its parent were encountered. Possible bad chain linkage.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 510624862, index ID 1. Page (1:7002605) is missing a reference from previous page (1:7002604). Possible chain linkage problem.
DBCC results for 'GLT_JRNL'.
There are 27377000 rows in 528568 pages for object 'GLT_JRNL'.
CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'GLT_JRNL' (object ID 510624862).
repair_rebuild is the minimum repair level for the errors found by DBCC CHECKTABLE (CMSOPEN.dbo.GLT_JRNL ).
Any suggestions as to what might be wrong or how to fix it? Thanks!
April 6, 2005 at 10:33 am
Read Books Online regarding DBCC CHECKTABLE. It has repair capabilities. I would attempt it from least risk to greatest, in other words, REPAIR_FAST first, if that doesn't work, then REPAIR_REBUILD, if that doesn't work, the REPAIR_ALLOW_DATA_LOSS. If that doesn't work, then you'll need to restore from backup. Depending on the database, you might be able to restore the database to a new name, then drop the offending table and copy it from the restored version. This will depend on data dependencies, foreign keys, etc, and may result in data loss as well. Know your data first!
Steve
April 6, 2005 at 11:54 am
I Agree with steve
April 7, 2005 at 8:50 am
Thanks! We ended up rebooting the cluster and it fixed itself. (It was a caching issue.)
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply