Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

DB Contention when using large object in the DML



When using Larget objects in DMLs, database contention occurs in the applicatoin and the system does not respond.

Error Messages

[WebContainer : 26] [ ] [ ] [ ] (web.impl.WebStandardImpl) ERROR   - : Problem retrieving input data: Async IO operation failed (3), reason: RC: 107  Transport endpoint is not connected

Steps to Reproduce

  1. Add  multiple work tables and one Assign_worklist table.
  2. Have a large number users (3K concurrent) accessing the assignments from worklist . Contention occurs and the system does not respond

Root Cause

A defect or configuration issue in the operating environment  Securefiles DMLs cause high 'buffer busy waits' & 'enq: TX - contention' wait events leading to whole database performance degradation (Doc ID 1532311.1).


Perform the following local-change:
  1. Log in to the database as a sysdba.
  2. Run the following query:

    alter system set "_securefiles_concurrency_estimate"=50 scope=spfile;
  3. Restart the database instance and application server for the changes to take effect. By increasing this parameter, less concurrency contention is expected on the securefiles.
  4. Recreate any table that contains securefiles especially the contended table (recreating the contended table is necessary since the hidden parameter '_securefiles_concurrency_estimate' is picked up for securefiles setting only during creation'.
  5. To reduce the number of concurrent requests, use a Composite Range Hash partition to partition the table affected by TX - contention.


Published May 11, 2019 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us