Pattern Goal

The goal of the Oracle RDBMS Database Detail patterns is to obtain a detailed mapping of a given Database structure. The Database pattern (Atrium Discovery 8.3 and later) creates a DatabaseDetail node that represents an instance of the Oracle Database Server which allows the CMDB sync mechanism to map it to the BMC_Database CI in Atrium CMDB. The SchemasAndTables pattern returns the list of Schemas managed by a given database (represented by a SID or a server_name), and, furthermore, it returns (optionally, and disabled by default) the list of all Tables within these Schemas. The TablespacesAndDataFiles pattern returns the list of Tablespaces for a given SID or service_name, and, furthermore, it can return (optionally, and disabled by default) the list of all DataFiles, for each Tablespace.

The Oracle schema and table information is then stored within the Atrium Discovery Model as DatabaseDetail Nodes.

The patterns with exception of the Database pattern connect to the Oracle DB Server using a JDBC connection.

Configuration Required

The Database Detail Patterns require additional configuration before they can be used.

Setting of Database Integration Point

• Set the Connection Parameters, including Username and Password.

Setting the port:

Atrium Discovery 8.0 and 8.1

The core TKU Oracle RDBMS pattern can be configured to set the listening port for a SID to a given value. In the case where that value isn't present, the Database Detail pattern will use the default port which is set in its Configuration Parameters. If the default port is likely to be different in your environment, please alter the Pattern Configuration, according to your needs. Changing Pattern Configuration is detailed in Atrium Discovery Documentation .

Atrium Discovery 8.2 and later

The pattern uses 'success_login_cred' attribute of related "Oracle Database Server" SI to run DB Query.

Editing Pattern Configuration

• Decide whether the pattern should attempt to retrieve Tables and DataFiles, or not, and whether any specific Databases should be ignored

Database User Configuration

In order for Atrium Discovery to retrieve the Database details, it will need to be able to access the Database as a legitimate user, with privileges sufficient to execute the SQL Queries below.

SQL Queries Executed for credentials using Oracle Database Server SID

The pattern executes the following SQL Queries.

• Obtaining a list of Schemas for a SID: SELECT username FROM all_users ORDER BY username

• Obtaining a list of Tables within a Schema: SELECT table_name FROM all_tables WHERE owner = %schema%

• Obtaining a list of Tablespaces for a SID: SELECT * FROM dba_tablespaces

• Obtaining a list of DataFiles within a Tablespace: SELECT * FROM DBA_DATA_FILES WHERE TABLESPACE_NAME = %tablespace_name%

SQL Queries Executed for credentials using Oracle Database Server service_name

The pattern executes the following SQL Queries.

• Obtaining a list of Schemas: SELECT username FROM all_users ORDER BY username

• Obtaining a list of Tables within a Schema: SELECT table_name FROM all_tables WHERE owner = %schema%

• Obtaining a list of Tablespaces: SELECT * FROM dba_tablespaces

• Obtaining a list of DataFiles within a Tablespace: SELECT * FROM DBA_DATA_FILES WHERE TABLESPACE_NAME = %tablespace_name%