Fixes are available
APAR status
Closed as program error.
Error description
Approver Initials: MB Severity: 1 Reported Release: 623 Compid: 5724C04PS Tivoli Enterprise Portal Server PROBLEM DESCRIPTION: After upgrading or installing DB2 v9.7 fp7 the TEPS fails to connect to the DB2 TEPS database. The following message displays in the TEPS cq log: ctsqlconnectionodbc.cpp,528,"CTSQLEvaluatorODBC_i::Connection::_ init") Using SQLDriverConnect with 'TEPS2'. ctsqlconnectionodbc.cpp,215,"CTSQLEvaluatorODBC_i::Connection::s qlErrorCheck") [IBM][CLI Driver] CLI0004W Invalid connection string attribute. SQLSTATE=01S00 +50FEBD81.0000 ERR: -99999, +50FEBD81.0000 SQLDriverConnect rc=1: SQL_SUCCESS_WITH_INFO This is caused by an extra parameter passed in the connection string "CONNECTION_LIMIT=100". DB2 does not prevent the connection but returns SQL_SUCCESS_WITH_INFO. This appears to be new. The subsequent call to GetConnectionAttr fails and throws an exception. This has only been reported in Windows 32 bit environment. It is unclear why the exception is thrown from GetConnectionAttr, but solution is to simply remove the additional connection paramter that is not valid for DB2.
Local fix
The Windows registry can be updated with a connection string that does not contain the CONNECTION_LIMIT=100 parameter.
Problem summary
After upgrade to DB2 v9.7.7 the portal server has problems connecting to the portal server database. With no tracing turned on messages like the following will display: ctsqlconnectionodbc.cpp,543,"CTSQLEvalODBC::Connection::establis hConnection") Unknown SQL Exception: dsn = TEPS2 ctsqlconnectionodbc.cpp,544,"CTSQLEvalODBC::Connection::establis hConnection") EXCEPTION: Unknown exception ctsqlaccessodbc.cpp,290,"CTSQLEvalODBC::IssueStatementWorker::ru n") ERROR: unable to establish database connection to 'TEPS2' ctpropertysequence.cpp,716,"CTPropertySequence::Dump") ---> name = EXCEPTION: Previous SQL Exception: connection = 05025B20 Turning on the following tracing at the portal server: ERROR (UNIT:ctsql INPUT ERROR)(UNIT:ctdata INPUT ERROR)(UNIT:ctsqlconnectionodbc ERROR DETAIL INPUT) Will give the following error messages at the time of failure: ctsqlconnectionodbc.cpp,632,"CTSQLEvalODBC::Connection::_init") Using SQLDriverConnect with 'TEPS2'. ctsqlconnectionodbc.cpp,289,"CTSQLEvalODBC::Connection::sqlError Check") [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed, GENERIC SQLSTATE: IM006, ERR: 0 +511A7CE6.0000 SQLDriverConnect rc=1: SQL_SUCCESS_WITH_INFO ctsqlconnectionodbc.cpp,543,"CTSQLEvalODBC::Connection::establis hConnection") Unknown SQL Exception: dsn = TEPS2 ctsqlconnectionodbc.cpp,544,"CTSQLEvalODBC::Connection::establis hConnection") EXCEPTION: Unknown exception ctsqlaccessodbc.cpp,290,"CTSQLEvalODBC::IssueStatementWorker::ru n") ERROR: unable to establish database connection to 'TEPS2' This problem has only been seen only on 32 bit Windows portal server platforms.
Problem conclusion
This problem is related to a parameter value passed in the connection string "CONNECTION_LIMIT=100". This parameter has no meaning to DB2, and is ignored by DB2. The SQLDriverConnect function returns SQLDriverConnect rc=1: SQL_SUCCESS_WITH_INFO. But the subsequent call to SQLGetConnectAttr throws an unknown exception. Removing the CONNECTION_LIMIT=100 parm from the connection string corrects the problem. Changed the portal server connection code to remove the CONNECTION_LIMIT parameter from the connection string. The fix for this APAR is included in the following maintenance vehicle: | fix pack | 6.2.3-TIV-ITM-FP0003 | Note: Search the IBM technical support web site for maintenance package availability.
Temporary fix
The connection string is encrypted and stored in the Windows registry. As a work around, the following registry key can be updated: HKEY_LOCAL_MACHINE\SOFTWARE\Candle\KFW\CNPS\KFWSRV\Environment\D SC0 with the value: DSN=TEPS2;UID=xxxxxx;PWD=yyyyyy Where xxxxxx is the userid used to connect to DB2, by default the userid is TEPS and yyyyyy is the password for that userid.
Comments
APAR Information
APAR number
IV35831
Reported component name
TEPS
Reported component ID
5724C04PS
Reported release
622
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-01-24
Closed date
2013-02-13
Last modified date
2013-05-07
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TEPS
Fixed component ID
5724C04PS
Applicable component levels
R623 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"622"}]
Document Information
Modified date:
30 December 2022