DB2 FOR LUW / DB2FORLUW / 910 - DB2

IBM OLEDB Provider listing in "Data Link Provider" does not show 
DB2 copy names when multiple copies are installed. 
 
Repro steps 
open the excel 2007 
Go to menu 
Data -> Get External Data -> using wizard (3rd option) -> 
Other/Advanced drivers -> choose driver with copy name 
For excel 2003 the 
Data->import external data->Connect to new data 
source->Other/advanced 
 
Using sql server managment studio 
Connect to sql server using sql server mangement studio 
Go to linked server ->new linked server 
it will open linked server diaglog box which will list oledb 
providers. 
 
It lists OLE DB Provider(s) and that is where IBM OLEDB 
Providers are listed . Some of them might be displayed 
without having copyname appended 
 
This can happen if the installed DB2 copy is default and in that 
case the DB2 COPY name is not appended to OLEDB provider. 
the problem doesnot happen when installed DB2 copy is non 
default one where the actually copy name is appended. 
 
the excel/SQl server management studo reads the DB2 OLE DB 
provider from 
"HKEY_CLASSES_ROOT\CLSID\{IBMDADB2 guid}\OLE DB Provider" key

IBM OLEDB Provider listing in "Data Link Provider" does not show 
DB2 copy names when multiple copies are installed.

To get copy name for other IBM oledb providers which has not 
showing copy name appended in DB2 oledb provider list, do this 
process as workaround 
 
1)Using regedit go to 
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\InstalledCopies 
2) Change the  named "Default" to some value like DB2 ( value 
other than installed DB2Copy names) 
3)Get the sqllib/bin folder path which correspond to db2copy 
which is not appended in oledb provider string in excel DSN 
dialog box. 
4) Run regsvr32 "DB2copypath/sqllib/bin/ibmdadb2.dll" from 
start->run 
5) Repeat step 3 and 4 for other DB2copies for which OLEDB 
provider copy name is not appended in excel DSN dialog box. 
6) Close the excel and reopen it and check if dsn dialog box is 
showing the copyname now 
7) Revert back the DB2 copy value changed in step 2 to original 
DB2 copy

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
 

Target fix is V9.1 fp10

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

24.08.2010
14.06.2011
14.06.2011

9.1.FP10