Solution : https://service.sap.com/sap/support/notes/170319 (SAP Service marketplace login required)
Summary :
The reported issue occurs when the JCL job, engaged in fetching size information for Transaction DB02, exits with a non-zero return code, resulting in incomplete execution of the DB02 Refresh job. The subsequent data collection ignores this discrepancy, leading to corrupted historical data reports in DB02. The cause is pinpointed to inadequate error handling during the refresh operation. SAP advises importing specific transports, as detailed in Note 101217 relevant to the respective R/3 Releases, to address this issue and ensure error mitigation. Continuous review and update of the applied patches are recommended to maintain system integrity.
Key words :
additional key words db2, prerequisites missing error handling, size information displayed, newest maintenance level, db02 refresh job, jcl submission service, return code unequal, return code, missing data, additional analysis
Related Notes :
| 170271 | DB2/390: Data on init. scrn of DB12 multiplely det. |
| 151394 | DB2/390: Transports for 4.5B |
| 101303 | DB2/390: Transports for 3.1I |
| 101217 | DB2 z/OS: Overview of transports and corrections |
| 13719 | Preliminary transports to customers (note for customers) |