In this cloud-era it’s almost weird to explore stuff on-premises, but I did…. In this case a slightly Higher Availibility configuration of Oracle Enterprise Manager (OEM) that doesn’t cost anything, is not disruptive to the existing configuration and gives a tiny bit more confidence during patching of OEM : Always On Monitoring (AOM). Maybe a
The metric 'swap utilisation (%)' on the node where Grid Control resides, shows permanently a very hig value. Red Hat Linux, 64-bits, 32GB RAM, 4GB swap. Adding 4GB to the swap-file solved the problem.
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.
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 a lot
Noticed that the following error was popping up in the emagent.trc of a 10.2.04 – Grid Control-agent on a specific node, every 5 seconds. Annoying, unnecessary: 2007-09-18 12:15:14 Thread-134875 ERROR vpxoci: Error on dequeue from SYS.ALERT_QUE: ORA-00604: error occurred at recursive SQL level 1 ORA-06502: PL/SQL: numeric or value error ORA-06512: at line 30 ORA-25228:
© Copyright 2012 - 2023 | Jobacle by Job | All Rights Reserved | Powered by WordPress
