User's Manual

Upgrading consolidated databases
This section describes issues in upgrading a consolidated database in a
SQL Remote environment. The same considerations apply to Adaptive
Server Anywhere databases that are primary sites in a Sybase Replication
Server installation.
Installing new software does not always make new features available. In
many cases, new features require the Upgrade utility to be run on databases.
The Upgrade utility adds any information to the system catalog required for
new features to be available. When you run the Upgrade utility, it tells you
to archive the transaction log. The reason for this is that a new transaction
log is created by the Upgrade utility, with a new file format.
When using SQL Remote or Replication Server, the transaction log must be
kept for the Message Agent and the Replication Agent, respectively. After
running the Upgrade utility, you should shut down the engine, rename the
log, and leave it for the Message Agent to delete. The log should also be
archived for backup purposes.
☞ For information on the Upgrade utility, see “The Upgrade utility” [ASA
Database Administration Guide, page 599].
Unloading and reloading a database participating in replication
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” [What’s New in SQL Anywhere Studio, page 230]. 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.
258