DB2 - Problem description
Problem IC98273 | Status: Closed |
ERROR CLI0199E WHEN CONNECTING TO A CATALOGED DATABASE IF AUTHENTICATION IS SPECIFIED IN CONNECTION STRING OR DB2CLI.INI | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
You get error "CLI0199E Invalid connection string attribute" when you try to connect using the CLI (Call Level Interface) API to a cataloged database if the Authentication parameter is specified in the connection string or in the db2cli.ini initialization file. Related APARs IC95688, IC95824, IC96358 and IC96683 are for an error when the Authentication parameter is specified not in the connection string or in the db2cli.ini initialization file but in the db2dsdriver.cfg file. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of DB2 for Linux, UNIX and Windows applications that * * use the CLI (Call Level Interface) API to connect to a * * database * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * . * **************************************************************** | |
Local Fix: | |
As a workaround, you can omit the Authentication parameter from the connection string and the db2cli.ini initialization file. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 10.1 Fix Pack 4 At a minimum, this fix should be applied on the client. | |
Workaround | |
As a workaround, you can omit the Authentication parameter from the connection string and the db2cli.ini initialization file. | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC98475 IC98476 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 11.12.2013 03.06.2014 03.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 |