Urgent Problem

[grimmy]

Hello,<br>I am currently experiencing problems with a database on my SQL server (6.15). When I click into the tables directory to bring the list of tables up I get the following error:-<br><br>Error 605 - Attempt the fetch logical page 4416 in database 'QReport' belongs to object '0', not to object sysindexes.<br><br>The tables then do not appear. I have tried a DBCC DBREINDEX and this has not solved the problem. The last backup of this database was over a month ago as well, so just restoring the backup is not an option. I KNOW....I NEED SACKING.<br><br>Please help me save my job!!!!!!!!!<br><br>Paul.<br>

 

[rgordley]

Looks like a program corruption problem rather than a database corruption problem. Make a new backup (separate from your month old backup) hide it away somewhere and reinstall SQL server.

 

[CountRaven]

Hi, hope the following helps:<br><br>Execute DBCC CHECKTABLE on the second object specified in the error message. To determine the full extent of the corruption, execute DBCC CHECKDB as soon as possible. Also check the error log for other errors, which often accompany a 605 error. <br><br>If the 605 error is not transient, the problem is severe and you must run DBCC CHECKDB with one of the repair clauses. If the error involves an index page, use the REPAIR_REBUILD clause. If the error involves a data page, it may be necessary to use the REPAIR_ALLOW_DATA_LOSS clause. In the likely event that you cannot allow the loss of data, you will need to restore from a known clean backup. If the problem persists, contact your primary support provider. Have the output from DBCC CHECKDB available for review.<br><br>The REPAIR_REBUILD clause rebuilds corrupt indexes and the REPAIR_ALLOW_DATA_LOSS clause fixes allocation problems. Sometimes, deleting pages is the only way to fix allocation problems. Typically, these pages contain data that was already deleted, but the pages may contain valid data. Therefore, deleting pages is a more risky option than using DBCC CHECKDB with a repair clause. Using DBCC CHECKDB with a repair clause fixes database corruption when a database backup is not available. <br><br>Cheers,<br>Chris (<A HREF="mailto:chris@elite-mail.co.uk">chris@elite-mail.co.uk</A>)