Recovering After Media Failure of the Database File

You can recover the ERSSD database file.

1. Make an extra backup copy of the current transaction log. If the database file is gone, the only record of changes since the last backup is in the transaction log.
2. Create a recovery directory to hold the files you use during the recovery process.
3. Copy the database file from the last full backup to the recovery directory. You can find the database file in the backup directory. It is named erssd_name.db.
4. Copy the backup transaction log into the recovery directory. The backup transaction log, named erssd_name.log, is in the backup directory.
5. Apply the transactions from the backup transaction log to the recovery database:

   dbsrv16 erssd_name.db -a erssd_name.log

6. Copy the online transaction log into the recovery directory. The online transaction log, named erssd_name.log, is in the log directory.
7. Apply the transactions from the online transaction log to the recovery database:

   dbsrv16 erssd_name.db -a erssd_name.log

8. Make a post-recovery backup by making an extra copy of the database file.
9. Move the database file to the production directory and restart the database. Use the command dbspawn from the Replication Server error log.
10. (Optional) Issue these commands if the location of the post-recovery Replication Server differs from the location of the pre-recovery Replication Server:

    dblog -t <fully_qualified_directory>erssd_name.log <fully_qualified_directory>erssd_name.db
    dblog -m <fully_qualified_directory>erssd_name.mlg <fully_qualified_directory>erssd_name.db

11. Perform validity checks on the recovery database:

    dbvalid -c 
    "uid=primary_user_name;
    pwd=primary_user_password;eng=erssd_name;
    LINKS=tcpip
    (DOBROAD=NONE;HOST=localhost;PORT=port)"

12. Restart Replication Server.