Grid Agent Configuration: "ORA-20233: Invalid Agent name" When Running mgmt_target.set_agent_tzrgn Procedure in Repository DB (Doc ID 388280.1)

Last updated on JUNE 19, 2015

Applies to:

Enterprise Manager Base Platform - Version 10.1.0.2 to 11.1.0.1 [Release 10.1 to 11.1]
Information in this document applies to any platform.
***Checked for relevance on 25-March-2013***

Symptoms

When the Agent is unable to startup due to timezone (TZ) issues, troubleshooting steps as suggested in <Note 330737.1>: Grid Agent Configuration: How to Troubleshoot Timezone Issues in Enterprise Manager Grid Agent Setup, are followed:

-  Comment out the agentTZRegion parameter in the <AGENT_HOME>/sysman/config/emd.properties file.
-  Choose the correct value of TZ which is present in the following files:

<AGENT_HOME>/sysman/admin/supportedtzs.lst and
<AGENT_HOME>/sysman/admin/nsupportedtsz.lst

-  Set the TZ at the OS level to above chosen value.
-  Reset the timezone of the agent using:

cd <AGENT_HOME>/bin
emctl resetTZ agent

This will return an output similar to:

$ emctl resetTZ agent
Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
Updating /home/em/oracle/gc102/agent10g/sysman/config/emd.properties...
Successfully updated /home/em/oracle/gc102/agent10g/sysman/config/emd.properties.
Login as the em repository user and run the script:
exec mgmt_target.set_agent_tzrgn('agentmachine.domain:3872','Asia/Calcutta')
and commit the changes
This can be done for example by logging into sqlplus and doing
SQL> exec mgmt_target.set_agent_tzrgn('agentmachine.domain:3872','Asia/Calcutta')
SQL> commit

 -  But connecting to the Repository as sysman user and executing the above command fails with:

SQL> exec mgmt_target.set_agent_tzrgn('agentmachine.domain:3872','Asia/Calcutta')
fails with :

ERROR at line 1:
ORA-20233: Invalid agent name agentmachine.domain:3872
ORA-06512: at "SYSMAN.MGMT_TARGET", line 3683
ORA-06512: at line 1

Changes

This is a new installation of the Agent or Agent is being started up after deletion of all targets from the Grid Console.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms