Kbase P153289: How to disable a Fathom Replication database Offline.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/16/2010 |
|
Status: Verified
GOAL:
How to disable a Fathom Replication database Offline.
GOAL:
How to disable a Fathom Replication Source database
GOAL:
How to disable a Fathom Replication Target database
FACT(s) (Environment):
All Supported Operating Systems
Fathom Replication
OpenEdge Replication
FIX:
To disable Fathom replication offline:
[source]
1. disable replication:
$ proutil source_db_name -C disablesitereplication source
2. Maintenance:
- stop/remove any dsrutil cron jobs/utilities that access the source database
- delete *.recovery and *.repl.properties (for source)
- any LOCKED ai files will now be marked FULL
3. if after-imaging also needs to be disabled, run:
$ proutil source_db_name -C aimage end
- stop/remove any rfutil cron jobs/utilities that access the source database
- remove AIW from starting against source database (proaiw)
- remove the -aibufs from source database startup
- consider removing the ai files from source at next shutdown (prostrct remove source_db_name ai )
[target]
- stop and delete the target database (note, if target was running when you disabled against source, it will be in PRE-Transition state and still running)
- stop/remove any cron jobs, utilities that access target database
- delete *.recovery and *.repl.properties (for target)
To disable Fathom replication online: (available since Fathom Replication 3.0)
[source]
1. disable replication:
$ dsrutil source_db_name -C terminate server # the replication server needs to be stopped if running currently
$ dsrutil source_db_name -C RELWAITS # to release any pending waits
$ echo y | dsrutil source_db_name -C disablesitereplication source
2. Maintenance:
- stop/remove any dsrutil cron jobs/utilities that access the source database
- delete *.recovery and *.repl.properties (for source)
- any LOCKED ai files will now be marked FULL
3. if after-imaging also needs to be disabled, run:
$ rfutil source_db_name -C aimage aioff
- stop/remove any rfutil cron jobs/utilities that access the source database
- remove AIW from starting against source database (proaiw)
- remove the -aibufs from source database startup
- consider removing the ai files from source at next shutdown (prostrct remove source_db_name ai )
[target]
- stop and delete the target database (note, if target was running when you disabled against source, it will be in PRE-Transition state and still running)
- stop/remove any cron jobs, utilities that access target database
- delete *.recovery and *.repl.properties (for target)
Once the source database is disabled, the only way to replicate the database again is to re-enable Fathom Replication for both the source and the target databases.