Update an agent’s time zone when the OS TZ has changed

Posted on : 30-06-2013 | By : Elisabeta Olteanu | In : Oracle Enterprise Manager targets

Tags: , , ,

0

When changing the time zone on an agent machine, at the operating system level the agent loses the connection with the Oracle Management Server and becomes unreachable:

In order to be able to identify if the server time zone is the actual cause of the agent unreachability issue, one can check for the emagent.nohup log residing in the following folder \sysman\log . If there is a server time zone agent problem related to the OS time changethe latest entries in the above mentioned file should resemble the following lines:

—– Wed Jun 23 11:32:51 2010::Agent Launched with PID 3852 at time Wed Jun 23 11:32:51 2010 —–
(pid=3852): starting emagent version 10.2.0.5.0
(pid=3852): emagent started successfully
OMS decided to shutdown the agent because of the following reason sent from OMS: AGENT_TZ_MISMATCH(pid=3852): emagent now exiting abnormally – initialization failure. Consult ‘.trc’ and ‘.log’ files.
—– Wed Jun 23 11:34:39 2010::Pid 3852 not found. reaped=3852, processStatus=14080 —–
—– Wed Jun 23 11:34:40 2010::Checking status of EMAgent : 3852 —–
—– Wed Jun 23 11:34:40 2010::EMAgent exited at Wed Jun 23 11:34:40 2010 with return value 55. —–
—– Wed Jun 23 11:34:40 2010::EMAgent has exited due to initialization failure. —–
—– Wed Jun 23 11:34:40 2010::Stopping other components. —–
—– Wed Jun 23 11:34:40 2010::Commiting Process death. —–
—– Wed Jun 23 11:34:40 2010::Exiting watchdog loop

In order to solve this issue the following actions need to be performed:
Comment the current value of the “agentTZRegion” parameter in the file
\sysman\config\emd.properties by adding a hash at the beginning of the “agentTZRegion” line
# agentTZregion=GMT

Run the following commands from the Agent home:
cd \bin
emctl stop agent
emctl resetTZ agent

Open the file AGENT_HOME\sysman\config\emd.properties and check whether a new entry for the “agentTZRegion” parameter is added with the new timezone value. Make sure that the new value corresponds to the value set at the operating system level, for example:
agentTZregion=Europe/Paris

Login to the Repository Database as the sysman user through sqlplus or SQL Developer and execute the SQL statement shown in the command output:

SQL> exec mgmt_target.set_agent_tzrgn(‘‘,’Europe/Paris’)
SQL> commit;

Where is : . This can be obtained from the EMD_URL in the AGENT_HOME/sysman/config/emd.properties file.

Start the agent:

cd AGENT_HOME\bin
emctl start agent

For further details on this topic please consult the following article on Oracle Support: Troubleshooting : Grid Agent Configuration: How to Troubleshoot Timezone Issues in Enterprise Manager Grid Agent Setup

The simplest way to patch an OEM agent

Posted on : 30-06-2013 | By : Elisabeta Olteanu | In : Oracle Enterprise Manager targets

Tags: , ,

0

Login in the OEM Grid Control Console with the a user for which you have previously setup the My Oracle Support connection details and select the Deployments tab:

In the Deployments home page, the Patching Section, click on the “Patch Agent” link:

In the “Patch: Select patch” page fill in the patch number you would like to apply (eg: the one recommended by Oracle (Support) ) and select the platform/operating system version and the language (not always necessary) :

After filling in the patch and the platform click the “Go” button. If you would like find out more details about how to apply the selected patch manually click the “ReadMe” button in the right column of the patch row.
Make sure to mark the patch “Select” Checkbox. Click the “Next” button to proceed with the following patch step.
In the “Patch: Select Destination” field you are required to select the agent that you would like to patch. Here, you are also, able to see the agents that have been already patched with the previously selected update and the ones that are not patched. To do this, one can use the “View” drop-down list, where the following options can be selected: “All Targets”, ”Unpatched Targets” ,”UP targets”.

The selected targets can be chosen for upgrade by using the “Move”/”Move all” links:

After selecting the targets click the “Next” button.
In the next step you are required to fill in the host credentials for the agents to be upgraded (admin-isa or isaadmin and their corresponding passwords):

Click the “Next“ button to proceed to the next step.
In the “Patch: Stage or Apply” step you can leave the default selections and click the “Next” buton:

In the “Patch: My Oracle Support Details” page choose either to de-select the “I wish to receive security updates via My Oracle Support” checkbox or to keep it and click “Next”:

Click “Yes”/ “No”, when asked “Do you wish to remain uninformed of critical security issues in your configuration?”.

In the “Patch: Schedule” step, leave the default selections and click the “Next “ button:

In the “Patch: Summary” step you can see a review of your selections and you can start the patching by clicking the “Finish” button:

In the final “Confirmation” page one can choose to view the status of the job (s) or to “Return” to the Deployments page.

By clicking the “View job” button one can monitor the patching job(s) activity:

The job(s) should complete successfully. If not click the execution link and furthermore the step links to identify the cause of the failure.
The OEM agent patches can be applied also manually/directly on the desired server, but the procedure depends usually on each patch instructions.