Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
wshepherd
Starting Member
1 Post |
 Posted - 2007-10-30 : 22:47:14
|
| Having a problem with my backup database. Tonight I got this error:Msg 8921, Level 16, State 1, Line 3Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.Msg 824, Level 24, State 2, Line 3SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x55555555; actual signature: 0x55555545). It occurred during a read of page (1:934) in database ID 12 at offset 0x0000000074c000 in file 'E:\Somefolder\Somedatabase.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.Tried to restore from my local .bak file and it was giving me the same error and since I cant get my database back online I cant run the restore from tape. I did some online research and found this command:EXEC sp_resetstatus 'BEDB';ALTER DATABASE BEDB SET EMERGENCYDBCC checkdb('BEDB')ALTER DATABASE BEDB SET SINGLE_USER WITH ROLLBACK IMMEDIATEDBCC CheckDB ('BEDB', REPAIR_ALLOW_DATA_LOSS)ALTER DATABASE BEDB SET MULTI_USERDidnt correct the problem and produced the same error above. This has happened once before and I rebuit the entire backup server. That seems to not "fix" the problem because it has happened again. Does anyone have a suggestion. Keep in mind that the storage for the database is on iSCSI if that means anything but I have 11 other databases (including a BES Database) that never have any issues. OS: Windows 2003 Server Standard Edition R2 SP2SQL: SQL 2005 Enterprise Edition SP2 |
|
|
Kristen
Test
22859 Posts |
Posted - 2007-11-01 : 08:13:09
|
Suggest running:DBCC CHECKDB('MyDatabase') WITH NO_INFOMSGSon all databases. Schedule that test so that you become aware of any database corruption as soon after it occurs as possible to alert you before it has propagated to all your backup files  Check Event logs for Hardware problems. Database corruption is usually caused by failing hardware, and obviously a good idea to fix the hardware before proceeding. Maybe a disk in a RAID failed and the controller failed to complete the disk write (that would cause a Torn page error); a power cut could probably do it too.Are you backing up the database directly with Backup Exec? if so my recommendation would be to change that practice to backup to disk file first, and then have Backup Exec push that file to tape. It is not infrequent for people using 3rd party backup programs to post messages here saying they have got stuck for one reason or another "Possibly tempdb out of space or a system table is inconsistent."Presumably there is plenty of disk space available to TEMPDB?Kristen |
 |
|
|
|
|
|
Problem with Backup Exec 11d Database