IBM Support

PH11973: BIG SQL HEAD NODE CRASHES AFTER SUBMITTING A RUNSTATS COMMAND ON A HADOOP TABLE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • A user incorrectly submits a Db2 RUNSTATS command with the
    TABLESAMPLE SYSTEM clause against a Hadoop table, which leads
    to the head node aborting.  At the client the RUNSTATS
    operation will return the following error:
    SQL2310N  The utility could not generate statistics.  Error
    "-1224" was returned.
    On the head node host in the /var/ibm/bigsql/diag/DIAG0000
    directory an FODC_Trap directory is generated at the time the
    head node crashed.  For example:
    FODC_Trap_2018-12-06-14.47.27.902544_0015
    In this FODC_Trap directory there will be one or trap.txt
    files, for example:
    357523.1675.015.trap. txt
    In this Trap directory you observe a stack trace containing the
    following:
    0x00007F321752E853
    _Z29sqlbGetAdjustedPrefetchAmountP12SQLB_GLOBALSt + 0x0063
                    (/home/bigsql/sqllib/lib64/libdb2e.so.1)
    0x00007F321D404661
    _Z18sqlr_tstat_preheapP8sqeAgentiPhS1_S1_iibP10SQLD_TSTATPiPP16s
    qlrl_stats_colsPPsjPPtjdjdjPmS4_PS4_P8sqlrg_pdiiPPP10SQLD_ISTATt
    tmliPS3_P9SQLD_IDEFS4_S4_S4_S4_PP8sqlrg_idS4_SC_ + 0x5021
                    (/home/bigsql/sqllib/lib64/libdb2e.so.1)
    0x00007F321D40AA8D
    _Z15sqlr_init_tstatP8sqeAgentiPhS1_S1_iiiP16sqlrl_stats_colsPPsj
    PPtjdjdjPmPiPS9_P8sqlrg_pdiiPPP10SQLD_ISTATttmliPP10SQLD_TSTATP9
    SQLD_IDEFS8_b + 0x042d
                    (/home/bigsql/sqllib/lib64/libdb2e.so.1)
    0x00007F321D3C3F99
    _Z17sqlrLocalRunstatsP8sqlrr_cbP11sqlrrstringS2_S2_httPP8sqlrg_p
    diiiiP16sqlrl_stats_colsPPsjPPtjdjdtPP20SQLR_RUNSTATS_RESULTS8_m
    mttjlmP17sqlrlc_stats_infoPKhPKcm + 0x1639
                    (/home/bigsql/sqllib/lib64/libdb2e.so.1)
    0x00007F321D3F7D94
    _Z8sqlrrstaP8sqlrr_cbP11sqlrrstringS2_S2_hhP17sqlrl_stats_parmsP
    KhPs + 0x14e4
                    (/home/bigsql/sqllib/lib64/libdb2e.so.1)
    0x00007F321D47BB96 _Z17sqlrr_runstats_DAP5sqldaP5sqlca + 0x1876
                    (/home/bigsql/sqllib/lib64/libdb2e.so.1)
    0x00007F321B3C4290
    _Z19sqlerKnownProcedureiPcPiP5sqldaS2_P13sqlerFmpTableP8sqeAgent
    P5sqlca + 0x1160
                    (/home/bigsql/sqllib/lib64/libdb2e.so.1)
    0x00007F321B3C68B7 _Z11sqlerCallDLP14db2UCinterfaceP9UCstpInfo
    + 0x1377
                    (/home/bigsql/sqllib/lib64/libdb2e.so.1)
    0x00007F321B66F238
    _Z19sqljs_ddm_excsqlsttP14db2UCinterfaceP13sqljDDMObject +
    0x0618
                    (/home/bigsql/sqllib/lib64/libdb2e.so.1)
    

Local fix

  • The problem can be avoided by not performing the Db2 RUNSTATS
    command on Hadoop tables.  Instead the ANALYZE command as
    documented in the IBM Db2 Big SQL Knowledge Center should be
    used.
    

Problem summary

  • Please see problem description.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PH11973

  • Reported component name

    IBM BIG SQL

  • Reported component ID

    5737E7400

  • Reported release

    503

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-05-09

  • Closed date

    2020-09-09

  • Last modified date

    2020-09-09

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

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

Fix information

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCRJT","label":"IBM Db2 Big SQL"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"503"}]

Document Information

Modified date:
10 September 2020