|
Default
Parameters for OraJobsTest
This test monitors Oracle jobs and reports the number of jobs that have failed and those that are broken.
This page depicts the default
parameters that need to be configured for the OraJobsTest
.
-
In order to monitor an
Oracle database server, a special database user account has to be created in
every Oracle database instance that requires monitoring. A
Click here hyperlink
is available in the test configuration page, using which a new oracle
database user can be created. Alternatively, you can manually create the special database user. When doing so, ensure that this user is vested with the select_catalog_role and create session privileges. The sample script we recommend for user creation for eG
monitoring is:
create user oraeg identified by oraeg
create role oratest;
grant create session to oratest;
grant select_catalog_role to oratest;
grant oratest to oraeg;
The name of this user has to be specified in
the USER text box, and the password of this user has to be entered in
the PASSWORD text box. Confirm
the password by retyping it in the CONFIRM PASSWORD text box. This
login information is required to query Oracle's internal dynamic views, so
as to fetch the current status / health of the various database components.
-
To make diagnosis
more efficient and accurate, the eG system embeds an optional
detailed diagnostic capability. With this capability, the eG
agents can be configured to run detailed, more elaborate tests as
and when specific problems are detected. To enable the detailed
diagnosis capability of this test, by default, for a particular
server-type, choose the On option against DETAILED
DIAGNOSIS. To disable the capability, click on the Off
option.
The option to
selectively enable/disable the detailed diagnosis capability will
be available only if the following conditions are fulfilled:
-
If the ISPASSIVE parameter is set to YES, then it means that, by default, all Oracle servers being monitored by the eG system are the passive servers of an Oracle cluster. No alerts will be generated if the servers are not running. Measures will be reported as "Not applicable" by the agent if the servers are not up.
When changing default configurations of tests, the values with "$" indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to "xyz" and $port will be changed to "80" when configuring a test.
|