BerkeleyDB DB_RUNRECOVERY =>
Berkeley DB Reference Guide: Error returns to applications
There exists a class of errors that Berkeley DB considers fatal to an entire
Berkeley DB environment. An example of this type of error is a corrupted
database page. The only way to recover from these failures is to have
all threads of control exit the Berkeley DB environment, run recovery of the
environment, and re-enter Berkeley DB. (It is not strictly necessary that the
processes exit, although that is the only way to recover system
resources, such as file descriptors and memory, allocated by Berkeley DB.)
The log files ought to be able to tell you more about the cause of the error.
Recovery procedures can help you recover your database.
| MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!" |
| I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README). |
| ** The third rule of perl club is a statement of fact: pod is sexy. |
