When there is a schema change or other significant database change, you may need to perform a manual unload and reload.
For version 16 databases, you must have the following system privileges:
VALIDATE ANY OBJECT
SELECT ANY TABLE
Follow the standard precautions for upgrading software. See Upgrade and rebuild precautions.
Stop all database activity.
Perform a successful synchronization and validate and back up the remote database.
Run the dbtran utility to display the starting offset and ending offset of the database transaction log. Make note of the ending offset.
Rename the transaction log to ensure that it is not modified during the unload process. Move the renamed log file to a secure location, such as an offline directory.
Unload the database, without using any of the dbunload -a switches to automatically reload the database into another database.
Initialize a new database.
Reload the data into the new database using dbisql to read the reload.sql file generated by dbunload.
Shut down the new database.
Erase the new database's transaction log.
Run dblog on the new database, using the following options:
dblog -x 0 -z 137829 database-name.db
Start dbmlsync, specifying the location of the original log file that you moved earlier.
See dbmlsync syntax.
When you no longer need the old log file, set the database option delete_old_logs.
Discuss this page in DocCommentXchange.
|Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0|