Salesforce

How to disable a Fathom Replication database Offline?

« Go Back

Information

 
TitleHow to disable a Fathom Replication database Offline?
URL Name000013565
Article Number000134849
EnvironmentProduct: Fathom OpenEdge Replication
Version: All supported versions
OS: All supported platforms
Question/Problem Description
How to disable an OpenEdge Fathom Replication database Offline.
How to disable an OpenEdge Replication Source database
How to disable a Fathom Replication Target database
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
Once source database replication is disabled, the only way to replicate the database again is to re-enable Replication on the source database then re-baseline the target.

To Disable Fathom OpenEdge Replication Offline: 

[source]

1. Disable Replication:
$  proutil source_dbname -C disablesitereplication source

2. Maintenance:
  • Stop and archive all DSRUTIL cron jobs / scheduled tasks / utilities that access the source database
  • Delete the *.repl.recovery and archive or rename the *.repl.properties files (for source)
  • Remove the -DBService replserv and -pica database startup parameters
  • Any LOCKED ai files will be marked FULL after disabling source replication
3. If after-imaging also needs to be disabled:
$  proutil source_dbname -C aimage end

4. Maintenance:
  • Stop and archive all RFUTIL cron jobs / scheduled tasks / utilities that access the source database
  • Remove AIW from starting against source database (proaiw)
  • Remove -aibufs and -aistall source database startup parameters
  • If AI Management was enabled, remove the -aiarcdir, -aiarcinterval, -aiarcdircreate source database startup parameters
  • Consider removing the ai files from source at next shutdown:  $   prostrct remove source_dbname ai
5. It is recommended to first backup this database before or shortly after restarting it.

[target]

1. If the target database was running when replication was disabled against source, it will be in PRE-Transition state and still running.
$   proshut target_dbname -by

2. Delete the target database (*)
$   prodel target_dbname

3. Maintenance:
  • Stop and archive all cron jobs / scheduled tasks / utilities that access the target database
  • Delete the *.repl.recovery and archive or rename the *.repl.properties files (for target)
(*) If the target database needs to be preserved, disable target replication instead of deleting it:
$   proutil target_dbname -C disablesitereplication target
  • Remove the -DBService replagent and -pica database startup parameters
Workaround
Notes
Keyword Phrase
Last Modified Date11/20/2020 7:24 AM

Powered by