Production Database Marked as Suspect (SQL Server 2000)

Hello,
Our production database was marked as suspect due to a
possible hardware error. Hardware error has been resolved
but when SQL server was restarted the production database
was marked as suspect. After the sp_resetstatus and tried
to recover the status is still suspect with the following
error message in the errorlog :
2004-01-07 12:02:47.66 spid13 Error: 3456, Severity:
21, State: 1
2004-01-07 12:02:47.66 spid13 Could not redo log record
(26822:23441:10), for transaction ID (0:21782102), on page
(1:3042), database 'FS84PRD' (9). Page: LSN = (26817:26440:2), type = 1. Log: OpCode = 2, context 2,
PrevPageLSN: (26822:23351:7)..
2004-01-07 12:02:47.66 spid13 ex_raise2: Exception
raised, major=34, minor=56, severity=25, attempting to
create symptom dump
2004-01-07 12:02:47.68 spid13 Using 'dbghelp.dll'
version '4.0.5'
2004-01-07 12:02:47.94 spid13 Error: 3313, Severity:
21, State: 2
2004-01-07 12:02:47.94 spid13 Error while redoing
logged operation in database 'FS84PRD'. Error at log
record ID (26822:23441:10)..
2004-01-07 12:02:57.19 spid13 Error: 3414, Severity:
21, State: 1
2004-01-07 12:02:57.19 spid13 Database 'FS84PRD'
(database ID 9) could not recover. Contact Technical
Support..
2004-01-07 12:03:17.24 spid3 Recovery complete.
2004-01-07 12:03:17.40 spid3 SQL Server is terminating
due to 'stop' request from Service Control Manager.
Is there any way to recover this or is my only option to
restore from the backup ? If the only solution is the
latter, will I be able to perform a normal restore using
enterprise manager ?
Thanks for everyone's help in advance !
WillyHi,
Try to start the database in emergency mode and try out.
update sysdatabases
set status=32768
where name='FS84PRD'
Now probably you will be able to access the database.
Thanks
Hari
MCDBA
"Willy Ong" <anonymous@.discussions.microsoft.com> wrote in message
news:08ef01c3d516$bbadeb40$a601280a@.phx.gbl...
> Hello,
> Our production database was marked as suspect due to a
> possible hardware error. Hardware error has been resolved
> but when SQL server was restarted the production database
> was marked as suspect. After the sp_resetstatus and tried
> to recover the status is still suspect with the following
> error message in the errorlog :
> 2004-01-07 12:02:47.66 spid13 Error: 3456, Severity:
> 21, State: 1
> 2004-01-07 12:02:47.66 spid13 Could not redo log record
> (26822:23441:10), for transaction ID (0:21782102), on page
> (1:3042), database 'FS84PRD' (9). Page: LSN => (26817:26440:2), type = 1. Log: OpCode = 2, context 2,
> PrevPageLSN: (26822:23351:7)..
> 2004-01-07 12:02:47.66 spid13 ex_raise2: Exception
> raised, major=34, minor=56, severity=25, attempting to
> create symptom dump
> 2004-01-07 12:02:47.68 spid13 Using 'dbghelp.dll'
> version '4.0.5'
> 2004-01-07 12:02:47.94 spid13 Error: 3313, Severity:
> 21, State: 2
> 2004-01-07 12:02:47.94 spid13 Error while redoing
> logged operation in database 'FS84PRD'. Error at log
> record ID (26822:23441:10)..
> 2004-01-07 12:02:57.19 spid13 Error: 3414, Severity:
> 21, State: 1
> 2004-01-07 12:02:57.19 spid13 Database 'FS84PRD'
> (database ID 9) could not recover. Contact Technical
> Support..
> 2004-01-07 12:03:17.24 spid3 Recovery complete.
> 2004-01-07 12:03:17.40 spid3 SQL Server is terminating
> due to 'stop' request from Service Control Manager.
> Is there any way to recover this or is my only option to
> restore from the backup ? If the only solution is the
> latter, will I be able to perform a normal restore using
> enterprise manager ?
> Thanks for everyone's help in advance !
> Willy|||Your best option is to restore from backup. Database integrity is
questionable when recovery is not performed.
Yes, you can perform a normal restore using EM or Query Analyzer.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Willy Ong" <anonymous@.discussions.microsoft.com> wrote in message
news:08ef01c3d516$bbadeb40$a601280a@.phx.gbl...
> Hello,
> Our production database was marked as suspect due to a
> possible hardware error. Hardware error has been resolved
> but when SQL server was restarted the production database
> was marked as suspect. After the sp_resetstatus and tried
> to recover the status is still suspect with the following
> error message in the errorlog :
> 2004-01-07 12:02:47.66 spid13 Error: 3456, Severity:
> 21, State: 1
> 2004-01-07 12:02:47.66 spid13 Could not redo log record
> (26822:23441:10), for transaction ID (0:21782102), on page
> (1:3042), database 'FS84PRD' (9). Page: LSN => (26817:26440:2), type = 1. Log: OpCode = 2, context 2,
> PrevPageLSN: (26822:23351:7)..
> 2004-01-07 12:02:47.66 spid13 ex_raise2: Exception
> raised, major=34, minor=56, severity=25, attempting to
> create symptom dump
> 2004-01-07 12:02:47.68 spid13 Using 'dbghelp.dll'
> version '4.0.5'
> 2004-01-07 12:02:47.94 spid13 Error: 3313, Severity:
> 21, State: 2
> 2004-01-07 12:02:47.94 spid13 Error while redoing
> logged operation in database 'FS84PRD'. Error at log
> record ID (26822:23441:10)..
> 2004-01-07 12:02:57.19 spid13 Error: 3414, Severity:
> 21, State: 1
> 2004-01-07 12:02:57.19 spid13 Database 'FS84PRD'
> (database ID 9) could not recover. Contact Technical
> Support..
> 2004-01-07 12:03:17.24 spid3 Recovery complete.
> 2004-01-07 12:03:17.40 spid3 SQL Server is terminating
> due to 'stop' request from Service Control Manager.
> Is there any way to recover this or is my only option to
> restore from the backup ? If the only solution is the
> latter, will I be able to perform a normal restore using
> enterprise manager ?
> Thanks for everyone's help in advance !
> Willy