In Microsoft SQL Server 2005, you use log shipping for a database. You set the secondary database to use the STANDBY mode. When transaction log backups are being restored on the secondary database, the following error messages are logged in the SQL Server 2005 error log file:
Date Time Backup Log was restored. Database: PCO, creation date(time): Date (Time), first LSN: 38876:162309:1, last LSN: 38877:175363:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'L:PCO_20070509202011.trn'}). This is an informational message. No user action is required.
Date Time SPID Starting up database 'PCO'.
Date Time SPID The database 'PCO' is marked RESTORING and is in a state that does not allow recovery to be run.
Date Time SPID Error: 9003, Severity: 20, State: 1.
Date Time SPID The log scan number (38842:37318:3) passed to log scan in database 'PCO' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
Date Time SPID Error: 3313, Severity: 16, State: 2.
Date Time SPID During redoing of a logged operation in database 'PCO', an error occurred at log record ID (0:0:0). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
Additionally, a minidump file is generated when this issue occurs.