USING specification for IMPORT
USING dataSetName
The USING option is required when you specify the IMPORT command. USING specifies the name of the migration file created by the BMC AMI Copy EXPORT command. The migration file contains migration information for one or more table spaces and index spaces. This information includes object identifiers, copy data set names and other data relating to the target table spaces and index spaces.
Option | Description | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
CHANGE TABLE FROM creator1.tableName1 TO creator2.tableName2 or CHANGE INDEX FROM creator1.indexName1 TO creator2.indexName2 | When the table names or index names are not the same between the source and the target subsystems, use the CHANGE ... FROM ... TO syntax to resolve differences. Each table or index must contain a creator and a name. You can use an asterisk (*) as any portion of the name. You must take care when using wildcard. If the name in the FROM clause does not produce a one-to-one match for all the tables or indexes on the target space, the space is considered unrecoverable. For example, you might want to copy the production payroll tables to the test subsystem, but the creator names between these two subsystems are different. Use the CHANGE TABLE feature to identify table name matches between the two subsystems. The migration file is searched for the FROM table name pattern and is substituted with the TO table name pattern. Multiple CHANGE TABLE FROM ... TO clauses are allowed in a single USING specification. In the following specification, all the tables in the migration file with the creator name of PAYPROD resolve to a creator name of PAYTEST, which matches the tables on the target subsystem. IMPORT USING <dataSetName> CHANGE TABLE FROM PAYPROD.* TO PAYTEST.* | ||||||||||||
EXCLUDE (dbname.ts or qualifier.ix) | The EXCLUDE option in the USING specification excludes one or more objects from the import process. You can use wildcards or specific names to specify the exclusions. The following wildcards are valid:
List the excluded objects following the EXCLUDE keyword. Each item in the list must be in the form dbname.ts or qualifier.ix and you must separate the individual items with commas. Enclose the list in parentheses.
| ||||||||||||
SYNC | The SYNC option indicates if migration should include all spaces in the IMPORT command or only those spaces that have changed since the last migration. SYNC is useful in cases where the image copy indicated by the current EXPORT file is identical to the spaces imported previously.
| ||||||||||||
INDEXES | The INDEXES option specifies how BMC AMI Recover handles indexes when you specify the IMPORT command. (You can also use INDEX or INDEXS instead of INDEXES.)
| ||||||||||||
RESET | The RESET keyword causes the log points in each data page to be reset to '0'. You must specify RESET when you are migrating data from one Db2 non-data-sharing system to another because the log point values on the first subsystem are meaningless or misleading on the target Db2. | ||||||||||||
NOCOPYPEND | The NOCOPYPEND option resets COPY-pending status and issues message BMC96232 to inform you that COPY-pending status has been reset even though the space is not recoverable. You might want to use the NOCOPYPEND option if you are migrating data from one Db2 subsystem to another in a query or testing system where you do not need to be able to run a recovery on the target space. Because the input copy is not registered on the target system, the target space is not recoverable after the IMPORT. You cannot run a RECOVER to current on the target system because no usable copies are registered in SYSCOPY or BMCXCOPY (but you could run IMPORT again). | ||||||||||||
STATS | The STATS option allows you to carry forward existing RUNSTATS from a migration file. These RUNSTATS might then be optionally applied during an BMC AMI Recover IMPORT. To import stats, you must have specified STATS YES in the BMC AMI Copy EXPORT command.
| ||||||||||||
COLSTATS | You can use the COLSTATS option to carry forward existing RUNSTATS column statistics from a migration file and to apply these column statistics during a BMC AMI Recover IMPORT. To import statistics, you must have specified STATS YES COLSTATS YES in the BMC AMI Copy EXPORT command.
| ||||||||||||
MATCHING | The MATCHING option controls the logic of IMPORT and MIGRATE processing if the table definitions are not the same for the source and target subsystems.
For more information about what data types are compatible, see the "IBM SQL Reference" for ALTER TABLE, SET DATA TYPE, and Data Type Compatibility for Assignments and Comparisons table. | ||||||||||||
DEFNOSRC | The DEFNOSRC option specifies whether BMC AMI Recover should reset the target space so that it is empty. This option works only if the source table space was created with the DEFINE NO attribute and is not yet populated.
| ||||||||||||
UPDMAXASSIGNEDVAL | The UPDMAXASSIGNEDVAL option specifies whether BMC AMI Recover updates the MAXASSIGNEDVAL column in the SYSIBM.SYSSEQUENCES catalog table for identity columns.
| ||||||||||||
UPDXMLVER (BMC.DB2.SPE2310) | This option specifies whether BMC AMI Recover should update the catalog and DBD information for a target XML Tablespace when a version mismatch is detected during an IMPORT operation. Valid values are as follows:
|