Using the special dump transaction options

Using the special dump transaction options

In certain circumstances, the simple model described above does not apply. Table 11-1 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 in Table 11-1. 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.

**Table 11-1: 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

Table 11-1: 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