Oracle Database Configuration Settings

Managing Product Components › Configure a Product Component › Oracle Database Configuration Settings

Oracle Database Configuration Settings

After you install the product, if you are using Oracle as the database for the CA MDB, you can change the settings for the Oracle database server.

The following fields require explanation:

DBA User Name

The user name for connecting to the target database. The user name must be for a privileged user.

Default: sys

Listen Port

The database connection port.

Default: 1521

Oracle Service Name

The service name for the target database.

Default: orcl

Oracle Net Service Name

The net service name for the target database.

Default: orcl

Tablespace Path

The location of the Oracle tablespaces.

Default: c:\oracle\product\10.2.0\oradata\orcl

Data Tablespace Name

The name of the data tablespace.

Default: MDB_DATA

Data Tablespace Size

The amount of disk space to be allocated for the data tablespace.

Default: 400 MB

Index Tablespace Name

The name of the index tablespace.

Default: MDB_INDEX

Index Tablespace Size

The amount of disk space to be allocated for the index tablespace.

Default: 100 MB

mdbadmin Password

The password that is associated with the mdbadmin user. If a new CA MDB is being created, this is the password that is assigned to the mdbadmin user.

Command Timeout

The maximum amount of time that the application waits for a response from the database.

Stored Procedure Command Timeout

The maximum amount of time that the application waits for a response from the database stored procedures.

Max Connection Pool Size

The maximum number of requests that the database can process simultaneously.

Enable CORA Connection Pooling

Placeholder for the flag that enables CORA connection pooling. Currently, CORA does not support connection pooling.

CORA Connection Pool Lifetime

Placeholder for the lifetime of the CORA connection pool. Currently, CORA does not support connection pooling.

CORA Connection Pool Size

Placeholder for the size of the CORA connection pool. Currently, CORA does not support connection pooling.

Last Run Date Option

Determines if the imported data should update the existing CA APM data.

Note: CA APM receives discovered hardware data imports and uses the data to match ownership and discovery data. CA APM determines if the imported data is more current than the existing data by comparing their inventory dates. Then CA APM decides whether the imported data should update the existing CA APM data.

Default: 2

Note: See the following table for a description of all valid options.

Option	Definition
1	Always update the existing CA APM data with the imported data.
2	(Default) Update the existing CA APM data only if the inventory date of the imported asset is more current than the inventory date of the existing asset. If the imported asset does not have an inventory date, an error occurs and the imported asset data does not update the existing CA APM data.
3	Update the existing CA APM data only if the inventory date of the imported asset is more current than the inventory date of the existing asset. If the imported asset does not have an inventory date, update the existing CA APM data with the imported data.

Option

Definition

Always update the existing CA APM data with the imported data.

(Default) Update the existing CA APM data only if the inventory date of the imported asset is more current than the inventory date of the existing asset.

If the imported asset does not have an inventory date, an error occurs and the imported asset data does not update the existing CA APM data.

Update the existing CA APM data only if the inventory date of the imported asset is more current than the inventory date of the existing asset.

If the imported asset does not have an inventory date, update the existing CA APM data with the imported data.