Upgrading a User Database

You can load dumps into the current version of SAP ASE from any version of SAP ASE that is at version 11.9 and later. The loaded database is not upgraded until you issue online database.

Use load database to load a database dump. load database sets the database status to “offline.”
Use load transaction to load, in order, all transaction logs generated after the last database dump. Load all transaction logs before going to step 3.
Use online database to upgrade the database. The online database command upgrades the database because its present state is incompatible with the current version of SAP ASE. When the upgrade completes, the database status is set to “online,” which makes the database available for public use.
Make a dump of the upgraded database. A dump database must occur before a dump transaction command is permitted.

See the Reference Manual: Commands.

Occasionally, performing the steps described above does not apply.

The table below describes when to use the special with no_log and with truncate_only options instead of the standard dump transaction command.

Warning! Use the special dump transaction commands only as indicated below. In particular, use dump transaction with no_log as a last resort and use it only once after dump transaction with no_truncate fails. The dump transaction with no_log command frees very little space in the transaction log. If you continue to load data after entering dump transaction with no_log, the log may fill completely, causing any further dump transaction commands to fail. Use alter database to allocate additional space to the database.

When to use dump transaction with truncate_only or with no_log
When	Use
The log is on the same segment as the data.	dump transaction with truncate_only to truncate the log dump database to copy the entire database, including the log
You are not concerned with the recovery of recent transactions (for example, in an early development environment).	dump transaction with truncate_only to truncate the log dump database to copy the entire database
Your usual method of dumping the transaction log (either the standard dump transaction command or dump transaction with truncate_only) fails because of insufficient log space.	dump transaction with no_log to truncate the log without recording the event dump database immediately afterward to copy the entire database, including the log