How DB-Push Works.
Originally Published: 2000-11-13
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
The ntpq command gives the error "Request timed out" in RSA Authentication Manager Number of Views XudaJurisdictionGetCA() call returns XrcNOTFOUND even though the CA object exists Number of Views Resynchronize a Token Number of Views Prompt Authenticate Tokencode Users for PINs on Their First Authentication to Cloud Access Service Number of Views Set User Expectations for Device Registration and Authentication Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?
