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

INGEST MAY FAIL IF 'ALIAS' AND 'NAME' IS DIFFERENT IN DB2DSDRIVER.CFG

product:
DB2 FOR LUW / DB2FORLUW / B10 - 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 "" was not found."

  For example, with a db2dsdriver.cfg such as this:


  
    
    
  
  
    
    
  


  After connecting to "alias1", INGEST will attempt to use
database "name1" in host2.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* INGEST users using db2dsdriver.cfg                           *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 version 11.1.0102                             *
****************************************************************
Local Fix:
- Catalog the database
- or have the alias match the name in db2dsdriver.cfg
- or Use other utilities such as load
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT18422 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.08.2017
10.10.2017
10.10.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)