|
Problem IT05819
|
Status: Closed |
ERROR WHEN RUNNING MULTIPLE TABLESPACE ROLLFORWARD COMMANDS WITH INVALID TIMESTAMPS |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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. |
| Solution |
Problem is first fixed in DB2 UDB version 10.1 fix pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.11.2014
24.07.2015
24.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
