Domino 7.0 unter SLES9 will nicht starten

console_ln-fra-01_2009_10_12@07_26_33.log

Lotus Domino (r) Server, Release 7.0, August 18, 2005 Copyright (c) IBM Corporation 1987, 2005. All Rights Reserved.  C9:37    Thread=[12082:00002-47922144] Stack base=0xBFFEC7BC, Stack size = 1852 bytes PANIC: Transaction log is damaged!

ln-fra-01.log

Fatal Error signal = 0x0000000b PID/TID = 14607/47922144  12/10/2009 7:43:25  Running NSD NSD is in progress .................  Please attach the following files to your bug report along with the server log: Log file                : /daten2/ln-fra-01/IBM_TECHNICAL_SUPPORT/nsd_Linux_ln-fra-01_2009_10_12@07_43_25.log 12/10/2009 7:43:42  Termination is in progress 12/10/2009 7:43:42  Terminating tasks 12/10/2009 7:43:47  Freeing resources 12/10/2009 7:43:47  Termination completed  ln-fra-01:/etc/init.d #

Hat jemand eine Idee zum Lösen des Fehlers? Nen PMR ist schon offen, vielleicht sind wir ja schneller.

Viele Grüße

Marc

Fixed mittels:

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

5. Delete the transaction log files and the control file.

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.

9. Restart the server to correct the problem, and then stop the server so it shuts down cleanly.

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.