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 IT18392 Status: Closed

THE SAME 'DATABASE NAME' IS LISTED AT 'LOCAL DATABASE
ALIAS' EVEN IF 'ALIAS' AND 'NAME' ARE DIFFERENT IN
DB2DSDRIVER.CFG.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
If db2dsdriver.cfg is used to connect to a database that is 
not catalogued, the same 'Database name' is listed at 'Local 
database alias' on the 'connect database' or 'get connection 
state' command even though 'alias' and 'name' are differently 
configured in db2dsdriver.cfg. 
 
  For example, if '<dsn alias="alias1" name="name1" host="host1" 
port="portnum"/>' is defined in db2dsdriver.cfg, the 'get 
connection state' command returns as below, 
 
    Database Connection State 
 
    Connection state       = Connectable and Connected 
    Connection mode        = SHARE 
    Local database alias   = name1 
    Database name          = name1 
    Hostname               = host1 
    Service name           = portnum 
 
  But if 'alias1' is cataloged for the database 'name1' by 
"catalog database name1 as alias1 at node host1" command, 
'alias1' is properly listed at 'Local database alias' as below. 
 
    Connection state       = Connectable and Connected 
    Connection mode        = SHARE 
    Local database alias   = alias1 
    Database name          = name1 
    Hostname               = host1 
    Service name           = portnum
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* db2dsdriver.cfg user                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 FixPack 9 or later               * 
****************************************************************
Local Fix:
- Catalog the database 
- have the alias match the name in db2dsdriver.cfg
Solution
Fixed in DB2 Version 10.5 FixPack 9
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.12.2016
27.09.2017
27.09.2017
Problem solved at the following versions (IBM BugInfos)
9.0.
Problem solved according to the fixlist(s) of the following version(s)