Dumb: I posted this in another group a week ago, then wondered why I got no
reply. Turns out that group doesn't exist anymore--at least on msnews,
other newsservers stil carry it, but the activity level is near-zero
-----


I'm trying to recover as much as possible from a database that has become
the victim of data corruption on disk.

The database uses simple recovery model. There are daily full backups,
archived to 7 days back, but the problem was detected too late, so the
errors also exist in all available backups.

I restored the latest backup on another machine, set it to single user, and
tried to run DBCC CHECKDB with the REPAIR_FAST option.

This results in an error message:

Msg 5244, Level 16, State 1, Server WS-LUC-2, Line 1
Repair statement not processed. One or more files in the database are
read-only and must be made writeable in order to run repair.

None of the database files is read-only though, there must be another
reason why writing fails.

Has anyone ever encountered this?


PS: the database was created on SQL Server 2005 Express Edition, I've tried
the repair on 2005 EE as well as on a full 2005 server. The result remains
the same.

Hi Luc,
Could you please let me know what the newsgroup in which you put the same
post was? Is it a managed newsgroup? If your original post was not posted
at a Managed newsgroup, it could not be monitored by Microsoft Newsgroup
Support Team.

For your issue, I understand that you were trying to recover your database
from the latest database backup. When you ran DBCC CHECKDB with REPAIR_FAST
option, you encountered the error.
If I have misunderstood, please let me know.

After you restore the latest version of your database, I recommend that you
first trying detaching your database and then attaching the database with
single file, such as:
exec sp_detach_db 'database name'
Go
exec sp_attach_single_file_db @dbname='database name',@physname=N'your mdf
file path'
Go
After that, run DBCC CHECKDB with REPAIR_FAST to see if it can succeed.

Please note that REPAIR_FAST actually did not perform any repair actions.
If you want to repair the reported errors from DBCC CHECKDB, please specify
REPAIR_ALLOW_DATA_LOSS or REPAIR_REBUILD (minor repair).

If the same error occurs, I recommend that you try running DBCC CHECKTABLE
on each of your table to see if which tables could not be repaired. You may
check if you can replace the table by creating a new one. Also as a more
convenient way, you may consider exporting all of your data tables to
another database via Import/Export Data wizard from SQL Server Management
Studio and then run DBCC CHECKDB to see if there are any errors.

Hope this s. If you have any other questions or concerns, please feel
free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@microsoft.com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

On Tue, 01 Apr 2008 03:56:37 GMT, changliw@online.microsoft.com (Charles
Wang[MSFT]) wrote:

> Hi Luc,
> Could you please let me know what the newsgroup in which you put the same
> post was? Is it a managed newsgroup? If your original post was not posted
> at a Managed newsgroup, it could not be monitored by Microsoft Newsgroup
> Support Team.

My fault: it's not a managed newsgroup (microsoft.public.sqlserver.misc).

It must still have existed in the newsgroup list of my newsreader (Forté
Agent) from years ago.

Agent must have fallen back to another server when the group was deleted
from msnews.microsoft.com (I'm using two other servers in addition to
msnews to get access to non-MS newsgroups, but I also use them for
microsoft.public newsgroups because they keep old messages much longer,
which sometimes comes in handy if a question has been asked and answered
long ago).


> After you restore the latest version of your database, I recommend that you
> first trying detaching your database and then attaching the database with
> single file, such as:
> exec sp_detach_db 'database name'
> Go
> exec sp_attach_single_file_db @dbname='database name',@physname=N'your mdf
> file path'
> Go
> After that, run DBCC CHECKDB with REPAIR_FAST to see if it can succeed.

I get the same error.

To be sure I deleted the database, restored it again from the same backup,
detached it, and then ran these queries:

exec sp_attach_single_file_db @dbname='PLRest',
physname=N'F:\Temp2\PLRest.mdf'
alter database PLRest set SINGLE_USER
dbcc checkdb('PLRest',REPAIR_FAST)

The result is a single message:

Msg 5244, Level 16, State 1, Line 3
Repair statement not processed. One or more files in the database are
read-only and must be made writeable in order to run repair.


The "set SINGLE_USER" line is there only because DBCC CHECKDB insists on
it.



Being only the developer who wrote the application, I haven't seen the
machine where the database comes from, but the engineer who was sent there
to repair it on site and who brought back the copy of the backup file,
reports the same error from dbcc checkdb there.


Changing REPAIR_FAST to REPAIR_REBUILD doesn't either: same error.

Only without a REPAIR option, dbcc checkdb succeeds and reports about a
dozen errors.

Hi Luc,
Could you please post the DBCC CHECKDB error here for further research? Or
you may mail it to me (changliw_at_microsoft_dot_com).

Also I would like to know if you have tried my suggestion of
importing/exporting your data tables to another database? Does it ?

Note that regarding data corruption, it is always not an easy thing and
sometimes it is impossible to recover for some serious corruptions. We will
try our best to give you some suggestions, however if it does not at
last, you may consider contacting third party data recovery company to
repair your data.

If you have any other questions or concerns, please feel free to let me
know. Have a nice day!


Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =======
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@microsoft.com.
================================================== =======
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

On Wed, 02 Apr 2008 14:52:52 GMT, changliw@online.microsoft.com (Charles
Wang[MSFT]) wrote:

> Hi Luc,
> Could you please post the DBCC CHECKDB error here for further research? Or
> you may mail it to me (changliw_at_microsoft_dot_com).

See below.

> Also I would like to know if you have tried my suggestion of
> importing/exporting your data tables to another database? Does it ?

I had already had tried that, but exporting the full tables fails.

OTOH, I noticed that I can recover some (probably most) data from the
damaged tables by selecting part of the records through an index, trying to
guess what range is damaged and skipping over it.
Both damaged tables contain event logging records and are indexed on time,
so that isn't hard to do.


For the moment I'm waiting for someone to send me a copy of the actual .mdf
file itself instead of a backup (as I had originally asked for, but someone
decided it would be easier to send me a backup).

The application is still running, and as far as I can see from here, the
actual mdf file is in better condition than the backups (backup might have
stopped prematurely when it ran into the damaged section?)

Adding new records to the damaged tables still seems to work in the
original DB, but when I tried the same in the restored backup, it failed.
Selecting data fails in both cases (depending on the selection criteria).



> Note that regarding data corruption, it is always not an easy thing and
> sometimes it is impossible to recover for some serious corruptions. We will
> try our best to give you some suggestions, however if it does not at
> last, you may consider contacting third party data recovery company to
> repair your data.

The data are not that critical (in fact some of them are, there's a legal
requirement to archive them for 10 years, but backups on paper exist).


> If you have any other questions or concerns, please feel free to let me
> know. Have a nice day!

And to you too.




Result of checkdb follows.
It says "repair_allow_data_loss is the minimum repair level", but I tried
that as well and it gives the same error.


DBCC results for 'PlayersRJMM'.
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 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:13734) contains an incorrect page ID in its page
header. The PageId in the page header = (0:0).
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:13735) contains an incorrect page ID in its page
header. The PageId in the page header = (0:0).
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:13737) contains an incorrect page ID in its page
header. The PageId in the page header = (0:0).
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:13738) contains an incorrect page ID in its page
header. The PageId in the page header = (0:0).
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:13741) contains an incorrect page ID in its page
header. The PageId in the page header = (0:0).
Msg 8939, Level 16, State 5, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0
(type Unknown), page (1:13744). Test (m_headerVersion == HEADER_7_0)
failed. Values are 0 and 1.
Msg 8939, Level 16, State 6, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0
(type Unknown), page (1:13744). Test ((m_type >= DATA_PAGE && m_type <=
UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE && level == BASIC_HEADER))
failed. Values are 0 and 0.
Msg 8939, Level 16, State 7, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0
(type Unknown), page (1:13744). Test (m_freeData >= PAGEHEADSIZE &&
m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot)) failed. Values
are 0 and 8192.
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:13746) contains an incorrect page ID in its page
header. The PageId in the page header = (0:0).
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:13747) contains an incorrect page ID in its page
header. The PageId in the page header = (0:0).
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:13748) contains an incorrect page ID in its page
header. The PageId in the page header = (0:0).
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:13749) contains an incorrect page ID in its page
header. The PageId in the page header = (0:0).
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:13750) contains an incorrect page ID in its page
header. The PageId in the page header = (0:0).
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:13751) contains an incorrect page ID in its page
header. The PageId in the page header = (0:0).
Msg 8939, Level 16, State 5, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0
(type Unknown), page (1:13752). Test (m_headerVersion == HEADER_7_0)
failed. Values are 0 and 1.
Msg 8939, Level 16, State 6, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0
(type Unknown), page (1:13752). Test ((m_type >= DATA_PAGE && m_type <=
UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE && level == BASIC_HEADER))
failed. Values are 0 and 0.
Msg 8939, Level 16, State 7, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0
(type Unknown), page (1:13752). Test (m_freeData >= PAGEHEADSIZE &&
m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot)) failed. Values
are 0 and 8192.
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:13753) contains an incorrect page ID in its page
header. The PageId in the page header = (0:0).
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:13754) contains an incorrect page ID in its page
header. The PageId in the page header = (0:0).
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:13755) contains an incorrect page ID in its page
header. The PageId in the page header = (0:0).
CHECKDB found 0 allocation errors and 20 consistency errors not associated
with any single object.
DBCC results for 'sys.sysrowsetcolumns'.
There are 632 rows in 6 pages for object "sys.sysrowsetcolumns".
DBCC results for 'sys.sysrowsets'.
There are 104 rows in 1 pages for object "sys.sysrowsets".
DBCC results for 'sysallocunits'.
There are 120 rows in 2 pages for object "sysallocunits".
DBCC results for 'sys.sysfiles1'.
There are 2 rows in 1 pages for object "sys.sysfiles1".
DBCC results for 'sys.syshobtcolumns'.
There are 632 rows in 9 pages for object "sys.syshobtcolumns".
DBCC results for 'sys.syshobts'.
There are 104 rows in 1 pages for object "sys.syshobts".
DBCC results for 'sys.sysftinds'.
There are 0 rows in 0 pages for object "sys.sysftinds".
DBCC results for 'sys.sysserefs'.
There are 120 rows in 1 pages for object "sys.sysserefs".
DBCC results for 'sys.sysowners'.
There are 16 rows in 1 pages for object "sys.sysowners".
DBCC results for 'sys.sysprivs'.
There are 122 rows in 1 pages for object "sys.sysprivs".
DBCC results for 'sys.sysschobjs'.
There are 96 rows in 2 pages for object "sys.sysschobjs".
DBCC results for 'sys.syscolpars'.
There are 479 rows in 8 pages for object "sys.syscolpars".
DBCC results for 'sys.sysnsobjs'.
There are 1 rows in 1 pages for object "sys.sysnsobjs".
DBCC results for 'sys.syscerts'.
There are 0 rows in 0 pages for object "sys.syscerts".
DBCC results for 'sys.sysxprops'.
There are 0 rows in 0 pages for object "sys.sysxprops".
DBCC results for 'sys.sysscalartypes'.
There are 27 rows in 1 pages for object "sys.sysscalartypes".
DBCC results for 'sys.systypedsubobjs'.
There are 0 rows in 0 pages for object "sys.systypedsubobjs".
DBCC results for 'sys.sysidxstats'.
There are 179 rows in 4 pages for object "sys.sysidxstats".
DBCC results for 'sys.sysiscols'.
There are 308 rows in 3 pages for object "sys.sysiscols".
DBCC results for 'sys.sysbinobjs'.
There are 23 rows in 1 pages for object "sys.sysbinobjs".
DBCC results for 'sys.sysobjvalues'.
There are 207 rows in 47 pages for object "sys.sysobjvalues".
DBCC results for 'sys.sysclsobjs'.
There are 15 rows in 1 pages for object "sys.sysclsobjs".
DBCC results for 'sys.sysrowsetrefs'.
There are 0 rows in 0 pages for object "sys.sysrowsetrefs".
DBCC results for 'sys.sysremsvcbinds'.
There are 0 rows in 0 pages for object "sys.sysremsvcbinds".
DBCC results for 'sys.sysxmitqueue'.
There are 0 rows in 0 pages for object "sys.sysxmitqueue".
DBCC results for 'sys.sysrts'.
There are 1 rows in 1 pages for object "sys.sysrts".
DBCC results for 'sys.sysconvgroup'.
There are 0 rows in 0 pages for object "sys.sysconvgroup".
DBCC results for 'sys.sysdesend'.
There are 0 rows in 0 pages for object "sys.sysdesend".
DBCC results for 'sys.sysdercv'.
There are 0 rows in 0 pages for object "sys.sysdercv".
DBCC results for 'sys.syssingleobjrefs'.
There are 134 rows in 1 pages for object "sys.syssingleobjrefs".
DBCC results for 'sys.sysmultiobjrefs'.
There are 110 rows in 1 pages for object "sys.sysmultiobjrefs".
DBCC results for 'sys.sysdbfiles'.
There are 2 rows in 1 pages for object "sys.sysdbfiles".
DBCC results for 'sys.sysguidrefs'.
There are 0 rows in 0 pages for object "sys.sysguidrefs".
DBCC results for 'sys.sysqnames'.
There are 91 rows in 1 pages for object "sys.sysqnames".
DBCC results for 'sys.sysxmlcomponent'.
There are 93 rows in 1 pages for object "sys.sysxmlcomponent".
DBCC results for 'sys.sysxmlfacet'.
There are 97 rows in 1 pages for object "sys.sysxmlfacet".
DBCC results for 'sys.sysxmlplacement'.
There are 17 rows in 1 pages for object "sys.sysxmlplacement".
DBCC results for 'sys.sysobjkeycrypts'.
There are 0 rows in 0 pages for object "sys.sysobjkeycrypts".
DBCC results for 'sys.sysasymkeys'.
There are 0 rows in 0 pages for object "sys.sysasymkeys".
DBCC results for 'sys.syssqlguides'.
There are 0 rows in 0 pages for object "sys.syssqlguides".
DBCC results for 'sys.sysbinsubobjs'.
There are 0 rows in 0 pages for object "sys.sysbinsubobjs".
DBCC results for 'ZipCodes'.
There are 42134 rows in 208 pages for object "ZipCodes".
DBCC results for 'Photos'.
There are 860 rows in 5 pages for object "Photos".
DBCC results for 'IDCards'.
There are 817 rows in 7 pages for object "IDCards".
DBCC results for 'A2SCards'.
There are 501 rows in 4 pages for object "A2SCards".
DBCC results for 'A2SHistory'.
There are 18 rows in 1 pages for object "A2SHistory".
DBCC results for 'Presence'.
There are 14692 rows in 1260 pages for object "Presence".
DBCC results for 'PhotoPresence'.
Msg 8928, Level 16, State 1, Line 1
Object ID 277576027, index ID 1, partition ID 72057594039435264, alloc unit
ID 71794310283722752 (type LOB data): Page (1:13734) could not be
processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 277576027, index ID 1, partition ID 72057594039435264, alloc unit
ID 71794310283722752 (type LOB data): Page (1:13735) could not be
processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 277576027, index ID 1, partition ID 72057594039435264, alloc unit
ID 71794310283722752 (type LOB data): Page (1:13744) could not be
processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 277576027, index ID 1, partition ID 72057594039435264, alloc unit
ID 71794310283722752 (type LOB data): Page (1:13746) could not be
processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 277576027, index ID 1, partition ID 72057594039435264, alloc unit
ID 71794310283722752 (type LOB data): Page (1:13747) could not be
processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 277576027, index ID 1, partition ID 72057594039435264, alloc unit
ID 71794310283722752 (type LOB data): Page (1:13748) could not be
processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 277576027, index ID 1, partition ID 72057594039435264, alloc unit
ID 71794310283722752 (type LOB data): Page (1:13749) could not be
processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 277576027, index ID 1, partition ID 72057594039435264, alloc unit
ID 71794310283722752 (type LOB data): Page (1:13750) could not be
processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 277576027, index ID 1, partition ID 72057594039435264, alloc unit
ID 71794310283722752 (type LOB data): Page (1:13751) could not be
processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 277576027, index ID 1, partition ID 72057594039435264, alloc unit
ID 71794310283722752 (type LOB data): Page (1:13752) could not be
processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 277576027, index ID 1, partition ID 72057594039435264, alloc unit
ID 71794310283722752 (type LOB data): Page (1:13753) could not be
processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 277576027, index ID 1, partition ID 72057594039435264, alloc unit
ID 71794310283722752 (type LOB data): Page (1:13754) could not be
processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 277576027, index ID 1, partition ID 72057594039435264, alloc unit
ID 71794310283722752 (type LOB data): Page (1:13755) could not be
processed. See other errors for details.
There are 14685 rows in 105 pages for object "PhotoPresence".
CHECKDB found 0 allocation errors and 13 consistency errors in table
'PhotoPresence' (object ID 277576027).
DBCC results for 'EPISLog'.
Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13577), slot 13, text ID 31002918912 does not
match its reference from page (1:56), slot 3.
Msg 8974, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13577), slot 13, text ID 31002918912 is
pointed to by page (1:56), slot 3 and by page (1:11416), slot 37.
Msg 8961, Level 16, State 3, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13577), slot 14, text ID 31002984448 does not
match its reference from page (1:56), slot 3.
Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13577), slot 14, text ID 31002984448 does not
match its reference from page (1:56), slot 3.
Msg 8974, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13577), slot 14, text ID 31002984448 is
pointed to by page (1:13577), slot 15 and by page (1:56), slot 3.
Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13624), slot 10, text ID 26153123840 does not
match its reference from page (1:56), slot 1.
Msg 8974, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13624), slot 10, text ID 26153123840 is
pointed to by page (1:56), slot 1 and by page (1:56), slot 53.
Msg 8961, Level 16, State 3, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13624), slot 11, text ID 26280329216 does not
match its reference from page (1:56), slot 4.
Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13624), slot 11, text ID 26280329216 does not
match its reference from page (1:56), slot 4.
Msg 8974, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13624), slot 11, text ID 26280329216 is
pointed to by page (1:56), slot 4 and by page (1:13624), slot 12.
Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13624), slot 12, text ID 26280329216 does not
match its reference from page (1:56), slot 4.
Msg 8974, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13624), slot 12, text ID 26280329216 is
pointed to by page (1:56), slot 61 and by page (1:56), slot 4.
Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13624), slot 13, text ID 31065440256 does not
match its reference from page (1:56), slot 7.
Msg 8974, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13624), slot 13, text ID 31065440256 is
pointed to by page (1:56), slot 7 and by page (1:11416), slot 44.
Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13624), slot 14, text ID 31262507008 does not
match its reference from page (1:56), slot 7.
Msg 8974, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13624), slot 14, text ID 31262507008 is
pointed to by page (1:11417), slot 15 and by page (1:56), slot 7.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13659), slot 13, text ID 25953894400 is
referenced by page (1:56), slot 9, but was not seen in the scan.
Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13660), slot 7, text ID 26151878656 does not
match its reference from page (1:56), slot 9.
Msg 8974, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13660), slot 7, text ID 26151878656 is pointed
to by page (1:56), slot 50 and by page (1:56), slot 9.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594039238656, alloc unit
ID 71800601762136064 (type LOB data): Page (1:13737) could not be
processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594039238656, alloc unit
ID 71800601762136064 (type LOB data): Page (1:13738) could not be
processed. See other errors for details.
Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13739), slot 0, text ID 25952976896 is not
referenced.
Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 373576369, index ID 1, partition ID
72057594039238656, alloc unit ID 71800601762136064 (type LOB data). The
off-row data node at page (1:13740), slot 0, text ID 25953042432 is not
referenced.
Msg 8928, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594039238656, alloc unit
ID 71800601762136064 (type LOB data): Page (1:13741) could not be
processed. See other errors for details.
Msg 8929, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594039238656, alloc unit
ID 72057594043236352 (type In-row data): Errors found in off-row data with
ID 25952518144 owned by data record identified by RID = (1:56:1)
Msg 8929, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594039238656, alloc unit
ID 72057594043236352 (type In-row data): Errors found in off-row data with
ID 25952780288 owned by data record identified by RID = (1:56:3)
Msg 8929, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594039238656, alloc unit
ID 72057594043236352 (type In-row data): Errors found in off-row data with
ID 25952976896 owned by data record identified by RID = (1:56:4)
Msg 8929, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594039238656, alloc unit
ID 72057594043236352 (type In-row data): Errors found in off-row data with
ID 25953501184 owned by data record identified by RID = (1:56:7)
Msg 8929, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594039238656, alloc unit
ID 72057594043236352 (type In-row data): Errors found in off-row data with
ID 25953894400 owned by data record identified by RID = (1:56:9)
Msg 8929, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594039238656, alloc unit
ID 72057594043236352 (type In-row data): Errors found in off-row data with
ID 26151878656 owned by data record identified by RID = (1:56:50)
Msg 8929, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594039238656, alloc unit
ID 72057594043236352 (type In-row data): Errors found in off-row data with
ID 26153123840 owned by data record identified by RID = (1:56:53)
Msg 8929, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594039238656, alloc unit
ID 72057594043236352 (type In-row data): Errors found in off-row data with
ID 26280329216 owned by data record identified by RID = (1:56:61)
Msg 8929, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594039238656, alloc unit
ID 72057594043236352 (type In-row data): Errors found in off-row data with
ID 31002918912 owned by data record identified by RID = (1:11416:37)
Msg 8929, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594039238656, alloc unit
ID 72057594043236352 (type In-row data): Errors found in off-row data with
ID 31065440256 owned by data record identified by RID = (1:11416:44)
Msg 8929, Level 16, State 1, Line 1
Object ID 373576369, index ID 1, partition ID 72057594039238656, alloc unit
ID 72057594043236352 (type In-row data): Errors found in off-row data with
ID 31262507008 owned by data record identified by RID = (1:11417:15)
There are 8770 rows in 135 pages for object "EPISLog".
CHECKDB found 0 allocation errors and 35 consistency errors in table
'EPISLog' (object ID 373576369).
DBCC results for 'CountryCodes'.
There are 239 rows in 1 pages for object "CountryCodes".
DBCC results for 'sys.queue_messages_565577053'.
There are 0 rows in 0 pages for object "sys.queue_messages_565577053".
DBCC results for 'sys.queue_messages_597577167'.
There are 0 rows in 0 pages for object "sys.queue_messages_597577167".
DBCC results for 'sys.queue_messages_629577281'.
There are 0 rows in 0 pages for object "sys.queue_messages_629577281".
DBCC results for 'PlayerNameBackupUpdate11'.
There are 14554 rows in 112 pages for object "PlayerNameBackupUpdate11".
DBCC results for 'CountryCodesISO2'.
There are 239 rows in 1 pages for object "CountryCodesISO2".
DBCC results for 'Players'.
There are 24059 rows in 418 pages for object "Players".
CHECKDB found 0 allocation errors and 68 consistency errors in database
'PlayersRJMM'.
repair_allow_data_loss is the minimum repair level for the errors found by
DBCC CHECKDB (PlayersRJMM).
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.

Hi Luc,
Thanks for your detailed response.

I notice that almost all the errors are regarding indexes on the two table
'EPISLog' and 'PhotoPresence'. Also the errors are for consistency not
allocation, so I recommend that you run "DBCC CHECKDB('GT',REPAIR_REBUILD)"
to repair indexes to see if it s. Please set your database to single
user mode with the following statement before you run it:
alter database <database name>
set single_user
Go

Please feel free to let me know if you have any other questions or oncerns.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =======
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@microsoft.com.
================================================== =======
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Luc,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =======
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@microsoft.com.
================================================== =======
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

On Wed, 09 Apr 2008 06:13:09 GMT, changliw@online.microsoft.com (Charles
Wang[MSFT]) wrote:

> Hi Luc,
> I am interested in this issue. Would you mind letting me know the result of
> the suggestions? If you need further assistance, feel free to let me know.
> I will be more than happy to be of assistance.

Sorry for the delay.

REPAIR_REBUILD returns the same error as the other repair options, saying
one of the database files is read only.

Before that, I had also tried to rebuild the indexes on a freshly restored
copy of the database through SQL Server Management Studio, select each
index of the affected tables in turn in the object browser tree,
right-click and select Rebuild: that succeeded without any error message,
which I find even stranger.



But I had to give up on the issue, because the customer still hasn't
provided me with a copy of the original MDF after I asked them for the
second time (in fact, I haven't heard from them again).

If I've been informed correctly, the behavior of the original database is
not fully the same as that of the restored backup, so I see no point in
trying to fix such a restored backup.