|
Problem IC91739
|
Status: Closed |
CLPPLUS WILL THROW A JCC EXCEPTION WHEN CONNECTION FAILS TO ESTABLISH AND 'WHENEVER SQLERROR' CLAUSE IS SET. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
CLPPlus will throw a JCC exception when it encounters invalid
user name, password, instance port or connection is simply
refused. It is preferred that CLPPlus when 'whenever
sqlerror' clause is set acts accordingly to define action.
>clpplus
CLPPlus: Version 1.6
Copyright (c) 2009, 2011, IBM CORPORATION. All rights reserved.
SQL> WHENEVER SQLERROR EXIT
SQL> CONNECT username/password@localhost:50000/db_name
[jcc][t4][2043][11550][3.64.114] Exception
java.net.ConnectException: Error
opening socket to server localhost/127.0.0.1 on port 50,000 with
message:
Connection refused. ERRORCODE=-4499, SQLSTATE=08001
Enter DATABAE NAME [db_name]:
Above is an example of JCC exception that is side effect of
wrongly entered instance port. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All platforms. *
****************************************************************
* PROBLEM DESCRIPTION: *
* Please See Error Description. *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to DB2 10.1 FP3 *
**************************************************************** |
| Local Fix: |
No local fix is available. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC95296 IC97527
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.04.2013
08.05.2013
08.05.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
