DB2 - Problem description
Problem IT18422 | Status: Closed |
INGEST MAY FAIL IF 'ALIAS' AND 'NAME' IS 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, and the alias and name specified is different, INGEST may fail with errors such as "SQL1031N The database directory cannot be found on the indicated file system." If there is another entry in db2dsdriver with the same name where the alias matches the database name, INGEST will attempt to use that entry for its connection, which may result in errors such as "SQL1336N The remote host "<hostname>" was not found." For example, with a db2dsdriver.cfg such as this: <configuration> <dsncollection> <dsn alias="name1" name="name1" host="host2" port="portnum"/> <dsn alias="alias1" name="name1" host="host1" port="portnum"/> </dsncollection> <databases> <database name="name1" host="host2" port="portnum"/> <database name="name1" host="host1" port="portnum"/> </databases> </configuration> After connecting to "alias1", INGEST will attempt to use database "name1" in host2. | |
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 - or have the alias match the name in db2dsdriver.cfg - or Use other utilities such as load | |
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) |