dbcc checkdb error; object id 0

290 pts.
SQL Server 2005
SQL Server database

We have been ask by one of our customer to restore a database from SQL Server 2000 and SQL Server 2005. The restore completed however when we run a integrity check on the database errors occurred.

We than ran an integrity check with repair allow data loss option, as the customer is happy to loss same potential data, this repair 3 of the 4 error that were associated with a particular table where object id was 546512167, however 1 of error indicated it couldn't be repair. The following is the error.

DBCC results for 'sys'. Service Broker Msg 9675, State 1: Message Types analyzed: 14. Service Broker Msg 9676, State 1: Service Contracts analyzed: 6. Service Broker Msg 9667, State 1: Services analyzed: 3. Service Broker Msg 9668, State 1: Service Queues analyzed: 3. Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0. Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0. Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0. Msg 8939, Level 16, State 98, Line 1 Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -2314885530818510848 (type Unknown), page (57311:-538976289). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12584969 and -1.         Could not repair this error. CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object. DBCC results for 'sys.sysrowsetcolumns'.

Our main question is what does this error mean? It isn't even associated with an object as the object id is zero, so what is actually corrupted? Is this corruption likely be caused by the source database? And how can we address this?


Software/Hardware used:
SQL Server 2005

Answer Wiki

Thanks. We'll let you know when a new response is added.

I’d start by running DBCC on the source database and see if there’s anything wrong with the source database.

It sounds like the corrupt page isn’t associated with a table, so the engine doesn’t know what to do with it. If the source database has this same corruption you may want to call Microsoft and see what they say.

Discuss This Question:  

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: