IBM Support

Collecting data for Unexpected Errors in InfoSphere Federation Server

Question & Answer


Question

What information should be collected when I experience an unexpected error with my software? Collecting this information before calling IBM support will help you understand the problem and save time analyzing the data.

Answer

1. Exact name of product installed by issue this command and operating system command prompt:
db2licm -l

2. Current version of DB2 engine level. Enter the following from an operating system command prompt:
   db2level

3. The operating system type, and release, where Federation Server is installed.
On UNIX/Linux, enter the following from an operating system command prompt:
   uname -a

    For AIX, also run below command:
    oslevel -s

    For Linux, provide the vendor/flavor/release too
    - On SuSE Linux, enter:
        cat /etc/SuSE-release
    - On RedHat Linux, enter:  
        cat /etc/redhat-release

On Windows, right click on "My Computer", then select the Properties option.

4. What is the data source used? Provide data source client and server exact release and version.
Examples commands:
    DB2 for LUW
    Enter the following from an operating system command prompt:
    db2level

    Informix
    Enter following from an operating system command prompt:
    cd $INFORMIXDIR/bin
    ./ifx_getversion clientsdk
    ./ifx_getversion libasf.a
    ./ifx_getversion libasf.so

    Oracle
    Enter the following from an operating system command prompt:
    cd $ORACLE_HOME/bin
    ./sqlplus

    Microsoft SQL Server
    Issue the following SQL statement (from the Microsoft Query Analyzer):
    select @@version

    IBM Branded DataDirect ODBC driver
    Go to directory <IBM_branded_odbc_install_dir>/bin and execute below command:
    ddtestlib <libname>

    For example:
    i) Get ODBC driver manager version:
    ddtestlib <IBM_branded_odbc_install_dir>/lib/odbc.so

    ii) Get Microsoft SQL Server ODBC driver version:
    ddtestlib <IBM_branded_odbc_install_dir>/lib/VMmsss23.so


    Sybase
    sybase client version:
    Go to directory $SYBASE/$SYBASE_OCS/bin and execute below command:
    isql -v

    Sybase server version:
    Issue the following SQL statement after connecting database using isql command:
    select @@version
    go

    Teradata
    Start DWB
    issue get version command

5. Have there been any recent changes to your environment (hardware, operating system, software version)?

6. Has this problem occurred before? If yes, do you have a previous PMR number?

7. How often does this problem occur?

8. Can the problem be reproduced? If so, provide exact details of the setups and steps performed when problem encountered.
a. DDLs for the remote tables on datasource
b. Samples of data in remote tables if it's data related
c. Federation objects definitions:
db2look -d <dbname> -e -o <output_filename> -fedonly
d. Operations that trigger the error and exact error output


9. Please run following commands to collect db2support and db2trace data:
    a. db2support <output_path> -d <db name> -cl 0
    b. db2trc on -f trace.trc # turn on tracing and trace all components
    <Run command that recreate the error>
    db2trc off # turn off tracing
    db2trc flw trace.trc trace.flw # format the trace flow diagram into file trace.flw
    db2trc fmt trace.trc trace.fmt # format the trace data into file trace.fmt
    db2trc fmt -c trace.trc trace.fmc # format the trace data into file trace.fmc if DRDA wrapper

10. Provide <db2_install_path>/sqllib/cfg/db2dj.ini file
    For ODBC and Microsoft SQL Server data sources, please provide your odbc.ini file and ODBC trace.
To enable ODBC trace, please refer to the following links:
On Unix:
    Refer to <odbc_driver_install_path>docs/odbcdiag/odbcdiag.pdf Chapter "ODBC Trace".
On Windows:
11. Is this a production, development, or test environment?

12. What is the business impact of this problem?
Examples:
    a. Cannot roll out a new application
    b. Cannot monitor in-store security systems
    c. Losing money due to applications not talking to each other

13. Zip, or compress, all files and rename with PMR number as prefix before submitting ; example 12345.678.999.files.zip.

Submitting information to IBM Support

Once you have collected your information, you can begin Problem Determination through the product Support web page, or simply submit the diagnostic information to IBM support. Use the URL below for submitting information to IBM Support.
http://www.ecurep.ibm.com/app/upload

For a listing of all technotes, downloads, and educational materials specific to the InfoSphere® Federation Server component, search the product support site at the following link : http://www-01.ibm.com/software/data/infosphere/support/federation-server/

[{"Product":{"code":"SS2K5T","label":"InfoSphere Federation Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"General Issues","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.7;10.1;10.5","Edition":"All Editions","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 June 2018

UID

swg21441924