IBM Support

JR30491: POSSIBLE INSTANCE ABEND WITH ACCESS VIOLATION WHEN COMPILING A QUERY ON Windows 64 BIT AMD64 or INTEL EM64T V9.1 FP 5 DB2

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A crash may occur on Windows AMD64 or Intel EM64T with db2 v9.1
    Fixpak 5 in 64 bit mode when compiling a query.
    This happens when memory addresses greater than 4GB are in use.
    Some stack tracebacks that have been observed for this apar are
    :
    
    1.
    
      [...]in <sqlno_order_cover> <sqlno_order.C:806>
      [...]in <sqlno_crule_glue_root> <sqlno_crule.C:14670>
      [...]in <sqlno_crule_glue> <sqlno_crule_main.C:3688>
      [...]in  <sqlno_itr_get_plan> <sqlno_get_best.C:488>
      [...]in <sqlno_itr_plan::next> <sqlno_crule_clib.C:1405>
      [...]in <sqlno_crule_simple_mate> <sqlno_crule.C:10216>
      [...]in <sqlno_crule_mate_root> <sqlno_crule.C:10003>
      [...]in <sqlno_crule_mate> <sqlno_crule_main.C:1757>
      [...]in <sqlno_plan_end_opr> <sqlno_scan_plan.C:2166>
      [...]in <sqlno_each_opr> <sqlno_scan_utils.C:958>
      [...]in <sqlno_walk_qun> <sqlno_scan_utils.C:686>
      [...]in <sqlno_each_opr> <sqlno_scan_utils.C:784>
      [...]in <sqlno_walk_qun> <sqlno_scan_utils.C:686>
      [...]in <sqlno_each_opr> <sqlno_scan_utils.C:784>
      [...]in <sqlno_top_qtb> <sqlno_scan_utils.C:647>
      [...]in <sqlno_each_qur> <sqlno_scan_utils.C:595>
      [...]in <sqlno_scan_qgm>
    
    2.
    
      [...]in <sqlno_order_cover> <sqlno_order.C:806>
      [...]in <sqlno_int_order_itr_mgjn> <sqlno_int_order.C:4613>
      [...]in <sqlno_crule_mgjn> <sqlno_crule.C:12333>
      [...]in <sqlno_crule_join_root> <sqlno_crule.C:11697>
      [...]in <sqlno_crule_join> <sqlno_crule_main.C:2196>
      [...]in <sqlno_gen_partitions_for_QTB> <sqlno_scan_plan.C:703>
      [...]in <sqlno_plan_end_opr> <sqlno_scan_plan.C:1816>
      [...]in <sqlno_each_opr> <sqlno_scan_utils.C:958>
      [...]in <sqlno_walk_qun> <sqlno_scan_utils.C:686>
      [...]in <sqlno_each_opr> <sqlno_scan_utils.C:784>
      [...]in <sqlno_walk_qun> <sqlno_scan_utils.C:686>
      [...]in <sqlno_each_opr> <sqlno_scan_utils.C:784>
      [...]in <sqlno_walk_qun> <sqlno_scan_utils.C:686>
      [...]in <sqlno_each_opr> <sqlno_scan_utils.C:784>
      [...]in <sqlno_walk_qun> <sqlno_scan_utils.C:686>
      [...]in <sqlno_each_opr> <sqlno_scan_utils.C:784>
    
    3.
    
      [...]in <sqlno_int_order_push> <sqlno_int_order.C:3338>
      [...]in <sqlno_int_order_qun_add> <sqlno_int_order.C:3131>
      [...]in <sqlno_int_order_get_grby> <sqlno_int_order.C:2044>
      [...]in <sqlno_int_order_get_qtb> <sqlno_int_order.C:294>
      [...]in <sqlno_int_order_get_qtb> <sqlno_int_order.C:294>
      [...]in <sqlno_int_order_scan> <sqlno_int_order.C:205>
      [...]in <sqlno_prep_phase> <sqlno_main.C:1640>
      [...]in <sqlno_exe> <sqlno_main.C:980>
      [...]in <sqlnn_cmpl> <sqlnn_cmpl.C:2881>
      [...]in <sqlnn_cmpl> <sqlnn_cmpl.C:483>
      [...]in <sqlra_compile_var> <sqlra_cmpl.C:962>
      [...]in <sqlra_find_var> <sqlra_dyn.C:3488>
      [...]in <sqlra_get_var> <sqlra_var.C:572>
      [...]in <sqlrr_prepare> <sqlrr_req_sql.C:2639>
      [...]in <sqljs_ddm_prpsqlstt> <sqljspds.C:605>
    

Local fix

  • n/a
    

Problem summary

  • Users Affected : users on Windows AMD64 running 64bit db2 v9.1
    fp5
    Problem summary : crash may occur during query compilation
    Problem conclusion : this apar fix corrects the code and avoids
    the crash
    

Problem conclusion

  • First fixed in DB2 UDB Version 9, FixPak 6
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR30491

  • Reported component name

    DB2 UDB ESE WIN

  • Reported component ID

    5765F4101

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-09-15

  • Closed date

    2008-11-03

  • Last modified date

    2010-02-24

  • 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 UDB ESE WIN

  • Fixed component ID

    5765F4101

Applicable component levels

  • R910 PSY

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

Document Information

Modified date:
12 October 2021