17.9.1 Base table operations (in the case of the cold standby configuration)

(1) Releasing a base table from non-updatable status (in the case of the cold standby configuration)

If hot standby processing occurs while the adbimport command, the adbidxrebuild command, or the adbunarchivechunk command is executing, the target base table becomes non-updatable. If this happens, re-execute the command in the new active system.

If the following file systems can be accessed from both hosts using the same paths, you can resume the processing from the point where it was interrupted when the command is re-executed:

• File system storing the DB directory

• File system storing the input data files that are used in data import processing (applicable to the adbimport command)

• File system storing temporary work files

For details about the non-updatable status of base tables, see 15.8.1 Steps to take when a base table becomes non-updatable.

To Page Top

(2) Operation when using archivable multi-chunk tables (in the case of the cold standby configuration)

Make sure that the archive directory can be referenced using the same absolute path from both the active and standby systems.

For example, when using the distributed file system NFS, use the following procedure to prepare the archive directory:

Procedure:

1. Prepare the NFS server, and then create an archive directory on the NFS server.

2. Export the archive directory you created in step 1.

   Perform this operation on the NFS server.

3. Mount the directory exported in step 2 so that the paths are the same on the active and standby systems.

   Perform this operation on the active system and standby system.

The following figure shows an example system configuration using NFS:

To Page Top