IC65795: IBM OLE DB PROVIDER WILL NOT SHOW UP IN THE LIST OF AVAILABLE 'NATIVE OLE DB' DRIVERS IN DB2 RUN-TIME CLIENT FOR 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

• On Windows 32-bit/64-bit server with DB2 V9.1 Runtime Client,
  IBM OLE DB Provider will not show up in the list of available
  'native OLE DB' drivers
  for example within Microsoft SQL Server 2005/2008 and SQL
  Server Business Intelligence Development Studio
  

Local fix

• Workaround is to register OLEDB manually using regsvr32, i.e,
  OLEDB provider self registration code is called when you call
  regsvr32 command.
  
  for 32bit RTCL, run
  C:\WINDOWS\system32\regsvr32 /s
  <DB2InstallationPath>\bin\ibmdadb2.dll
  
  for 64bit RTCL, run
  C:\windows\syswow64\regsvr32 /s
  <DB2InstallationPath>\bin\ibmdadb2.dll - to register a 32-bit
  dll
  C:\windows\system32\regsvr32 /s
  <DB2InstallationPath>\bin\ibmdadb264.dll - to register a 64-bit
  dll
  
  For example, if the product is installed in
  "C:\ProgramFiles\IBM"
  folder on a 32-bit Windows server, running below dll
  registration command resolves the problem
  
  C:\WINDOWS\system32\regsvr32  /s C:\Program
  
  Files\IBM\SQLLIB\BIN\ibmdadb2.dll
  
  For regsvr32 usage options, refer:
  http://support.microsoft.com/kb/249873
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Windows                                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * IBM OLE DB PROVIDER WILL NOT SHOW UP IN THE LIST OF          *
  * AVAILABLE 'NATIVE OLE DB' DRIVERS ON DB2 RUN-TIME CLIENT FOR *
  * WINDOWS                                                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to DB2 V9.1 FP 9 or higher                           *
  *                                                              *
  * OR                                                           *
  *                                                              *
  * Use Temporary Fix                                            *
  ****************************************************************
  

Problem conclusion

• First fixed in DB2 V9.1 FP 9
  

Temporary fix

• Workaround is to register OLEDB manually using regsvr32, i.e,
  
  
  OLEDB provider self registration code is called when you call
  regsvr32 command.
  
  for 32bit RTCL, run
  
  
  C:\WINDOWS\system32\regsvr32 /s
  <DB2InstallationPath>\bin\ibmdadb2.dll
  
  for 64bit RTCL, run
  
  
  C:\windows\syswow64\regsvr32 /s
  <DB2InstallationPath>\bin\ibmdadb2.dll - to register a 32-bit
  dll
  C:\windows\system32\regsvr32 /s
  <DB2InstallationPath>\bin\ibmdadb264.dll - to register a 64-bit
  dll
  
  For example, if the product is installed in
  
  "C:\ProgramFiles\IBM"
  
  
  folder on a 32-bit Windows server, running below dll
  
  
  registration command resolves the problem
  
  C:\WINDOWS\system32\regsvr32  /s C:\Program
  
  
  Files\IBM\SQLLIB\BIN\ibmdadb2.dll
  
  For regsvr32 usage options, refer:
  
  http://support.microsoft.com/kb/249873
  

Comments

APAR Information

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

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

  IC65887 IC65888

Fix information

• Fixed component name

  DB2 CONNECT

• Fixed component ID

  DB2CONNCT

Applicable component levels

• R910 PSY

     UP