August 8, 2007 at 12:14 am
Hi,
This is the error we are reciving while running dbcc checkdb on sql server 2005 user db
running on VMWARE.
Msg 8921, Level 16, State 1, Line 3
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of
space or a system table is inconsistent. Check previous errors.
Msg 8998, Level 16, State 2, Line 3
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database
ID 5 pages from (1:4836624) to (1:4844711). See other errors for cause.
Msg 8909, Level 16, State 1, Line 3
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 282134203858944 (type
Unknown), page ID (1:4836624) contains an incorrect page ID in its page header. The PageId
in the page header = (0:357).
CHECKDB found 2 allocation errors and 0 consistency errors not associated with any single
object.
CHECKDB found 2 allocation errors and 0 consistency errors in database 'dfp3'.
Msg 824, Level 24, State 2, Line 3
SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected
1:4836668; actual 0:357). It occurred during a read of page (1:4836668) in database ID 7 at
offset 0x00000939a78000 in file 'G:\MSSQL\Data\dfp3_Data.MDF:MSSQL_DBCC7'. 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.
Error started on aug 3. So, we restored the full backup from aug 2nd. We still see the same
error.
Tempdb and master db are ok.
We can see the tables but receive the error while trying to see the list of stored
procedures under programmability.
Is there anyway to fix it?
-N
August 8, 2007 at 1:44 am
Ouch - got some nice issues there.
Worrying that the backup is the same. Have you checked the event log for any disk errors? Might be that one of your disks is on it's way out.
You can do a checkdb with repair [allow loss] and see if that helps.
The allow loss might fix some issues but as the word says, you are not guaranteed on what you will have at the end.
Sorry, can't be of more help..
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply