|
Problem IT34589
|
Status: Closed |
ON WINDOWS PLATFORM CLIDRIVER CAN LOG SQL1531N DURING CONNECT EVEN WHEN CONNECTION IS SUCCESSFUL WITH SQL_SUCCESS_WITH_INFO
|
| product: |
DB2 CONNECT / DB2CONNCT / B50 - DB2 |
| Problem description: |
on Windows platform from V11.5.4, User level db2dsdriver.cfg
file is supported in C:Users path . When cli driver
connects to DSN , it searched in User level db2dsdriver.cfg in
C:Users path before System level db2dsdriver.cfg
file. In case DSN is not found in User level db2dsdriver.cfg it
will log the error internally and continue to search DSN in
system level db2dsdriver.cfg file and if it find the DSN then it
will try to connect to it. If the connection is successful and
if there is some invalid keyword attribute value used in
db2dsdriver.cfg /db2cli.ini or trial license is used then in
that case cli driver connect will return with
SQL_SUCCESS_WITH_INFO. if application is calling SQLGetDiagField
Function or when connection is tested with "db2cli validate -dsn
dsnname -connect " then it can show SQL1531N error.
this logging of SQL1531N error doesnot affect the subsequent SQL
operation using the connection and can be ignored. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Db2Connect users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.5.5.1 or higher *
**************************************************************** |
| Local Fix: |
Local fix
1) As logging of SQL1531N error doesnot affect the subsequent
SQL operation using the connection, it can be ignored
OR
2) Correct the cause due to which cli driver is returning
with SQL_SUCCESS_WITH_INFO after connect .
for example some invalid keyword attribute value used in
db2dsdriver.cfg /db2cli.ini or trial license used can cause the
warning
due to which SQL1531N is shown.
To find invalid keyword attribute value use ?db2cli validate
-dsn dsnname -connect? command.
Once cause is fixed cli driver will return with SQL_SUCCESS .
OR
3) Configure DSN in user level db2dsdriver.cfg file also in
C:Users path . One can reuse the same DSN
information which is present in system level db2dsdriver.cfg
file |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Db2Connect users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.5.5.1 or higher *
**************************************************************** |
| Comment |
Upgrade to Db2 11.5.5.1 or higher |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.10.2020
09.04.2021
09.04.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
