JR28136: DB2 PERFMON PROVIDER (DB2PERF.DLL) LEAKING HANDLES ON WINDOWS

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

• When the DB2 PerfMon provider (DB2PERF.DLL) is used to monitor
  DB2 performance counters on Windows, a handle leak may occur
  during every load of the DB2PERF.DLL library. The leak can be
  observed for example in Windows Task Manager as an increasing
  number in the "Handles" column.
  .
  WinDbg (Windows debugger) will reveal a leaking stack similar
  to the following when the "!htrace -diff" command is used:
  .
  kernel32 ! CreateEventA + 0x00000068
  DB2Perf ! OpenDB2NTPerformanceData + 0x0000015c
  ADVAPI32 ! OpenExtObjectLibrary + 0x0000058f
  ADVAPI32 ! QueryExtensibleData + 0x000003d8
  ADVAPI32 ! PerfRegQueryValue + 0x00000513
  ADVAPI32 ! LocalBaseRegQueryValue + 0x00000306
  ADVAPI32 ! RegQueryValueExA + 0x000000de
  test + 0x00001291
  test + 0x000014a1
  test + 0x00001643
  kernel32 ! BaseProcessStart + 0x00000023
  .
  The leak is one Event per one load of DB2PERF.DLL.
  

Local fix

• If the handle leak can be observed in a user application,
  change the application to reduce the number of DB2PERF.DLL
  loads and unloads as much as possible.
  

Problem summary

• Users Affected: see APAR text
  Problem Summary: see APAR text
  Problem Description: see APAR text
  

Problem conclusion

• First fixed in DB2 UDB Version 9.5, FixPak 1
  

Temporary fix

• see APAR text
  

Comments

APAR Information

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

  JR26971

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

Modules/Macros

• ENGN_SQO
  

Fix information

• Fixed component name

  DB2 UDB ESE WIN

• Fixed component ID

  5765F4101

Applicable component levels

• R950 PSN

     UP