SAP Knowledge Base Article - Preview

2419091 - Database locks are held for over an hour.

Symptom

For an implementation of Omnichannel banking using an Oracle database, there are numerous cases of SQL queries being locked in the database for over an hour, impacting overall database performance.  The queries must be released/killed manually several times a day.  Some of the queries which are causing the greatest issue are:

UPDATE MBK_SEC_FACTOR_AUTHEN SET numberOfTries = ? , version = ? WHERE ((systemId = ? ) AND (version = ? ))
UPDATE BPW_PmtInstruction SET CustomerID=?, PayeeID=?, PayeeListID=?, BankID=?, AcctDebitID=?, AcctDebitType=?, PayAcct=?, DateCreate=?, CurDef=?, Amount=?, RouteID=?, StartDate=?, Status=?, Memo=?, SubmittedBy=?, LastModified=?, ImmediateFundAllocation=?, ImmediateProcessing=? WHERE SrvrTID=?
DELETE FROM MBK_SEC_FACTOR_AUTHEN WHERE ((systemId = :1 ) AND (version = :2 ))


Read more...

Environment

  • SAP Online Retail Banking 8.3
  • SAP Online Business Banking 8.3
  • Oracle Database Management System 11

Product

SAP Online Business Banking 8.3 ; SAP Online Retail Banking 8.3

Keywords

Omnichannel, OCB, database, locks, Oracle , KBA , FS-OCB , SAP Omnichannel Banking , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.