January 5, 2009 at 12:29 am
Msg 7985, Level 16, State 2, Line 1
System table pre-checks: Object ID 4. Could not read and latch page (1:358) with latch type SH.
Check statement terminated due to unrepairable error.
Msg 5233, Level 16, State 98, Line 1
Table error: alloc unit ID 262144, page (1:358). The test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed.
The values are 12716297 and -4.
CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 1 consistency errors in database 'CBATH'.
January 5, 2009 at 12:42 am
Your only option to fix this is to restore a clean backup that was taken before the corruption. If the DB is in full recovery and there are tran log backups, make sure that you first backup the tail of the log so that you can restore without data loss.
That error is saying that one of the critical system tables is corrupt. CheckDB can't read it in order to find out what should be in the database and hence it can neither scan nor repair. There is no way around this error.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 5, 2009 at 1:21 am
Hi Gail,
Thanks a lot for your reply.
infact i dont have a backup of the database.
i was having only one copy of the database that is giving me this error.
is there any way i can recover the data
Thanks
Shahnawaz
January 5, 2009 at 1:32 am
shahnawaz (1/5/2009)
infact i dont have a backup of the database.i was having only one copy of the database that is giving me this error.
Why no backup?
is there any way i can recover the data
It's unlikely you will get everything back. Without a backup and with an irreparable error, the only remaining option is to generate scripts of all the objects (some will probably fail because of the corruption) and then bcp out all the data that you can (some tables will probably fail because of the error)
Create a new database, apply the scripts, reload the data.
You may want to also check the IO subsystem on that server. Corruption is typically an IO problem.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 5, 2009 at 2:43 am
Ok i will see how much data i can recover with this.
Thanks a lot
Shahnawaz
February 5, 2009 at 12:01 pm
PHEW...
System table is gone...
export as much as possible
WTF --> if you have a DB which is important ..dont be lazy to take backup .....
Atleast once a Week for sake
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply