PFR replication performance degraded

Symptom

After a few months of fast PFR replication, you may notice that PFR has become significantly slower. It may take 15 minutes to a few hours to replicate one file. This is due to the history file of the fileset becoming too large (say, more than 20000 lines). But if you delete the history files PFR will think that none of the primary files are replicated and so, replicate ALL the primary files to DR. To avoid this, at primary you must first move already replicated archive log files to a different directory.

?The detailed steps are below:

?1. At primary, move to a backup folder all the archive log files that are ALREADY COPIED to DR. The backup folder should NOT be under the source folder.
?Note: If it is difficult to identify which .arc files are on DR, simply move the .arc files that are two and more days old.
?2. ON BOTH PRIMARY and DR servers:
? Login as root.
?3. cd $EAMSROOT
?4 ./PFR.sh stop # Stop PFRService.
?5. ./PFRAgent.sh stop # Stop the PFR agent.
?6. ps -aef | grep -i pfr # Verify that both are stopped. Use the unix kill command if any are still running.
?7. cd $EAMSROOT/panacesFileReplicator
?8. rm -f filesets/*/*.history bak/*/*.history (That is, delete the history files under both the folders filesets and bak).
?9. ./PFR.sh start # Start PFRService.
?10. ./PFRAgent.sh start # Start the PFR agent.

?Remember: steps 2 to 10 on BOTH servers.