Solution : https://service.sap.com/sap/support/notes/539376 (SAP Service marketplace login required)
Summary :
SAP Note identifies an issue where tables on DB2/390 are not always deleted as expected during operations such as client copy or deletion. The problem stems from reliance on outdated statistical data that inaccurately reports zero entries in tables, thus skipping the deletion process. The solution involves implementing advance corrections or updates from the Basis Support Package alongside regular updates of database statistics using the RUNSTATS command scheduled through transaction DB13. It is recommended to perform a comprehensive update of statistical data for all R/3 objects and maintain regular updates post-client operations to ensure database performance.
Key words :
relevant basis support package eliminate, attached advance corrections, client copy relies, relevant jobs, client copy, customizing copy, client deletion, symptom tables, deleted successfully, 0 0the table
Related Notes :
| 448877 | CC-ERROR: Data loss on DB2/390 |
| 206523 | CC-RELEASE: Client copy errors in 4.6C and 4.6D |
| 161495 | CC-RELEASE: Error in client copy in 4.6A and 4.6B |
| 96732 | CC-INFO: DB2/390 - client copy is very slow |