home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT04943 Status: Geschlossen

DB2RFPEN MIGHT SET INCORRECT TIME TO GLFH WHEN USING NON-DB2 OFFLINE BACKUP
IMAGE

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - 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:                                              * 
* DB2 UDB Version 10.1                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.1 FixPack 5.                           * 
****************************************************************
Local-Fix:
Not available.
Lösung
Problem was first fixed in DB2 UDB Version 10.1 FixPack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
15.10.2014
17.07.2015
17.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList