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

A LOAD TERMINATE MIGHT FAIL WITH THE FOLLOWING: SQL3508N ERROR IN
ACCESSING..."TEMP_FILE"... RC "1"

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
ABSTRACT: A load terminate might fail with the following: 
SQL3508N Error in accessing a file or path of type "TEMP_FILE" 
during load or load query.  Reason code: "1" 
 
PROBLEM SUMMARY: If the temporary load files created by the load 
utility are missing/deleted from the "TEMP_FILE" location after 
a load has been interrupted, a load terminate may fail with 
SQL3508N RC 1 since it can't locate the files.  This problem 
occurs when LOAD is able to access the load.loc file (which 
resides in a load/DB2mmmmm.PID/DB2nnnnn.OID directory underneath 
the database directory), but the LOAD temporary directory (as 
specified by TEMPFILES PATH option),  is gone.  The load.loc 
file directs LOAD to look for files in the TEMP_FILE path, but 
LOAD cannot find the files. 
 
Note: mmmmm is the tablespace ID (in hexadecimal) and nnnnn is 
the table ID (in hexadecimal) of the table in question
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of DB2 Version 9.7                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If the temporary load files created by the load utility are  * 
* missing/deleted from the "TEMP_FILE" location after a load   * 
* has been interrupted, a load terminate may fail with         * 
* SQL3508N RC 1 since it can't locate the files.  This problem * 
* occurs when LOAD is able to access the load.loc file (which  * 
* resides in a load/DB2mmmmm.PID/DB2nnnnn.OID directory        * 
* underneath                                                   * 
* the sqllib directory), but the LOAD temporary directory (as  * 
* specified by TEMPFILES PATH option),  is gone. The load.loc  * 
* file directs LOAD to look for files in the TEMP_FILE path,   * 
* but LOAD cannot find the files.                              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 1 or later.              * 
****************************************************************
Local-Fix:
- Delete the load.loc file from the first directory 
(db_dir/load/DB2mmmmm.PID/DB2nnnnn.OID) 
- Then issue the LOAD TERMINATE. 
 
The LOAD TERMINATE will now be successful and will bring the 
table out of load pending state. 
 
NOTE: In a DPF system, delete the load.loc file from all nodes 
involved in the load.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Lösung
DB2 Version 9.7 Fix Pack 1 contains fix whereby load will work 
in the absence of the temporary files, but the missing data 
will cause a LOAD RESTART to take longer to complete.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.08.2009
01.03.2010
01.03.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP1
Problem behoben lt. FixList in der Version
9.7.0.1 FixList