IBM Support

IC66082: DB2 instance terminates abnormally or returns -901 compiling a query

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Compiling a query on DB2 v9.1 fix pack 8 may result in the DB2
    instance terminating abnormally with a stack similar to this
    example from Linux:
    
      0000002A9AE8F0BE ossDumpStackTrace + 0x0186
      0000002A9AE8CBD4 _ZN11OSSTrapFile4dumpEmiP7siginfoPv + 0x00aa
      0000002A97F4A8DF sqlo_trce + 0x03cf
      0000002A96D94B78 sqloEDUCodeTrapHandler + 0x02b8
      0000003130A0C5B0 address: 0x0000003130A0C5B0 ; dladdress:
    0x0000003130A00000 ;
      0000002A965D4FB9 _Z21sqlnq_const_fold_treeP9sqlnq_pidRbP3loc +
    0x0171
    
    Another possible symptom of this problem is SQLCODE -901 with
    one of the two following reason codes:
    
      SQL0901N  The SQL statement failed because of a non-severe
    system error.
      Subsequent SQL statements can be processed.  (Reason "invalid
    qnc assigment".)
      SQLSTATE=58004
    
    or
    
      SQL0901N  The SQL statement failed because of a non-severe
    system error.
      Subsequent SQL statements can be processed.  (Reason "column
    number out of range".)
      SQLSTATE=58004
    
    To hit this problem, a query must have an outer join whose
    result is inner joined with a base table and there must be a
    join predicate, for example:
    
      create view V as select * from T1 left outer join T2 ...
      select * from V, T3 where V.C1=T3.C2
    
    The problem only occurs on v9.1 fix pack 8.
    

Local fix

  • Upgrade to DB2 v9.1 fix pack 9 or reverse the order in the join
    predicate, for the example above: T3.C2=V.C1
    

Problem summary

  • Users affected :  Users compiling a query in DB2 V9.1 fix pak 8
    
    Problem Description : Compiling a  query  in V9.1 fix pak 8 can
    crash the  DB2 instance. Please  see APAR description for the
    details
    
    Problem Summary : Compiling a query in V9.1 fix pak 8 can crash
    the DB2  instance
    

Problem conclusion

  • First Fixed in DB2 Version V9.1 fix pak 9
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC66082

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-02-04

  • Closed date

    2010-04-21

  • Last modified date

    2010-09-30

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

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

    IC66230 IC66239 IC66487

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
30 September 2010