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 ««12

How to get the table name from a objectID? Expand / Collapse
Author
Message
Posted Monday, July 15, 2013 5:38 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, June 5, 2014 2:13 AM
Points: 25, Visits: 105
george sibbald (7/15/2013)
check also the minimum repair level checkdb reports.

If its a non-clustered index that turns out to be corrupted you may be able to just drop and recreate it.

Do you have a clean backup? almost always your best way out of a corruption.


Unfortunately no recent clean backup and ive been i cannot repair as its seriously corrupt

I dont know if its a non-clustered index or table that is corrupted. My strategy as i stated above was to create a new db and script all the objects that are 'good' and not the 'bad' ones. This is why im trying to ascertain the corrupt objects.
Post #1473596
Posted Monday, July 15, 2013 5:54 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: 2 days ago @ 10:21 AM
Points: 5,886, Visits: 13,042
the checkdb will give you the corrupted object names

---------------------------------------------------------------------

Post #1473602
Posted Monday, July 15, 2013 5:56 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, June 5, 2014 2:13 AM
Points: 25, Visits: 105
OK, here is the output from the CHECKDB (i cannot see the objectname?)

Msg 8946, Level 16, State 12, Line 2
Table error: Allocation page (1:28502112) has invalid PFS_PAGE page header values. Type is 0. Check type, object ID and page ID on the page.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -25000, index ID 0, page ID (1:28502112). The PageId in the page header = (0:0).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID -25000, index ID 0, page ID (1:28502112). The PageId in the page header = (0:0).
CHECKDB found 1 allocation errors and 1 consistency errors in table '(Object ID -25000)' (object ID -25000).
Msg 8921, Level 16, State 1, Line 1
CHECKTABLE terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID 10 pages from (1:28502112) to (1:28510199). See other errors for cause.
Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID 10 pages from (1:28510200) to (1:28518287). See other errors for cause.
Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID 10 pages from (1:28518288) to (1:28526375). See other errors for cause.
CHECKDB found 3 allocation errors and 0 consistency errors not associated with any single object.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 632864, index ID 17051, page ID (1:28510200). The PageId in the page header = (55702:800).
CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object ID 632864)' (object ID 632864).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 134676585, index ID 1, page ID (1:28518288). The PageId in the page header = (26880:131072).
CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object ID 134676585)' (object ID 134676585).
CHECKDB found 6 allocation errors and 1 consistency errors in database 'Bon_Live'.
Post #1473604
Posted Monday, July 15, 2013 6:30 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 @ 9:43 AM
Points: 40,404, Visits: 36,847
That is corrupt beyond the point of being able to identify objects. You've got fatal metadata corruption and allocation page corruption.
You're going to be very lucky if you get much at all out of that.

Go through the tables one by one (select name from sysobjects where xtype='U'), see if you can generate the script, see if you can select any of the data. I suspect a good number of objects will fail. It will take quite some time.

May be easier just to go back to the last good backup and accept that everything since is lost.



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 #1473618
Posted Monday, July 15, 2013 7:07 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, June 5, 2014 2:13 AM
Points: 25, Visits: 105
GilaMonster (7/15/2013)
That is corrupt beyond the point of being able to identify objects. You've got fatal metadata corruption and allocation page corruption.
You're going to be very lucky if you get much at all out of that.

Go through the tables one by one (select name from sysobjects where xtype='U'), see if you can generate the script, see if you can select any of the data. I suspect a good number of objects will fail. It will take quite some time.

May be easier just to go back to the last good backup and accept that everything since is lost.


Many Thanks Gila!

** NOW JUST NEED THE ADMINS TO MOVE THIS THREAD TO THE SQL 2000 FORUM **
Post #1473637
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse