000039121 - Access Requests and Workflows rely on the Application Server and Database Server times to be in synch in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jul 14, 2020
Version 1Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000039121
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: All
Platform (DB): Oracle remote database
 
IssueWhen setting up a remote Oracle database for use with RSA Identity Governance & Lifecycle, it is important to ensure that the RSA Identity Governance & Lifecycle application server and the Oracle database server times are within one minute or less of each other. A discrepancy between the two times greater than one minute can result in unpredictable behaviors such as:
  • Escalation workflows may not trigger
  • Change requests may show incorrect request times or future dates
  • Workflows may get stuck in nodes that have no work to be performed, and
  • Other unexpected behaviors
ResolutionThe RSA Identity Governance & Lifecycle application has a built-in check upon startup that prevents the application from starting if the application server time and the database server time are greater than five minutes apart. However, unless these times are within a minute of each other the above unpredictable behaviors may occur. Ensure your application server and database server times are in synch.
 

Attachments

    Outcomes