INZU756E THE SET OF OUTPUT FILES IMPLIED BY THE EXECUTION SPECIFIED IS NOT COMPATIBLE WITH A SUBSEQUENT EXTERNAL TABLE CREATION (REASON CODE n).

An Optim™ High Performance Unload execution has been submitted with the EXTERNAL output format, in order to prepare a subsequent Db2® external table creation. The creation of such a table can be based on, either a unique data file, or a set of data files following the naming convention appropriate for a data distribution at the Db2 level (a single radix, and an extension with a period and a 3-digit number). For the current execution, the data unload task is specified so that the data is going to be split into several files. But the set of generated output files would not be suitable for the creation of an external table, because their names would not follow the expected naming convention mentioned above. Various conditions may lead to such a situation, each one being addressed by its specific reason code:

• reason code 1: the OUTFILE clause contains the use of the %{listValDir} or %{listValFile} template keyword.
• reason code 2: the OUTFILE clause contains a comma-separated list of files.
• reason code 3: the OUTFILE clause as it is specified implies the creation of output files which names refer to partition numbers. But these names are not suitable because:
  • either the unique mention of the partition numbers is not at the appropriate location or is not well formatted in these names,
  • or there are two mentions of partition numbers implied by two associated template keywords, the %{source_node} one and the %{target_node} one which might be implicitly added because data repartitioning is enabled.