Release 9.2.0
Part Number A96675-01
 Home |
 Book List |
 Master Index |
 Feedback |
 Contents |
| Oracle Enterprise Manager Event Test Reference Manual Release 9.2.0 Part Number A96675-01 |
|
The Oracle Enterprise Manager Advanced Event Tests for Oracle9iAS Release 2 (9.0.2) are divided into categories that will enable you to find the event test you are interested in registering.
The following categories of events are included:
The following tables list the Oracle9iAS Release 2 (9.0.2) event tests by target type. The full descriptions of the individual event tests follow the tables. The event tests are in alphabetical order.
| Event Test | Description |
|---|---|
|
OC4J UpDown |
This event test checks whether the OC4J server is running. A critical alert is generated whenever the value is 0, that is, whenever OC4J stops. |
| Event Test | Description |
|---|---|
|
Web Cache UpDown |
This event test checks whether Web Cache is running. A critical alert is generated whenever the value is 0, that is, whenever Web Cache stops. |
| Event Test | Description |
|---|---|
|
JServ UpDown |
This event test checks whether JServ is running. A critical alert is generated whenever the value is 0, that is, whenever JServ stops. |
The Oracle9iAS Release 2 (9.0.2) event tests are listed in alphabetical order within target type.
This event test checks whether the Enterprise Manager Web Site is running. A critical alert is generated whenever the Enterprise Manager Web Site is down or an error occurs.
None.
If the EM Web Site UpDown event test identifies a problem, one of the following messages may be generated. See the Oracle9i Application Server Administrator's Guide for additional information.
Cause: The emtab file does not have read permissions.
Action: Verify that the emtab file has the read permissions set.
Cause: The Enterprise Manager Web Site home may be invalid, there is an invalid format in the emtab file, or the emctl executable may be in the incorrect directory
Action: There are several actions to perform. Verify that the Enterprise Manager Web Site home is valid. Correct the format in the emtab file. The format should be "DEFAULT=<ORACLE_HOME>". Verify that the emctl command is located in the ORACLE_HOME/bin directory. Also, verify that the emctl command is an executable.
Cause: The Enterprise Manager Web Site may not be successfully installed.
Action: Verify that the Enterprise Manager Web Site is installed. If the Enterprise Manager Web Site is installed, verify that the emtab file is placed in the correct directory. For example, on Solaris the emtab file should be located at /var/opt/oracle/emtab. On HP, the file should be located at /etc/emtab. On NT, emtab is stored in the em_loc registry key which is located at HKEY_LOCAL_MACHINE\Software\Oracle.
Cause: $(SOME_JAVA_HOME) is an incorrect JAVA_HOME
Action: Make sure JAVA_HOME is set correctly.
Cause: This class could not be found and is required for getting the status of the Enterprise Manager Web Site.
Action: Verify that the $ORACLE_HOME variable is correctly set. If you still get the same error after verifying $ORACLE_HOME, verify that the CLASSPATH variable is correctly set.
Cause: This class could not be found and is required for getting the status of the Enterprise Manager Web Site.
Action: Verify that the $ORACLE_HOME variable is correctly set.
Cause: The Enterprise Manager Web Site is down.
Action: Restart the Enterprise Manager Web Site by accessing the $ORACLE_HOME/bin/ directory and typing the command: emctl start emd. If this does not work, consult the emd.log file in the $ORACLE_HOME/sysman/log directory. The log file can provide additional information to help determine the problem.
Cause: The Enterprise Manager Web Site is up but the Enterprise Manager control returned an HTTP404 (Not Found) error.
Action: Verify that the EMD_URL variable is correctly set in the $ORACLE_HOME/sysman/config/emd.properties file.
This event test measures the amount of time, in seconds, a connection stays open.
Amount of time (in seconds)
The open time has exceeded the threshold. Currently the open time is 30 seconds.
5 minutes
Examine your computer resources. Determine whether there is enough available CPU time for the HTTP Server. If not, reallocate the CPU resources needed.
This event test measures the percentage of requests that have errors. The type of errors can include: illegal page access and pages that do not exist.
Percentage of requests that have errors
Error Rate (%) is too high. The current value is 2%.
5 minutes
Look at HTTP Error Log to see what pages are causing the errors.
This event test checks whether the HTTP server is running. A critical alert is generated whenever the value is 0, that is, whenever the HTTP server stops.
Critical Threshold: Threshold for critical alert. Default is 0. This threshold is read only.
States whether the HTTP server is up or down.
5 minutes
If the HTTP server is down, click Start Server on the HTTP Server home page.
This event test measures the average time, in seconds, it takes to process an HTTP Server request.
Average amount of time (in seconds)
HTTP Server is taking too long to process requests. Currently it is taking an average of 5 seconds.
5 minutes
Examine the processes and identify all processes that are taking a long time to process. Investigate the HTTP Server Response and Load metrics from the EM Web Site. Consult the Oracle9i Application Server Administrator's Guide for additional information.
This event test checks whether the OC4J server is running. A critical alert is generated whenever the value is 0, that is, whenever OC4J stops.
Critical Threshold: Threshold for critical alert. Default is 0. This threshold is read only.
States whether the OC4J server is up or down.
5 minutes
If the OC4J server is down, click Start Server on the OC4J home page.
This event test checks whether Web Cache is running. A critical alert is generated whenever the value is 0, that is, whenever Web Cache stops.
Critical Threshold: Threshold for critical alert. Default is 0. This threshold is read only.
States whether Web Cache is up or down.
5 minutes
If Web Cache is down, click Start Web Cache on the Web Cache home page.
This event test checks whether JServ is running. A critical alert is generated whenever the value is 0, that is, whenever JServ stops.
Critical Threshold: Threshold for critical alert. Default is 0. This threshold is read only.
States whether JServ is up or down.
5 minutes
You may need to restart the Apache server. Click Start Server on the HTTP Server home page. JServ will be started as part of the Apache startup.
|
 Copyright © 2001, 2002 Oracle Corporation. All Rights Reserved. |
|
