DB Suspect (full error log attached)

Hi Gurus,
One of my DBs on a SQL box (SQL 2000 enterprise edtion SP3 on Win2k Advanced server) went suspect yesterday. Here is part of the error log. Would appreciate any help/suggestions.
2004-06-07 16:17:42.74 spid72 Getpage: bstat=0x9, sstat=0x10000, cache
2004-06-07 16:17:42.74 spid72 pageno is/should be:objid is/should be:
2004-06-07 16:17:42.74 spid72 (1:772511)/(1:772511)457768688/1269579561
2004-06-07 16:17:42.74 spid72 ... IAM indicates that page is allocated to this object
2004-06-07 16:17:42.74 spid72 Error: 605, Severity: 21, State: 1
2004-06-07 16:17:42.74 spid72 Attempt to fetch logical page (1:772511) in database 'S094000' belongs to object 't050_pre_arch', not to object 't050_campaign_candidate'..
2004-06-07 16:17:42.75 spid72 Error: 644, Severity: 21, State: 5
2004-06-07 16:17:42.75 spid72 Could not find the index entry for RID '16905830100' in index page (1:772510), index ID 9, database 'S094000'..
2004-06-07 16:17:42.75 spid72 Error: 3314, Severity: 21, State: 4
2004-06-07 16:17:42.75 spid72 Error while undoing logged operation in database 'S094000'. Error at log record ID (63154:9493:281)..
2004-06-07 16:17:42.80 spid72 Using 'dbghelp.dll' version '4.0.5'
*Dump thread - spid = 72, PSS = 0x70f85200, EC = 0x70f85528
(actual dump manually taken out here)
* ----
2004-06-07 16:17:44.77 spid72 Stack Signature for the dump is 0x03737F82
2004-06-07 16:17:44.77 spid72 SQL Server Assertion: File: <scanrid.cpp>, line=321
Failed Assertion = 'm_len != 0'.
2004-06-07 16:17:44.77 spid72 Error: 3624, Severity: 20, State: 1.
2004-06-07 16:17:45.05 spid72 Error: 3314, Severity: 21, State: 4
2004-06-07 16:17:45.05 spid72 Error while undoing logged operation in database 'S094000'. Error at log record ID (63154:9493:281)..
2004-06-07 16:17:45.05 spid72 Error: 9001, Severity: 21, State: 1
2004-06-07 16:17:45.05 spid72 The log for database 'S094000' is not available..
2004-06-07 16:17:45.36 spid72 Error: 3314, Severity: 21, State: 5
2004-06-07 16:17:45.36 spid72 Error while undoing logged operation in database 'S094000'. Error at log record ID (63154:9189:1)..
2004-06-07 16:17:46.34 spid15 Starting up database 'S094000'.
2004-06-07 16:17:47.56 spid15 Analysis of database 'S094000' (27) is 16% complete (approximately 2 more seconds)
2004-06-07 16:17:49.28 spid15 Analysis of database 'S094000' (27) is 100% complete (approximately 0 more seconds)
2004-06-07 16:17:49.30 spid15 Recovery of database 'S094000' (27) is 0% complete (approximately 28 more seconds) (Phase 2 of 3).
2004-06-07 16:18:09.83 spid15 Recovery of database 'S094000' (27) is 17% complete (approximately 98 more seconds) (Phase 2 of 3).
2004-06-07 16:18:13.50 spid15 Recovery of database 'S094000' (27) is 21% complete (approximately 88 more seconds) (Phase 2 of 3).
2004-06-07 16:18:18.67 spid15 Recovery of database 'S094000' (27) is 25% complete (approximately 83 more seconds) (Phase 2 of 3).
2004-06-07 16:18:23.36 spid15 Recovery of database 'S094000' (27) is 30% complete (approximately 77 more seconds) (Phase 2 of 3).
2004-06-07 16:18:28.38 spid15 Recovery of database 'S094000' (27) is 34% complete (approximately 72 more seconds) (Phase 2 of 3).
2004-06-07 16:18:34.88 spid15 Recovery of database 'S094000' (27) is 39% complete (approximately 69 more seconds) (Phase 2 of 3).
2004-06-07 16:18:39.81 spid15 Recovery of database 'S094000' (27) is 43% complete (approximately 64 more seconds) (Phase 2 of 3).
2004-06-07 16:18:44.13 spid15 Recovery of database 'S094000' (27) is 48% complete (approximately 58 more seconds) (Phase 2 of 3).
2004-06-07 16:18:48.85 spid15 Recovery of database 'S094000' (27) is 52% complete (approximately 53 more seconds) (Phase 2 of 3).
2004-06-07 16:18:54.44 spid15 Recovery of database 'S094000' (27) is 56% complete (approximately 48 more seconds) (Phase 2 of 3).
2004-06-07 16:19:00.66 spid15 Recovery of database 'S094000' (27) is 61% complete (approximately 44 more seconds) (Phase 2 of 3).
2004-06-07 16:19:06.38 spid15 Recovery of database 'S094000' (27) is 65% complete (approximately 39 more seconds) (Phase 2 of 3).
2004-06-07 16:19:12.85 spid15 Recovery of database 'S094000' (27) is 70% complete (approximately 35 more seconds) (Phase 2 of 3).
2004-06-07 16:19:19.55 spid15 Recovery of database 'S094000' (27) is 74% complete (approximately 30 more seconds) (Phase 2 of 3).
2004-06-07 16:19:27.02 spid15 Recovery of database 'S094000' (27) is 78% complete (approximately 26 more seconds) (Phase 2 of 3).
2004-06-07 16:19:34.21 spid15 Recovery of database 'S094000' (27) is 82% complete (approximately 21 more seconds) (Phase 2 of 3).
2004-06-07 16:19:43.72 spid15 Recovery of database 'S094000' (27) is 86% complete (approximately 17 more seconds) (Phase 2 of 3).
2004-06-07 16:19:52.25 spid15 Recovery of database 'S094000' (27) is 90% complete (approximately 12 more seconds) (Phase 2 of 3).
2004-06-07 16:20:02.85 spid15 Recovery of database 'S094000' (27) is 93% complete (approximately 7 more seconds) (Phase 2 of 3).
2004-06-07 16:20:14.79 spid15 Recovery of database 'S094000' (27) is 97% complete (approximately 3 more seconds) (Phase 2 of 3).
2004-06-07 16:20:23.47 spid15 Recovery of database 'S094000' (27) is 99% complete (approximately 0 more seconds) (Phase 2 of 3).
2004-06-07 16:20:23.47 spid15 266 transactions rolled forward in database 'S094000' (27).
2004-06-07 16:20:23.72 spid15 Recovery of database 'S094000' (27) is 99% complete (approximately 0 more seconds) (Phase 3 of 3).
2004-06-07 16:20:25.04 spid15 Recovery of database 'S094000' (27) is 100% complete (approximately 0 more seconds) (Phase 3 of 3).
2004-06-07 16:20:25.04 spid15 1 transactions rolled back in database 'S094000' (27).
2004-06-07 16:20:25.05 spid15 Recovery is checkpointing database 'S094000' (27)
2004-06-07 16:21:19.65 spid61 Getpage: bstat=0x9, sstat=0x10000, cache
2004-06-07 16:21:19.65 spid61 pageno is/should be:objid is/should be:
2004-06-07 16:21:19.65 spid61 (1:772511)/(1:772511)457768688/1269579561
2004-06-07 16:21:19.65 spid61 ... IAM indicates that page is allocated to this object
2004-06-07 16:21:19.65 spid61 Error: 605, Severity: 21, State: 1
2004-06-07 16:21:19.65 spid61 Attempt to fetch logical page (1:772511) in database 'S094000' belongs to object 't050_pre_arch', not to object 't050_campaign_candidate'..
2004-06-07 16:21:19.71 spid61 Error: 644, Severity: 21, State: 5
2004-06-07 16:21:19.71 spid61 Could not find the index entry for RID '16905830100' in index page (1:772510), index ID 9, database 'S094000'..
2004-06-07 16:21:19.71 spid61 Error: 3314, Severity: 21, State: 4
2004-06-07 16:21:19.71 spid61 Error while undoing logged operation in database 'S094000'. Error at log record ID (63154:10761:6)..
2004-06-07 16:21:19.71 spid61 Using 'dbghelp.dll' version '4.0.5'
*Dump thread - spid = 61, PSS = 0x43897200, EC = 0x43897528
Hi -
1. Important :: {Do you have previously clean backup? If yes, please restore
from the backup.}
OR
1. Execute DBCC CHECKDB to determine the extent of the damage, use the
REPAIR_REBUILD clause. If problem persists drop and re-create the index
Also Please provide output from DBCC CHECKDB.
2. Examine the error log for any errors prior to error 3414. It is important
to examine errors that occurred before the first occurrence of error 3414
because subsequent attempts to start the server might not give the detailed
error information you need to diagnose the problem. If you do not have
sufficient information to recover from the previous errors, you can recover
from known clean backups
I guess the problem is with the corrupt index Allocation Map or some thing
whirred in the sysobjects table.
Thanks
-Surajit
"G0" <anonymous@.discussions.microsoft.com> wrote in message
news:6AB317BC-5A70-43FC-BB47-33D5ED697253@.microsoft.com...
> Hi Gurus,
> One of my DBs on a SQL box (SQL 2000 enterprise edtion SP3 on Win2k
Advanced server) went suspect yesterday. Here is part of the error log.
Would appreciate any help/suggestions.
>
> 2004-06-07 16:17:42.74 spid72 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:17:42.74 spid72 pageno is/should be: objid is/should
be:
> 2004-06-07 16:17:42.74 spid72 (1:772511)/(1:772511)
457768688/1269579561
> 2004-06-07 16:17:42.74 spid72 ... IAM indicates that page is allocated
to this object
> 2004-06-07 16:17:42.74 spid72 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:17:42.74 spid72 Attempt to fetch logical page (1:772511)
in database 'S094000' belongs to object 't050_pre_arch', not to object
't050_campaign_candidate'..
> 2004-06-07 16:17:42.75 spid72 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:17:42.75 spid72 Could not find the index entry for RID
'16905830100' in index page (1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:17:42.75 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:42.75 spid72 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:9493:281)..
> 2004-06-07 16:17:42.80 spid72 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 72, PSS = 0x70f85200, EC = 0x70f85528
> (actual dump manually taken out here)
>
* ----
--
> 2004-06-07 16:17:44.77 spid72 Stack Signature for the dump is
0x03737F82
> 2004-06-07 16:17:44.77 spid72 SQL Server Assertion: File:
<scanrid.cpp>, line=321
> Failed Assertion = 'm_len != 0'.
> 2004-06-07 16:17:44.77 spid72 Error: 3624, Severity: 20, State: 1.
> 2004-06-07 16:17:45.05 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:45.05 spid72 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:9493:281)..
> 2004-06-07 16:17:45.05 spid72 Error: 9001, Severity: 21, State: 1
> 2004-06-07 16:17:45.05 spid72 The log for database 'S094000' is not
available..
> 2004-06-07 16:17:45.36 spid72 Error: 3314, Severity: 21, State: 5
> 2004-06-07 16:17:45.36 spid72 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:9189:1)..
> 2004-06-07 16:17:46.34 spid15 Starting up database 'S094000'.
> 2004-06-07 16:17:47.56 spid15 Analysis of database 'S094000' (27) is
16% complete (approximately 2 more seconds)
> 2004-06-07 16:17:49.28 spid15 Analysis of database 'S094000' (27) is
100% complete (approximately 0 more seconds)
> 2004-06-07 16:17:49.30 spid15 Recovery of database 'S094000' (27) is 0%
complete (approximately 28 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:09.83 spid15 Recovery of database 'S094000' (27) is
17% complete (approximately 98 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:13.50 spid15 Recovery of database 'S094000' (27) is
21% complete (approximately 88 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:18.67 spid15 Recovery of database 'S094000' (27) is
25% complete (approximately 83 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:23.36 spid15 Recovery of database 'S094000' (27) is
30% complete (approximately 77 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:28.38 spid15 Recovery of database 'S094000' (27) is
34% complete (approximately 72 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:34.88 spid15 Recovery of database 'S094000' (27) is
39% complete (approximately 69 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:39.81 spid15 Recovery of database 'S094000' (27) is
43% complete (approximately 64 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:44.13 spid15 Recovery of database 'S094000' (27) is
48% complete (approximately 58 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:48.85 spid15 Recovery of database 'S094000' (27) is
52% complete (approximately 53 more seconds) (Phase 2 of 3).
> 2004-06-07 16:18:54.44 spid15 Recovery of database 'S094000' (27) is
56% complete (approximately 48 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:00.66 spid15 Recovery of database 'S094000' (27) is
61% complete (approximately 44 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:06.38 spid15 Recovery of database 'S094000' (27) is
65% complete (approximately 39 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:12.85 spid15 Recovery of database 'S094000' (27) is
70% complete (approximately 35 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:19.55 spid15 Recovery of database 'S094000' (27) is
74% complete (approximately 30 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:27.02 spid15 Recovery of database 'S094000' (27) is
78% complete (approximately 26 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:34.21 spid15 Recovery of database 'S094000' (27) is
82% complete (approximately 21 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:43.72 spid15 Recovery of database 'S094000' (27) is
86% complete (approximately 17 more seconds) (Phase 2 of 3).
> 2004-06-07 16:19:52.25 spid15 Recovery of database 'S094000' (27) is
90% complete (approximately 12 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:02.85 spid15 Recovery of database 'S094000' (27) is
93% complete (approximately 7 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:14.79 spid15 Recovery of database 'S094000' (27) is
97% complete (approximately 3 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 Recovery of database 'S094000' (27) is
99% complete (approximately 0 more seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 266 transactions rolled forward in
database 'S094000' (27).
> 2004-06-07 16:20:23.72 spid15 Recovery of database 'S094000' (27) is
99% complete (approximately 0 more seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 Recovery of database 'S094000' (27) is
100% complete (approximately 0 more seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 1 transactions rolled back in database
'S094000' (27).
> 2004-06-07 16:20:25.05 spid15 Recovery is checkpointing database
'S094000' (27)
> 2004-06-07 16:21:19.65 spid61 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:21:19.65 spid61 pageno is/should be: objid is/should
be:
> 2004-06-07 16:21:19.65 spid61 (1:772511)/(1:772511)
457768688/1269579561
> 2004-06-07 16:21:19.65 spid61 ... IAM indicates that page is allocated
to this object
> 2004-06-07 16:21:19.65 spid61 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:21:19.65 spid61 Attempt to fetch logical page (1:772511)
in database 'S094000' belongs to object 't050_pre_arch', not to object
't050_campaign_candidate'..
> 2004-06-07 16:21:19.71 spid61 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:21:19.71 spid61 Could not find the index entry for RID
'16905830100' in index page (1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:21:19.71 spid61 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:21:19.71 spid61 Error while undoing logged operation in
database 'S094000'. Error at log record ID (63154:10761:6)..
> 2004-06-07 16:21:19.71 spid61 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 61, PSS = 0x43897200, EC = 0x43897528
>
>
|||In addition to Surajit's post:
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"G0" <anonymous@.discussions.microsoft.com> wrote in message
news:6AB317BC-5A70-43FC-BB47-33D5ED697253@.microsoft.com...
> Hi Gurus,
> One of my DBs on a SQL box (SQL 2000 enterprise edtion SP3 on Win2k Advanced server) went suspect yesterday.
Here is part of the error log. Would appreciate any help/suggestions.
>
> 2004-06-07 16:17:42.74 spid72 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:17:42.74 spid72 pageno is/should be: objid is/should be:
> 2004-06-07 16:17:42.74 spid72 (1:772511)/(1:772511) 457768688/1269579561
> 2004-06-07 16:17:42.74 spid72 ... IAM indicates that page is allocated to this object
> 2004-06-07 16:17:42.74 spid72 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:17:42.74 spid72 Attempt to fetch logical page (1:772511) in database 'S094000' belongs to
object 't050_pre_arch', not to object 't050_campaign_candidate'..
> 2004-06-07 16:17:42.75 spid72 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:17:42.75 spid72 Could not find the index entry for RID '16905830100' in index page
(1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:17:42.75 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:42.75 spid72 Error while undoing logged operation in database 'S094000'. Error at log
record ID (63154:9493:281)..
> 2004-06-07 16:17:42.80 spid72 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 72, PSS = 0x70f85200, EC = 0x70f85528
> (actual dump manually taken out here)
> * ----
> 2004-06-07 16:17:44.77 spid72 Stack Signature for the dump is 0x03737F82
> 2004-06-07 16:17:44.77 spid72 SQL Server Assertion: File: <scanrid.cpp>, line=321
> Failed Assertion = 'm_len != 0'.
> 2004-06-07 16:17:44.77 spid72 Error: 3624, Severity: 20, State: 1.
> 2004-06-07 16:17:45.05 spid72 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:17:45.05 spid72 Error while undoing logged operation in database 'S094000'. Error at log
record ID (63154:9493:281)..
> 2004-06-07 16:17:45.05 spid72 Error: 9001, Severity: 21, State: 1
> 2004-06-07 16:17:45.05 spid72 The log for database 'S094000' is not available..
> 2004-06-07 16:17:45.36 spid72 Error: 3314, Severity: 21, State: 5
> 2004-06-07 16:17:45.36 spid72 Error while undoing logged operation in database 'S094000'. Error at log
record ID (63154:9189:1)..
> 2004-06-07 16:17:46.34 spid15 Starting up database 'S094000'.
> 2004-06-07 16:17:47.56 spid15 Analysis of database 'S094000' (27) is 16% complete (approximately 2 more
seconds)
> 2004-06-07 16:17:49.28 spid15 Analysis of database 'S094000' (27) is 100% complete (approximately 0 more
seconds)
> 2004-06-07 16:17:49.30 spid15 Recovery of database 'S094000' (27) is 0% complete (approximately 28 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:09.83 spid15 Recovery of database 'S094000' (27) is 17% complete (approximately 98 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:13.50 spid15 Recovery of database 'S094000' (27) is 21% complete (approximately 88 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:18.67 spid15 Recovery of database 'S094000' (27) is 25% complete (approximately 83 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:23.36 spid15 Recovery of database 'S094000' (27) is 30% complete (approximately 77 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:28.38 spid15 Recovery of database 'S094000' (27) is 34% complete (approximately 72 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:34.88 spid15 Recovery of database 'S094000' (27) is 39% complete (approximately 69 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:39.81 spid15 Recovery of database 'S094000' (27) is 43% complete (approximately 64 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:44.13 spid15 Recovery of database 'S094000' (27) is 48% complete (approximately 58 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:48.85 spid15 Recovery of database 'S094000' (27) is 52% complete (approximately 53 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:18:54.44 spid15 Recovery of database 'S094000' (27) is 56% complete (approximately 48 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:00.66 spid15 Recovery of database 'S094000' (27) is 61% complete (approximately 44 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:06.38 spid15 Recovery of database 'S094000' (27) is 65% complete (approximately 39 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:12.85 spid15 Recovery of database 'S094000' (27) is 70% complete (approximately 35 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:19.55 spid15 Recovery of database 'S094000' (27) is 74% complete (approximately 30 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:27.02 spid15 Recovery of database 'S094000' (27) is 78% complete (approximately 26 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:34.21 spid15 Recovery of database 'S094000' (27) is 82% complete (approximately 21 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:43.72 spid15 Recovery of database 'S094000' (27) is 86% complete (approximately 17 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:19:52.25 spid15 Recovery of database 'S094000' (27) is 90% complete (approximately 12 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:02.85 spid15 Recovery of database 'S094000' (27) is 93% complete (approximately 7 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:14.79 spid15 Recovery of database 'S094000' (27) is 97% complete (approximately 3 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 Recovery of database 'S094000' (27) is 99% complete (approximately 0 more
seconds) (Phase 2 of 3).
> 2004-06-07 16:20:23.47 spid15 266 transactions rolled forward in database 'S094000' (27).
> 2004-06-07 16:20:23.72 spid15 Recovery of database 'S094000' (27) is 99% complete (approximately 0 more
seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 Recovery of database 'S094000' (27) is 100% complete (approximately 0 more
seconds) (Phase 3 of 3).
> 2004-06-07 16:20:25.04 spid15 1 transactions rolled back in database 'S094000' (27).
> 2004-06-07 16:20:25.05 spid15 Recovery is checkpointing database 'S094000' (27)
> 2004-06-07 16:21:19.65 spid61 Getpage: bstat=0x9, sstat=0x10000, cache
> 2004-06-07 16:21:19.65 spid61 pageno is/should be: objid is/should be:
> 2004-06-07 16:21:19.65 spid61 (1:772511)/(1:772511) 457768688/1269579561
> 2004-06-07 16:21:19.65 spid61 ... IAM indicates that page is allocated to this object
> 2004-06-07 16:21:19.65 spid61 Error: 605, Severity: 21, State: 1
> 2004-06-07 16:21:19.65 spid61 Attempt to fetch logical page (1:772511) in database 'S094000' belongs to
object 't050_pre_arch', not to object 't050_campaign_candidate'..
> 2004-06-07 16:21:19.71 spid61 Error: 644, Severity: 21, State: 5
> 2004-06-07 16:21:19.71 spid61 Could not find the index entry for RID '16905830100' in index page
(1:772510), index ID 9, database 'S094000'..
> 2004-06-07 16:21:19.71 spid61 Error: 3314, Severity: 21, State: 4
> 2004-06-07 16:21:19.71 spid61 Error while undoing logged operation in database 'S094000'. Error at log
record ID (63154:10761:6)..
> 2004-06-07 16:21:19.71 spid61 Using 'dbghelp.dll' version '4.0.5'
> *Dump thread - spid = 61, PSS = 0x43897200, EC = 0x43897528
>
>