Solution : https://service.sap.com/sap/support/notes/101717 (SAP Service marketplace login required)
Summary :
SAP systems face an issue where database transactions do not release memory, leading to operating system swaps. This memory retention is linked to database or configuration issues. The provided workaround involves setting the 'rdisp/wp_auto_contained' parameter for periodic work process restarts in SAP. This not only restarts the work process but also exits the corresponding database session, clearing sessions bogged down by large transactions. Work processes will restart automatically when exceeding preset memory limits or time intervals, ensuring data consistency via 'commit' operations. Implementation requires caution; settings should only be adjusted in instance profiles and monitored for impacts on system performance and enqueue processing.
Key words :
restart work processes periodically, rdisp/wp_no_enq = 3 rdisp/elem_per_queue = 5000, enque work process runs, restarted sap work processes, sap dialog work processes, sap work process checks, sap dispatcher starts automatically, sap work processes, check sap settings, additional key words
Related Notes :
| 789011 | FAQ: Oracle memory areas |
| 586824 | Restart SAP work processes for BW |
| 502782 | Composite SAP Note ora-4030 |
| 128221 | Increased memory consumption with Oracle >8.0.X |
| 101031 | Oracle shadow processes increase continuously |
| 53050 | Resetting of SAP Statement Cache |
| 41360 | Database configuration using onconfig parameter |
| 38307 | Reducing shared memory consumption |