on Jun 14, 2016Article Content
| Article Number | 000029596 |
| Applies To | RSA Product Set: RSA Identity Governance & Lifecycle RSA Product/Service Type: Appliance RSA Version/Condition: 6.9.0, 6.9.1, 7.0.0, 7.0.1 |
| Issue | Change Requests show a completion date and time in the future. (Requests > Requests > {Request name}). For example, a change request created at 9:00 AM, completed at 9:30 AM and viewed at 11:00 AM may show as completed at 4:00 PM that day which is five hours ahead of the time the change request is actually being viewed, i.e. a time that has not yet occurred. Another symptom seen are workflows getting stuck in the Approval phase even when there are no approvals to perform. (Requests > Requests > {Request name} > Workflow Jobs: Processing Workflow). If the processing workflow is edited and the approval nodes are removed, the workflow progresses to the Fulfillment phase and then gets stuck in the Fulfillment phase. There may be other symptoms not yet observed/reported. |
| Cause | This is a known issue reported in engineering ticket ACM-52283. The timezone on an RSA Identity Governance & Lifecycle appliance is defined in three places and must be the same in all three places.
where $HOSTNAME is the node name where the Oracle database is installed
Incorrect change request completion dates and stuck workflows can be caused by a mismatch between any of the three places where the timezone is defined. |
| Resolution | Starting in RSA Identity Governance & Lifecycle 6.9, the timezone defined in the Oracle Timezone file needs to be modified from TZ=GMT+<some number> to TZ=<timezone> to be the same as the timezones specified in /etc/sysconfig/clock and select dbtimezone from dual. This issue is resolved in the following RSA Identity Governance & Lifecycle versions and patch levels:
|
| Workaround | To workaround change request timing issues and stuck workflows, manually modify the value of TZ in $ORACLE_GRID_HOME/crs/install/s_crsconfig_$HOSTNAME_env.txt from TZ=GMT+<some number> to TZ=<timezone> where timezone is the value of TIMEZONE defined in /etc/sysconfig/clock and the value returned from the query select dbtimezone from dual.
Log into the Linux server as root and execute the following:
Sample output:
Using a tool such as SQL*Plus, SQL Developer or SQuirrel, connect to the Oracle database as avuser and execute the following:
Sample output:
This should report the same output as Step 1. If it does not, update the database to the same timezone. Login to the database as SYSDBA and execute the below ALTER DATABASE statement:
In this example, the command would be:
Login to the database server as user oracle and execute the following where $HOSTNAME is the node name of your server:
Sample output:
FROM: TZ=GMT+<some number> TO: TZ=<timezone value from steps 1 and 2> For example, modify: FROM: TZ=GMT+10:00 TO: TZ=Australia/Melbourne
|