IBM Support

IT12568: DB2 INSTANCE MAY ABEND WHEN CREATING COMPOUND STATEMENTS CONTAINING LIKE PREDICATES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • DB2 might terminate abnormally while
    creating a compound statement containing multiple like
    predicates.
    Problem is more likely to happen on 9.7 FP11, 10.1 FP5, and 10.5
    FP7
    An example stack trace seen in this scenario appears below:
    
    Stack Trace:
    
    ------FUNCTION------
    ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvmm
    ossDumpStackTraceV98
    OSSTrapFile6dumpExEmiP7siginfoPvm
    sqlo_trce
    sqloEDUCodeTrapHandler
    sqlnq_fcsqclchild2ppEv
    sqlnq_pid9same_nodeEPKS_PiiiP12sqlnq_colmapP11sqlnq_qunpsS6_iPj
    sqlnq_pid9same_treeEPKS_PiiiP12sqlnq_colmapP11sqlnq_qunpsS6_iPj
    sqlnq_pid9same_treeEPKS_PiiiP12sqlnq_colmapP11sqlnq_qunpsS6_iPj
    sqlnq_pid12makeOnceOnlyEP3loc
    sqlnq_encap_like_add_compP3locP9sqlnq_pid11sqlvFuncNumbP12sqlnq_
    stringPh
    sqlnq_encap_doitiP9sqlnq_pidPS0_P12sqlnq_stringPhP3loc
    sqlnq_fun_res_walkP9sqlnq_pidP12sqlnq_stringPhPS0_P3locii
    sqlnq_fun_tresP9sqlnq_pidP12sqlnq_stringPhPS0_P3locii
    sqlnq_prdC1EP9sqlnq_oprP9sqlnq_pidP17sqlnn_dat_TYPTYPEP12sqlnq_s
    tringPhRiP3locbb
    sqlnq_sem_wherePP8stknode_i10actiontypePhP3loc
    sqlnp_smactnP8sqlnp_cbi
    sqlnp_parserP8sqlnp_cb
    sqlnp_mainP12sqlnq_stringbP3locPP9sqlnq_qur
    sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sqlrr_
    cmpl_enviiPP9sqlnq_qur
    sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sqlrr_
    cmpl_env
    sqlra_compile_varP8sqlrr_cbP14sqlra_cmpl_envPhitiiiiiP14SQLP_LOC
    K_INFOP16sqlra_cached_varPiS5_Pb
    sqlra_find_varP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idjjPhj
    thP14sqlra_cmpl_env15sqlra_fill_modePiiS8_iiiS8_P14SQLP_LOCK_INF
    OPP16sqlra_cached_varS8_bSA_Pb
    sqlra_get_varP8sqlrr_cbiibPbS1_
    sqlri_ddl_get_sectionP8sqlrr_cb
    sqlri_ddl_commonP8sqlrr_cb
    qlriddlP8sqlrr_cb
    sqlriExecThreadP8sqlrr_cbP12sqlri_opparm
    sqlriSectInvokeP8sqlrr_cbP12sqlri_opparm
    sqlrr_execute_immediateP8sqlrr_cbi
    sqlrr_execimmdP14db2UCinterfaceP16db2UCprepareInfo
    sqljs_ddm_excsqlimmP14db2UCinterfaceP13sqljDDMObject
    sqljsParseRdbAccessedP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UCint
    erface
    sqljsParseP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb
    sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T
    sqeAgent6RunEDUEv
    sqzEDUObj9EDUDriverEv
    sqlzRunEDUPcj
    sqloEDUEntry
    __clone
    
    In db2diag.log:
    2015-10-27-02.37.56.029312+060 I1443623E622          LEVEL:
    Severe
    PID     : 1573                 TID : 139864167147264 PROC :
    db2sysc 0
    INSTANCE: db2inst1             NODE : 000            DB   :
    ibmdb
    APPHDL  : 0-19                 APPID:
    *LOCAL.db2inst1.151026101731
    AUTHID  : DB2INST1             HOSTNAME: ibmtst
    EDUID   : 26                   EDUNAME: db2agent (MDSP1141) 0
    FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc,
    probe:250
    RETCODE : ZRC=0x87120007=-2028863481=SQLR_SEVERE_PGM_ERROR
              "Severe programming error"
              DIA8516C A severe internal processing error has
    occurred.
    

Local fix

  • No Local Fix.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 10.5 FP8                                      *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT12568

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A50

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-12-03

  • Closed date

    2017-01-11

  • Last modified date

    2017-03-22

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

    IT12567

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

Fix information

Applicable component levels

  • RA50 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":"10.5","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
13 January 2022