TARGET

The file name of each of the output files contains the specified database partition number of the target table in the following format: base_filename.target_partition_number. The base_filename is set in the output_file clause. You can use the Db2 Load command on the target database with these output files.

Depending on your approach to repartitioning, you can choose either the KEYS or the TABLE option.

KEYS option parameters

Use the KEYS option to identify the column or columns that will comprise the partitioning key of the target table and the desired database partition numbers in the target table's instance. These values are used when you create the database partition map for the target table. The KEYS option accepts two parameters.

Column list

The column list parameter of the TARGET KEYS option is required and specifies the columns that comprise the partitioning key. You can choose either CURRENT, DEFAULT, or a comma-separated list of column names or numbers.

The CURRENT keyword specifies that the current definition of the partitioning key should be kept. It sets the partitioning key for the target table to the same value or values as the source table that is identified in the fast_select block. If you select CURRENT, you must also ensure that the source table columns that are a part of the partitioning key are included in the corresponding SELECT statement in the fast_select block.

The DEFAULT keyword means that the first valid column in the fast_select block will be the column that is used in the partitioning key. If the first column in the fast_select block is not valid, Optim High Performance Unload will issue an error message and move to the next column until it finds a valid one.

PARTS

The PARTS parameter is optional. It identifies the database partition numbers that are used when Optim High Performance Unload creates a database partition map for the target table. The parameter can take the value for a single database partition, a comma-separated list of database partition numbers, a range (for example, 4:8 includes database partitions 4 through 8), a combination of these options, the keyword ALL or the keyword IN plus a filename. The database partition default is PARTS ALL. If you choose the DEFAULT option with PARTS ALL, the generated database partition map will reflect the list of database partition numbers of the database partition group associated with the table space in which the source table is defined. If you select an explicit list of database partition numbers or use the ALL option, the database partition numbers will be listed in round robin order (for example: 1,2,3,1,2,3,1,2,3,1...). If you select the IN option, you must specify a file location, corresponding to a file which has been generated by the db2gpmap Db2 utility.

"filename"

This required lexeme corresponds to the external file where the partition map definition was extracted with the db2gpmap Db2 utility.

The partition map file can only contain numbers, space characters and carriage return characters. Any other character is not allowed.

This file must be formatted according to the following model:

0 1 2 ... n

or

0
1
2
...
n

This partition map file must not contain unexpected characters and must contain the expected number of entries. To determine the expected number of entries, you have to take into account the Db2 version you are using:

• if Optim High Performance Unload is executed against a Db2 instance which level is at least V9.7, the expected number of values is 32768
• if Optim High Performance Unload is executed against a Db2 instance which level is less than V9.7, the expected number of values is 4096

Syntax

TARGET KEYS (DEFAULT | CURRENT | (column list) [PARTS (ALL) | (database partition list) | IN "filename"])

Variable

column list- The list of column names or numbers.

database partition list- The list or range of partition numbers.

filename-Location of a file generated by the db2gpmap Db2 utility.

Default

No default for column list. ALL if PARTS is not specified.

TABLE option parameters

Use the TABLE option to identify a table to be used as a model that has the partitioning characteristics that you choose. This existing model table does not have to be in the same database, but it must be in the same Db2 instance. This model table must have the same partitioning key and database partition numbers as the intended target table. The parameter is the name of the model table to be used as the database partition map model. Optionally, it can be prefixed with a qualifying schema or creator ID. If this table resides in a different database, it is followed by the keyword IN and the name of the database.

Syntax

TARGET TABLE (model_table)

TARGET TABLE (creator.model_table IN database)

Variables

database, creator, and model_table.

Default

None.