DB2 - Problembeschreibung
Problem IC90146 | Status: Geschlossen |
DATABASE ROLLFORWARD FAILS DURING REPLAY OF A CLASSIC REORG IF THE REQUIRED SYSTEM TEMPSPACE IS IN RF PENDING | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
During roll forward of a classic (offline) table reorg that included the 'USE tablespace' clause, if the specified temporary tablespace is in roll forward pending state, the replay of the reorg will fail. This will not happen with a full database restore, but with any type of restore that involves specifying a subset of tablespaces that includes the specified system temporary tablespace; for example, 'RESTORE DATABASE <name> REBUILD WITH ALL TABLESPACES IN IMAGE EXCEPT (some other tablespace)', or 'RESTORE DATABASE <name> TABLESPACE', either with no listed table spaces (meaning all are to be restored) or with a list that includes the specified temporary tablespace. You will see severe error messages in the db2diag.log that include the error 'SQLB_NO_TEMP_AVAIL'. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Any doing classic reorg with a tempspace and a subsequent * * restore and rollforward through that operation * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10 fixpack 3 or later * **************************************************************** | |
Local-Fix: | |
Perform a full database restore without the REBUILD or TABLESPACE clauses, if possible. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
Problem first fixed in DB2 version 10 fixpack 3 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 11.02.2013 28.10.2013 28.10.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 |