Invalid transaction log path

If Domino cannot access the transaction log path, the server console displays error messages indicating: the invalid log path, databases requiring media recovery or Fixup, and a panic.

1. Check the log path to make sure it exists.

2. Check that the server has write access to the log path.

3. If the log path is correct and the device is good, restart the server. The problem should be fixed and you do not need to continue to step 4.

4. If log path is correct but the device is bad, replace the device on the log path, or edit the TRANSLOG_Path setting in NOTES.INI to point to a different log path.

Note If you edit the TRANSLOG_Path setting when you restart the server, be sure to make the same edit to the "Log path" field in the Server document. Otherwise, Domino reverts to the old path upon the next server restart.

6. If "Automatic fixup of corrupt databases" is set to Yes in the Server document, the Fixup task runs on the databases that require media recovery or Fixup. Otherwise, you must run the Fixup task manually.

7. Perform full database backups.

Transaction log damaged or corrupted

If the transaction log appears to be damaged or corrupted, the server console displays error messages indicating: the log is damaged, databases requiring media recovery or Fixup, and a panic.

The error may occur because of a failed read from or write to the transaction log.

1. Restart the server to correct the error. If the damaged log error does not appear again, the log is not damaged.

2. Stop the server again so it shuts down cleanly.

3. Perform full database backups.

4. Restart the server.

If you continue to received the damaged log error, the active transaction log is damaged or corrupted.

6. Restart the server. Domino creates new log files and a control file and assigns new DBIIDs to all Domino 5 or higher databases.

7. If "Automatic fixup of corrupt databases" is set to Yes in the Server document, the Fixup task runs on the databases that require media recovery or Fixup. Otherwise, you must run the Fixup task manually.

8. Perform full database backups.

If the error occurred during media recovery, an archived log file may be corrupted.

10. While the server is down, use the third-party backup utility to perform media recovery. If the archived log still cannot be used, allow database backups to be restored without the transactions in the corrupted log.

11. Perform full database backups.

12. Restart the server.

Related topics

Troubleshooting the Domino system
Lotus Support

Glossary