Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Recover for Db2 13.1.

TABLESPACE specification option

The TABLESPACE option specifies the target table space to be migrated.

The syntax diagram for the TABLESPACE specification is in IMPORT syntax.

Option

Description

TABLESPACE databaseName.tableSpaceName

If you do not specify the TABLESPACE option, all of the table spaces in the migration file will be imported. If you specify the TABLESPACE option, only the specified table spaces will be imported.

  • databaseName is the name of the database containing the table space. The default is DSNDB04. The name cannot be DSNDB01, DSNDB06, DSNDB07, or any database that is defined with TYPE='W' in SYSIBM.SYSDATABASE.
  • tableSpaceName is the name of the table space within the named database. BMCUTIL, BMCSYNC, and BMCXCOPY (tables that are used by BMC utilities) cannot be used.

AUX

The AUX option specifies if auxiliary objects will be included with the migration of the base table spaces.

Important

If you specify the AUX keyword and the related table spaces are not included in the migration file, the migration will fail.

If you do not specify AUX on one of these commands, BMC AMI Recover uses the value of the AUX installation option (AUX-NO), which defaults to NO.

Command

Description

AUX NO

BMC AMI Recover does not include any auxiliary objects in the migration.

AUX ALL

BMC AMI Recover includes XML and LOB objects in the migration.

AUX XML

BMC AMI Recover includes all XML data objects along with the XML base table space. All implicitly created XML table spaces will be processed along with the base XML table space.

AUX LOB

BMC AMI Recover includes all LOB data objects along with the LOB base table space. All table spaces created with the LOB attribute will be processed along with the base LOB table space.

HISTORY

The HISTORY option specifies if history tables should be included in the migration. You must use the AUX keyword to use the HISTORY keyword.

The meaning of the HISTORY keyword depends on which AUX option you specify, as follows:

  • AUX NO HISTORY includes regular tables, system-time base tables, and their related HISTORY tables. It does not include related XML or LOB objects.
  • AUX ALL HISTORY includes regular tables, system-time base tables and their related HISTORY tables, and all related XML or LOB objects.
  • AUX XML HISTORY includes regular tables, system-time base tables and their related HISTORY tables, and all related XML objects.
  • AUX LOB HISTORY includes regular tables, system-time base tables and their related HISTORY tables, and all related LOB objects.

Similar to IBM Db2 RECOVER VERIFYSET NO behavior, BMC AMI Recover does not check that:

  • The system-maintained temporal space and the history space are migrated as a set
  • The system-maintained temporal space and the history space migrate to the same log point
  • All DSNUMs are migrated in the same SYSIN

ARCHIVE

When you specify ARCHIVE, BMC AMI Recover recovers archive-enabled base tables and their related archive tables.

You must specify the AUX option with ARCHIVE to tell BMC AMI Recover whether to include auxiliary XML or LOB objects in the recovery:

  • AUX NO ARCHIVE (or AUX ARCHIVE). It does not include related XML or LOB objects.
  • AUX ALL ARCHIVE includes all related XML and LOB objects.
  • AUX XML ARCHIVE includes all related XML objects.
  • AUX LOB ARCHIVE includes all related LOB objects.

RICHK

RICHK specifies if BMC AMI Recover will check for referential integrity constraints on the objects being recovered.

Value

Description

RICHK YES

RICHK YES checks for referential integrity constraints and sets check pending (CHKP) status for dependent objects not recovered in the same step to the same PIT.

RICHK NO

(Default) RICHK NO does not check for referential integrity.


Related topics

IMPORT-command

Example-14-Simulating-recovery

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*