|
Problem IT38431
|
Status: Closed |
DB2ADUTL UPLOAD FAILS TO UPLOAD THE WHOLE RANGE OF LOGS IF ONE OF THE LOGS WAS ALREADY UPLOADED
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
db2adutl UPLOAD fails to upload the whole range of logs if one
of the logs was already uploaded. For example, if we run
'db2adutl UPLOAD logs between s1 and s10' and log file 5 was
already uploaded to the TSM server, db2adutl UPLOAD will not
upload the whole range of logs (between s1 and s10). Instead,
db2adutl UPLOAD will only upload the log range that is after the
one that was already uploaded, that is between s6 and s10 in our
example. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all db2 for LUW users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* avoid uploading logs that were already uploaded *
**************************************************************** |
| Local Fix: |
avoid uploading logs that were already uploaded |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* all db2 for LUW users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* avoid uploading logs that were already uploaded *
**************************************************************** |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.09.2021
28.09.2021
28.09.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
