000025720 - Error: 'Error running sdrepmgmt. Unable to connect to database. A replica management session may already be running. Only one session at a time is allowed'

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

Article Content

Article Number000025720
Applies ToRSA ACE/Server 5.1 (no longer supported as of 7-14-2006)
Sun Solaris 2.8
Authentication Manager or ACE/Server
IssueError: "Error running sdrepmgmt. Unable to connect to database. A replica management session may already be running. Only one session at a time is allowed"
Unable to run the sdrepmgmt command, Aborting with errExitStatus: 4...
Error: "Unable to connect to log database"
A replica management session may already be running. Only one session at a time is allowed.
sdrepmgmt: Aborting with errExitStatus: 4...
sdrepmgmt error encountered. Aborting procedure
Executing sdrepmgmt list fails
Executing sdrepmgmt add fails
Executing programs (admenv, emergency, repltok, resync, setpin) in the ..../ace/utils/oldutil directory fails
As an example, the shell environment (output of env) show PROPATH being equal to the following:
PROPATH=/opt/ace/prog:/opt/ace/prog/protrig:/opt/ace/prog/progui:/opt/ace/prog/proapi
Causesdrepmgmt list fails because the PROPATH variable is not correctly set
Resolution

The correct PROPATH variable on older versions equals:

PROPATH=/opt/ace/prog:/opt/ace/prog/protrig:/opt/ace/prog/proapi/adbapi.pl:/opt/ace/prog/proapi/sdproapi.pl

To correct this, edit the environment file(s) to reflect the correct PROPATH values for ACE/Server 5.1.

On newer versions, run admenv to find the correct variables, and set them, and export PROPATH

WorkaroundUpgrade from ACE/Server 4.1 to ACE/Server 5.1
Legacy Article IDa15354

Attachments

    Outcomes