|
Problem IC78755
|
Status: Closed |
AFTER LOAD CLIENT FAILURE, DB2 TABLESPACE IS IN 0X20020 STATE, BUT LOAD QUERY SHOWS TABLE IN NORMAL STATE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
This APAR is a complement of APAR JR35683.
APAR JR35683 fixed the problem only when client and server
systems are of the same endian, i.e. both are big-endian
platforms or both are little-endian platforms. This APAR fixes
the problem in all cases.
Big-endian platforms are AIX, HP on IA64, Solaris SPARC, Linux
on zSeries, Linux on pSeries.
Little-endian platforms are Solaris x64, Linux on IA-64, Linux
on AMD64 and Intel EM64T, 32-bit Linux on x86, Windows.
If the input file is incorrect while loading a table with LOAD
CLIENT, load encounters error, and the tablespace is left in
"Load in progress" state. For example:
1:----
LOAD CLIENT FROM C:\a.del OF DEL MODIFIED BY COLDEL0x09
USEDEFAULTS METHOD P (1, 2, 3) replace INTO AYSEL.TABLO1 (A,
B,C) COPY NO INDEXING MODE AUTOSELECT
SQL3039W The memory available to LOAD for DATA BUFFER prohibits
full
LOAD parallelism. Load parallelism of "4" will be used
SQL3109N The utility is beginning to load data from file
"C:\a.del".
SQL2036N The path for the file or device "C:\a.del" is not
valid.
SQL3107W There is at least one warning message in the message
file.
Number of rows read = 0
Number of rows skipped = 0
Number of rows loaded = 0
Number of rows rejected = 0
Number of rows deleted = 0
Number of rows committed = 0
2:----
LOAD query table AYSEL.TABLO1
SQL3039W The memory available to LOAD for DATA BUFFER prohibits
full LOAD parallelism. Load parallelism of "4" will be used
SQL3109N The utility is beginning to load data from file
"C:\a.del".
SQL2036N The path for the file or device "C:\a.del" is not
valid.
SQL3532I The Load utility is currently in the "UNKNOWN" phase.
Tablestate:
Load in Progress
3:----
Customer terminates LOAD:
LOAD CLIENT FROM C:\a.del OF DEL MODIFIED BY COLDEL0x09
USEDEFAULTS METHOD P (1, 2, 3) terminate INTO AYSEL.TABLO1
SQL3110N The utility has completed processing. "0" rows were
read from the input file.
Number of rows read = 0
Number of rows skipped = 0
Number of rows loaded = 0
Number of rows rejected = 0
Number of rows deleted = 0
Number of rows committed = 0
4:----
Customer checks the table state:
LOAD query table AYSEL.TABLO1
Tablestate:
Normal
5:----
Customer checks the tablespace
Name = AYSELTS01
Type = System managed space
Contents = All permanent data. Regular table space.
State = 0x20020
Detailed explanation:
Backup pending
Load in progress
Although no load job are running and table is in normal state,
the tablespace is left in "Load in progress" state. As a result
customer cannot take any backup. Drop/Create Tablespace or
db2stop/db2start solves the issue. Deactivate the database or
disconnect all clients from the database should also clear the
"Load in progress" state. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users of version 9.5 on Linux, Unix and Windows *
* platforms. *
****************************************************************
* PROBLEM DESCRIPTION: *
* This APAR is a complement of APAR JR35683. *
* APAR JR35683 fixed the problem only when client and server *
* systems are of the same endian, i.e. both are big-endian *
* platforms or both are little-endian platforms. This APAR *
* fixes the problem in all cases. *
* Big-endian platforms are AIX, HP on IA64, Solaris SPARC, *
* Linux on zSeries, Linux on pSeries. *
* Little-endian platforms are Solaris x64, Linux on IA-64, *
* Linux on AMD64 and Intel EM64T, 32-bit Linux on x86, *
* Windows. *
* *
* If the input file is incorrect while loading a table with *
* LOAD CLIENT, load encounters error, and the tablespace is *
* left in "Load in progress" state. For example: *
* *
* *
* *
* 1:---- *
* *
* *
* *
* LOAD CLIENT FROM C:\a.del OF DEL MODIFIED BY COLDEL0x09 *
* USEDEFAULTS METHOD P (1, 2, 3) replace INTO AYSEL.TABLO1 (A, *
* B,C) COPY NO INDEXING MODE AUTOSELECT *
* *
* *
* *
* SQL3039W The memory available to LOAD for DATA BUFFER *
* prohibits *
* full *
* *
* LOAD parallelism. Load parallelism of "4" will be used *
* *
* *
* *
* SQL3109N The utility is beginning to load data from file *
* *
* "C:\a.del". *
* *
* *
* *
* SQL2036N The path for the file or device "C:\a.del" is not *
* *
* valid. *
* *
* *
* *
* SQL3107W There is at least one warning message in the *
* message *
* file. *
* *
* *
* *
* Number of rows read = 0 *
* *
* Number of rows skipped = 0 *
* *
* Number of rows loaded = 0 *
* *
* Number of rows rejected = 0 *
* *
* Number of rows deleted = 0 *
* *
* Number of rows committed = 0 *
* *
* *
* *
* *
* *
* 2:---- *
* *
* *
* *
* LOAD query table AYSEL.TABLO1 *
* *
* *
* *
* SQL3039W The memory available to LOAD for DATA BUFFER *
* prohibits *
* *
* *
* full LOAD parallelism. Load parallelism of "4" will be used *
* *
* *
* *
* SQL3109N The utility is beginning to load data from file *
* *
* "C:\a.del". *
* *
* *
* *
* SQL2036N The path for the file or device "C:\a.del" is not *
* *
* valid. *
* *
* *
* *
* SQL3532I The Load utility is currently in the "UNKNOWN" *
* phase. *
* *
* *
* Tablestate: *
* *
* Load in Progress *
* *
* *
* *
* *
* *
* 3:---- *
* *
* Customer terminates LOAD: *
* *
* *
* *
* LOAD CLIENT FROM C:\a.del OF DEL MODIFIED BY COLDEL0x09 *
* *
* USEDEFAULTS METHOD P (1, 2, 3) terminate INTO AYSEL.TABLO1 *
* *
* *
* *
* SQL3110N The utility has completed processing. "0" rows *
* were *
* read from the input file. *
* *
* *
* *
* Number of rows read = 0 *
* *
* Number of rows skipped = 0 *
* *
* Number of rows loaded = 0 *
* *
* Number of rows rejected = 0 *
* *
* Number of rows deleted = 0 *
* *
* Number of rows committed = 0 *
* *
* *
* *
* *
* *
* 4:---- *
* *
* Customer checks the table state: *
* *
* *
* *
* LOAD query table AYSEL.TABLO1 *
* *
* *
* *
* Tablestate: *
* *
* Normal *
* *
* *
* *
* *
* *
* 5:---- *
* *
* Customer checks the tablespace *
* *
* *
* *
* *
* *
* Name = AYSELTS01 *
* *
* Type = System managed space *
* *
* Contents = All permanent data. Regular table space. *
* *
* State = 0x20020 *
* *
* Detailed explanation: *
* *
* Backup pending *
* *
* Load in progress *
* *
* *
* *
* *
* *
* Although no load job are running and table is in normal *
* state, *
* the tablespace is left in "Load in progress" state. As a *
* result *
* customer cannot take any backup. Drop/Create Tablespace or *
* *
* db2stop/db2start solves the issue. Deactivate the database *
* or *
* disconnect all clients from the database should also clear *
* the *
* "Load in progress" state. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB Version 9.5 Fix Pak 9 or higher levels. *
**************************************************************** |
| Local Fix: |
Deactivate the database or disconnect all clients from the
database should clear the "Load in progress" state. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 LUW Version 9.5 Fix Pak 9. |
| Workaround |
Deactivate the database or disconnect all clients from the
database should clear the "Load in progress" state. |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC79471
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.09.2011
12.03.2012
12.03.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.0.,
9.5.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.9
|
 |
