Solution : https://service.sap.com/sap/support/notes/843042 (SAP Service marketplace login required)
Summary :
In scenarios with multiple Oracle database connections, database locks generated by the "SELECT FOR UPDATE" command are not being released after a COMMIT. This issue appears when this command is used across several simultaneous database connections, which can lead to deadlocks. The underlying error is due to lock retention post-COMMIT operation. The resolution involves updating the SAP kernel to specific support package versions for different SAP releases, ensuring that locks are correctly released post-COMMIT in multi-connection environments.
Key words :
oracle lock reason, support package 5o 6, support package 72o 6, support package 1908o 4, symptom database locks, oracle database connections 3, affected database connection, support package 2058, oracle database, database connections
Related Notes :
| 843166 | DB: Load processes and deadlock on the RSMDATASTATE table |
| 745639 | FAQ: Oracle enqueues |