|
Problem IC66788
|
Status: Closed |
BAD ARGUMENT -443 IN UTL_TCP.IMP_READ_LINE() FROM CALL TO UTL_SMTP.OPEN_CONNECTION |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
db2set DB2_COMPATIBILITY_VECTOR=ORA
db2start
db2 create db...
given the following call:
UTL_SMTP.OPEN_CONNECTION(CONST_V_SERVER, CONST_V_PORT, W_O_SMTP,
NULL, W_O_REPLY);
got the following error.
SQL0443N Routine "UTL_TCP.IMP_READ_LINE" (specific name
"UTL_TCP_IMP_READ_LINE") has returned an error SQLSTATE with
diagnostic text "UTL_TCP.BAD_ARGUMENT". SQLSTATE=5UA0I |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See the APAR description. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB version 9.7 fixpack 2. *
**************************************************************** |
| Local Fix: |
Specify positive value instead of NULL in timeout value. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 2. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC67123
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.03.2010
17.05.2010
17.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
