Solution : https://service.sap.com/sap/support/notes/67014 (SAP Service marketplace login required)
Summary :
Records persist in VBMOD and VBDATA update tables without display in SM13, due to some transactions preemptively logging entries before final dialog interactions and cancelling, leaving behind unexecuted, hanging update requests. These accumulate, especially as update servers start infrequently, consuming unnecessary memory and occasionally causing reorganization-based data inconsistencies. To mitigate, reorganization now triggers a user confirmation dialog, with background attempts halted and reported via syslog. Resolutions include specified kernel patches or setting profile parameter rdp/vbreorg to 0, and manually clearing incomplete requests via RSM13002 with appropriate cautions.
Key words :
current production operation occasionally caused data inconsistencies, consume memory space unnecessarily, profile parameter rdisp/vbreorg, delete incomplete update requests, reorganizing update data, aforementioned measures fail, incomplete update requests, final screen change, incomplete update request, warning dialog box
Related Notes :
1429935 | Report UMG_CHECK_APPLICATION_TABS |
1083709 | Error when you import Support Packages |
1081287 | Data extraction orders block the upgrade process |
762951 | Organization of structure changes in the LBWE |
706478 | Preventing Basis tables from increasing considerably |
652310 | LBWE: Message MCEX 140 with extract structure change |
571592 | XPRA RMCSBWXP_SD_2 terminates during upgrade to PI 2002.1 |
542521 | CST Patch Collection 31 2002 |
396647 | FAQ: V3 update: Questions and answers |