LI73467: DB2 LOAD UTILITY DOES NOT FAIL WHEN AN IPC MESSAGE QUEUE ERROR OCCURS, RESULTING IN INCORRECT ROW COUNT LOADED.

DB2 Version 9.1 Fix Pack 7  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

• Description:
  During a load, in the very rare scenario that an IPC message
  queue error occurs at the OS level which results in an invalid
  buffer being received by the Load formatter process (db2lfrm0),
  the process will log an error message, but continue to
  completion instead of failing. This can result in not all of the
  rows being loaded into the table from the data file.
  
  Example db2diag.log message:
  2008-01-18-13.56.34.333596+540 I10751563A493      LEVEL: Error
  PID  : 2071        TID  : 1           PROC :  db2lrid0
  INSTANCE: db2inst1             NODE : 000         DB   : CODB
  APPHDL  : 0-2502               APPID:
  *LOCAL.db2inst1.080118045626
  AUTHID  : DB2INST1
  FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0
  DATA #1 : String, 127 bytes
  LOADID: 24413.2008-01-18-13.56.27.887972.0 (10;31)
  Unexpect msg! , 43, 0000000000000000, Detected in
  file:sqlulrid.C, Line:1647
  

Local fix

• The reason for the invalid buffer is suspected to be an OS bug
  but never confirmed, it has only occurred when IPC queue
  resouce contention was a factor, so using CPU_PARALLELISM 1 or
  increasing kernel.msgmnb value to avoid the contention can be a
  workaround.
  

Problem summary

• Users Affected: Any users of the LOAD functionality in DB2
  Problem Description: During a Load and IPC message queue error
  does NOT fail the load resulting in a incorrect row count
  loaded.
  Problem Summary: See above.
  

Problem conclusion

• First fixed in DB2 UDB Version 9.1, FixPak 6 (s081007)
  

Temporary fix

• n/a
  

Comments

APAR Information

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

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

  LI73468

Fix information

• Fixed component name

  DB2 UDE ESE LIN

• Fixed component ID

  5765F4104

Applicable component levels

• R810 PSN

     UP

• R820 PSN

     UP

• R910 PSN

     UP

• R950 PSN

     UP