home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC96909 Status: Closed

IT IS POSSIBLE TO CATALOG A DATABASE WITHOUT A DB NAME OR ALIAS WHEN
CREATING AN ODBC DSN IN MICROSOFT ODBC ADMINISTRATOR

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 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.)
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First Fixed in 10.1 Fix Pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.10.2013
02.06.2014
02.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList