Version: 10.1.*
10.2.*
(Last version checked is 10.2.0.3)
Agent installation can be hard. I have lots of problems installing the mass deployment agent, and are now only using the GUI installation found in ..agent/runInstaller included in the zip-file.
Problem
You are seeing this error message:
The agentTZRegion value in /u01/app/oracle/product/10.2.0/agent10g/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(, ) to get the value propagated to repository. Consult the log files in: /u01/app/oracle/product/10.2.0/agent10g/sysman/log
Solution
Edit $AGENT_HOME/sysman/config/emd.properties and set timezone to GMT (bottom of the file)
agentTZRegion=GMT
Restart the agent (emctl start agent), do not use emctl resetTZ agent!!
Problem
You are having problems with host discovery in Enterprise Manager Grid Control.
You might see this in the logfiles:
“The config assistant was running into problems because of an PERL5LIB setting
@ in the system environment. Removing this setting and rerunning the install
@ fixes the issue. “
Solution
Check if the OS user has the PERL5LIB environment set. If it does, unset it!!
Problem
Installation was broken or did not complete, agent is not started and is not abel to upload.
Solution
Sometimes there is a problem with securing the agent or with the first upload to OMS. It
often helps to do a clearstate of the agent.
Clearstate
Stop the agenten and remove these files from $AGENT_HOME:
$ rm -r sysman/emd/state/*
$ rm -r sysman/emd/upload/*
$ rm sysman/emd/agntstmp.txt
$ rm sysman/emd/lastupld.xml
$ rm sysman/emd/protocol.ini
Start the agent.
Run:
emctl clearstate agent
emctl upload agent
Problem
The agent is not discovering all targets or discovers old targets that where deleted.
Solution
Discovery in grid control checks targets.xml file from the agent and all Sqlnet files like
listener.ora,tnsnames.ora. It also checks /etc/oratab. Check these files for errors or old
information.
Problem
You get this error messages when discovering a target:
"...java.sql.SQLException: ORA-00060: deadlock detected while waiting for resource ORA-06512:
at "SYSMAN.EM_TARGET", line 1681 ORA-06512: at "SYSMAN.EM_TARGET", line 1926 ORA-06512: at
"SYSMAN.MGMT_TARGET",line 2834 ORA-06512: at line 1 - ORA-00060: deadlock detected while
waiting for resource ORA-06512:
Solution
The installation might have used an ip address instead of hostname.
You can solve this by setting this environment variable before installing:
ORACLE_HOSTNAME=hostname
Problem
Agent will not start after boot.
Solution
Check the existence of these files:
/etc/rc.d/rc3.d/S99gcstartup
/etc/rc.d/rc5.d/S99gcstartup
Check the file:
$AGENT_HOME/install/unix/scripts/agentstup
If the file has "user=null" change this to "user=oracle". (user for agent installation)
Problem
I cant install the agent, several reinstalls have done a mess with the repository
Solution
1.Remove agent and associated targets from within Grid Control.
2.Uninstall agent.
3.Log into the repository DB as sysman, query the MGMT_TARGETS_DELETE table
for the GUID of the removed agent. Use the GUID from the MGMT_TARGETS_DELETE table to identify
the corresponding targets and delete
them from the MGMT_EMD_PING, MGMT_EMD_PING_CHECK, and the MGMT_TARGETS_DELETE tables.
4. Reinstall the agent
Problem
AGENT do not autodicsover duplicated databases
Solution
1. Edit $ORACLE_HOME/sysman/emd/targets.xml
change the values for MachineName, OracleHome, Port,SID etc.,
Set the dbsnmp password in clean text and change ENCRYPTED="FALSE"
and bounce the agent.
or,
emctl config agent addtarget
2. Use GC itself
Targets > Databases > Add Button
Select appropriate host and Continue. Auto discovery will occur.
Problem
Problems with uploading agent
Solution
If the agent is successfully installed, up and running and you still get error messages
when running emctl upload agent, try to do a new secure of the agent:
emctl secure agent
I have experienced several times that some agents need the manual secure job to be abel to
work after install.
Some emctl examples
emctl config agent addtarget /home/oracle/labs/asm1_target_RDBB.xml
emctl secure agent welcome (welcome er passordet til oms)
emctl clearstate agent (after this you need to do emctl upload agent)
emctl upload agent
emctl secure status agent
