Event Id | 3445 |
Source | MSSQLServer |
Description | File %ls is not a valid undo file for database %.*ls, database ID %d. |
Event Information | CAUSE: When you use the STANDBY clause of the RESTORE process, an undo file is created each time you issue RESTORE LOG ... WITH STANDBY. The next RESTORE LOG uses the previous undo log to first apply transactions that were rolled back during the previous RESTORE LOG. You will receive the above error if the undo log is not in the expected format or if the file or its underlying media is damaged. For more information about standby servers, see "Using Standby Servers," "How to set up, maintain, and bring online a standby server (Enterprise Manager)," and "How to set up, maintain, and bring online a standby server (Transact-SQL)" in Books Online. RESOLUTION: Do not delete or edit the undo file between transaction log restores. Verify the integrity of the media where the undo file resides. |
Reference Links | Microsoft product: SQL Server Version: 2000.80.760.0 Event Source: MSSQLServer Event ID: 3445 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.