JR31948: Security: DB2 instance terminates abnormally while compiling a SQL query

DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• Compiling a SQL query may cause the DB2 instance to terminate
  abnormally.  The call stack looks similar to the following from
  Linux:
  
  0000002A9B71C853 ossDumpStackTraceEx + 0x01f7
  
  (/view/db2_v95fp2_linuxamd64_s080811/vbs/INST/lib/libdb2osse.so.
  1)
  0000002A9B7183C8 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 0x00b4
  
  (/view/db2_v95fp2_linuxamd64_s080811/vbs/INST/lib/libdb2osse.so.
  1)
  0000002A97CB6222 sqlo_trce + 0x034a
  
  (/view/db2_v95fp2_linuxamd64_s080811/vbs/INST/lib/libdb2e.so.1)
  0000002A97CF3BC7 sqloEDUCodeTrapHandler + 0x0105
  
  (/view/db2_v95fp2_linuxamd64_s080811/vbs/INST/lib/libdb2e.so.1)
  0000002A95679260 address: 0x0000002A95679260 ; dladdress:
  0x0000002A9566D000 ; offset in lib: 0x000000000000C260 ;
                  (/lib64/tls/libpthread.so.0)
  0000002A985EA24B _Z8sqlrxcp2PK14sqlrxCollationP10sqlz_valueS3_j
  + 0x0bef
  
  (/view/db2_v95fp2_linuxamd64_s080811/vbs/INST/lib/libdb2e.so.1)
  0000002A97825F63
  _ZN9sqlnq_qnc21compare_constant_qncsEPS_P10sqlz_valueS2_PiP3loc
  + 0x01e5
  
  (/view/db2_v95fp2_linuxamd64_s080811/vbs/INST/lib/libdb2e.so.1)
  0000002A9770DC39 _Z24sqlnq_betw_eq_const_argsP9sqlnq_pidPiP3loc
  + 0x011d
  
  (/view/db2_v95fp2_linuxamd64_s080811/vbs/INST/lib/libdb2e.so.1)
  0000002A9770DD12
  _Z21sqlnq_encap_betw_rewrP9sqlnq_pidiPS0_P12sqlnq_stringPhP3loc
  + 0x00a2
  
  (/view/db2_v95fp2_linuxamd64_s080811/vbs/INST/lib/libdb2e.so.1)
  

Local fix

• NONE.
  
  First fixed in V9.5 FP5
  

Problem summary

• DB2 instance terminates abnormally while compiling a
  SQL query.
  

Problem conclusion

• The Stack trace for the crash on Linux looks similar to:
  
  0000002A9B778047 ossDumpStackTraceEx + 0x01f7
  
  (/view/db2_v95fp3_linuxamd64_s081118/vbs/INST/lib/libdb2osse.so.
  1)
  0000002A9B773BBC _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 0x00b4
  
  (/view/db2_v95fp3_linuxamd64_s081118/vbs/INST/lib/libdb2osse.so.
  1)
  0000002A9B773C83 _ZN11OSSTrapFile4dumpEmiP7siginfoPv + 0x0009
  
  (/view/db2_v95fp3_linuxamd64_s081118/vbs/INST/lib/libdb2osse.so.
  1)
  0000002A97CEE7A5 sqlo_trce + 0x03f3
  
  (/view/db2_v95fp3_linuxamd64_s081118/vbs/INST/lib/libdb2e.so.1)
  0000002A97D2D1CD sqloEDUCodeTrapHandler + 0x0107
  
  (/view/db2_v95fp3_linuxamd64_s081118/vbs/INST/lib/libdb2e.so.1)
  0000002A95679260 address: 0x0000002A95679260 ; dladdress:
  0x0000002A9566D000 ; offset in lib: 0x000000000000C260 ;
          (/lib64/tls/libpthread.so.0)
  0000002A98627A0B _Z8sqlrxcp2PK14sqlrxCollationP10sqlz_valueS3_j
  + 0x0bef
  
  (/view/db2_v95fp3_linuxamd64_s081118/vbs/INST/lib/libdb2e.so.1)
  0000002A978575F1
  _ZN9sqlnq_qnc21compare_constant_qncsEPS_P10sqlz_valueS2_PiP3loc
  + 0x01e5
  
  (/view/db2_v95fp3_linuxamd64_s081118/vbs/INST/lib/libdb2e.so.1)
  0000002A9773C795 _Z24sqlnq_betw_eq_const_argsP9sqlnq_pidPiP3loc
  + 0x011d
  (/view/db2_v95fp3_linuxamd64_s081118/vbs/INST/lib/libdb2e.so.1)
  0000002A9773C86E
  
  _Z21sqlnq_encap_betw_rewrP9sqlnq_pidiPS0_P12sqlnq_stringPhP3loc
  + 0x00a2
  (/view/db2_v95fp3_linuxamd64_s081118/vbs/INST/lib/libdb2e.so.1)
  0000002A969CB5EC
  
  _Z16sqlnq_encap_doitiP9sqlnq_pidPS0_P12sqlnq_stringPhP3loc +
  0x644c
  (/view/db2_v95fp3_linuxamd64_s081118/vbs/INST/lib/libdb2e.so.1)
  

Temporary fix

Comments

APAR Information

• 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 WSE WIN

• Fixed component ID

  5765F3501

Applicable component levels

• R950 PSY UP

     950