000012292 - Data Transfer Status on the replica is 'Needs Action' after another replica is attached

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000012292
Applies ToRSA Authentication Manager 7.1.2
RSA SecurID Appliance 3.0
 
IssueTroubleshoot the replica, and resolve the Data Transfer Status error message "Needs Action".
Data Transfer Status is "Needs Action".
Attaching a new replica causes existing replica status to show "needs action".
After attaching a new replica, the Replication Status report shows a previously existing replica as "needs action". The replica was functioning normally before the new replica was attached.
Detaching the failing replica and re-attaching causes the other replica to show "Needs action" in the replication status report.
The system log has events that look like the following examples:
A replication process stopped with an error

The apply process on remote site [server name] is ABORTED
ORA-26714: User error encountered while applying
Error: needs action
CauseThis is a known issue that is addressed in RSA Authentication Manager 7.1 Service Pack 2 Hot Fix Rollup 2 (SP2 HF2), Service Pack 2 Hot Fix Rollup 3 (SP2 HF3), and Service Pack 4 (SP4).
ResolutionData Transfer Status on the replica is "Needs Action" after another replica is attached
To resolve this replication status error, upgrade your RSA Authentication Manager deployment to RSA Authentication Manager 7.1 Hot Fix Rollup 3 and follow the instructions in this article to resolve the replication status error.
Important: After you resolve the replication status error, RSA recommends that you upgrade your deployment to SP4, or to the most current version available. You must resolve the replication status error before you can install SP4, because the SP4 installer does not run the upgrade if the system reports a replication status error.
To resolve this issue:
  1. Call RSA Customer Support (1-800-995-5095 for U.S. customers) and request SP2 Hot Fix Rollup 3.
    Note: Obtain the patch from RSA Customer Support, but do not install it yet.
  2. (Appliances only) Connect to the Appliance using the console or an SSH client. (For remote access using an SSH client, verify in the RSA Operations Console that the Appliance is enabled for SSH connectivity. For more information, see the Operations Console help.) Then log on using the emcsrv account and the Operating System password.
  3. Open a command prompt, and set the current directory to RSA_HOME/utils where RSA_HOME is the RSA installation path.
  4. Enable replication manually on the primary.
    Notes: Do not copy and paste these commands. Also, consider monitoring the alert log as you run these commands to watch the progress.
     
    Appliances and UNIX

    a. Log on as the file owner (for example, rsaadmin), and then set environmental variables. Run:
      . ./rsaenv
    Note: This command begins with a period, space, period, and forward slash.

    b. Run:
      ./rsautil manage-database -a exec-sql -U com.rsa.replication.admin -f diagnostics/apply.sql ?q
    When prompted, enter the master password for the deployment.
    Note: This command begins with a period and forward slash.

    c. Run:
    ./rsautil manage-database -a exec-sql -U com.rsa.replication.admin -f diagnostics/enable-rep.sql -q


    Windows

    a. Log on as the administrator.

    b. Run:
       rsautil manage-database -a exec-sql -U com.rsa.replication.admin -f diagnostics/apply.sql ?q
    When prompted, enter the master password for the deployment.

    c. Run:
      rsautil manage-database -a exec-sql -U com.rsa.replication.admin -f diagnostics/enable-rep.sql -q

  5. Wait several minutes, and check the replication status again. 
Legacy Article IDa49794

Attachments

    Outcomes