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

ADMIN_MOVE_TABLE WITH COPY_USE_LOAD AND WITHOUT COPY_WITH_INDEXE S LOADS
DATA AND BUILDS ALL INDEXES IN ONE TRANSACTION

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
When ADMIN_MOVE_TABLE is run with COPY_USE_LOAD and without 
COPY_WITH_INDEXES, target table with primary key (if applicable) 
is created, loaded an all indexes built in a single transaction. 
When source table has multiple indexes, it will consume 
signification transactional log space and my eventually fail 
with -964 "transactional log full" error. 
This APAR will change this behavior and transaction will be 
committed after LOAD phase and index rebuilt phase will be 
continued in a separate transaction.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5 Fix Pack 7 or higher.            * 
****************************************************************
Local-Fix:
Do not use COPY_USE_LOAD or enable COPY_WITH_INDEXES option
Lösung
Fixed in DB2 version 10.5 Fix Pack 7.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.03.2015
19.01.2016
19.04.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList