Resetting the Database Transaction Log for ERSSD

If Replication Agent is running and there are existing routes, you can reset the database transaction log for the ERSSD after you recover from media failure on the log.

ERSSD is an SQL Anywhere database and you must execute the dblog, dbeng11, and dbstop SQL Anywhere commands at the system prompt. See the SQL Anywhere documentation for the command syntax and to set the environment for the commands.

Shut down Replication Server using shut down.
Reset the ERSSD database log at a system prompt:
```
dblog -il erssd_name.db
```
Move the current database log file from the translog directory in Replication Server to another location.
Retain the current log file for a few days in case you encounter problems with the new log file.
Start a new database log file.
For example, in UNIX enter:
```
dblog -t erssd_name.db $SYBASE/REP_15-5/ASA12/translog/erssd_name.log
```
Start the ERSSD database server at the system prompt:
```
dbeng11 erssd_name.db
```
Reset the ERSSD database locator value to 0:
1. Start isql.
2. Execute rs_zeroltm on the ERSSD database:
```
rs_zeroltm erssd_name, erssd_name
```
3. Exit isql.

Stop the ERSSD database at the system prompt:

dbstop -c
“eng=erssd_name;uid=primary_user_name;
pwd=primary_user_password”

Start Replication Server.