DB2 - Problembeschreibung
Problem IC93911 | Status: Geschlossen |
IT IS POSSIBLE TO CATALOG A DATABASE WITHOUT A DB NAME OR ALIAS WHEN CREATING AN ODBC DSN IN MICROSOFT ODBC ADMINISTRATOR | |
Produkt: | |
DB2 CONNECT / DB2CONNCT / 970 - DB2 | |
Problembeschreibung: | |
If you use the Microsoft Windows ODBC Administrator to create a new ODBC DSN, it is possible to create the DSN while leaving the Database Name and Alias both blank. This results in a database catalog entry that would look similar to the following. From this point, you can not uncatalog that database entry via the command line (CLP) environment, and deleting the DSN from the ODBC administrator does not remove the catalog entry. Database 1 entry: Database alias = Database name = Node name = NDE66812 Database release level = d.00 Comment = Directory entry type = Remote Authentication = SERVER Catalog database partition number = -1 Alternate server hostname = Alternate server port number = | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 10 * **************************************************************** | |
Local-Fix: | |
You can successfully remove the blank database catalog entry via either the Configuration Assistant or Control Center GUI tools. (The same workaround has not been validated via Optim Data Studiol.) | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
Lösung | |
First Fixed in Version 9.7 Fix Pack 10 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC96909 IC96914 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 03.07.2013 10.11.2014 10.11.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP10 | |
Problem behoben lt. FixList in der Version | |
9.7.0.9 | |
9.7.0.9 | |
9.7.0.10 |