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 IC84353 Status: Geschlossen

IN DPF ENV., LOADING FROM REMOTE FETCH CURSOR BETWEEN DIFFERENT
ENDIAN-BASED PLATFORMS MIGHT CAUSE DATA LOSS

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
When loading data using the CURSOR file type between two 
different databases (aka. Load Remote Fetch), if both of 
databases are partitioned databases, but on different 
endian-based platforms, e.g. one is Linux on x86/x86-64 
(little-endian) and the other is AIX on POWER (big-endian), the 
data on some partitions might not be loaded into the target 
database you currently connect to. 
 
db2move might also have the same problem when using the COPY 
action to move data between two different databases.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When loading data using the CURSOR file type between two     * 
* different databases (aka. Load Remote Fetch), if both of     * 
* databases are partitioned databases, but on different        * 
* endian-based platforms, e.g. one is Linux on x86/x86-64      * 
* (little-endian) and the other is AIX on POWER (big-endian),  * 
* the                                                          * 
* data on some partitions might not be loaded into the target  * 
* database you currently connect to.                           * 
*                                                              * 
* db2move might also have the same problem when using the COPY * 
* action to move data between two different databases.         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v10fp1.                                       * 
*                                                              * 
* Use EXPORT or db2move with the EXPORT action to export data  * 
* from                                                         * 
* the source database to data files, then load data from the   * 
* data                                                         * 
* files to the target database.                                * 
****************************************************************
Local-Fix:
Use EXPORT or db2move with the EXPORT action to export data from 
the source database to data files, then load data from the data 
files to the target database.
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
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
The fix will be included in db2_v10fp1.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.06.2012
07.11.2012
07.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList