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

TABLESPACE IS LEFT IN STATE "LOAD IN PROGRESS" (0X20000) AFTER A
LOAD WITH COPY NO OPTION FAILED

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Problem Description: 
On a recoverable database, DB2 may leave the tablespace state in 
"load in progress" (0x20000) when a DB2 load is running against 
a table in this tablespace. 
 
If the DB2 load uses the COPY NO option (either explicitly, or 
implicitly as COPY NO is the default option), DB2 will attempt 
to put the tablespace into "backup pending" state.  If the 
attempt fails, the tablespace may be left in "load in progress" 
(0x20000) state even after the load application exited. 
 
Restarting the database can bring the tablespace back to normal 
(0x0000) from 0x20000.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL.                                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* On a recoverable database, DB2 may leave the tablespacestate * 
* in "load in progress" (0x20000) when a DB2 load isrunning    * 
* against a table in this tablespace.If the DB2 load uses the  * 
* COPY NO option (either explicitly,or implicitly as COPY NO   * 
* is the default option), DB2 willattempt to put the           * 
* tablespace into "backup pending" state.If the attempt fails, * 
* the tablespace may be left in "load inprogress" (0x20000)    * 
* state even after the load applicationexited.Restarting the   * 
* database can bring the tablespace back tonormal (0x0000)     * 
* from 0x20000.                                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to version 9.7 fix pack 2 or later.                   * 
****************************************************************
Local-Fix:
restart database after problem happened, or 
proactively use LOAD COPY YES or NONRECOVERABLE (instead of LOAD 
COPY NO) to avoid DB2 trying to put the tablespace into "backup 
pending".
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
This problem is first fixed in version 9.7 fix pack 2.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
06.01.2010
25.05.2010
25.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList