Internal replication error occurs after AM8.6 upgrades
Last Modified: 2023-10-06
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.6
Issue
(e.g.)
Cause
Resolution
Workaround
2. Check the replication, if it failed with the related to trusted root certificate (e.g. cert_RADIUS-Root-Cert.der), then login to the database on each REPLICA, run like this command:
delete from ims_certificates where name='cert_RADIUS-Root-Cert.der' and purpose ='RADIUS_TRUST_CERT' and ref_id ='NULL';
3. Then login to PRIMARY database, run this sql:
update RSA_REP.IMS_INSTANCE set deployed_state='out_of_sync' where is_primary='FALSE';
4. Then you should be able to synch the primary to replica in OC.
Notes
You can see the similar messages into ReplicaReplication.log.
| Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "uk_ims_certificates" Detail: Key (name, purpose, ref_id)=(cert_RADIUS-Root-Cert.der, RADIUS_TRUST_CERT, NULL) already exists. |
Related Articles
Replication Showing Internal Replication Error During Upgrade to RSA Authentication Manager 8.2 1.02KNumber of Views Replication Status 253Number of Views AM 8.1 Replication Error Internal Replication Error Shows up under the primary OC instance status 1.34KNumber of Views Radius Servers Replication Status "Cannot determine Status" 294Number of Views Changing replication status to Out of Sync for RSA Authentication Manager 8.2 or later with a script (Script attached) 2.57KNumber of Views
Trending Articles
How to Change the Token Lifetime Extension Window in Authentication Manager Using rsautil RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA Authentication Manager Upgrade Process RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to Download OTP Token Seed Files from myRSA
Don't see what you're looking for?