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 |
|
Sunge
Starting Member
3 Posts |
 Posted - 2011-07-13 : 03:09:18
|
We have a machine which was maliciously formatted. I managed to recover the data using GetDataBack software and there was no backups. After reinstalling the databases and ACCPAC on a different machine, one company is able to do almost all the transaction while the other is giving errors of data inconsistency as follows:
Description: Schedule. Database error (operation=GET-GE, error=824). [Microsoft][SQL Server Native Client 10.0][SQL Server]SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:5980; actual 0:0). It occurred during a read of page (1:5980) in database ID 8 at offset 0x00000002eb8000 in file Please refer this error to your database administrator or see your database documentation for further assistance.
Source: 06:28:33
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2011-07-13 : 03:51:42
|
Run the following, post the full and complete output.
DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
--
Gail Shaw
SQL Server MVP |
 |
|
|
Sunge
Starting Member
3 Posts |
Posted - 2011-07-13 : 05:09:11
|
Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:8088) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 8 pages from (1:8088) to (1:16175). See other errors for cause.
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 'YDFDAT'.
Msg 824, Level 24, State 2, Line 1
SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:5977; actual 0:0). It occurred during a read of page (1:5977) in database ID 15 at offset 0x00000002eb2000 in file 'C:\Users\User\Documents\MSSQL\Data\YDFDAT_Data.MDF:MSSQL_DBCC15'. 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.
|
|
|
|
Sunge
Starting Member
3 Posts |
Posted - 2011-07-13 : 05:10:24
|
Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:8088) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 8 pages from (1:8088) to (1:16175). See other errors for cause.
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 'YDFDAT'.
Msg 824, Level 24, State 2, Line 1
SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:5977; actual 0:0). It occurred during a read of page (1:5977) in database ID 15 at offset 0x00000002eb2000 in file 'C:\Users\User\Documents\MSSQL\Data\YDFDAT_Data.MDF:MSSQL_DBCC15'. 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.
|
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2011-07-13 : 16:23:34
|
It's toast. Unrepairable.
Script what objects you can, some will fail. Export what data you can, some will fail. Recreate the DB. Since it's a vendor app's DB, the app will likely break as well, I suggest you get hold of their support people to help recreate the DB.
--
Gail Shaw
SQL Server MVP |
|
|
|
|
|
|
|
|
SQL 2005 error 824