In this mode, database update logs are not collected after an RDAREA is updated, so processing time is reduced by a comparable amount of time, which reduces UAP or utility execution time (as compared with execution in the log acquisition mode).

This is the default mode; we recommend that you use it when the database load utility or database reorganization utility is executed.

(a) Back up any updated RDAREAs after you execute the UAP or utility

If the system log information used as input by the pdrstr command for recovery of an RDAREA includes any logs that were collected in the pre-update log acquisition mode, the pdrstr command will result in an error. Consequently, unless you back up the RDAREA before executing the UAP or utility, you will not be able to recover that RDAREA to its most recent status, if the need arises to do so (with the pdrstr command). This means that you will not be able to restore updates that occurred after the UAP or utility executed; you will only be able to restore the RDAREA to its status before the UAP or utility executed.

(b) Ensure no other users can update the RDAREA you are updating

Assume that tables T1 and T2 are stored in RDAREA1, table T1 is updated in the pre-update log acquisition mode and table T2 is updated in the log acquisition mode. If the need arises to recover RDAREA1 with the pdrstr command, it will not be possible to restore this RDAREA to its most recent status because the pdrstr command can only recover table T1 to a synchronization point prior to the updating. This is because execution of the pdrstr command results in an error if the system log information used for input includes any logs collected in the pre-update log acquisition mode.

Therefore, before executing a utility, use the pdhold command to place the RDAREA to be updated on hold. For a UAP, do not update an RDAREA that might be updated by other users.

(a) Executing the database reorganization utility in the pre-update log acquisition mode

For details about using the database reorganization utility in the pre-update log acquisition mode, see 13.2.3 Selecting an update log acquisition mode for a database and 13.3 Reorganizing a table (examples).

(b) Executing a UAP that updates a user LOB RDAREA in the pre-update log acquisition mode

The following is the procedure for executing a UAP that updates a user LOB RDAREA in the pre-update log acquisition mode.

Procedure

1. Execute a UAP that updates a user LOB RDAREA in the pre-update log acquisition mode.
2. Use the pdlogswap -d sys -w command to swap the system log files.
3. Use the pdcopy command to back up the RDAREAs to be updated.
   For details about how to back up RDAREAs, see 6.4.8 Example 8 (backing up specified RDAREAs).