000020367 - How to reload database from dump file on a Nominated Replica preserving the port numbers

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 Number000020367
Applies ToRSA ACE/Server 5.1 (no longer supported as of 7-14-2006)
UNIX (AIX, HP-UX, Solaris)
Microsoft Windows
IssueHow to reload database from dump file on a Nominated Replica preserving the port numbers
Primary Server that has been nominated previously not communicating to Replica Servers
CauseLoading the database from a dump file will reconfigure the current host as replica 0 at the base replication port securidprop_00
ResolutionTo preserve the existing Replica Table, use the -a option (i.e. sdload -s -a).

NOTE: Using the -a option will not verify any of the existing data in the database while loading. Using the -a option incorrectly can render an ACE/Server Realm non-functioning. Never use this option when moving the ACE/Server Primary to a different server. When reloading a Replica Server it is strongly recommended that a new Replica Package be generated on the Primary Server and applied to the Replica Server.

To carry out the following procedure, you must have a dump file generated on the current Primary, and the server must have been a Primary Server at the time the dump file was generated.

To rebuild a Primary Server that was not the original Primary, follow these steps:


On UNIX:

1. Reinstall the ACE/Server software on the system if the original software installation was corrupted. If only the database is corrupted, run sdnewdb and create a new server database.

2. Change directory to where the sdserv.dmp file is located

3. Run "sdload -s -a" providing the path to ace/prog/sdload as needed

4. If the dmp file has a different license record use the -k option as well (i.e. sdload -s -a -k license.rec)

5. Run "sdrepmgmt list" to verify the Replica numbers and Service Port numbers are correct

NOTE: If you do not have a dump file from the current Primary or you want to re-sequence the Replica Table so the Primary is Replica 0 , use the -r option instead.


On Windows:

1. Reinstall the ACE/Server software on the system if the original software installation was corrupted. If only the database is corrupted, run sdnewdb and create a new server database.

2. Open a command prompt (run cmd) to execute the following commands

3. Change directory to where the sdserv.dmp file is located

4. Run "sdloadsrv -s -a" providing the path to ace\prog\sdload if needed

5. If the dmp file has a different license record use the -k option as well (i.e. sdload -s -a -k license.rec)

6. Run "sdrepmgmt list" to verify the Replica numbers and Service Port numbers are correct

If you do not have a dump file from the current Primary or you want to re-sequence the Replica Table so the Primary is Replica 0 , run the sdload gui which defaults to using the recovery option.
WorkaroundLoaded Primary server database from a dump (.dmp) file
Legacy Article IDa16218

Attachments

    Outcomes