home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC98141 Status: Closed

THE UTL_MAIL.SEND PROCEDURE RETURNS SQL1336 AFTER APPLYING SOLARIS PATCH

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
This is very similar to apar IC85101. 
Even though the SMTP server has been configured correctly in the 
db cfg, the UTL_MAIL.SEND procedure may still fail on the 
Solaris OS. 
This happens when running a version that fixes APAR IC85101 as 
well as after applying the relevant solaris path that fixes a 
problem with the getaddrinfo OS function. 
 
When this patch is installed, the DB2 code no longer handles the 
"right" value leading to the SQL1336 error.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 on Solaris OS users.                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the database server to V10.1 Fix Pack 4              * 
****************************************************************
Local Fix:
Uninstall the Solaris Patch.
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
This problem has first been fixed in V10.1 Fix Pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.12.2013
26.06.2014
26.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 FixList