Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

checkdb error on index ID 0 Expand / Collapse
Author
Message
Posted Monday, December 3, 2012 12:10 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, July 9, 2014 12:04 PM
Points: 30, Visits: 160
I need help on fixing checkdb error.

Here's the output of checkdb:

Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -1627389056, index ID 0, page ID (1:611861). The PageId in the page header = (14131:894586624).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:611862). The PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:611863). The PageId in the page header = (0:0).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 226099846, index ID 0: Page (1:611860) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 226099846, index ID 0, page (1:611860). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 226099846, index ID 0: Page (1:611861) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 226099846, index ID 0: Page (1:611862) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 226099846, index ID 0: Page (1:611863) could not be processed. See other errors for details.
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -1627389056)' (object ID -1627389056).
CHECKDB found 0 allocation errors and 2 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 5 consistency errors in table 'REQ_ITEM' (object ID 226099846).
CHECKDB found 0 allocation errors and 8 consistency errors in database 'PMM'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (PMM ).



It's running on SQL 2000 SP3.
Can I repair these errors with 'REPAIR_REBUILD'?

Thanks in advance,
David.
Post #1392105
Posted Monday, December 3, 2012 12:51 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 2:44 PM
Points: 42,443, Visits: 35,498
David Kang (12/3/2012)
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (PMM ).


Since repair allow data loss is the minimum repair level necessary, running checkDB with any lesser repair level will be a waste of time. Minimum repair level is exactly that.

You will lose data. Four pages of data from the table REQ_ITEM.

I assume there's no good backup available...



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1392119
Posted Monday, December 3, 2012 1:10 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, July 9, 2014 12:04 PM
Points: 30, Visits: 160
Gail! Thanks for quick response.

So, can I run page level restore for this? or restore the whole DB to temp location then extract the 'REQ_ITEM' table?

Thanks again,
David.
Post #1392123
Posted Monday, December 3, 2012 3:33 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 2:44 PM
Points: 42,443, Visits: 35,498
If you have a clean backup (one without any corruption) and an unbroken chain of log backups up to present, you can do a page restore. Or you can restore the full backup over the DB followed by all log backups to bring the DB back to current time with no corruption (take a tail-log backup first).

If the DB is not in full recovery or you don't have the necessary log backups, then you're looking at either losing data by restoring to the last good backup or by repairing. You can, in that case, try to repair then restore a copy of the DB elsewhere and sync in the missing data.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1392167
Posted Wednesday, December 5, 2012 12:15 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, February 7, 2013 5:14 AM
Points: 4, Visits: 2
Now a Days, when you search on the Google, many companies providing a data recovery services as well as recovery software. In such types of software one is recoveryfix for sql repair software, this company offering a free trial version software, with the help of this trial version you can see the preview of recoverable data.

Thanks
Post #1392810
Posted Wednesday, December 5, 2012 11:13 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 9:57 AM
Points: 7,080, Visits: 12,571
Since you're on SQL 2000 you do not have the option of doing page restores. As Gail outlined, you can restore from backup that do not include the corruption (including tail-log) to bring the database to current or look into bringing up a parallel copy of the database that does not include the corruption to recover the data manually, or do the repair allowing for data loss.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1393328
Posted Monday, December 10, 2012 1:15 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, July 9, 2014 12:04 PM
Points: 30, Visits: 160
Thanks both.

After I ran the checkDB with allow data loss, there were 100 rows are missing on REQ_ITEM table.
Since it was only affected single table, I was restore from last good backup and re-inserted missing data back to REQ_ITEM table.

Thanks again,
David.
Post #1394766
Posted Thursday, February 20, 2014 4:27 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, July 16, 2014 10:30 AM
Points: 238, Visits: 317
Hello Help will be appreciated,

When I try to run repair_allow_data_loss in the particular database it says no stored procedure,

This is the result,

There are 41752 rows in 1155 pages for object "cfgWFLogs".
CHECKDB found 0 allocation errors and 69 consistency errors in table 'cfgWFLogs' (object ID 1810105489).
DBCC results for 'cfgInvLoadConflictPolicies'.
There are 12 rows in 1 pages for object "cfgInvLoadConflictPolicies".
DBCC results for 'cfgLCObjectHistory'.
There are 845 rows in 11 pages for object "cfgLCObjectHistory".
DBCC results for 'Ticket_Closure_Code'.
There are 39 rows in 1 pages for object "Ticket_Closure_Code".
DBCC results for 'System_Images'.
There are 1 rows in 1 pages for object "System_Images".
DBCC results for 'cfgInvLoadConflicts'.
There are 61 rows in 2 pages for object "cfgInvLoadConflicts".
DBCC results for 'Status'.
There are 163 rows in 3 pages for object "Status".
DBCC results for 'cfgSecurityRoleViews'.
There are 363 rows in 3 pages for object "cfgSecurityRoleViews".
DBCC results for 'Ticket_Medium'.
There are 5 rows in 1 pages for object "Ticket_Medium".
DBCC results for 'cfgLCEmails'.
There are 79 rows in 3 pages for object "cfgLCEmails".
DBCC results for 'cfgInvLoadConflictMembers'.
There are 61 rows in 1 pages for object "cfgInvLoadConflictMembers".
DBCC results for 'sys.ifts_comp_fragment_1675153013_779'.
There are 731 rows in 4 pages for object "sys.ifts_comp_fragment_1675153013_779".
DBCC results for 'Ticket_Priority'.
There are 16 rows in 1 pages for object "Ticket_Priority".
DBCC results for 'Brands'.
There are 668 rows in 8 pages for object "Brands".
DBCC results for 'sys.queue_messages_1977058079'.
There are 0 rows in 0 pages for object "sys.queue_messages_1977058079".
DBCC results for 'cfgSPID'.
There are 0 rows in 1 pages for object "cfgSPID".
DBCC results for 'cfgCustDepends'.
There are 85 rows in 1 pages for object "cfgCustDepends".
DBCC results for 'sys.queue_messages_2009058193'.
There are 0 rows in 0 pages for object "sys.queue_messages_2009058193".
DBCC results for 'SLA'.
There are 4 rows in 1 pages for object "SLA".
DBCC results for 'sys.queue_messages_2041058307'.
There are 0 rows in 0 pages for object "sys.queue_messages_2041058307".
DBCC results for 'Person_Logins'.
There are 914 rows in 8 pages for object "Person_Logins".
DBCC results for 'sys.filestream_tombstone_2073058421'.
There are 0 rows in 0 pages for object "sys.filestream_tombstone_2073058421".
DBCC results for 'PO'.
There are 67 rows in 8 pages for object "PO".
DBCC results for 'HTML_Preview'.
There are 23 rows in 1 pages for object "HTML_Preview".
DBCC results for 'sys.syscommittab'.
There are 0 rows in 0 pages for object "sys.syscommittab".
DBCC results for 'Work_Calendar_Items'.
There are 7 rows in 1 pages for object "Work_Calendar_Items".
DBCC results for 'Solution_Ratings'.
There are 116 rows in 2 pages for object "Solution_Ratings".
DBCC results for 'sys.ifts_comp_fragment_510624862_769'.
There are 683 rows in 4 pages for object "sys.ifts_comp_fragment_510624862_769".
DBCC results for 'Email_Types'.
There are 2 rows in 1 pages for object "Email_Types".
DBCC results for 'sys.ifts_comp_fragment_510624862_770'.
There are 19 rows in 1 pages for object "sys.ifts_comp_fragment_510624862_770".
DBCC results for 'cfgMCJobOptions'.
There are 9 rows in 1 pages for object "cfgMCJobOptions".
DBCC results for 'Work_Calendars'.
There are 3 rows in 1 pages for object "Work_Calendars".
CHECKDB found 0 allocation errors and 1464 consistency errors in database 'AlloyNav'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (AlloyNav).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Post #1543767
Posted Friday, February 21, 2014 12:10 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 2:44 PM
Points: 42,443, Visits: 35,498
Please post new questions in a new thread. Thank you.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1543846
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse