IBM Support

IT29545: DB2 MIGHT TRAP OR FAIL WITH SQL0901 DURING THE ACCESS TO BLU TABLES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Db2 might trap or fail with SQL0901 and one of the following
    db2diag.log messages:
    
    First message:
    
    2019-06-20-05.08.09.143898-300 I138709293E891        LEVEL:
    Severe
    PID     : 24439                TID : 140572983551744 PROC :
    db2sysc
    INSTANCE: db2inst1               NODE : 000            DB   :
    MYDB1
    APPHDL  : 0-29442              APPID:
    *LOCAL.db2inst1.180130145331
    AUTHID  : db2inst1               HOSTNAME: MYHOST1
    EDUID   : 10541                EDUNAME: db2agent (MYDB1)
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc,
    probe:250
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
     sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 30
     sqlerrmc: Invalid cdeInterface detected!
     sqlerrp : SQLRI3D4
     sqlerrd : (1) 0x00000000      (2) 0x00000000      (3)
    0x00000000
               (4) 0x00000000      (5) 0xFFFFFCE9      (6)
    0x00000000
     sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)
               (7)      (8)      (9)      (10)        (11)
     sqlstate:
    
    Second message:
    
    2019-06-20-15.04.31.054734-300 I225944383E1836       LEVEL:
    Severe (Origin)
    PID     : 64560                TID : 140425495045888 PROC :
    db2sysc 0
    INSTANCE: db2inst1               NODE : 000            DB   :
    MYDB1
    APPHDL  : 0-146                APPID:
    127.0.0.1.39445.171213195637
    AUTHID  : db2inst1               HOSTNAME: MYHOST1
    EDUID   : 2799                 EDUNAME: db2agnts (MYDB1) 0
    FUNCTION: DB2 UDB, CDE Trace, cdeDiagnosticsFacility, probe:3620
    MESSAGE : SQL0901N  The SQL statement or command failed because
    of a database
              system error. (Reason "".)
    DATA #1 : <preformatted>
    'mScheduler != 0' failed. Info:mScheduler is null
    CALLSTCK: (Static functions may not be resolved correctly, as
    they are resolved to the nearest symbol)
      [0] 0x00007FCB8C53175D pdLogPrintf + 0x8D
      [1] 0x00007FCB8CE9A003
    _ZN7ibm_cde8services24AssertionFailedException4doneEv + 0x773
      [2] 0x00007FCB8CE9D689
    _ZN7ibm_cde8services24AssertionFailedException17constructAndThro
    wENS0_11ComponentIDEPKcmS4_S4_RNS0_16CdeOStringStreamE + 0x149
      [3] 0x00007FCB8F637F75
    _ZN12cdeInterface11openFetcherEP8sqlrr_cbR17cdeIteratorHandle +
    0x5B5
      [4] 0x00007FCB92D24E73
    _Z12sqlriCdeOpenP8sqlrr_cbP17sqlriCdeStatement + 0x1B3
      [5] 0x00007FCB92D248D7 _Z13sqlriCdeQueryP8sqlrr_cb + 0x297
      [6] 0x00007FCB92DAD5EB
    _Z15sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm + 0x49B
      [7] 0x00007FCB927ED0FD
    _Z21sqlrr_subagent_routerP8sqeAgentP12SQLE_DB2RA_T + 0xDAD
      [8] 0x00007FCB904EAE07
    /home/perfpol2/sqllib/lib64/libdb2e.so.1 + 0x59E9E07
      [9] 0x00007FCB904E9850 _Z21sqleProcessSubRequestP8sqeAgent +
    0x3E0
      [10] 0x00007FCB9051CF77 _ZN8sqeAgent6RunEDUEv + 0x5D7
      [11] 0x00007FCB93BCC446 _ZN9sqzEDUObj9EDUDriverEv + 0x116
      [12] 0x00007FCB921BFD98 sqloEDUEntry + 0x578
      [13] 0x00007FCB99CD0806 /lib64/libpthread.so.0 + 0x7806
      [14] 0x00007FCB8968564D clone + 0x6D
    
    Third message:
    
    2019-06-20-23.47.28.859689-240 I478043033E631        LEVEL:
    Severe
    PID     : 3528                 TID : 140327755179776 PROC :
    db2sysc 0
    INSTANCE: db2inst1               NODE : 000            DB   :
    MYDB1
    APPHDL  : 0-219                APPID:
    127.0.0.1.45187.190416181104
    AUTHID  : db2inst1               HOSTNAME: MYHOST1
    EDUID   : 2198                 EDUNAME: db2agntcol (MYDB1) 0
    FUNCTION: DB2 UDB, runtime interpreter, sqlriSectInitializeSMP,
    probe:4566
    MESSAGE : SQL0901N  The SQL statement or command failed because
    of a database
             system error. (Reason "".)
    DATA #1 : String, 30 bytes
    Invalid cdeInterface detected!
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT29545

  • 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-06-25

  • Closed date

    2020-01-16

  • Last modified date

    2022-03-29

  • 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:
03 May 2022