Solution : https://service.sap.com/sap/support/notes/356208 (SAP Service marketplace login required)
Summary :
After a transport or a Support Package import involving DDIC changes, such as adding a column to table VBAK, there is potential for a lock on table D010SINF. This lock arises because the system sets a lock during program generation, which is triggered when a 'touched' program (a program using the modified table) is run. Problems occur when a background job, which does not perform DB commits like a dialog transaction, locks the database because the COMMIT WORK command or the job completion which releases the lock happens much later. This scenario leads to lock contention visible via SM50 or DB01. SAP's recommended solution is to use remote generation or to pre-generate impacted objects using SGEN to prevent such situations.
Key words :
system adjusts generation tables d010linf, lock situation convenientlyin transaction db01, oracle master data id, explicit abap commit work, sql trace display popup, background job starts directly, avoid running background jobs, system setsa database lock, application server ebihp750 / process 25, avoid changing tables
Related Notes :
| 745639 | FAQ: Oracle enqueues |
| 351695 | LOAD_PROGRAM_CLASS_MISMATCH |
| 5451 | LOAD_PROGRAM_LOST |