- Article Type: General
- Product: Aleph
- Product Version: 17.01
The Oracle instance for our production database (aleph16) shut down unexpectedly at approximately 11:30 this morning. We restarted Oracle and everything looks to be back to normal, but we need to know why this happened. In looking at the log files, it seems that the Oracle logwriter process encountered a problem.
The initial, significant message is:
ORA-00345: redo log write error block 65221 count 11
This is the interpretation for this message:
ORA-00345: redo log write error block string count string
Cause: An IO error has occurred while writing the log
Action: Correct the cause of the error, and then restart the system. If the log is lost, apply media/incomplete recovery.
"Write error" may indicate a possible disk problem.
We suggest that you check the Web and check with Oracle to see if there's any reason to believe that this is a disk problem -- or, in general, how to interpret the message.
If they believe that the application software might be involved and that Ex Libris, as the application vendor, should do something, let us know what that is.
oracle, crash, redo
- Article last edited: 10/8/2013