%1 (%2) %3Database %4 requires logfile %5 created at %6 in order to recover successfully. Recovery found the logfile created at %7.
Data width of the physical memory, in bits. A data width of 0 and a total width of 8 would indicate that the memory is solely ...
Database %4 cannot be incrementally backed-up. You must first perform a full backup before performing an incremental backup. ...
Database %4 has lost %5 committed log files (%6-%7), however lost log resilience has allowed ESE to recover this database ...
Database %4 requires log files %5-%6 in order to recover all committed data. Recovery could only locate up to log file: %7, ...
Database %4 requires logfile %5 created at %6 in order to recover successfully. Recovery found the logfile created at %7. ...
Database %4 requires logfiles %5-%6 (%8 - %9) in order to recover successfully. Recovery could only locate logfiles up to ...
Database %4 requires logfiles %5-%6 in order to recover successfully. Recovery could only locate logfiles starting at %7. ...
Database %4: Page %5 failed verification due to a flush-order dependency mismatch. This page should have flushed before page ...
Database %4: Page %5 failed verification due to a timestamp mismatch. The expected timestamp was %6 but the actual timestamp ...