March 29, 2018 at 7:38 am
Okay long story short, we were running the SQL Express Edition without knowing it, and it ran out of space. We've since upgraded to SQL Standard, but we keep getting these errors every time the system backs up our DB. Which is nightly.
DB202: Database Consistency Check Failure: Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
DB204: Error Reindexing Table <Table>: Database ID 6, Page (1:150151) is marked RestorePending, which may indicate disk corruption. To recover from this state, perform a restore.
DB204: Error Reindexing Table <Table>: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.
We get those errors on tables P - Z
Our Tech support has tried tried to fix it via:
DBCC CHECKDB repair_allow_data_loss
ALTER INDEX ALL ON <table> REBUILD
I've even detached the DB, made a copy, and ran it through some 3rd party software to no effect.
I feel it important to note that the "Database ID 6, Page (1:150151) is marked RestorePending" is also not actually marked as restore pending in the object explorer. But I could also be interpreting SQL wrong.
I'm not really an SQL guy, little to no experience. But I'm the only IT where I work, so it's on me to get this back in working order.
We're running SQL Server 2008 Standard Edition in Windows Server 2008 R2 Enterprise edition on a Dell r510 Dual Processor, 24GB RAM.
March 29, 2018 at 10:17 am
Have you considered copying that file elsewhere, and then performing a database restore? Push comes to shove, you'll have the copy to go back to....
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
March 29, 2018 at 10:31 am
Yeah sorry, I should have mentioned that we don't have a clean backup to restore from anymore (we keep a record of 14 days, unfortunately we didn't notice this until it was too late). Otherwise That would certainly be the first solution to try.
March 29, 2018 at 10:36 am
christian043.ellis - Thursday, March 29, 2018 10:31 AMYeah sorry, I should have mentioned that we don't have a clean backup to restore from anymore (we keep a record of 14 days, unfortunately we didn't notice this until it was too late). Otherwise That would certainly be the first solution to try.
Hopefully, that 14 days will change significantly ASAP! Most business data is retained for at least 7 years, unless it's in the category of most useless in a relatively short period of time. I'd definitely check system error logs to see if there might be a hardware problem with that drive. You might consider putting a new drive in, then copying the database file to it after detaching it, and then re-attaching it, and then using that same DBCC command again, to see if that makes a difference. Do keep a copy (or two or 3) of the original file.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply