Kalmeradmin
asked on
DBCC Checkdb Error
A third party backup software that we are using to backup a clients MS SQL server returns the following error:
An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services. Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
SQL:declare @dbName nvarchar(255) set @dbName = ? exec (N'dbcc checkdb (['+ @dbName+ N'],noindex) with no_infomsgs') (I03DEC2010)
The "tempdb out of space" issue has been ruled out. It sounds like the customer's database has an issue. My question is, what steps should be taken to diagnose or fix this problem?
Thanks
An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services. Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
SQL:declare @dbName nvarchar(255) set @dbName = ? exec (N'dbcc checkdb (['+ @dbName+ N'],noindex) with no_infomsgs') (I03DEC2010)
The "tempdb out of space" issue has been ruled out. It sounds like the customer's database has an issue. My question is, what steps should be taken to diagnose or fix this problem?
Thanks
Kaffiend
How reliable is the third party backup software? Did you try to do a manual backup using SQL Server's built-in tools to confirm that it is not the fault of the backup software?
The other question -- is it just running a plain DBCC CHECKDB or is it trying to run a repair option?
If it is trying to run a repair, the database needs to be in single user mode. If you have replication or a service that is constantly connected, it can't put the DB in single user and then connect to it.
If it is trying to run a repair, the database needs to be in single user mode. If you have replication or a service that is constantly connected, it can't put the DB in single user and then connect to it.
ASKER
The third party software has been very reliable in the past. It's just running a plain DBCC CHECKDB, not a repair. It is currently set to stop if the DBCC fails.
Can you see any errors in the SQL Log or or SQL Agent Logs?
ASKER
I found this error:
DBCC encountered a page with an LSN greater than the current end of log LSN (94:0:1) for its internal database snapshot. Could not read page (1246:96732842), database 'I03DEC2010' (database ID 19), LSN = (293339922:6293742:257), type = 21, isInSparseFile = 1. Please re-run this DBCC command.
It was immediately followed by this:
DBCC CHECKDB (I03DEC2010, noindex) WITH no_infomsgs executed by (domain name)\Administrator terminated abnormally due to error state 1. Elapsed time: 0 hours 0 minutes 6 seconds.
DBCC encountered a page with an LSN greater than the current end of log LSN (94:0:1) for its internal database snapshot. Could not read page (1246:96732842), database 'I03DEC2010' (database ID 19), LSN = (293339922:6293742:257), type = 21, isInSparseFile = 1. Please re-run this DBCC command.
It was immediately followed by this:
DBCC CHECKDB (I03DEC2010, noindex) WITH no_infomsgs executed by (domain name)\Administrator terminated abnormally due to error state 1. Elapsed time: 0 hours 0 minutes 6 seconds.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for all the help here. Our customer determined that the corrupt database was not needed and we simply excluded it from our backup.
ASKER
This was the information that I needed.