Monday 26 May, 2008 - 11:40
I have managed to get around the startup problems with gridctrl temporarily by starting the systems individually and waiting for initialisation to complete.
As such, I am able to run all four (4) systems satisfactorily at this stage.
To the OMS agent to start on richmond1 and richmond2, I had to set the default runlevel to 3 via /etc/inittab . This would be a consistent design approach by Oracle to have all managed servers running without X11 in multiuser mode.
Although the agents are running on both nodes of the richmond cluster, the OMS web page does not display the hosts.
$ $OMS_HOME/bin/emctl status agent
Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent Version : 10.2.0.1.0
OMS Version : 10.2.0.1.0
Protocol Version : 10.2.0.0.0
Agent Home : /u00/app/oracle/OracleHomes/agent10g/richmond2
Agent binaries : /u00/app/oracle/OracleHomes/agent10g
Agent Process ID : 2832
Parent Process ID : 2813
Agent URL : http://richmond2:3872/emd/main
Repository URL : http://gridctrl:4889/em/upload/
Started at : 2008-05-26 11:09:44
Started by user : oracle
Last Reload : 2008-05-26 11:09:44
Last successful upload : (none)
Last attempted upload : (none)
Total Megabytes of XML files uploaded so far : 0.00
Number of XML files pending upload : 44
Size of XML files pending upload(MB) : 2.85
Available disk space on upload filesystem : 36.90%
Last successful heartbeat to OMS : 2008-05-26 11:21:36
---------------------------------------------------------------
Agent is Running and Ready
It would appear that the collected data has not been uploaded to the repository. Since there has been no attempts at upload, I would assume that the agent installation is incomplete.