IBM Support

IT31247: LOAD HANGS WHEN RUNNING A LOAD FROM CURSOR ON A COLUMN-ORGANIZEDTABLE AND LOAD RECEIVES A -955 AT A PARTICULAR STAGE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a LOAD from cursor is being run on a Column Organized
    table, and LOAD receives a -955 at a particular stage during the
    process from the cursor then LOAD hangs. This defect is to fix
    LOAD from hanging, so that LOAD returns the -955 error
    correctly.
    
    db2diag.log showed that after starting analyze phase, we hit a
    -955 which resulted in LOAD hanging:
    
    YYYY-MM-DD-07.24.13.369328+060 I182299957A625       LEVEL:
    Warning
    PID     : 6685274              TID : 43910          PROC :
    db2sysc 0
    INSTANCE: sample                 NODE : 000           DB   :
    BLUDB
    APPHDL  : 0-1143               APPID: *LOCAL.sample.YYMMDD100813
    AUTHID  : TESTDBM             HOSTNAME: testhost
    EDUID   : 43910                EDUNAME: db2ltfm0 0
    FUNCTION: DB2 UDB, database utilities, sqlulPrintPhaseMsg,
    probe:317
    DATA #1 : String, 110 bytes
    Starting ANALYZE phase at MM/DD/YYYY 07:24:DD.350120.
    
    YYYY-MM-DD-07.31.49.708128+060 I182727785A633       LEVEL: Error
    PID     : 6685274              TID : 251112         PROC :
    db2sysc 0
    INSTANCE: sample                 NODE : 000           DB   :
    BLUDB
    APPHDL  : 0-1143               APPID: *LOCAL.sample.YYMMDD100813
    AUTHID  : TESTDBM             HOSTNAME: testhost
    EDUID   : 251112               EDUNAME: db2agent (BLUDB) 0
    FUNCTION: DB2 UDB, database utilities, sqluReportErrToDiag,
    probe:0
    DATA #1 : String, 110 bytes
     , -955, 0, Detected in file:sqlulxld_fetch.C, Line:274
    
    YYYY-MM-DD-07.31.49.708644+060 I182728419A630       LEVEL: Error
    PID     : 6685274              TID : 251112         PROC :
    db2sysc 0
    INSTANCE: sample                 NODE : 000           DB   :
    BLUDB
    APPHDL  : 0-1143               APPID: *LOCAL.sample.YYMMDD100813
    AUTHID  : TESTDBM             HOSTNAME: testhost
    EDUID   : 251112               EDUNAME: db2agent (BLUDB) 0
    FUNCTION: DB2 UDB, database utilities, sqluReportErrToDiag,
    probe:0
    DATA #1 : String, 107 bytes
     , 0, 0, Detected in file:sqlulxld_fetch.C, Line:794
    
    YYYY-MM-DD-07.31.49.709081+060 I182729050A633       LEVEL: Error
    PID     : 6685274              TID : 251112         PROC :
    db2sysc 0
    INSTANCE: sample                 NODE : 000           DB   :
    BLUDB
    APPHDL  : 0-1143               APPID: *LOCAL.sample.YYMMDD100813
    AUTHID  : TESTDBM             HOSTNAME: testhost
    EDUID   : 251112               EDUNAME: db2agent (BLUDB) 0
    FUNCTION: DB2 UDB, database utilities, sqluReportErrToDiag,
    probe:0
    DATA #1 : String, 110 bytes
     , -955, 0, Detected in file:sqlulxld_fetch.C, Line:795
    
    YYYY-MM-DD-07.31.49.709677+060 I18272968å4A649       LEVEL:
    Error
    PID     : 6685274              TID : 251112         PROC :
    db2sysc 0
    INSTANCE: sample                 NODE : 000           DB   :
    BLUDB
    APPHDL  : 0-1143               APPID: *LOCAL.sample.YYMMDD100813
    AUTHID  : TESTDBM             HOSTNAME: testhost
    EDUID   : 251112               EDUNAME: db2agent (BLUDB) 0
    FUNCTION: DB2 UDB, database utilities, sqluReportErrToDiag,
    probe:0
    DATA #1 : String, 126 bytes
    
    YYYY-MM-DD-07.31.49.710376+060 I182730334A635       LEVEL: Error
    PID     : 6685274              TID : 251112         PROC :
    db2sysc 0
    INSTANCE: sample                 NODE : 000           DB   :
    BLUDB
    APPHDL  : 0-1143               APPID: *LOCAL.sample.YYMMDD100813
    AUTHID  : TESTDBM             HOSTNAME: testhost
    EDUID   : 251112               EDUNAME: db2agent (BLUDB) 0
    FUNCTION: DB2 UDB, database utilities, sqluReportErrToDiag,
    probe:0
    DATA #1 : String, 112 bytes
     , -2145779603, 0, Detected in file:sqluvld.C, Line:12532
    
    (Actual line numbers may vary slightly due to different Db2
    version or fixpack level.)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * all                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1.4.6 or higher                            *
    ****************************************************************
    

Problem conclusion

  • Upgrade to Db2 11.1.4.6 or higher
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT31247

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-12-11

  • Closed date

    2021-03-31

  • Last modified date

    2021-03-31

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

  • 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

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
04 May 2022