The workpoint log has daily occurrences of ORA-02049: timeout: distributed transaction waiting for lock errors in RSA Identity Governance & Lifecycle
Originally Published: 2018-03-05
Article Number
Applies To
RSA Version/Condition: 7.0,+, 7.0.1+, 7.0.2+, 7.1.0+
Issue
ORA-02049: timeout: distributed transaction waiting for lock
Cause
Resolution
- Login to SQL as sysdba.
- Run the following command:
SQL> ALTER system set distributed_lock_timeout=305 scope=spfile; SQL> commit;
- In the UI, navigate to Admin > System > Settings > Edit and scroll to the bottom.
- On the Custom tab, add the following two custom values:
- Set WFSaveRetries custom value to 10.
- Set WFSaveRetryWait to 3000.
Related Articles
SA error "TransportException: 28800 second timeout reached waiting for server response" 14Number of Views Change Requests in Pending Submission state are not being deleted by the daily scheduled task in RSA Identity Governance &… 70Number of Views WebSphere clustered server node causes system outages due to 'ORA-02049: timeout: distributed transaction waiting f… 363Number of Views RSA DLP Network ERROR - HttpChannel.sendViaClient(144) | javax.net.ssl.SSLException: Certificate not verified 68Number of Views RSA Governance & Lifecycle Recipes: Dashboard - Telemetry Daily 9Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?