ASA SQL User's Guide
  Importing and Exporting Data
    Rebuilding databases

Rebuilding a database involved in replication

To rebuild a database involved in replication

1. Shut down the database.

2. Perform a full off-line backup by copying the database and transaction log files to a secure location.

3. At a command prompt, run dbunload to rebuild the database:

   dbunload -c connection_string -ar directory

   where connection_string is a connection with DBA authority, directory is the directory used in your replication environment for old transaction logs, and there are no other connections to the database.

   The -ar option only applies to connections to a personal server, or connections to a network server over shared memory.

   For more information, see Unload utility options.

4. Shut down the new database. Perform validity checks that you would usually perform after restoring a database.

5. Start the database using any production options you need. You can now allow user access to the reloaded database.

Notes 

There are additional options available for the dbunload utility that allow you to tune the unload, as well as connection parameter options that allow you to specify a running or non-running database and database parameters.

If the above procedure does not meet your needs, you can manually adjust the transaction log offsets. The following procedure describes how to carry out that operation.

To rebuild a database involved in replication, with manual intervention

1. Shut down the database.

2. Perform a full off-line backup by copying the database and transaction log files to a secure location.

3. 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.

4. Rename the current transaction log file so that it is not modified during the unload process, and place this file in the dbremote off-line logs directory.

5. Rebuild the database.

   For information on this step, see Rebuilding databases.

6. Shut down the new database.

7. Erase the current transaction log file for the new database.

8. Use dblog on the new database with the ending offset noted in step 3 as the -z parameter, and also set the relative offset to zero.

   dblog -x 0 -z 137829 database-name.db

9. When you run the Message Agent, provide it with the location of the original off-line directory on its command line.

10. Start the database. You can now allow user access to the reloaded database.