LI73966: TO_DATE/TIMESTAMP_FORMAT SCALAR FUNCTION WITH GRAPHIC/VARGRAPHIC FORMAT-STRING CAUSES INSTANCE TO TERMINATE ABNORMALLY

DB2 Version 9.5 Fix Pack 4  for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4a for Linux, UNIX, and Windows
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

• The DB2 instance terminates abnormally during SQL statement
  compilation.  This can happen when the SQL statement includes
  the SYSIBM.TO_DATE or SYSIBM.TIMESTAMP_FORMAT scalar function,
  the format-string is a GRAPHIC or VARGRAPHIC with a length
  attribute greater than 84 and the format-string is not a
  literal.  For example:
  
    SELECT TO_DATE( COL1, CAST( ? AS VARGRAPHIC(4000) ) FROM T
  
  The stack trace looks similar to this example from Linux:
  
  Stacktrace
  0000002A9D866F19 ossDumpStackTraceEx + 0x0373
  
  (/view/db2_v95fp2_linuxamd64_n080811/vbs/INST/lib/libdb2osse.so.
  1)
  0000002A9D86122C _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 0x0270
  
  (/view/db2_v95fp2_linuxamd64_n080811/vbs/INST/lib/libdb2osse.so.
  1)
  0000002A98B8CE08 sqlo_trce + 0x035a
  
  (/view/db2_v95fp2_linuxamd64_n080811/vbs/INST/lib/libdb2e.so.1)
  0000002A98C6CDE1 sqloEDUCodeTrapHandler + 0x01bb
  
  (/view/db2_v95fp2_linuxamd64_n080811/vbs/INST/lib/libdb2e.so.1)
  0000002A95679260 address: 0x0000002A95679260 ; dladdress:
  0x0000002A9566D000 ; offset in lib: 0x000000000000C260 ;
          (/lib64/tls/libpthread.so.0)
  0000002A96DF9EE6 _ZN17sqlnq_qunqncchild2ppEv + 0x0010
  
  (/view/db2_v95fp2_linuxamd64_n080811/vbs/INST/lib/libdb2e.so.1)
  0000002A982438F2
  _ZN9sqlnq_qnc18field_value_locateERPhR17sqlnn_dat_TYPTYPE +
  0x007c
  
  (/view/db2_v95fp2_linuxamd64_n080811/vbs/INST/lib/libdb2e.so.1)
  0000002A981CCE01
  _Z16sqlnq_encap_doitiP9sqlnq_pidPS0_P12sqlnq_stringPhP3loc +
  0x17881
  
  (/view/db2_v95fp2_linuxamd64_n080811/vbs/INST/lib/libdb2e.so.1)
  0000002A97FB7D68
  _Z18sqlnq_fun_res_walkP9sqlnq_pidP12sqlnq_stringPhPS0_P3locii +
  0x1418
  
  (/view/db2_v95fp2_linuxamd64_n080811/vbs/INST/lib/libdb2e.so.1)
  0000002A97FB64B9
  _Z14sqlnq_fun_tresP9sqlnq_pidP12sqlnq_stringPhPS0_P3locii +
  0x0187
  
  (/view/db2_v95fp2_linuxamd64_n080811/vbs/INST/lib/libdb2e.so.1)
  0000002A9800EC0C
  _Z23sqlnq_sem_function_callPP8stknode_i10actiontypePhP3loc +
  0x00b2
  
  
  The query should fail with the SQLCODE -171, SQLSTATE 42815
  because the length attribute of the format-string is greater
  than the maximum documented length of 254 bytes (or 84 GRAPHIC
  characters).
  

Local fix

• Change the length attribute of the format-string to less than
  254 bytes (or 84 GRAPHIC characters).
  

Problem summary

• TO_DATE/TIMESTAMP_FORMAT SCALAR FUNCTION WITH
  GRAPHIC/VARGRAPHICFORMAT-STRING CAUSES INSTANCE TO TERMINATE
  ABNORMALLY
  

Problem conclusion

• First fixed in DB2 UDB Version 9.5, FixPak 4
  

Temporary fix

• Change the length attribute of the format-string to less than
  254 bytes (or 84 GRAPHIC characters)
  

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 UDE ESE LIN

• Fixed component ID

  5765F4104

Applicable component levels

• R950 PSY

     UP