|
Problem IC96683
|
Status: Closed |
DB2CLI VALIDATE -DSN <DSN> -CONNECT FAILES WITH SQL1032N ERROR |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
db2cli validate -dsn <dsn> -connent, fails with SQL1032N error.
The problem only happens under these conditions:
1. DSN is defined in db2dsdriver.cfg and parameter
name=authentication is set.
e.g.
<dsn alias="HA" host="hostname" name="SAMPLE" port="12345">
<parameter name="Authentication" value="client" />
AND
2. Same dbalias name as DSN name is catalog in database
directory.
e.g.
db2 catalog tcpip node nodename remote hostname server 12345
db2 catalog db sample as ha at node nodename authentication
client
Sample output:
db2cli validate -dsn ha -connect
Connecting to: ha
[IBM][CLI Driver] SQL1032N No start database manager command
was issued. SQLSTATE=57019
Connect Status: failure
End Connection Section
----------------------------------------------------------------
-----------
Error: The validation operation failed. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 Users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 10.1.4 or later *
**************************************************************** |
| Local Fix: |
Remove this line in db2dsdriver.cfg: <parameter
name="Authentication" value="client" /> |
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Upgrade to 10.1.4 or later |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.10.2013
26.06.2014
26.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
