000031682 - New Change Requests become stuck at every Approval Node regardless of Approval status in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support on Sep 2, 2020
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000031682
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle 
RSA Version/Condition: All
Platform/Application Server: WildFly
Platform: SUSE Linux Enterprise Server (SLES)
 
IssueNew Change Requests become stuck at each node of the Approval Workflow even if the request has been approved or no approval is required.The Change Request remains in the Approval phase long after all needed approvals have been completed and eventually moves to the Fulfillment phase, possibly more than a day later.
 
CauseThere is a time difference between the WildFly application server and the Oracle database.
 
ResolutionTo resolve this issue, login to the RSA Identity Governance & Lifecycle server as the oracle user and follow the below steps to adjust the time.
  1. Stop RSA Identity Governance & Lifecycle and the Oracle services:


acm stop
acm stoporacle


  1. Switch to the root user and set the correct time zone. This step may be skipped if the configured timezone is correct. 

  If /etc/localtime is NOT a symbolic link:


  1. Check the contents of /etc/localtime to verify if the timezone is already correct. If it is, then skip to Step 3.


zdump /etc/localtime


  1. Backup the currently configured timezone:


su -
cp /etc/localtime /etc/localtime.backup_<date>


  1. Find your correct timezone in /usr/share/zoneinfo. An example would be /usr/share/zoneinfo/US/Eastern.
  2. Replace the currently configured timezone with the correct one.  


cp <new_timezone> /etc/localtime


EXAMPLE:



cp /usr/share/zoneinfo/US/Eastern /etc/localtime



If /etc/localtime is a symbolic link:



  1. Check the link to verify if the timezone is already correct. If it is, then skip to Step 3.


# ll /etc/localtime
/etc/localtime -> /usr/share/zoneinfo/<timezone>


EXAMPLE:



# ll /etc/localtime
/etc/localtime -> /usr/share/zoneinfo/US/Eastern


  1. Backup the symbolic link:


tar -cvf localtime_backup<date>.tar /etc/localtime


  1. Find your correct timezone in /usr/share/zoneinfo. An example would be /usr/share/zoneinfo/US/Eastern.
  2. Modify the symbolic link to point to the new timezone.


ln -sfn /usr/share/zoneinfo/<new_timezone> localtime


EXAMPLE:



ln -sfn /usr/share/zoneinfo/US/Eastern localtime


  1. Set the correct date and time. The command should look like this.


date -s "DD MMM YYYY HH:MM:SS"


  1. Sync the BIOS hardware clock.


hwclock -w


  1. Switch to the oracle user, then start Oracle services.


su - oracle
acm startoracle


  1.  Login to the database as SYSDBA to clear any database cache issues related to time:


SQLPLUS / as SYSDBA
SQL> STARTUP FORCE;


  1. Start RSA Identity Governance & Lifecycle 


acm start


 

Attachments

    Outcomes