|
|
|
SSC Eights!
 
Group: General Forum Members
Last Login: Tuesday, November 03, 2009 11:45 AM
Points: 915,
Visits: 1,255
|
|
Getting the error when querying sysobjects.
Looks like CHECKDB isn't like this database.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 1, page ID (1:15). The PageId in the page header = (0:0).
CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.
DBCC results for 'sysobjects'.
Msg 8928, Level 16, State 1, Line 1
Object ID 1, index ID 2: Page (1:15) could not be processed. See other errors for details.
object_id 1 is sysobjects! Ruh roh.
It is not enough to succeed. Others must fail.
SQLSlayer.com
|
|
|
|
|
SSC Eights!
Group: General Forum Members
Last Login: Tuesday, November 03, 2009 11:45 AM
Points: 915,
Visits: 1,255
|
|
see above, removed
It is not enough to succeed. Others must fail.
SQLSlayer.com
|
|
|
|
|
SSChampion
Group: General Forum Members
Last Login: Today @ 8:26 AM
Points: 14,526,
Visits: 10,414
|
|
Is that the full and complete output of checkDB? If not, please run the following ad post all of the output.
DBCC CHECKDB (< Database Name > ) WITH NO_INFOMSGS, ALL_ERRORMSGS
Gail Shaw
We walk in the dark places no others will enter
We stand on the bridge and none may pass
|
|
|
|
|
SSC Eights!
Group: General Forum Members
Last Login: Tuesday, November 03, 2009 11:45 AM
Points: 915,
Visits: 1,255
|
|
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 1, page ID (1:15). The PageId in the page header = (0:0).
CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.
Msg 8928, Level 16, State 1, Line 1
Object ID 1, index ID 2: Page (1:15) could not be processed. See other errors for details.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1, index ID 2. Index node page (0:0), slot 0 refers to child page (1:15) and previous child (0:0), but they were not encountered.
CHECKDB found 0 allocation errors and 2 consistency errors in table 'sysobjects' (object ID 1).
CHECKDB found 0 allocation errors and 3 consistency errors in database 'AllPolicies'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (AllPolicies ).
Although this database more than likely is garbage (can't seem to find anyone using it), I'm really curious to know what allowing data loss will do when it's sysobjects that appears to be the issue.
It is not enough to succeed. Others must fail.
SQLSlayer.com
|
|
|
|
|
SSChampion
Group: General Forum Members
Last Login: Today @ 8:26 AM
Points: 14,526,
Visits: 10,414
|
|
Hang on.... sysobjects? This is a SQL 2000 server?
I've requested Steve to move this to a SQL 2000 forum.
Generally, with CheckDB if there's a repair level specified then the error is repairable. This error reminds me of a question a while back. Will look for it.
Gail Shaw
We walk in the dark places no others will enter
We stand on the bridge and none may pass
|
|
|
|
|
SSC Eights!
Group: General Forum Members
Last Login: Tuesday, November 03, 2009 11:45 AM
Points: 915,
Visits: 1,255
|
|
Indeed. Sorry, I hate people who don't post in the right forums, but I hang out primarily in the 2005 forums and it gets alot more traffic. Wish they'd merge the boards and have a drop down to select version ...
But yeah, object_name(1) is sysobjects.
It is not enough to succeed. Others must fail.
SQLSlayer.com
|
|
|
|
|
SSChampion
Group: General Forum Members
Last Login: Today @ 8:26 AM
Points: 14,526,
Visits: 10,414
|
|
Adam Bean (6/19/2009)
Indeed. Sorry, I hate people who don't post in the right forums, but I hang out primarily in the 2005 forums and it gets alot more traffic.
The version is very important for data corruption issues as the repair options and method often differ greatly across the versions.
Gail Shaw
We walk in the dark places no others will enter
We stand on the bridge and none may pass
|
|
|
|
