How DB-Push Works.
Originally Published: 2000-11-13
Last Modified: 2023-10-06
Article Number
Applies To
UNIX (AIX, HP-UX, Solaris)
Microsoft Windows NT 4.0
Microsoft Windows 2000 Server
Issue
Resolution
A copy of the Primary server database will be pushed to the Replica through the _acesyncd process or replication engine. The Replica will then shutdown automatically and restart using the new database. You may have to wait one full replication delay cycle (default 100 seconds) for the Replica to restart. The replica cannot be manually restarted at this point. If you do not wait for the process to restart automatically, use the following solution to recover: How to start RSA ACE/Server Replica after DBPUSH fails
You should not open an administration or logmonitor process on the Replica during the DB-Push evolution. If a DB-Push is not successful, the ACE/Server authentication engine or _aceserver processes will not be able to restart on the Replica. 'Sdconnect start', or the startup of the brokers, is successful on the Replica. 'Aceserver start' results in no additional processes running on the Replica.
The Primary and Replica should be able to replicate or synchronize after a successful DB-Push. For more information, see the solution How to tell the Primary and a Replica are synchronizing in RSA ACE/Server and RSA Authentication Manager.
Related Articles
Safely backout of a failed configuration push in RSA Web Threat Detection Number of Views How to troubleshoot RSA Authenticator app push authentications Number of Views Some OOTB App Metadata Collector fields are missing in the Application table options in RSA Identity Governance & Lifecyle Number of Views Unable to create attribute change rule with RSA Identity Governance and Lifecycle 6.9.1P08 or later when the condition use… Number of Views How to recreate a replica package set for push in RSA ACE/Server Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Unable to login to RSA Authentication Manager Security Console as super admin RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Governance & Lifecycle 8.0.0 Installation Guide Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6
Don't see what you're looking for?
