IT32875: FILE HANDLE LEAK USING ORACLE ODBC WITH THE SERVERNAME PROPERTY

APAR status

• Closed as program error.

Error description

• The connection properties for an Oracle ODBC datasource as
  specified in the odbc.ini file typically include HostName,
  PortNumber and ServiceName for the target database server. But
  if there is a local tnsnames.ora file available, it is possible
  to configure the datasource so that the ODBC driver looks in the
  tnsnames.ora file to retrieve the connection information for
  the required Oracle services. Instead of using the HostName,
  PortNumber and ServiceName properties, the following two
  properties can be used in the datasource definition:
  
  ServerName
  
  Specifies a net service name that exists in the TNSNAMES.ORA
  file. The corresponding net service name entry in the
  TNSNAMES.ORA file is used to obtain Host, Port Number, and
  Service Name or SID information.
  
  
  TNSNamesFile
  
  Specifies the name and path of the TNSNAMES.ORA file.
  
  
  With the Oracle ODBC driver (version 08.02.2305) from IBM
  Integration Bus 10.0.0.20 and IBM App Connect Enterprise
  11.0.0.8, when the odbc.ini datasource is configured to use
  ServerName and TNSNamesFile properties to obtain the service
  connection details from a local tnsnames.ora file, there is a
  leak of file handles for every new connection established. Over
  a period of time, the following error may be reported in the
  system log:
  
  
  
  BIP2112E: Integration node internal error: diagnostic
  information 'Too many open files', '24'.
  

Local fix

• Use the DataDirect Oracle ODBC driver from an earlier Fix Pack.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus v10 and IBM App Connect
  Enterprise v11 using ODBC connectivity to an Oracle database.
  
  
  Platforms affected:
  AIX, HP-UX Itanium platform, Linux on Power platform, Linux on
  x86-64 platform, Linux on zSeries platform, Solaris x86-64
  platform, Solaris SPARC platform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The connection properties for an Oracle ODBC datasource as
  specified in the odbc.ini file typically include HostName,
  PortNumber and ServiceName for the target database server. But
  if there is a local tnsnames.ora file available, it is possible
  to configure the datasource so that the ODBC driver looks in the
  tnsnames.ora file to retrieve the connection information for the
  required Oracle services. Instead of using the HostName,
  PortNumber and ServiceName properties, the following two
  properties can be used in the datasource definition:
  
  ServerName
  
  Specifies a net service name that exists in the TNSNAMES.ORA
  file. The corresponding net service name entry in the
  TNSNAMES.ORA file is used to obtain Host, Port Number, and
  Service Name or SID information.
  
  TNSNamesFile
  
  Specifies the name and path of the TNSNAMES.ORA file.
  
  With the Oracle ODBC driver (version 08.02.2305) from IBM
  Integration Bus v10 Fix Packs 20/21 and IBM App Connect
  Enterprise v11 Fix Packs 8/9, when the odbc.ini datasource is
  configured to use ServerName and TNSNamesFile properties to
  obtain the service connection details from a local tnsnames.ora
  file, there is a leak of file handles for every new connection
  established. Over a period of time, the following error may be
  reported in the system log:
  
  BIP2112E: Integration node internal error: diagnostic
  information 'Too many open files', '24'.
  

Problem conclusion

• The product includes an updated level of ODBC drivers that
  resolves the problem.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.22
  v11.0      11.0.0.10
  
  The latest available maintenance can be obtained from:
  http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available,information on
  its planned availability can be found on:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

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:

Fix information

• Fixed component name

  INTEGRATION BUS

• Fixed component ID

  5724J0540

Applicable component levels