FIX: A RESTORE DATABASE WITH RECOVERY Statement Can Fail with Error 9003 or Error 9004 (328354)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
This article was previously published under Q328354 SQL Server 8.0:361676 SYMPTOMS When you run a RESTORE DATABASE WITH RECOVERY statement to
bring a standby server online, you might receive one of the following error
messages: Error: 9003 The LSN %S_LSN
passed to log scan in database '%.*ls' is invalid.
Error: 9004 An error occurred while processing the log
for database '%.*ls'.
CAUSE This problem occurs because physical characteristics
(virtual log parity) for inactive virtual log files in the transaction log are
not preserved when a full database backup is restored.
RESOLUTION To resolve this problem, obtain the latest
service pack for Microsoft SQL Server 2000. For additional information, click
the following article number to view the article in the Microsoft Knowledge
Base: 290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
HotfixNote The following hotfix was created before the release of Microsoft
SQL Server 2000 Service Pack 3. The English version of this fix has
the file attributes (or later) that are listed in the following table. The
dates and times for these files are listed in coordinated universal time (UTC).
When you view the file information, it is converted to local time. To find the
difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Version File name
------------------------------
8.00.678 Sqlservr.exe
Note Because of file dependencies, the most recent hotfix or feature
that contains the files may also contain additional
files. WORKAROUND To avoid this problem, reinitialize the primary and the
standby servers by using the same full database backup. This ensures that the
parity for all the virtual log files on both systems is equivalent.
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section of this
article.
This problem was first corrected in SQL
Server 2000 Service Pack 3.MORE INFORMATION After you apply the fix for this problem, you must restore
a full database backup on the standby server. For more information about standby servers, see the "How to
set up, maintain, and bring online a standby server" topic in the SQL Server
documentation.
For more information about the WITH RECOVERY option of
the RESTORE command, see the SQL Server documentation that describes the syntax
for the Transact-SQL RESTORE command.
Modification Type: | Minor | Last Reviewed: | 9/27/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbfix kbSQLServ2000preSP3fix KB328354 |
---|
|