DB2 Version 9.7 for Linux, UNIX, and Windows

Migration and version compatibility

The DB2_PARTITIONEDLOAD_DEFAULT registry variable can be used to revert to pre-DB2 Universal Database™ Version 8 load behavior in a multi-partition database.

Note: The DB2_PARTITIONEDLOAD_DEFAULT registry variable is deprecated and may be removed in a later release.

Reverting to the pre-DB2® UDB Version 8 behavior of the LOAD command in a multi-partition database, allows you to load a file with a valid distribution header into a single database partition without specifying any extra partitioned database configuration options. You can do this by setting the value of DB2_PARTITIONEDLOAD_DEFAULT to NO. You may choose to use this option if you want to avoid modifying existing scripts that issue the LOAD command against single database partitions. For example, to load a distribution file into database partition 3 of a table that resides in a database partition group with four database partitions, issue the following command:

   db2set DB2_PARTITIONEDLOAD_DEFAULT=NO

Then issue the following commands from the DB2 Command Line Processor:

   CONNECT RESET
   
   SET CLIENT CONNECT_NODE 3

   CONNECT TO DB MYDB

   LOAD FROM LOAD.DEL OF DEL REPLACE INTO TABLE1

In a multi-partition database, when no multi-partition database load configuration options are specified, the load operation takes place on all the database partitions on which the table is defined. The input file does not require a distribution header, and the MODE option defaults to PARTITION_AND_LOAD. To load a single database partition, the OUTPUT_DBPARTNUMS option must be specified.