IBM Support

IC84445: IMPORT FROM A REMOTE CLIENT WHERE THE IMPORT FILE IS PROCESSED ON THE SAME CLIENT FAILS WHEN THE FILE HAS EMPTY STRINGS.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When you try to import data from a remote client with the import
    file on the same client, it fails to read the input file if the
    file has empty strings.  If you use the same import file on the
    DB2 server, it completes successfully.
    
    For example,
    
    Import from a remote client, with the input file locally on
    C:\temp.
    
    import from C:\temp\staffexp.txt of DEL insert into db2v97.stff;
    
    SQL3196N  The input file was not found.
    
    If you use the same file on the server:
    When the location of the file on the server(/home/db2v97) is
    given, it correctly imports the data;
    
    
    import from /home/db2v97/staffexp.txt of DEL insert into
    db2v97.stff;
    Total number of rows read : 35
    
    Total number of rows skipped : 0
    
    Total number of rows inserted : 35
    
    Total number of rows updated : 0
    
    Total number of rows rejected : 0
    
    Total number of rows committed : 35
    
    DB250000I: The command completed successfully.
    
    The reason for error is the blank value in the delimited data to
    be imported.
    
    20,"Pernal",20,"Sales",,+78171.25,+00612.45      <- 5th column
    value is blank
    10,"Sanders",20,"Mgr  ",7,+98357.50,,                 <- last
    column value is blank
    

Local fix

  • Use input file on the DB2 server.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 on LUW V10 users.                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 V10 Fixpack 1.                                *
    ****************************************************************
    

Problem conclusion

  • The issue is fixed in DB2 on LUW V10 Fixpack 1.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC84445

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-14

  • Closed date

    2013-01-29

  • Last modified date

    2013-01-29

  • APAR is sysrouted FROM one or more of the following:

    IC81174

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RA10 PSY

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 10.1

Reference #: IC84445

Modified date: 29 January 2013