|
Problem IC63034
|
Status: Closed |
DATABASE DISCOVERY IS NOT WORKING PROPERLY IN IBM DATABASE ADD-INS FOR VISUAL STUDIO. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
In add connection dialog in IBM Database Add-Ins for Visual
Studio, database field is not showing all the databases.
Clicking on Discover button doesn't get list of all databases,
even for local server all the databases are not being shown. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* In add connection dialog, database field is not showing all *
* the databases. Clicking on Discover button doesn't get list *
* of all databases (even for local server). *
****************************************************************
* PROBLEM DESCRIPTION: *
* In add connection dialog, database field is not showing all *
* the databases. Clicking on Discover button doesn't get list *
* of all databases (even for local server). *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v971 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
==== State: Assigned by: avainch on 21 July 2009 14:09:25 ====
After discussing possible solutions between Kanchana, Reece and
myself, it was decided that the best way to resolve this would
be to modify the .NET provider's enumeration functionality to
behave consistently for local host discovery no matter what
combination of server name/port information was used.
The behavior for all cases described by Michael would be the
same as in case #1. The output would also be the same and would
contain rows for local databases with Server name and port
number set to NULL. It would be up to VS addons to display the
returned dbs property in the Add Connection wizard.
Ajay, does this approach present any problems for the Addons
team?
Thanks,
Alex |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.09.2009
21.01.2010
21.01.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
