home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC65091 Status: Geschlossen

IN DPF ENVIRONMENT, THE FINAL SQLCA RETURNED BY LOAD IS NOT PRINTED
INTO THE MESSAGES FILE.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Description: 
In non-DPF environment, when the Load utility is invoked with 
the MESSAGES option, all the warning and error messages that 
were generated on the server are sent back to the client and 
placed into a local message file in ascii format for easy 
legibility. Additionally, if the final sqlca returned by the 
Load utility is non zero (ie. a warning or error) then this 
warning or error message is also printed into the message file. 
 
However in DPF environment, Load will not print this final sqlca 
into the local message file. 
 
Problem Reproducible Steps: 
1.  vi db2node.pe 
    0 <hostname> 0 
    1 <hostname> 1 
2.  db2start 
3.  db2 create db sample 
4.  db2 connect to sample 
5.  db2 "create table test (c1 int, c2 int)" 
6.  db2 "load from /home/hidehy/test.del of del warningcount 1 
messages /home/hidehy/test.msg insert into hidehy.test copy yes 
to /home/hidehy/loadcopy" 
    * Please read directry names as needed 
    * The created test.msg is empty and file size is 0 on DPF 
    * If we run the above steps (except 2) on a single node, the 
test.msg has an error (SQL3522N logretain and userexit) and file 
size is not 0 as expected.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 9.7.                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description field for more information.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 FixPack 3.                            * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 UDB Version 9.7 FixPack 3.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
10.12.2009
11.10.2010
11.10.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.2 FixList
9.7.0.3 FixList
9.7.0.3 FixList