When loading transaction log dumps, always examine the “Checking Loss” message that is displayed during loss detection. If there is more than one message, choose the earliest date and time to determine which dumps to load.
For example, if the following message is generated by a Replication Server, you would load the dumps taken just before November 1, 1995 at 10:58 p.m.:
Checking Loss for DS3.RDB from DS1.PDB date=Nov-01-1995 10:58pm qid=0x01234567890123456789
The date in the message is the date and time of the oldest open transaction in the log when the last message received by the Replication Server was generated by the origin queue. Locate the most recent transaction dump with a timestamp before the date and time in the message. Then find the full database dump taken before that transaction dump.
The origin queue ID, or qid, is formed by the RepAgent and identifies a log record in the transaction log. The date is embedded in the qid as a timestamp. Replication Server converts the timestamp to a date for RepAgents for Adaptive Server.
Replication agents for non-Sybase data servers may also embed the timestamp in the qid. Replication Server converts the timestamp for non-Sybase data servers in bytes 20–27. The use of these bytes depends on the Replication Agent.
If the data server is not an Adaptive Server, the date
in the message may appear nonsensical. You may need to decode the qid in
bytes 20–27 to identify the dumps to load.
