|
Problem IC81707
|
Status: Geschlossen |
RESTORE WITH TRANSPORT MAY CAUSE INSTANCE TO FAIL |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
A restore with transport may cause the target database to trap
if the target database's current log file number is more 256
logs behind the current log file number of the source database.
In the db2diag.log, you may see a message similar to this:
2012-02-22-15.34.52.852044-300 I3857168A999 LEVEL: Error
PID : 18481336 TID : 3232 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000
EDUID : 3232 EDUNAME: db2logts (SAMPLE)
FUNCTION: DB2 UDB, recovery manager,
sqlpMarkDirtyPoolsInExtents, probe:1054
MESSAGE : infoForLog:
DATA #1 : Hexdump, 120 bytes
0x0A000200100299E8 : 0000 0137 0000 0000 0000 0001 3932 8001
...7........92..
0x0A000200100299F8 : 0000 0001 3A33 C000 0000 0001 4F44 FAE4
....:3......OD..
0x0A00020010029A08 : 4F45 150C 0000 0000 0000 0000 0167 0000
OE...........g..
0x0A00020010029A18 : 1002 9A18 0000 0000 0000 0000 0000 0000
................
0x0A00020010029A28 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x0A00020010029A38 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x0A00020010029A48 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x0A00020010029A58 : 0000 0000 0000 0000
........ |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* User of RESTORE WITH TRANSPORT *
****************************************************************
* PROBLEM DESCRIPTION: *
* A restore with transport may cause the target database to *
* trap *
* if the target database's current log file number is more 256 *
* logs behind the current log file number of the source *
* database. *
* In the db2diag.log, you may see a message similar to this: *
* *
* 2012-02-22-15.34.52.852044-300 I3857168A999 LEVEL: *
* Error *
* PID : 18481336 TID : 3232 PROC : *
* db2sysc *
* INSTANCE: db2inst1 NODE : 000 *
* EDUID : 3232 EDUNAME: db2logts (SAMPLE) *
* FUNCTION: DB2 UDB, recovery manager, *
* sqlpMarkDirtyPoolsInExtents, probe:1054 *
* MESSAGE : infoForLog: *
* DATA #1 : Hexdump, 120 bytes *
* 0x0A000200100299E8 : 0000 0137 0000 0000 0000 0001 3932 8001 *
* ...7........92.. *
* 0x0A000200100299F8 : 0000 0001 3A33 C000 0000 0001 4F44 FAE4 *
* ....:3......OD.. *
* 0x0A00020010029A08 : 4F45 150C 0000 0000 0000 0000 0167 0000 *
* OE...........g.. *
* 0x0A00020010029A18 : 1002 9A18 0000 0000 0000 0000 0000 0000 *
* ................ *
* 0x0A00020010029A28 : 0000 0000 0000 0000 0000 0000 0000 0000 *
* ................ *
* 0x0A00020010029A38 : 0000 0000 0000 0000 0000 0000 0000 0000 *
* ................ *
* 0x0A00020010029A48 : 0000 0000 0000 0000 0000 0000 0000 0000 *
* ................ *
* 0x0A00020010029A58 : 0000 0000 0000 0000 *
* ........ *
* Error Description *
* none *
****************************************************************
* RECOMMENDATION: *
* Apply DB2 Versoin 9.7 Fixpack 6 *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
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 |
Apply DB2 Versoin 9.7 Fixpack 6 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 28.02.2012
05.06.2012
05.06.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP6
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.6
|
 |
