LI73685: INSUFFICIENT INFO MESSAGES IN DB2DIAG.LOG ON DPF ENV AS COMPARED TO SINGLE PARTITION ENV FOR LOCKWAIT, LOCK MODE,APP,SQL

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

• Environment:
  
  DB2 ESE v9.1 FP3 on AIX
  DIAGLEVEL=4
  LOCKTIMEOUT=60
  
  Insufficient info messages in db2diag.log  on DPF env  as
  compared to Single Partition env
  -lockwait, lock mode, application and SQL
  
  We can get the below info from db2diag.log when we test on
  single single partition
  -lockwait object
  -lock mode the above object try to get
  -application that keeps lock
  -rollbacked SQL statement
  
  But I can't get the above info when I test on DPF env.
  I have attached db2diag.log end of this message.
  

Local fix

• There is a new lock timeout diagnosis tool that is shipped with
  v9 fp4.  You can read about it here:
  
  http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm
  .db2.udb.admin.doc/doc/c0052973.htm
  

Problem summary

• Users affected:
  All users using v9.1 FP3 and below.
  
  Problem Description:
  INSUFFICIENT INFO MESSAGES IN DB2DIAG.LOG  ON DPF ENV  AS
  COMPARED TO SINGLE PARTITION ENV FOR LOCKWAIT, LOCK MODE,APP,SQL
  
  Problem Summary:
  ERROR DESCRIPTION:
  Environment:
  
  DB2 ESE v9.1 FP3 on AIX
  DIAGLEVEL=4
  LOCKTIMEOUT=60
  
  Insufficient info messages in db2diag.log  on DPF env  as
  compared to Single Partition env
  -lockwait, lock mode, application and SQL
  
  We can get the below info from db2diag.log when we test on
  single single partition
  -lockwait object
  -lock mode the above object try to get
  -application that keeps lock
  -rollbacked SQL statement
  
  But I can't get the above info when I test on DPF env.
  I have attached db2diag.log end of this message.
  
  LOCAL FIX:
  There is a new lock timeout diagnosis tool that is shipped with
  v9 fp4.  You can read about it here:
  
  http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm
  .db2.udb.admin.doc/doc/c0052973.htm
  

Problem conclusion

• First fixed in DB2 UDB DB2_V95 FixPak 2
  

Temporary fix

• There is a new lock timeout diagnosis tool that is shipped with
  v9 fp4.  You can read about it here:
  
  http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm
  .db2.udb.admin.doc/doc/c0052973.htm
  

Comments

APAR Information

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

  LI72971

• 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