Recovering from RSSD or Replicate Database Failure

If hide_maintuser_pwd is on and the RSSD, ERSSD or replicate Adaptive Server database fails, you may need to reset the maintenance user password after you use a backup to recover from the failure.

Prerequisites

Recover from the RSSD or ERSSD failure. See Recovery from RSSD Failure in the Replication Server Administration Guide Volume 2

Task

If you enable maintenance user password protection, the maintenance user password that was encrypted and stored in the RSSD that you restored from an earlier backup may not match the current encrypted password in the Adaptive Server replicate database. Similarly, the maintenance user password in the replicate Adaptive Server database that you restored may not match the current password in the RSSD. After a restore, you must reset the password before you reenable maintenance user password protection.

Disable maintenance user password protection for all database connections.
```
configure replication server
set hide_maintuser_pwd off
```
Log in with the sso_role privilege to isql at the Adaptive Server replicate database and disable replication:
```
set replication off
go
```
At the Adaptive Server replicate database change the maintenance user password to one that is known to the administrator:
```
alter login maintenance user ID
...
modify password new_maintenance_user_password
...
go
```
Log in to Replication Server and change the password for all connections affected by the change to the maintenance user password to be the same as the password at the database:
```
alter connection to data_server.database
set password [to] new_maintenance_user_password
```
Enable replication. At the primary Adaptive Server database, enter:
```
set replication on
go
```
Enable maintenance user security for all database connections.
```
configure replication server
set hide_maintuser_pwd on
```