...
...
...
...
...
...
...
...
...
...
...
...
How do we resend a
...
PLOG?
A plog PLOG can be resend resent from the MINE process to the apply APPLY process by using an internal engine command. Please see API and Internal Commands for more information.
The process is:
- Stop the MINE and Apply processAPPLY processes
In the console type (use the plog PLOG sequence instead of X):
No Format dbvrep> ENGINE MINE RESET TO PLOG X
On the target or apply database, run:
runNo Format SQL> delete dbvrep.dbrsapply_plog_history where sequence>=X;
- On the target or Apply server, move all the plogs >= sequence X that are in the "apply" directory to another location for backup purposes.
- On the source or Mine server, move all the plogs >= sequence X that are in the "mine" directory to another location for backup purposes.
- Restart MINE process
- Restart Apply APPLY process if this was stopped
The following message in the log file may indicate that a plog PLOG needs to be resent if this message does not progress:
| No Format |
|---|
WARN-2403: Incomplete PLOG X, but not an online log. Rerequesting it from mine, sleeping and trying again |
| Note | ||
|---|---|---|
How to determine what is X? To determine which Plog sequence to resend from, look at which Plog sequence the Apply process is currently at. Once Apply has processed a Plog, it is not possible to re-apply this Plog. So the earliest Plog that be resend is the Plog that is currently being applied. On the command console, if the Apply status is showing the following:
Then the plog sequence to resend is 11078. |