OEM common agent issue:-
Issues:-
1 .Agent does not upload to OMS in OEM 12c :-
On OMS Server :-
$ORACLE_HOME/bin/emctl status oms
On Agent Server :-
$ORACLE_HOME/bin/emctl stop agent
delete files from $ORACLE_HOME/sysman/emd/state and $ORACLE_HOME/sysman/emd/upload
$ORACLE_HOME/bin/emctl clearstate agent
$ORACLE_HOME/bin/emctl unsecure agent
$ORACLE_HOME/bin/emctl secure agent
$ORACLE_HOME/bin/emctl start agent
$ORACLE_HOME/bin/emctl config agent addinternaltargets
$ORACLE_HOME/bin/emctl upload agent
Here while upload if it shows 'Upload timed out before completion' , then check the total size (MB) of data that is to be uploaded :-
emctl upload agent
---------------------------------------------------------------
EMD upload error: Upload timed out before completion.
Number of files to upload before the upload: 69, total size (MB): 23.37.
Remaining number of files to upload: 69, total size (MB): 23.37.
It 23.37 MB as shown above, Now try uploading again:-
emctl upload
---------------------------------------------------------------
EMD upload error: Upload timed out before completion.
Number of files to upload before the upload: 33, total size (MB): 1.82.
Remaining number of files to upload: 33, total size (MB): 1.82.
This time the remaining data is only 1.82 MB and likewise it will gradually decrease and finally upload will complete successfully :-
emctl upload
---------------------------------------------------------------
EMD upload completed successfully
2. Agent has stopped monitoring. The following errors are reported : COLL_DISABLED|DISK_FULL :-
(i) Stop the agent
$ORACLE_HOME/bin
./emctl stop agent
(ii) Remove all the files from $ORACLE_HOME/sysman/log/ directory.
(iii) Backup and edit $ORACLE_HOME/sysman/config/emd.properties.
(iv) Add this line:
NMUPM_TIMEOUT=120
(v) Uncomment: ThreadPoolModel = LARGE
(vi) start the agent
$ORACLE_HOME/bin/emctl start agent
Alert “COLL DISABLED|DISK FULL” is Raised for Agent Every Night due to Backup Manager (Doc ID
1056178.1)
The bug is documented in Doc Id: Note:602021.1
Patch number Patch 6780904 - AGENT DOWN ALERT - COLL_DISABLED
3. Sometimes the GRID CONTROL agent will not start because an old HTTP process is still running on the host – this usually happens if the agent has crashed for any reason :-
Example -
(i) Check status of agent.
$ORACLE_HOME/bin/emctl status agent
Oracle Enterprise Manager 10g Release 4 Grid Control 10.2.0.4.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
—————————————————————
Agent is Not Running
(ii) START AGENT -
$ORACLE_HOME/bin/emctl start agent
Oracle Enterprise Manager 10g Release 4 Grid Control 10.2.0.4.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Starting agent …… failed.
Failed to start HTTP listener.
Consult the log files in: /u01/oracle/agent10g/sysman/log
(iii) To solve the problem.
CHECK IF PORT 3872 – PORT USED BY AGENT IS IN USE.
netstat -an | grep 3872
tcp4 0 0 *.3872 *.* LISTEN
oracle(DATABASE)@hostname:ps -ef | grep emagent
oracle 864486 1 0 Jan 27 – 5:36 /u01/oracle/agent10g/perl/bin/perl /u01/oracle/agent10g/bin/emwd.pl agent /u01/oracle/agent10g/sysman/log/emagent.nohup
oracle 1593344 864486 0 Jan 27 – 97:38 /u01/oracle/agent10g/bin/emagent
(iv) KILL ALL EMAGENT PROCESSES STILL RUNNING -
oracle(DATABASE)@hostname:ps -ef | grep emagent | awk ‘ {print $2}’ | xargs kill -9
oracle(DATABASE)@hostname:ps -ef | grep emagent| grep -v grep
No emagent process running now.
(v)
$ORACLE_HOME/bin/emctl start agent
Oracle Enterprise Manager 10g Release 4 Grid Control 10.2.0.4.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
AGENT WILL START.
