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
Last Modified: 2023-11-30
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
Impersonation error when creating a token using runtimeAPI.createToken 22Number of Views WebSphere clustered server node causes system outages due to 'ORA-02049: timeout: distributed transaction waiting f… 374Number of Views AFX server fails to start with a message: WARNING!! Timed out waiting for AFX applications to start in RSA Identity Govern… 144Number of Views Questions on creating an AFX connector to PostgreSQL using a generic ODBC driver in RSA Identity Governance & Lifecycle 141Number of Views RSA Governance & Lifecycle 8.0 P07 HF01 Release Notes 48Number of Views
Trending Articles
Artifacts to gather in RSA Identity Governance & Lifecycle How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle How to Download and Reinstall the AFX Server Archive in RSA Governance & Lifecycle
Don't see what you're looking for?