HELP - Redo Log Error

All,
SQL 2000 sp3, Server 2000 sp3
below is the error I got when trying to do a restore. I've read that
going to sp3 should help, but I'm already there. What causes this
problem?
Executed as user: WINFREESTUFF\sqladmin. Deleting database file
'h:\wfsundo.bak'. [SQLSTATE 01000] (Message 3738) Processed 4287 pages
for database 'wfs', file 'wfs_log' on file 1. [SQLSTATE 01000] (Message
4035) Could not redo log record (161973:16059:9), for transaction ID
(0:-2134161807), on page (13:1408224), database 'wfs' (8). Page: LSN = (161973:12114:4), type = 1. Log: OpCode = 3, context 2, PrevPageLSN:
(138073:47239:227). [SQLSTATE HY000] (Error 3456). The step failed.
Thanks All,
Gary
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!I guess this is the same post as yesterday? As no-one has answered, I suggest you first search
KB and if you don't find anything there, open a case with MS PSS. To my understanding of SQL
Server (and with the little info we have), this shouldn't be happening.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Gary Abbott" <snyper@.uniserve.com> wrote in message
news:uxAghk1RDHA.704@.tk2msftngp13.phx.gbl...
> All,
> SQL 2000 sp3, Server 2000 sp3
> below is the error I got when trying to do a restore. I've read that
> going to sp3 should help, but I'm already there. What causes this
> problem?
> Executed as user: WINFREESTUFF\sqladmin. Deleting database file
> 'h:\wfsundo.bak'. [SQLSTATE 01000] (Message 3738) Processed 4287 pages
> for database 'wfs', file 'wfs_log' on file 1. [SQLSTATE 01000] (Message
> 4035) Could not redo log record (161973:16059:9), for transaction ID
> (0:-2134161807), on page (13:1408224), database 'wfs' (8). Page: LSN => (161973:12114:4), type = 1. Log: OpCode = 3, context 2, PrevPageLSN:
> (138073:47239:227). [SQLSTATE HY000] (Error 3456). The step failed.
>
> Thanks All,
> Gary
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!|||Tibor,
Thanks, it is the same post. I have had this before with no clear
resolution from microsoft. This is the fourth time I've had it since
I've been here. Last time they said it was because there was no checkdb
ran in months. So I accepted that, but now I do them every week and
still get the same problem. I'm calling MS again, to see what they
suggest this time. The documentation in KB says its due to an index
being built when the backup runs, I schedule my jobs very carefully. To
avoid such collisions, I only rebuild indexes on the weekends when most
of my users aren't using my servers. I must admit, over the years I have
not run into this problem before and think it may be hardware related.
Thanks All,
Gary
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!