|
Problem IT36810
|
Status: Closed |
FODC TRAP might occur when using UTL_MAIL module
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
When using UTL_MAIL module FODC TRAP might occur.
CLP Error:
SQL0443N Routine "UTL_TCP.IMP_WRITE_TEXT" (specific name
"UTL_TCP_IMP_WRITE_TEXT") has returned an error SQLSTATE with
diagnostic text "UTL_TCP.NETWORK_ERROR". SQLSTATE=5UA0H
Depending on the platform and where the trap occurs the name for
function sqleml_utl_tcp_read_line() might not show up on the
stack. Else a typical stack would show something like this:
#10 0x00007fb775bc393e in __mempcpy_sse2 () from
./core/lib64/libc.so.6
#11 0x00007fb775bb2689 in __GI__IO_default_xsputn () from
./core/lib64/libc.so.6
#12 0x00007fb775b8269d in vfprintf () from
./core/lib64/libc.so.6
#13 0x00007fb775ba7aab in vsprintf () from
./core/lib64/libc.so.6
#14 0x00007fb775b8b9f7 in sprintf () from
./core/lib64/libc.so.6
#15 0x00007fb0abdd717b in sqleml_utl_tcp_read_line () from
./core/home/bigsql/sqllib/bin/routine/db2modlib |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* First fixed in Db2 11.1 Mod 4 Fixpack 6 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* First fixed in Db2 11.1 Mod 4 Fixpack 6 *
**************************************************************** |
| Comment |
First fixed in Db2 11.1 Mod 4 Fixpack 6 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.05.2021
06.05.2021
06.05.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
