|
Problem IT38511
|
Status: Closed |
ROLLFORWARD OF LOAD COPY IMAGE FROM OBJECT STORAGE CANNOT BE RECOVERED DUE TO PATH TRUNCATION
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
A ROLLFORWARD operation which requires a Load Copy image file
from remote storage may fail because the full copy image file
location is truncated within the database recovery history file.
db2 rollforward db to end of logs
SQL3799W Load recovery for table "" at time
"2021091422025" on
node "0" is pending due to warning "-2036" with additional
information
"DB2REMOTE://[redacted]//LOAD/xxxxxxxxxx".
Do you want to continue(c), terminate this device only(d), abort
the utility(t) ? (c/d/t) t
SQL1271W Database "" is recovered but one or more table
spaces are offline
on members or nodes "0".
db2 rollforward db to end of logs and stop
SQL1271W Database "" is recovered but one or more table
spaces are offline
on members or nodes "0". |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Apply Db2 Version 11.5.7.0 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Apply Db2 Version 11.5.7.0 *
**************************************************************** |
| Comment |
Problem was first fixed in DB2 11.5 Mod 7 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.09.2021
01.12.2021
01.12.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
