Oracle User Tablespaces Test

This test measures the number of users currently using the system tablespace. This test is disabled by default. To enable the test, go to the enable / disable tests page using the menu sequence : Agents -> Tests -> Enable/Disable, pick Oracle Database as the Component type, Performance as the Test type, choose this test from the disabled tests list, and click on the << button to move the test to the ENABLED TESTS list. Finally, click the Update button.

Target of the test : An Oracle server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every instance of an Oracle database.

Configurable parameters for the test
  1. TEST PERIOD - How often should the test be executed
  2. Host – The host for which the test is to be configured
  3. Port - The port on which the server is listening

  4. User – 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.

  5. Password – Password of the specified database user

    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.

  6. Confirm password – Confirm the password by retyping it here.
  7. ISPASSIVE – If the value chosen is yes, then the Oracle server under consideration is a passive server in an Oracle cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable" by the agent if the server is not up.

  8. DETAILED DIAGNOSIS – To make diagnosis more efficient and accurate, the eG Enterprise 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. 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:

    • The eG manager license should allow the detailed diagnosis capability
    • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

System tablespace users:

Indicates the number of users (other than sys/system users) who are currently using the system tablespace as their default or temporary tablespace

Number

It is not desirable for application users to be using system tablespace as their default or temporary tablespace.

If you want the eG Enterprise to ignore a few users while measuring the number of current users, then set the Maximum Threshold accordingly. By default, the Maximum Threshold is set to “none”. For eg., OUTLN and DBSNMP are two default users of the system tablespace. Therefore, the value of this measure will also be 2, by default. Moreover, since the Maximum Threshold of this measure, is by default “none”, any value greater than 0, will trigger an alarm. Since the value 2 is greater than 0, an alarm will be generated for this measure. To avoid such an alarm-generation, change the Maximum Threshold to 2. When this is done, the eG Enterprise system will ignore the 2 default users and will generate an alarm only when additional users begin using the system tablespace.

The detailed diagnosis of the System tablespace users measure, if enabled, lists the users who are currently using the system tablespace (see Figure 1). When there is a steep increase in the number of system tablespace users, then, this information will help in identifying the specific users using the tablespace. Such users, if found unwanted, can be dropped. Alternatively, the default or temporary tablespace of such users can be changed.

systemtsusersDD-final

Figure 1 : The detailed diagnosis of the System tablespace users measure