Default Parameters for OraRacDgLogGapTest

For each destination to which the redo log files are to be archived, this test reports the count of redo log sequences received and the log sequences applied. The number of log sequences that could not be transmitted to the destination are also reported along with the status of the redo logs.

This page depicts the default parameters that need to be configured for the OraRacDgLogGapTest.

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

• The variable name of the oracle instance is specified in ORASID textbox.

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

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

• Provide the password of the specified database user in the PASSWORD textbox.

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

• This test uses destination and thread based approaches to collect redo log related metrics. By default, Yes is specified against Use Destination parameter, indicating that the test uses destination based approach by default. In this case, destination to which the redo log files are to be archived will be displayed as the descriptor of this test. However, if you want the test to report metrics based on threads, set this parameter to No. Then, the descriptor of this test will be threads in the eG monitoring console.

• By default, SSL flag is set to Yes, as the target Oracle cluster is SSL-enabled by default. If the target cluster is not SSL-enabled, then set this flag to No.

• Truststore Path parameter is applicable only if the target Oracle Cluster is SSL-enabled, if not, set this parameter to none. TrustStore is used to store certificates from Certified Authorities (CA) that verify and authenticate the certificate presented by the server in an SSL connection. Therefore, the eG agent should have access to the truststore where the certificates are stored to authenticate and connect with the target cluster and collect metrics. For this, provide the full path to this file in this text box. The location of this file should: $JDK_HOME/lib/security/cacerts. To know how to import the certificate into the keystore, Click here

• Specify what type of truststore contains the certificates for server authentication in TRUSTSTORE TYPE text box. By default, this parameter is set to the value JKS, which implies that the Java Truststore is by default used for storing the certificates. If the certificates in your environment are contained within a different type of truststore, then specify the exact type here - eg., PKCS12.

• If a Truststore File path is provided, then, in TRUSTSTORE PASSWORD text box, provide the password that is used to obtain the associated certificate details from the Truststore File. If none is specified against Truststore Path, then, set this parameter to none.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.