Logshipping ERROR(urgent)

Hi Guys,
I am facing following problem with MSSQL Server 2000.
I am using Microsoft sql server Log Shipping feature to have a standby
server for disaster recovery purposes.
in the logshipping Destination server while restoring the transaction log
the restore process is failling with following error.
"[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft]&
#91;ODBC SQL
Server Driver][SQL Server]Could not redo log record (8130:35542:2), for
transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
PrevPageLSN: (8122:7374:3)."
Both servers, source and destination were running with SQL SERVER
ENTERPRISE EDITION SP3 .
after this failure i rebuilded the logshipping process but same error
happened again so after one week updated the destination server with sql sp
4
and rebuilded the logshipping process . but the same error happened again.
During this error SQL Server is creating a dump file and text file
pls adviceAre you sure that your databases are consistent - run checkdb...
Bojidar Alexandrov
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][OD
BC
SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), fo
r
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice|||Hi Bojidar Alexandrov,
in source or destination?
source is consistent as i am doing dbcc every day and no errors found.
"Bojidar Alexandrov" wrote:

> Are you sure that your databases are consistent - run checkdb...
> Bojidar Alexandrov
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> SQL
> sp4
>|||"bijupg@.hotmail.com" schrieb:

> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft
][ODBC SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), fo
r
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice
Did you do transaction log backups in between? Don't forget that they empty
the TA-Log and produce a new sequence number - then the logshipping (being
fully incremental) are missing some data and cannot work any more ...|||No i am not doing any transaction log backup in between
"Christian Donner" wrote:

> "bijupg@.hotmail.com" schrieb:
>
> Did you do transaction log backups in between? Don't forget that they empt
y
> the TA-Log and produce a new sequence number - then the logshipping (being
> fully incremental) are missing some data and cannot work any more ...|||The type of error you are seeing is most likely being caused by corruption
in your transaction logs. Review system event logs on both servers for ANY
hardware-related warnings and errors. Update all your firmware and drivers.
Adrian
"bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
> Hi Guys,
> I am facing following problem with MSSQL Server 2000.
> I am using Microsoft sql server Log Shipping feature to have a standby
> server for disaster recovery purposes.
> in the logshipping Destination server while restoring the transaction log
> the restore process is failling with following error.
> "[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft
][ODBC
> SQL
> Server Driver][SQL Server]Could not redo log record (8130:35542:2), fo
r
> transaction ID (0:91843227), on page (1:519336), database 'REVENUES' (5).
> Page: LSN = (8130:29950:3), type = 1. Log: OpCode = 3, context 2,
> PrevPageLSN: (8122:7374:3)."
> Both servers, source and destination were running with SQL SERVER
> ENTERPRISE EDITION SP3 .
> after this failure i rebuilded the logshipping process but same error
> happened again so after one week updated the destination server with sql
> sp4
> and rebuilded the logshipping process . but the same error happened again.
> During this error SQL Server is creating a dump file and text file
> pls advice|||Biju.
You have been having trouble with this DB many times in the past. You had
corruption, it showed as fixed, and now it is back. You do not have torn
page detection on. Turn ton page detect ion on.
If your corruption continues, you will soon have a database that all you can
do it delete.
It may be worth your while to open a case with Microsoft PSS.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
> The type of error you are seeing is most likely being caused by corruption
> in your transaction logs. Review system event logs on both servers for ANY
> hardware-related warnings and errors. Update all your firmware and
> drivers.
> Adrian
>
> "bijupg@.hotmail.com" <bijupghotmailcom@.discussions.microsoft.com> wrote in
> message news:F6B405F2-0038-418C-8703-BB77E2C8435D@.microsoft.com...
>|||Hi Mike,
can you pls advice how to open case with Microsoft PSS.
"Mike Epprecht (SQL MVP)" wrote:

> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you c
an
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
>
>|||Hi guys,
DBCC CHECKDB is not giving any errors or warnings and database is
functioning normally.
there are no hardware related errors in event viewer.
and we are using compaq cluster with compaq smart array controller so is
there any chance to have a torn page?this type of diska should have mechanis
m
to ensure that data is completely written and also there are no power failur
e
at all.
i am using transactional replication for reporting and it is working fine if
there was any problem with source database then it should also fail like
logshipping.
what should be the ideal temperature in datacentres/server romms currently
we are keeping 20-22 degree celcius is it ok?
Pls advice.
"Mike Epprecht (SQL MVP)" wrote:

> Biju.
> You have been having trouble with this DB many times in the past. You had
> corruption, it showed as fixed, and now it is back. You do not have torn
> page detection on. Turn ton page detect ion on.
> If your corruption continues, you will soon have a database that all you c
an
> do it delete.
> It may be worth your while to open a case with Microsoft PSS.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:tsednVPPk5VQVjPfRVn-3Q@.rogers.com...
>
>