|
Configuration of OraAsmDiskSpaceTest
This test closely monitors how each disk in a disk group uses the space available to it, points you to the disks that are running out of space, and thus holds a mirror to space contentions on a disk group.
The default parameters associated with this test are as follows:
By default, this is set to none, indicating that the test, by default, runs a SQL query to pull out the space usage related metrics from the ASM. If you want the test to execute a script that exists in the ORACLE_HOME directory to extract the desired metrics, then, specify the full path to the ORACLE_HOME directory against the ORACLEHOME parameter. The ORACLE_HOME is the directory where you choose to install the software for a particular Oracle product - in the case of this test, the Oracle database server. The directory that you specify in the ORACLEHOME text box, should be a sub-directory of the Oracle base directory. For instance, your ORACLEHOME specification on a Unix platform can be: /u01/app/oracle/product/10.2.0/db_1. On Windows, the ORACLEHOME can be: D:\oracle\product\10.2.0\db_1.
By default, the USE ASM INSTANCE flag is set to Yes indicating that the eG agent extracts the metrics based on the name of the ASM instance. If you want the eG agent to extract the metrics using SID instead of the name of the ASM instance, set this flag to No.
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 (in Oracle database server versions before 12c) 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 sample script we recommend for user creation (in Oracle database server 12c) for eG monitoring is:
alter session set container=<Oracle_service_name>
create user <user_name> identified by <user_password> container=current default
tablespace <name_of_default_tablespace> temporary tablespace <name_of_temporary_tablespace>
Grant create, session to <user_name>
Grant select_catalog_role to <user_name>
The name of this user has to be specified here. If the USE ASM INSTANCE flag is set to Yes, then, the user monitoring the Oracle database server should be vested with an additional SYSDBA privilege. To provide this privilege, do the following:
grant sysdba to user <user_name>;
The name of this user has to be specified here.
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.
|