|
Problem IC96914
|
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 FOR LUW / DB2FORLUW / A50 - 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 10.5 Fix Pack 4 *
**************************************************************** |
| 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 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Lösung |
First fixed in version 10.5 Fix Pack 4 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 15.10.2013
15.09.2014
15.09.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.5.0.4
|
 |
