|Applies To||RSA Product Set: SecurID|
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 6.1
Platform (Other): N/A
O/S Version: Other
Product Name: null
Product Description: null
|Issue||Authentication Manager services do not start after restoring the data directory from a tar file. Customer does not have a dump file. Customer created a .tar file of data directory. Customer removed custom extension records to prepare the database for migration. He created a database dump file for migration. After that he restored the data directory by untarring the tar file. RSA services do not start after restoring the files from the tar file.|
The sdconnect start command fails with error "executive permissions missing."
The command sdrepmgmt list gives error: "Replica Management Error Status: Cannot connect to the database.
Another instance of RSA Authentication Manager Replica Management might be running. (61) "
env | grep ace
Refered to Progress articles:
Do you want to continue (y/n) [y]:
Do you want to save/rename the existing database (y/n) [y]:
Creating server database...
SQL Error Message: Last open date mismatch. (9215)
SQL Error Message: Extent /usr/ace/ace/data/sdlog.d1 has a different last opened
date Sun Nov 23 00:24:30 2014, (9213)
SQL Error Message: Control Area has a last open date of Sun Nov 16 06:47:58 2014
SQL Error Message: Probable backup/restore error. (605)
SQL Error Message: Database is damaged, see documentation. (1486)
SQL Error Message: Single-user session end. (334)
Connection Error: Unable to connect to log database. (-1)
Customer tried ./proutil prostrct unlock sdlogd1 referred in Progress article but it did not work.
sdconnect start command fails with error "executive permissions missing".
The creation of newdb takes place but it is complains about the large log database.
|Cause||The backup turned out to have a corrupted AM 6.1 log database, and that prevented the AM 6.1 services from restarting. The corrupted log database was caused by the Solaris tar utility not properly handling files as large as the log database. Further, the tar utility did not exit when it encountered the error, and did not report the error on exiting. The tar file which was created has a corrupt sdlog.d1 log database file. Since files in data directory were restored from a tar file, the services do not start.|
Remove the large sdlog.d1 file from the data directory.