The log scan number %1!s! passed to log scan in database '%2!s!' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
The Log Reader Agent was unable to connect to the Publisher using the specified login. Make sure that the login used by the ...
The log reader encountered a 'CANNOT SERIALIZE TRANSACTION' error (ORA-08177) while creating an XactSet at the publisher. ...
The log reader encountered a 'SNAPSHOT TOO OLD' error (ORA-01555) while creating an XactSet at the publisher. The creation ...
The log reader encountered an 'OBJECT NOT FOUND' error (ORA-00942) while creating an XactSet at the publisher. The creation ...
The log scan number %1!s! passed to log scan in database '%2!s!' is not valid. This error may indicate data corruption or ...
The log shipping primary database %1!s!.%2!s! has backup threshold of %3!s! minutes and has not performed a backup log operation ...
The log shipping secondary database %1!s!.%2!s! has restore threshold of %3!s! minutes and is out of sync. No restore was ...
The log was not truncated because records at the beginning of the log are pending replication or Change Data Capture. Ensure ...
The Log-Scan Process failed to construct a replicated command from log sequence number (LSN) {%1!s!:%2!s!:%3!s!}. Back up ...