MaxRep: No data throughput on all Protection Plans causes the Recovery Point Objective (RPO) to exceed the default time limit threshold
Last updated on JANUARY 05, 2018
Applies to:Pillar Axiom Replication Engine (MaxRep) - Version 3.0 to 3.0 [Release 3.0]
Information in this document applies to any platform.
The default threshold for the MaxRep Recovery Point Objective (RPO) value is 30 minutes. An alert will be sent if the RPO increases beyond this limit. The RPO can be increased or decreased under Protect -> Manage Protection Plan: Click on Modify to change the Protection Plan and select Modify Replication Options. Under normal operations, the RPO should be well below the default threshold of 30 minutes but due to a known issue, this value may start increasing and continue to increase until a workaround is applied by Oracle Support.
Below is an example of the symptoms as seen in the MaxRep Graphical User Interface (GUI) under Monitor -> Volume Protection:
Symptoms of the issue can also be determined in the following way:
a) Open a SSH to the source Engine IP address where the plans are being affected.
b) Check the source and target cache folder to determine if the differentials are draining correctly.
c) Under /home/svsystems/transport/log/, review the file cxps.err.log for timeout errors like these:
In the above analysis example it is shown that cachemgr was not draining the differentials from the source/target cache because it was hung displaying the "CLOSE_WAIT" message.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms