|
Problem IT34398
|
Status: Closed |
GET DB CFG FOR CAN FAIL IF GATEWAY CATALOGS TARGET DB WITH DIFFERENT NAME
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
get db cfg (db2CfgGet/db2CfgCall) can fail with SQL5005C in the
following setup:
(DB Client) (Gateway) (DB Server)
dbname: C -> dbname:B -> dbname:A
When we connect to C from the Client, then issue "get db cfg for
c" the request fails:
$ db2 connect to C user db2inst1
Database Connection Information
Database server = DB2/LINUXX8664 11.1.4.5
SQL authorization ID = DB2INST1
Local database alias = C
$ db2 get db cfg for c
SQL5005C The operation failed because the database manager
failed to access
either the database manager configuration file or the database
configuration file.
Some other Db2 utilities such as IMPORT and EXPORT may also fail
with
SQL5005C because they can call db2CfgCall API internally. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users who use gateway instance to connect target database, *
* and catalog db alias different name than db name. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to Db2 v11.1m4fp6 or later. *
**************************************************************** |
| Local Fix: |
Use the same DB alias as DB name. |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users who use gateway instance to connect target database, *
* and catalog db alias different name than db name. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to Db2 v11.1m4fp6 or later. *
**************************************************************** |
| Comment |
This problem is first fixed in Db2 v11.1m4fp6. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.09.2020
31.03.2021
31.03.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
