Converting Existing Replication Settings to RACLI Management
If replication was established with Recovery Appliance 21.1 or earlier with DBMS_RA commands, modifications to the configuration typically need to be performed with DBMS_RA unless you convert to RACLI (available Recovery Appliance 23.1 or later.) This requires two operations.
Add the partnership between the two Recovery Appliances. This only needs to be run on one Recovery Appliance.
racli add ra_partner --target_host=<RA2> --partner_user=NAME --partner_uid=UID
--admin_user=REPL_ADMIN_NAME --admin_key=VALUE
Enable RACLI to perform subsequent replication management.
racli enable replication_management --target_host=<RA2> FQDN
[--type=bidirectional] [--certificates=LIST]
This command migrates the original replication wallet to a new Orapki wallet and prompts the user for the new password for this wallet.
This retrieves the existing replication user, replication role, and replication server information from existing tables and updates metadata tables using the Recovery Appliance partner user. If a replication wallet doesn't exist, this creates a new replication wallet with “orapki”
type to accept certificate in the future. Replication parameters are updated accordingly.
After this conversion, replication is managed by RACLI and the Recovery Appliance partner user.