September 9, 2004 at 10:23 am
Good Day,
I am receiving the following message concerning MSDB on a clustered production system:
I/O error (bad page ID) detected during read at offset 0x00000004e10000 in file 's:\MSSQL$VSQL01\data\msdbdata.mdf'..
When I run DBCC CHECKDB MSDB, I recieve the following:
CHECKDB found 0 allocation errors and 22 consistency errors in database 'msdb'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (msdb ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
I am considering running DBCC CHECKDB with REPAIR FAST or REPAIR_ALLOW_DATA_LOSS options.
Has anyone else ever encountered this error message? Would the attempted repair adversely affect users in general? Any other suggestions?
Thanks!
Carpe diem!
September 13, 2004 at 8:00 am
This was removed by the editor as SPAM
September 13, 2004 at 9:19 am
MSDB only stores information regarding your jobs, DTS packages and maintenance plans. None of your users should be affected directly with you running a checkdb against msdb.
September 14, 2004 at 2:17 am
I had problems on another user db where by I had to run checkdb, repair fast. I found that I had to run the command several times to correct the problems. Each time it runs it corrects some things but still needs another pass.
You might find here that you'd be best to simply recover from a backup. In which case you'd need to stop sql agent, and possibly put the db into single user mode (not certain on this point).
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply