|
Problem IC76967
|
Status: Geschlossen |
RUNNING REMOTE FETCH OR SOURCEUSEREXIT LOAD + COPY YES, LOAD COM PLETED BUT COPY IMAGE IS MISSING, OR LOAD MAY FAIL WITH SQL0902C |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
A REMOTE FETCH LOAD refers to a LOAD from CURSOR, where the
cursor is defined using the DATABASE option (or equivalently
when using the sqlu_remotefetch_entry media entry with the
db2Load API).
A SOURCEUSEREXIT LOAD refers to a LOAD using the SOURCEUSEREXIT
option.
When running either of the LOAD above, plus using the COPY YES
option, most of the time the LOAD completed successfully, but
the load copy image file is missing. The impact is that if we
ever need to restore the database/tablespace and rollforward, we
won't be able to restore the load target table, the data will be
lost forever.
Sometimes the LOAD may fail with SQL902C (instead of completed
successfully but the load copy image file is missing), and
db2diag.log may contain the following error entry:
2011-05-13-09.20.43.765943+540 E243183A402 LEVEL: Severe
PID : 11337884 TID : 13881 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000
EDUID : 13881 EDUNAME: db2lmr 0
FUNCTION: DB2 UDB, database utilities, sqluInitFileDevice,
probe:615
MESSAGE : ZRC=0x84150089=-2078998391=SQLU_OUT_OF_BOUND
"Serializable media descriptor out of bounds"
A sample scenario:
(step 1) Executed declare cursor statement with DATABASE option.
declare curs1 cursor database SAMPLE user db2inst1 using
db2inst1 for select * from db2inst1.org1
(step 2) Execute load statement with cursor and with COPY YES
option
load from curs1 of cursor replace into db2inst1.org2 statistics
use profile copy yes to /COPY_DEVICE |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* A REMOTE FETCH LOAD refers to a LOAD from CURSOR, where the *
* cursor is defined using the DATABASE option (or equivalently *
* when using the sqlu_remotefetch_entry media entry with the *
* db2Load API). *
* *
* A SOURCEUSEREXIT LOAD refers to a LOAD using the *
* SOURCEUSEREXIT *
* option. *
* *
* When running either of the LOAD above, plus using the COPY *
* YES *
* option, most of the time the LOAD completed successfully, *
* but *
* the load copy image file is missing. The impact is that if *
* we *
* ever need to restore the database/tablespace and *
* rollforward, we *
* won't be able to restore the load target table, the data *
* will be *
* lost forever. *
* *
* Sometimes the LOAD may fail with SQL902C (instead of *
* completed *
* successfully but the load copy image file is missing), and *
* db2diag.log may contain the following error entry: *
* *
* 2011-05-13-09.20.43.765943+540 E243183A402 LEVEL: *
* Severe *
* PID : 11337884 TID : 13881 PROC : *
* db2sysc *
* 0 *
* INSTANCE: db2inst1 NODE : 000 *
* EDUID : 13881 EDUNAME: db2lmr 0 *
* FUNCTION: DB2 UDB, database utilities, sqluInitFileDevice, *
* probe:615 *
* MESSAGE : ZRC=0x84150089=-2078998391=SQLU_OUT_OF_BOUND *
* "Serializable media descriptor out of bounds" *
* *
* *
* A sample scenario: *
* *
* (step 1) Executed declare cursor statement with DATABASE *
* option. *
* declare curs1 cursor database SAMPLE user db2inst1 using *
* db2inst1 for select * from db2inst1.org1 *
* *
* (step 2) Execute load statement with cursor and with COPY *
* YES *
* option *
* load from curs1 of cursor replace into db2inst1.org2 *
* statistics *
* use profile copy yes to /COPY_DEVICE *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB version 9.7 fixpack 5. *
**************************************************************** |
| Local-Fix: |
Use COPY NO option instead of COPY YES, and backup the
tablespace or database after the LOAD operation |
| verfügbare FixPacks: |
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
Problem was first fixed in DB2 UDB Version 9.7 Fix Pack 5. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC77140
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 14.06.2011
12.12.2011
12.12.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP5
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.5
|
 |
