Installation of OMA Fails with Time Zone Issue

Contents

  1. 1 Overview
  2. 2 Status
  3. 3 Solution
  4. 4 References
  5. 5 Investigation
    1. 5.1 OMA Start Up Fails
    2. 5.2 Examine Logs
    3. 5.3 Check OMA Time Zone
  6. 6 Correct Time Zone
    1. 6.1 Check for Supported Time Zones
    2. 6.2 Update OMA Configuration
    3. 6.3 Configure OMA with New Time Zone
    4. 6.4 Update OMR
  7. 7 Continue with OMA Installation
    1. 7.1 Start OMA
    2. 7.2 Add Internal Targets to OMA
    3. 7.3 Run Root Script

Overview

Installation of OMA to gordon failed with Time Zone Mismatch.

Status

Resolved

Solution

Update time-zone as described in Doc ID 1519859.1 .

References

Investigation

OMA Start Up Fails

The start-up of the OMA fails with the following message: 

Oracle Enterprise Manager Cloud Control 12c Release 4  
Copyright (c) 1996, 2014 Oracle Corporation.  All rights reserved.
Starting agent .............failed.
Consult emctl.log and emagent.nohup in: /opt/app/oracle/agent12c/agent_inst/sysman/log

Examine Logs

The log, /opt/app/oracle/agent12c/agent_inst/sysman/log/emagent.nohup , shows the following message: 

OMS decided to shutdown the agent because of the following reason sent from OMS:  AGENT_TZ_MISMATCH

Check OMA Time Zone

I used the following command to check the time-zone used by the agent (OMA): 

/opt/app/oracle/agent12c/agent_inst/bin/emctl config agent getTZ

The result was: 

Oracle Enterprise Manager Cloud Control 12c Release 4  
Copyright (c) 1996, 2014 Oracle Corporation.  All rights reserved.
Australia/ACT

Correct Time Zone

Check for Supported Time Zones

The supported time zones are in /opt/app/oracle/agent12c/core/12.1.0.4.0/sysman/admin/supportedtzs.lst . In that file, I found the following time zone: 

Australia/Sydney

Update OMA Configuration

The OMA configuration in /opt/app/oracle/agent12c/agent_inst/sysman/config/emd.properties was updated with: 

agentTZRegion=Australia/Sydney

Configure OMA with New Time Zone

I used the following commands to update the OMA with the following commands: 

export TZ=Australia/Sydney
/opt/app/oracle/agent12c/agent_inst/bin/emctl resetTZ agent

The result was: 

Oracle Enterprise Manager Cloud Control 12c Release 4  
Copyright (c) 1996, 2014 Oracle Corporation.  All rights reserved.
Updating /opt/app/oracle/agent12c/agent_inst/sysman/config/emd.properties...
Successfully updated /opt/app/oracle/agent12c/agent_inst/sysman/config/emd.properties.
Login as the em repository user and run the  script:
exec mgmt_target.set_agent_tzrgn('gordon.yaocm.id.au:3872','Australia/Sydney')
and commit the changes
This can be done for example by logging into sqlplus and doing
SQL> exec mgmt_target.set_agent_tzrgn('gordon.yaocm.id.au:3872','Australia/Sydney')
SQL> commit

Update OMR

On REPOS , the following SQL*Plus commands were run: 

exec mgmt_target.set_agent_tzrgn('gordon.yaocm.id.au:3872','Australia/Sydney')
commit;

Continue with OMA Installation

Start OMA

Started OMA with the following command: 

/opt/app/oracle/agent12c/agent_inst/bin/emctl start agent

The result was: 

Oracle Enterprise Manager Cloud Control 12c Release 4  
Copyright (c) 1996, 2014 Oracle Corporation.  All rights reserved.
Starting agent ........ started.

Add Internal Targets to OMA

Added internal targets to the OMA with the following command: 

/opt/app/oracle/agent12c/agent_inst/bin/emctl config agent addinternaltargets

The result was: 

Oracle Enterprise Manager Cloud Control 12c Release 4  
Copyright (c) 1996, 2014 Oracle Corporation.  All rights reserved.

Run Root Script

Ran the OMA root script with the following command: 

sudo /opt/app/oracle/agent12c/core/12.1.0.4.0/root.sh

The result was: 

Finished product-specific root actions.
/etc exist

Creating /etc/oragchomelist file...