Disable Replication and re-establish the replication target baseline:There are other options that can be used instead of having to re-baseline replication after disabling after-imaging. Refer to Article:
Replication: source database does not restart due to error 3773 5350 on ai fileOn the Source Server: 1. Ensure that the RPLS has stopped, then once confirmed, release any pending waits on the source database by entering the following command:
$ dsrutil source -C terminate server
$ dsrutil source -C relwaits
2. Disable Replication online, then delete the
<source>.repl.recovery file:
$ dsrutil source -C DisableSiteReplication source
Note: If the source database is offline, the PROUTIL utility must be used to disable replication:
$ proutil dbname -C DisableSiteReplication source
$ delete the <source>.repl.recovery
3. Disabling the site replication will set all AI files that were marked as LOCKED are now marked FULL. Review the list of AI files then take an OS backup up of all FULL AI files should they be needed later for roll forward operations.
$ rfutil source -C aimage list
4. Disable and re enable After imaging.
$ rfutil dbname -C aimage aioff
$ probkup online dbname <devicename> enableai enableaiarchiver -aiarcdir <archiving directory> - aiarcinterval <n>
Note: If the source database is offline, disable and optionally re-enable offline:
$ rfutil dbname -C aimage end
Then start the database and re-enable online as instructed above or:
$ rfutil source -C mark backedup
$ rfutil source -C aimage begin
5. Enable the database for source replication; online or offline the same command line is used:
$ proutil source -C enableSiteReplication source
6. Take an online backup of the source database to create the target database.
$ probkup online source <device-name> -REPLTargetCreation
At this point:
- Source database activity still proceeds, writing AI transaction notes. As AI files are switched, they will again be set to the LOCKED status. Consider switching on demand as opposed to timed intervals until such time as the replication target database has been restored, started and completed synchronization.
- No further PROBKUP, PROQUIET disable markbackedup or RFUTIL mark backedup must be issued until the replication target database has been restored, started and completed synchronization or this will fail and the target baseline will have to be re-taken.
On the Target Server: 7. Ensure that the target.repl.properties is in the the directory where the target.db will be located. A template can be found in DLC/properties.
If the target database is still running stop it, then remove it:
$ proshut target -by
$ echo y | prodel target
8. Delete the
<target>.repl.recovery file then create the target replication enabled database by restoring the backup created above with the -REPLTargetCreation flag.
$ prorest target <device-file-name>
9. Enable Replication on the target database:
$ proutil target-C enableSiteReplication target
10. Start the target database and agent
$ proserve target-DBService replagent [+params ideally in a pf file]
On the Source Server: 11. If the Replication server has since stopped, re-start it:
$ dsrutil source -C restart server
