|
Problem IT08217
|
Status: Geschlossen |
DB2RFPEN MIGHT SET INCORRECT TIME TO GLFH WHEN USING NON-DB2 OFFLINE BACKUP IMAGE |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problembeschreibung: |
db2rfpen might set the incorrect time to GLFH when using the
non-DB2 offline backup image, such as TimeFinder image.
1. db2stop
2. Restore the non-DB2 offline backup image
3. db2start
4. db2rfpen on db_name
5. db2 rollforward db db_name query status
6. db2 rollforward db db_name to PIT using local time
7. db2 rollforward db db_name complete
"rollforward db db_name query status" might report the "Last
committed transaction" as "2106-02-07.06.28.15.000000 UTC", and
rollforward to PIT might fail with SQL1275N. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* Users who use non-DB2 offline backup image. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to DB2 V10.5 FixPack 7 or later. *
**************************************************************** |
| Local-Fix: |
Not available. |
| Lösung |
This problem was first fixed in DB2 V10.5 FixPack 7. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 10.04.2015
26.01.2016
26.01.2016 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.5.0.7
|
 |
