000034659 - How to remove an unnecessary scheduler from RSA Authentication Manager 7.1 SP4 on a Windows server

Document created by RSA Customer Support Employee on Jan 10, 2017Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 4Show Document
  • View in full screen mode

Article Content

Article Number000034659
Applies ToRSA Product Set:  SecurID
RSA Product/Service Type:  Authentication Manager
RSA Version/Condition:  7.1 SP4
IssueThis article provides information on how to remove the scheduler from RSA Authentication Manager 7.1 SP4 on Windows.
This is required if the following error is seen:

Long running txn detected

CauseA scheduler present in Authentication Manager is no longer needed once the server is patched to SP4. This scheduler has been found to cause resource issues and replication failures and needs to be removed. An upcoming hot fix will address this, but this can also be accomplished immediately by following the steps below.
Resolution
  1. Login to the primary Authentication Manager server.
  2. Launch the Windows services.msc.
  3. Starting at the top of the list for the RSA Authentication Manager services, stop all RSA services.
  4. When all of the services are stopped, reboot the server.
  5. Wait for all RSA services to come back online, and make sure you can log onto both the Security Console and Operations Console.
  6. Repeat steps 1 - 5 with each replica,  making sure to complete the steps on one replica before moving to the next.
  7. Log in as a local administrator to the primary Authentication Manager server.
  8. Open a command prompt and navigate to RSA_HOME\RSA Security\RSA Authentication Manager\utils.  By default, RSA_HOMEis be C:\Program Files.
  9. Run the command rsautil manage-replication -a pause.  You will be prompted to enter the master password.
  10. Download the IMS_UTILS_PKG.pck file from the RSA SFTP site.
  11. Copy the file ims_utils_pkg.pck to C:\Temp.
  12. Rename the existing IMS_UTILS_PKG.pck file in RSA_HOME\RSA Security\RSA Authentication Manager\utils.  If the file does not exist, then this is a good indication that you are not yet running SP4, although it is also possible that the older file has been deleted.
  13. Move the new file from C:\Temp to ..\utils.  
  14. Issue the following command (notice the requirement to confirm that you wish to execute SQL during the run of the command):
rsautil manage-data -U rep -a exec-sql -f IMS_UTILS_PKG.pck
Enter Master password: <enter master password>
Manage Database ims-2.0.4-build20110222120046
Copyright (C) 2010 RSA Security Inc. All rights reserved.  
%% Running at: myserver.acme.net:[necq3n12]
%% ===========================================  % 
            Execute SQL               
%  ===========================================  
Are you sure you want to execute the SQL file [c:\temp\IMS_UTILS_PKG.pck] ? (Y/N): y
SQL*Plus: Release 10.2.0.5.0 - Production on Fri May 27 11:47:01 2011
Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.
Connected to: .Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - Production
With the OLAP, Data Mining and Real Application Testing options
Package created.
Package body created.
SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - Production
With the OLAP, Data Mining and Real Application Testing options
Done...
bash-3.00$

  1. Repeat steps 8 - 14 with each replica,  making sure to complete the steps on one replica before moving to the next.
  2. From a command prompt on the primary, navigate to RSA_HOME\utils and issue the following command:
rsautil manage-replication -a resume

  1. To ensure all resources are returned and there are no hung processes, it is recommended that the instance be rebooted following this procedure.
Notes

Attachments

    Outcomes