IBM Support

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

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error 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         =
    

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

Problem summary

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

Problem conclusion

  • First Fixed in Version 9.7 Fix Pack 10
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC93911

  • Reported component name

    DB2 CONNECT

  • Reported component ID

    DB2CONNCT

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-07-03

  • Closed date

    2014-11-10

  • Last modified date

    2014-11-10

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IC96909 IC96914

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC93911

Modified date: 10 November 2014