Last updated on SEPTEMBER 06, 2012
Applies to:Oracle Server - Enterprise Edition - Version: 10.2.0.4
Enterprise Manager Base Platform - Version: 10.2.0.4 and later [Release: 10.2 and later]
HP-UX PA-RISC (64-bit)
IBM AIX on POWER Systems (64-bit)
Oracle Solaris on SPARC (64-bit)
Microsoft Windows x64 (64-bit)
***Checked for relevance on 12-Jan-2012***
Using a 10.2.0.4 Grid Agent to monitor a 10.2.0.4 Database.
The 10.2.0.4 Agent version is certified to monitor a 10.2.0.4 Database.
The <AGENT_HOME>/sysman/log/emagent.trc shows that the health_check metric is repeatedly failing for this database :
2008-06-09 15:21:11,173 Thread-3658 ERROR fetchlets.healthCheck: GIM-00105: file not found
2008-06-09 15:21:11,174 Thread-3658 ERROR engine: [oracle_database,dbname,health_check] : nmeegd_GetMetricData failed : Instance Health Check initialization failed due to one of the following causes: the owner of the EM agent process is not same as the owner of the Oracle instance processes; the owner of the EM agent process is not part of the dba group; or the database version is not 10g (10.1.0.2) and above.
Repeated failure while executing this metric can cause the Agent to re-start, as it runs out of file handlers at the OS level.
- The database is a 64 bit installation but emagent executable is of 32 bit installation though the
64 bit agent software is installed.
- Re-starting the database to create this hc_<SID>.dat file does not help in resolving the Healthcheck Metrics error.
- The <DATABASE_OH>/dbs/hc_<SID>.dat file has sufficient permissions to be read by the agent
Database and Agent have been upgraded to 10.2.0.4 from a lower version.
It is possible that when the Database / Agent were at 10.2.0.3 (or below), this metric was not failing.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms