|
Problem IC68201
|
Status: Closed |
TABLESPACE IS LEFT IN STATE "LOAD IN PROGRESS" (0X20000) AFTER A LOAD WITH COPY NO OPTION FAILED |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* 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. *
* *
* *
* 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". *
****************************************************************
* RECOMMENDATION: *
* Update to version 9.8 fixpack 3 or later fixpacks. *
**************************************************************** |
| 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". |
| available fix packs: |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
This problem is first fixed in version 9.8 fixpack 3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.04.2010
23.12.2010
23.12.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.3
|
 |
