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

SILENT RESPONSE KEYWORD DB2_ODBC_DSN_ACTION=ADD FAILS

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
DB2 silent response file using the keywords below will fail to
add the data sources defined in db2dsdriver.cfg and db2cli.ini
to the Windows Administrative Tools->Data Sources (ODBC)

DB2_ODBC_DSN_TYPE=USER
DB2_ODBC_DSN_ACTION=ADD

This APAR is affects:
IBM Data Server Client
IBM Data Server Runtime Client

This APAR does not affect:
IBM Data Server Driver Package (DS Driver)
IBM Data Server Driver for ODBC and CLI (CLI Driver)
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Silent response file installation on Windows                 *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Install using installation media from v11.1 M xx Fixpack xx  *
****************************************************************
Local Fix:
Post installation, manually execute the command:

 "db2cli registerdsn -add -alldsn -user" if registering USER
DSNs.
"db2cli registerdsn -add -alldsn -system" if registering SYSTEM
DSNs

For additional options refer to db2cli command documentation:

https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ib
m.db2.luw.admin.cmd.doc/doc/r0002045.html
Solution
Workaround
See LOCAL FIX
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.06.2018
02.08.2020
02.08.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)