Fusion Apps IDM - OID and ODSM Server EMAGENT giving Timezone Error and not Starting Up

Fusion Apps IDM - OID and ODSM Server EMAGENT giving Timezone Error and not Starting Up

Issue

Getting following errors while starting up OID and ODSM in Oracle Identity Management for Fusion Applications.

Error 1

failed to start a managed process after the maximum retry limit

Error 2

$ less EMAGENT/EMAGENT/sysman/log/emagent.nohup

----- Fri Apr 3 14:44:25 2015::tzOffset for Pacific/Auckland is 720(min), but agent is runnning with tzOffset 780(min)
-----
----- Fri Apr 3 14:44:25 2015::trying again after waiting for 1 sec to account for daylight transition
-----
----- Fri Apr 3 14:44:25 2015::tzOffset for Pacific/Auckland is 720(min), but agent is runnning with tzOffset 780(min)
-----
----- Fri Apr 3 14:44:25 2015::Mismatch detected between timezone in env (NZ) and in /app/oracle/config/instances/oid1/EMAGENT/EMAGENT/sysman/config/emd.properties (Pacific/Auckland). Forcing value to latter.. -----
----- Fri Apr 3 14:44:26 2015::tzOffset for Pacific/Auckland is 720(min), but agent is runnning with tzOffset 780(min)
-----
----- Fri Apr 3 14:44:26 2015::trying again after waiting for 1 sec to account for daylight transition
-----
----- Fri Apr 3 14:44:26 2015::tzOffset for Pacific/Auckland is 720(min), but agent is runnning with tzOffset 780(min)
-----
----- Fri Apr 3 14:44:26 2015::The agentTZRegion value in /app/oracle/config/instances/oid1/EMAGENT/EMAGENT/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute 'emctl resetTZ agent' and also execute the script mgmt_target.set_agent_tzrgn(<agent_name>, <new_tz_rgn>) to get the value propagated to repository -----
--- Shared agent
----- Fri Apr 3 14:44:28 2015::tzOffset for Pacific/Auckland is 720(min), but agent is runnning with tzOffset 780(min)
-----
----- Fri Apr 3 14:44:28 2015::trying again after waiting for 1 sec to account for daylight transition
-----
----- Fri Apr 3 14:44:28 2015::tzOffset for Pacific/Auckland is 720(min), but agent is runnning with tzOffset 780(min)

How to reporoduce the issue

Simply invoke the following script to start Oracle IDM for FA. The error will be thrown on the console.

$ cd /app/oracle/config/scripts
$ ./startall.sh

Resolution

Resolution for Error 1

1. On investigation we found that the following DB user accounts were under the status of 'Locked & Expired'.

MDSYS, MDDATA, SI_INFORMTN_SCHEMA, LBACSYS

2. Use following SQL to find out the DB users whose account atatus are locked and exprired:

select username, account_status from dba_users;

3. Simply unlock the above users and reset their password using following commands:

SQL> alter user MDSYS account unlock;

User altered.

SQL> alter user MDDATA account unlock;

User altered.

SQL> alter user SI_INFORMTN_SCHEMA account unlock;

User altered.

SQL> alter user LBACSYS account unlock;

User altered.

SQL > Alter user MDSYS identified by Welcome;
User altered.

SQL > Alter user MDDATA identified by Welcome;
User altered.

SQL > Alter user SI_INFORMTN_SCHEMA identified by Welcome;
User altered.

SQL > Alter user LBACSYS identified by Welcome;
User altered.

Resolution for Error 2

1. This problem is caused because EMAGENT does not seem to support NZDT (daylight savings time), so it expects offset of 720 for pacific auckland, instead of 780 (gmt-12 instead of gmt-13). So, the easiest solution is change the value of the agentTZRegion to one that's equivalent to offset 780.
But eventually, you'll need to change it back to pacific/auckland when the time changes again:

#@default=
altNmo=/app/oracle/products/dir/oid/bin/nmoprev
#agentTZRegion=Pacific/Auckland
agentTZRegion=Etc/GMT-12

2. Then restart the agent.

Environment

+ Oracle Linux 

+ Oracle Fusion Applications IDM 11.1.7

Credits

Entire credit for resolving this issue goes to our technical consulting team

Oracle Fusion: CommonDomain_webtier is not startin...
Hardening RHEL 7.1 (Maipo) - Part 1 - User access