Configuration of OraTabGrwthTest

This test monitors the objects in the target Oracle Database server and reports the count of objects that have exceeded growing beyond a pre-configured size. This test also reveals the maximum size up to which the objects can grow.

Note:

This test will not report metrics for an Oracle 12c CDB server.

The default parameters associated with this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, the host for which the test is to be configured has to be specified.

• In the PORT text box, enter the port number at which the target host being monitored listens.

• 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=;

  create user identified by container=current default tablespace temporary tablespace ;

  Grant create session to ;

  Grant select_catalog_role to ;

  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. 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.

• Confirm the password by retyping it in CONFIRM PASSWORD textbox.

• Specify the size limit (in GB) for the objects against the OBJECT SIZE GB text box beyond which the objects are termed as large objects. The default value is set to 1 GB.

• By default, the detailed diagnosis of this test, if enabled, will report only the top-10 records. This is why, the DD ROW COUNT parameter is set to 10 by default. If you want to include more or less records in detailed diagnosis, then change the value of this parameter accordingly.

• To exclude the objects that are created/managed by specific user accounts from the scope of monitoring, specify a comma-separated list of user accounts against the EXCLUDE OWNER text box. By default, SYS,SYSTEM is specified against this text box indicating that the objects created/managed by SYS and SYSTEM administrative user accounts will by default be excluded from the scope of monitoring i.e., object growth will not be reported for the objects created/managed by the SYS and SYSTEM administrative user accounts.

• In the EXCLUDE OBJECT TYPE text box, specify a comma-separated list of object types that you wish to exclude from the scope of monitoring. For example, specifying index,table partition will exclude those objects' growth from the scope of monitoring i.e., this test will not consider the growth of index and table partitions while reporting metrics. By default, this parameter is set to none.

• 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.

• 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.