Oracle Temporary Tablespace 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. alternate view – In large environments, where the volume of transactions to the Oracle database server is generally very high, this test may take time to execute and retrieve the desired results. To ensure that the test is faster and is resource-efficient, administrators of such environments can create an alternate ‘view’ on the target Oracle database server, and grant select privileges to the view to the special database user mentioned above. Once the view is created, the test should be configured to use the alternate view for metrics collection; to achieve this, specify the name of the view in the alternate view text box. By default, this text box is set to none, which implies that the alternate view is not used by default.

   This alternate ‘view’ should be created with the following structure:

CREATE OR REPLACE VIEW <VIEW_NAME> (

TABLESPACE_NAME,

FILE_ID,

BLOCK_ID,

BYTES,

BLOCKS,

RELATIVE_FNO

) AS

select /*+ use_hash (tsfi, fet2) */ tsfi.tablespace_name,

tsfi.file_id,

fet2.block_id,

tsfi.blocksize * fet2.blocks,

fet2.blocks,

tsfi.relfile#

from (select /*+ use_hash (ts, fi) */ ts.name tablespace_name,

fi.file# file_id,

ts.BLOCKSIZE,

fi.relfile#,

ts.ts#

from sys.ts$ ts,

sys.file$ fi

where ts.ts# = fi.ts#

and ts.online$ in (1,4)) Tsfi,

(select f.block# block_id,

f.length blocks,

f.file# file_id,

f.ts#

from sys.fet$ f

union all

select f.ktfbfebno block_id,

f.ktfbfeblks blocks,

f.ktfbfefno,

ktfbfetsn

from sys.x$ktfbfe f) Fet2

where fet2.file_id = tsfi.relfile#

and fet2.ts# = tsfi.ts# ;

8. 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.
9. SSL- By default, this flag is set to No, as the target Oracle database is not SSL-enabled by default. If the target database is SSL-enabled, then set this flag to Yes.
10. SSL Cipher-This parameter is applicable only if the target Oracle database is SSL-enabled, if not, set this parameter to none. A cipher suite is a set of cryptographic algorithms that are used before a client application and server exchange information over an SSL/TLS connection. It consist of sets of instructions on how to secure a network through SSL (Secure Sockets Layer) or TLS (Transport Layer Security). In this text box, provide a comma-seperated list of cipher suites that are allowed for SSL/TLS connection to the target database. By default, this parameter is set to none.
11. TRUSTSTORE FILE- This parameter is applicable only if the target Oracle database 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 database and collect metrics. For this, first import the certificates into the following default location <eG_INSTALL_DIR>/lib/security/mytruststore.jks. To know how to import the certificate into the truststore, refer toPre-requisites for monitoring Oracle Cluster. Then, provide the truststore file name in this text box. For example: mytruststore.jks. By default, none is specified against this text box.
12. TRUSTSTORE TYPE-This parameter is applicable only if the target Oracle database is SSL-enabled, if not, set this parameter to none.Specify the type of truststore that contains the certificates for server authentication in this text box. For eg.,JKS. By default, this parameter is set to the value none.

13. TRUSSTORE PASSWORD-This parameter is applicable only if the target Oracle database is SSL-enabled, if not, set this parameter to none. If a Truststore File name is provided, then, in this text box, provide the password that is used to obtain the associated certificate details from the Truststore File. By default, this parameter is set to none.