Configuration of OraUserAuditTest

This test periodically reports the count of logged in, logged out and failed user sessions.

Pre-Requisites for the test to report metrics

• Execute the following commands from the SQL prompt of the target Oracle Database server:
  audit create session whenever not successful;
  audit create session whenever successful;
  

• Ensure that DB is set as the value against the Audit_trail parameter. This ensures that the data captured is logged into the DBA_AUDIT_SESSION or DBA_AUDIT_TRAIL tables of the target Oracle database server. The eG agent retrieves the data from these tables and reports the metrics for this test.

The default parameters associated with this test are:

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

• Specify host for which the test is to be configured, in the HOST text box.

• Enter the port number on which the server is listening in the PORT text box. By default, this is 1521.

• 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 in the USER text box.

• Specify the password of the specified database user in the PASSWORD text box.

• Confirm the PASSWORD by retyping it here in the CONFIRM PASSWORD text box.

• If the value chosen for the ISPASSIVE flag 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.

• By default, the DD ROW COUNT parameter is set to 0. This indicates that this test will not report the detailed diagnosis by default. For this test to report the detailed diagnosis, you should specify a valid number against this parameter. For example, if you specify 5 against this parameter, the detailed diagnosis of this test will provide information pertaining to 5 user sessions by default.

• To make diagnosis more efficient and accurate, the eG Enterprise suite 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.

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