Solution : https://service.sap.com/sap/support/notes/928044 (SAP Service marketplace login required)
Summary :
As of BW Release 7.0, the BW lock server has been implemented for BW Integrated Planning and Business Planning and Simulation (BW-BPS), making prior implementations obsolete. This note clarifies that the BW lock server is distinct from the standard SAP lock server and outlines where the lock table can be stored: the SAP lock server, shared objects memory, or liveCache. For liveCache usage, see specific SAP Notes. It emphasizes necessary precautions to avoid system failures due to exceeding predetermined lock table sizes and provides guidelines for setting relevant system profile parameters. For systems utilizing standalone enqueue servers, adjustments must be made per Note 1003588. Additional SAP Notes and transaction RZ11 are referenced for further information on profile settings necessary for optimizing lock table functionality within BW environments.
Key words :
profile parameter isenque/process_location = remotesa, lock entry requires approximately 1 kb, profile parameters enque/snapshot_pck_size enque/snapshot_pck_ids, user 2 plans product group pg2, bw lock server response times, system issues message 'field catalog, values enque/snapshot_pck_size = 50000 enque/snapshot_pck_ids = 10000, older bw bps releases, profile parameter enque/table_size, user 1 plans product p1
Related Notes :
| 1594606 | BW lock server and standalone enqueue server II |
| 1531412 | liveCache as BW lock server |
| 1359361 | RSPLSE: Expert mode and display of navigation attributes |
| 1322182 | Memory consumption of ABAP Shared Objects |
| 1164657 | RSPLSE change mode: Radio button is not active |
| 1016594 | BI lock server and SAP standalone enqueue server |
| 1003588 | BI lock server: Error when you use the SAP lock server |
| 996238 | Dump: 'RFC connection error' after BW system copy |
| 994239 | BI lock server: Message RSPLS091 |
| 816730 | Lock server based on SAP liveCache technology |