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 IC88309 Status: Closed

UTL_MAIL.SEND() PROCEDURE RETURNS SQL1336N

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
UTL_MAIL.SEND() procedure returns SQL1336N on correctly 
configured DB2 installation. 
 
Example: 
    db2 "CALL UTL_MAIL.SEND('user1@ibm.com', 'user2@ibm.com', 
NULL, NULL, 'TEST', 'TEST)" 
 
    SQL1336N The remote host "mailserver.ibm.com" was not found. 
SQLSTATE=08001.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users running DB2 on Oracle Solaris 10.                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10 Fix Pack 2.                        * 
* Oracle Solaris 10 fix for CR# 6847733 'getaddrinfo returns   * 
* wrong protocol' is required.                                 * 
****************************************************************
Local Fix:
No local fix
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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
Problem fixed in DB2 Version 10 Fix Pack 2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.11.2012
01.07.2013
01.07.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList