|
Configuration of OraRacUnUsaTest
This test reports the space usage metrics of this undo tablespace in each Oracle instance.
The default parameters
associated with this test are as follows:
-
In order to monitor an
Oracle Cluster, 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.
A ServiceName exists for the entire Oracle RAC system. When clients connect to an Oracle cluster using the ServiceName, then the cluster routes the request to any available database instance in the cluster. By default, the SERVICE NAME is set to none. In this case, the test connects to the cluster using the ORASID and pulls out the metrics from that database instance which corresponds to that ORASID. If a valid SERVICE NAME is specified instead, then, the test will connect to the cluster using that SERVICE NAME, and will be able to pull out metrics from any available database instance in the cluster.
To know the ServiceName of a cluster, execute the following query on any node in the target cluster:
select name, value from v$parameter where name = ‘service_names’
-
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 for a particular server, 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 multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.
-
Once the necessary values
have been provided, clicking on the Update button will register the
changes made.
When changing the
configuration for specific servers, a "*" beside the text box
corresponding to the parameter signifies that these values have to be
manually configured by the user. The parameter values that require to be
configured will typically be prefixed with a "$" or contain a series of
"*". A value of "none"
in the parameter value indicates that the corresponding parameter
value can be changed if required.
|