Solution : https://service.sap.com/sap/support/notes/551104 (SAP Service marketplace login required)
Summary :
The SAPLS_CCDSNU_DB2 program frequently terminates due to exceeding its allotted run time, generating consistent short dumps. In the RZ20 transaction, the nodes for DB2 Universal Database on OS/390 related to R/3 consistency checks (both hourly and daily) show as inactive, impacting proper data monitoring and system maintenance. This issue stems from the incompatibility of ABAP syntax with releases prior to SAP 610, which lacks proper exception handling in stored procedure calls, leading to uncontrolled termination and deactivated data collection methods. Solutions include adjusting the rdisp/max_wprun_time parameter or deactivating data collection methods in RZ20, with medium-term corrective actions suggested through required transports and Support Package updates for stable system maintenance.
Key words :
/3 consistency - collecting bootstrap - hourly, critical stored procedure call, explicitly checks transaction rz20, maximum permissible runtime, db2 universal database, data collection method, data collection methods, stored procedure results, takes controlled steps, medium term solution
Related Notes :
| 765983 | DB2/zOS: Reducing number of DSNACCOR REORG recommendations |
| 507824 | DB2/390 V7: Real Time Statistics and DSNACCOR |
| 324739 | DB2 z/OS: CCMS transport for 4.6D |
| 217093 | DB2 z/OS: CCMS transports for 4.6C |
| 101217 | DB2 z/OS: Overview of transports and corrections |
| 13719 | Preliminary transports to customers (note for customers) |