SQL Remote User's Guide
Administering SQL Remote for Adaptive Server Anywhere
Transaction log and backup management
If a database is participating in replication, particular care needs to be taken if you wish to unload and reload the databases.
For instructions for unloading and reloading a database in Upgrading the database file format. The instructions in that section apply to databases involved in SQL Remote replication.
This section describes a manual way of unloading and reloading a database, and is provided in case there are special circumstances that make the use of the more automated procedure referenced above impossible, such as a schema or other significant database change.
Replication is based on the transaction log. When a database is unloaded and reloaded, the old transaction log is no longer available. For this reason, good backup practices are especially important when participating in replication.
To unload and reload a consolidated database (manual)
Shut down the existing database.
Perform a full off-line backup by copying the database and transaction log files to a secure location.
Run the dbtran utility to display the starting offset and ending offset of the database's current transaction log file. Note the ending offset for later use.
Rename the current transaction log file so that it is not modified during the unload process, and place this file in the off-line directory.
Start the existing database.
Unload the database.
Shut down the existing database. This database and any log file created in this and the previous step is no longer needed.
Initialize a new database.
Reload the data into the new database.
Shut down the new database.
Erase the current transaction log file for the new database.
Use dblog on the new database with the ending offset noted in step 3 as the -z option, and also set the relative offset to zero.
dblog -x 0 -z 137829 database-name.db
When you run the Message Agent, provide it with the location of the original off-line directory on its command line.