OGG-02945
Cannot automatically start Replicat group {0}, which abended due to an out of order transaction. Issue ETROLLOVER to advance the output trail sequence past the current trail sequence and restart. Then, use ALTER EXTSEQNO on the subsequent pump Extract output trail sequence past the current trail sequence and restart. Then, use ALTER EXTSEQNO on the subsequent pump Extract, or Replicat, process group to start reading from the new trail file created by ALTER ETROLLOVER; the downstream process will not automatically switch to the new trail file.
Cause
Manager cannot start the specified Replicat. The transactions in the current trail file are out of order. One possible cause is that Extract was configured to write to this trail, and then was reconfigured to write to a different trail, but was subsequently reconfigured to write the original trail again. It is also possible that Extract was repositioned backward in the transaction log and the data from the new position was appended to the end of the current trail file. You need to skip this record, and then reposition Replicat to start at the next one.
Action
Stop the Extract that should write to this trail, then issue the ALTER EXTRACT command with ETROLLOVER. Next, restart Extract. Next, issue the ALTER REPLICAT or ALTER EXTRACT command (depending on whether Replicat or a data pump Extract reads the trail) with the EXTSEQNO option and specify the sequence number of the new trail file. Finally, start Replicat or the data pump.
OGG-02945
Cannot automatically start Replicat group {0}, which abended due to an out of order transaction. Issue ETROLLOVER to advance the output trail sequence past the current trail sequence and restart. Then, use ALTER EXTSEQNO on the subsequent pump Extract output trail sequence past the current trail sequence and restart. Then, use ALTER EXTSEQNO on the subsequent pump Extract, or Replicat, process group to start reading from the new trail file created by ALTER ETROLLOVER; the downstream process will not automatically switch to the new trail file.
Cause
Manager cannot start the specified Replicat. The transactions in the current trail file are out of order. One possible cause is that Extract was configured to write to this trail, and then was reconfigured to write to a different trail, but was subsequently reconfigured to write the original trail again. It is also possible that Extract was repositioned backward in the transaction log and the data from the new position was appended to the end of the current trail file. You need to skip this record, and then reposition Replicat to start at the next one.
Action
Stop the Extract that should write to this trail, then issue the ALTER EXTRACT command with ETROLLOVER. Next, restart Extract. Next, issue the ALTER REPLICAT or ALTER EXTRACT command (depending on whether Replicat or a data pump Extract reads the trail) with the EXTSEQNO option and specify the sequence number of the new trail file. Finally, start Replicat or the data pump.
