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
WebSphere clustered server node causes system outages due to 'ORA-02049: timeout: distributed transaction waiting f… 370Number of Views Artifacts to gather in RSA Identity Governance & Lifecycle 3.93KNumber of Views AFX Server stuck in 'Not running' State, with error 'timed out waiting for AFX applications to start' 3.63KNumber of Views Queries to detect workflows and change requests that could overload the Workpoint Server in RSA Identity Governance & Life… 286Number of Views AveksaAdmin Super Account Locked or Password Lost in RSA Governance & Lifecycle 1.75KNumber of Views
Trending Articles
RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to Upgrade Internal SHA-1 Certificates to SHA-256 in Authentication Manager Using rsautil RSA Authentication Manager 8.9 Setup and Configuration Guide How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device
Don't see what you're looking for?