Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC88309 Status: Geschlossen

UTL_MAIL.SEND() PROCEDURE RETURNS SQL1336N

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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
verfügbare FixPacks:
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

Lösung
Problem fixed in DB2 Version 10 Fix Pack 2.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.11.2012
01.07.2013
01.07.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.2 FixList
10.5.0.2 FixList