Database %1: Page %2 failed verification due to a timestamp mismatch at log position %7. The remote ("before") timestamp persisted to the log record was %3 but the actual timestamp on the page was %4 (note: DbtimeCurrent = %6). This indicates the passive node lost a flush (error %5). This problem is likely due to faulty hardware "losing" one or more flushes on this page sometime in the past on the passive node. Please contact your hardware vendor for further assistance diagnosing the problem.
Database %1 requires logfiles %2-%3 in order to recover successfully. Recovery could only locate logfiles starting at %4. ...
Database %1: Page %2 failed verification due to a flush-order dependency mismatch. This page should have flushed before page ...
Database %1: Page %2 failed verification due to a timestamp mismatch at log position %7. The 'before' timestamp persisted ...
Database %1: Page %2 failed verification due to a timestamp mismatch at log position %7. The remote ("before") timestamp ...
Database %1: Page %2 failed verification due to a timestamp mismatch at log position %7. The remote ("before") timestamp ...
Database %1: Page %2 logical data checksum %3 failed to match logged scan check %4 checksum (seed %5) at log position %6. ...
Database %1: Page %2 was shown to be uninitialized at log position %5, while the remote ("before") timestamp persisted to ...
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 ...