June 18, 2010 at 6:33 am
Hi,
We've got a SQL 2000 instance which has been producing backup problems
'Error 823:I/O Error (bad page ID)'
We ran 'check db' and found that we have a problem on two of our tables on the msdb database:
There are 305 rows in 7 pages for object 'backupmediafamily'.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'backupmediafamily' (object ID 2069582411).
DBCC results for 'RTblVersions'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 2069582411, index ID 0: Page (1:1465) could not be processed. See other errors for details.
There are 2333 rows in 27 pages for object 'RTblVersions'.
There are 1 rows in 1 pages for object 'sysjobsteps'.
CHECKDB found 0 allocation errors and 2 consistency errors in database 'msdb'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (msdb ).
We feel we have an underlying problem with the disc and we're looking to move to another.
We tried running a check db repair but the tables are unavailable even to select, so it failed saying it was unablre to find the table.
The last good backup was over a week ago. Is it safe to restore the old version of the MSDB database to our present instance? any other suggestions gratefully accepted,
Thanks,
Andy
June 18, 2010 at 7:38 am
It is safe to restore an old backup, you'll lose backup and job history and any new jobs. It's generally not recommended to repair msdb anyway.
Fix the disks first though...
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
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply