Optim High Performance Unload for Db2 for Linux, UNIX and Windows - Must-gather information

The entire execution report of the failing scenario, showing:

 1.) Command line used to run db2hpu

 2.) Product version

 3.) Platform

4.)  Memory limits

5.) Control file

6.) Error messages

7.) db2hpu.cfg configuration file

8.) db2nodes.cfg file for the Db2 instance

9.) DDL for the table

Additional information might be required for further analysis

Traces generation and collection

 Trace files generated with the --debug and --traces options added into the command line

•  The --traces option enables trace generation

•  The --debug option enables extra trace information

 Trace file names are of the pattern $*_<pid>

 Files generated in the directory where the task is submitted from

 Trace file generated on each machine involved

Network service log file

 Set into the network service configuration

•  On Linux, into the file which name is the associated service name (value set to the ‘netservice’ configuration parameter), located into the /etc/xinetd.d directory

•  On AIX and Solaris, into the /etc/inetd.conf file, in the entry which name is the associated service name (value set to the ‘netservice’ configuration parameter)

•  Log levels set at the same location: its value can be set to a maximum of 7 in order to get more logging details

Installation traces

 Located into the ‘install’ subdirectory of the root installation directory

1.  ‘trace_install’ file: contains logging information for the installation process

2.  ‘trace_warning_install’ file: contains logging information for warning level occurred during the installation

3.  ‘trace_error_install’ file: contains logging information for error level occurred during the installation