DB2 - Problembeschreibung
Problem IT05819 | Status: Geschlossen |
ERROR WHEN RUNNING MULTIPLE TABLESPACE ROLLFORWARD COMMANDS WITH INVALID TIMESTAMPS | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
If you issue a tablespace rollforward to a point in time where the timestamp used is incorrect, and then you repeat this a second time with the same invalid timestamp, this problem may occur. For example: db2 'rollforward db sample to 2014-04-17-01.06.47.000000 USING LOCAL TIME and stop tablespace (DATA8K,INDEX8K,LONG8K) online' SQL1280N The stoptime passed to roll-forward must be less than or equal to "2014-04-17-00.28.34.000000 Local" for database "SAMPLE" because at least one of the table spaces was already rolled forward to this point in time. The SQL1280N is expected, but if you issue the command again, you may get SQL1042C. db2 'rollforward db sample to 2014-04-17-01.06.47.000000 USING LOCAL TIME and stop tablespace (DATA8K,INDEX8K,LONG8K) online' SQL1042C An unexpected system error occurred. SQLSTATE=58004 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users of tablespace rollforward * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Apply DB2 Version 10.1.0.5 * **************************************************************** | |
Local-Fix: | |
Use the timestamp from the SQL1280N message on the following rollforward command. | |
Lösung | |
Problem is first fixed in DB2 UDB version 10.1 fix pack 5. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 27.11.2014 24.07.2015 24.07.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.5 |