LI73169: SIGNAL #11 INSTANCE CRASH MIGHT OCCUR AFTER CONVERTING A STRING TO UPPER OR LOWER CASE USING FUNCTIONS LOWER/LCASE/UPPER/UCASE

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

APAR status

• Closed as program error.

Error description

• A memory overwrite and memory corruption might occur due to
  problem in the upper/lower character conversion functions for
  very specific data as follows:
  - This problem will happen in UTF-8 database only.
  - It is specific to the case when invalid UTF-8 string data is
  referenced (partial UTF-8 characters).
  This problem is seen for example when the last byte in the
  string is invalid: It is a first byte of the valid 2-byte
  character.  In this scenario conversion function could corrupt
  a few bytes of memory.
  In the cases where this has been seen, those few bytes of
  memory end up being used later on during a calculation for a
  much larger memory operation which results in a much larger
  memory overwrite that leads to an instance crash during query
  execution.
  If you look at the stack traceback file for the signal #11,
  the following are some of the stack tracebacks that have been
  seen:
  1)
  memcpy
  intel_fast_memcpy.A
  sqlri_serveFromBuffer
  sqlrita
  sqlriSectInvoke
  sqlrr_process_fetch_request
  sqlrr_open
  2)
  __restore_rt
  sqldRowFetch
  sqlriFetch
  sqlriNljnNonPiped
  sqlriSectInvoke
  sqlrr_process_fetch_request
  sqlrr_open
  3)
  sqldGetNextDataPartition
  sqldRowFetch
  sqlriFetch
  sqlriNljnNonPiped
  sqlriSectInvoke
  sqlrr_process_fetch_request
  sqlrr_open
  4)
  sqlplAddLockAttributes
  sqldProtectReadBlockLock
  sqldRowFetch
  sqlriFetchPerm
  sqlriFetch
  sqlriNljnNonPiped
  sqlriExecThread
  sqlriSectInvoke
  sqlrr_process_fetch_request
  sqlrr_open
  Please note that there may be other possible stack tracebacks
  that could happen as a result of this defect that have not been
  documented yet.
  This APAR will fix the character conversion functions so that
  the initial small-bytesize corruption does not occur.
  

Local fix

Problem summary

• A memory overwrite and memory corruption might occur due to
  problem in the upper/lower character conversion functions for
  very specific data as follows:
  - This problem will happen in UTF-8 database only.
  - It is specific to the case when invalid UTF-8 string data is
  referenced (partial UTF-8 characters).
  This problem is seen for example when the last byte in the
  string is invalid: It is a first byte of the valid 2-byte
  character.  In this scenario conversion function could corrupt
  a few bytes of memory.
  In the cases where this has been seen, those few bytes of
  memory end up being used later on during a calculation for a
  much larger memory operation which results in a much larger
  memory overwrite that leads to an instance crash during query
  execution.
  

Problem conclusion

• Project db2_v91fp5
  

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:

  LI73209 JR31371

Fix information

• Fixed component name

  DB2 UDE ESE LIN

• Fixed component ID

  5765F4104

Applicable component levels

• R910 PSY

     UP