After installing and configuring application server, the agent on that server started to sent messages like 'The number of active connections is ..' . But.. there are no connections yet on the system (as far as I know)! Grid Control (OMS + agent) = 10.2.05, application server 10.1.2.0.2
Grid Control is calling >> “Difference between OMS system time and Agent system time is 121 mins and has exceeded the critical threshold 120 mins”
The system time runs too fast on a (Suse) Linux-based (kernel 2.6) virtual machine, while the ntp has been configured. There are a lot of documents regarding this kind of issues. For explanation and understanding a few documents we used:
– http://support.microsoft.com/kb/918461 (Microsoft? seems to work for VM-ware too…)
– http://www.novell.com/coolsolutions/feature/15345.html (time not syncing with ntp-server)
Next option for me when all above should not be working, but didn’t have to use it:
Solution we implemented, seemed to work:
– add the clock=pit parameter to the kernel entry (for explanation, see below)
– in addition add the option ‘burst iburst‘ to the ntp-configuration.
To see by the way how the ntp is working:
# watch ntpq -p
Clock=pit for the GRUB bootloader
In the guest operating system, open the /boot/grub/menu.lst file by using a text editor such as Vi. For example, type the following command from a console, and then press ENTER:
This file contains the Linux boot options and resembles the following:
kernel (hd0,4)/vmlinuz root=/dev/hda7 vga=791
In the title Linux area of this file, add the clock=pit parameter to the kernel entry. This area should resemble the following:
kernel (hd0,4)/vmlinuz root=/dev/hda7 vga=791 clock=pit
Save the changes to the file, exit Vi, and then restart the Linux-based virtual machine.
Short one this time, all in favour of getting my green ‘pie’ in Grid Control management server.
Grid Control: 10.2.0.5. Discoverer: 10.1.2.x
In Grid Control, after upgrade to 10.2.0.5, a Discoverer target shows down in the list, while it’s functioning quite well.
It seemed an old bug (Grid Ctrl 10.1.04) is still not […]
After installing Oracle Application Server 10.2.0.2, with corresponding OID, Grid Control 10.2.0.5 gave me the obove mentioned error, and the the item OID gave a 'metric collection error'. To fix the metric collection error downloaded and applied Patch 5686191 on top of OID product.This is a sql-script to run against the OID-repository.
Platform: application server 10.1.2.0.2 on Suse Linux 9. Grid Control agent 10.2.04.
All components within the application server are up, but the home page of Grid Control showing it down.
Underlying cause: bug in discovering ports by the agent. Agent discovering process gets Forms url Port from < HOME_IAS>/10.1.2/forms/server/target2add.xml. But this port […]
Agent (10.2.0.4) crashes – on a site (64-bit) with many databases (10.2.0.3) a lot, intermittently – , too many open files, emagent.trc gives ‘health check’ error
Agent gave messages – in the past – like this:
Number files opened by Agent is 1140.
These files appeared to be the $ORACLE_HOME/dbs/hc<instance>_.dat which is loaded […]
On my Grid Control management-server (Suse Linux, OMS version 10.2.0.4) a very large number of <defunct> processes arose what eventually caused the OMS not to respond anymore.
Looked like this:
oracle 16932 15961 0 Mar03 ? 00:00:00 <defunct>
oracle 16987 15961 0 Mar03 ? 00:00:00 <defunct>
oracle 17027 15961 0 […]