|
Problem IC62561
|
Status: Closed |
A LOAD TERMINATE MIGHT FAIL WITH THE FOLLOWING: SQL3508N ERROR IN ACCESSING..."TEMP_FILE"... RC "1" |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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. |
| available fix packs: |
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
|
| Solution |
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 |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.08.2009
01.03.2010
01.03.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
