Friday 06 June, 2008 - 20:45
The critical error on gridctrl is:
The percentage of requests that resulted in errors is 9.3%
According to Enterprise Manager Oracle Application Server Metric Reference Manual, I should
Use the Enterprise Manager Application Server Control Console to examine the errors in this HTTP Server's error log file. For information about viewing HTTP Server error logs in the Enterprise Manager Application Server Control, see the "About the HTTP Server Log Files" topic in the Enterprise Manager Application Server Control help system.
This is triggered by
Scanned /app/oracle/OracleHomes/agent10g/sysman/log/emagent.log from line 85 to 96.
Found 3 occurences of the pattern:
ERROR; : 2008-06-06 17:26:40 Thread-3086894784 ParseError:
File=file:/app/oracle/OracleHomes/agent10g/sysman/emd/collection/website_EM_Website.xml,
Line=2, Msg= Target NAME=EM Website does not exist (01006);
: 2008-06-06 17:26:40 Thread-3086894784 fatal error
parsing /app/oracle/OracleHomes/agent10g/sysman/emd/collection/website_EM_Website.xml,
will be ignored (00405);
: 2008-06-06 17:27:50 Thread-3046103984 ParseError:
File=file:/app/oracle/OracleHomes/agent10g/sysman/emd/collection/website_EM_Website.xml,
Line=2, Msg= Target NAME=EM Website does not exist (01006); .
3 crossed warning (0) or critical ( ) threshold.
This problem happens only after the gridctrl server starts up. The EM Website was available from 17:32:14 (nearly six (6) minutes after the alert was generated).
It would appear that the EM Agent is trying to collect statistics from the EM Website but the target has not been brought online yet.
This is something I will have to live with.