DB2 CONNECT / DB2CONNCT / 970 - DB2

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         =

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 10                       * 
****************************************************************

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.)

DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

First Fixed in Version 9.7 Fix Pack 10

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC96909 IC96914 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

03.07.2013
10.11.2014
10.11.2014

9.7.FP10