This section contains information that is specific to the database type Oracle.

Supported Functions

The Oracle database can be used with:

• Audit Profile
• Callable Statements (APL)
• Database Bulk Lookup Functions (APL)
• Database Table Related Functions (APL)
• Database Collection/Forwarding Agents
• Data Masking
• Event Notifications
• Prepared Statements (APL)
• Reference Data Management
• Shared Table Profile
• SQL Collection/Forwarding Agents
• Task Workflows Agents (SQL)

Properties

When selecting the Oracle database type, you can configure the following properties using the Properties tab in the Database profile:

oracle.pool.connectionwaittimeout
oracle.pool.inactivitytimeout
oracle.pool.maxlimit
oracle.pool.minlimit
oracle.pool.propertycheckinterval
oracle.pool.refreshonsqlerror
oracle.net.encryption_client
oracle.net.encryption_types_client
oracle.net.crypto_checksum_client
oracle.net.crypto_checksum_types_client

Preparations

A database driver is required to connect to an Oracle database. This driver must be stored in the Platform Container. Follow these if Oracle was not set up during the installation of the Platform Container:

1. Download the JDBC driver (ojdbc<version>.jar) for the appropriate Oracle database version, and the ONS.jar driver in the case you use Oracle RAC.
    

2. Copy the downloaded file(s) to the directory MZ_HOME/3pp in the Platform Container.
    

3. Restart the Platform and EC/ECSAs for the change to take effect. You should be able to select the Oracle option from the Database profile after this step.
   

Advanced Connection Configuration for Oracle RAC

The Advanced Connection Setup is used for Oracle RAC Configurations.

To make the Connection String text area and the Notification Service text field appear, select the Advanced Connection Setup radio button. The Username, Password and Database Type fields will remain.

If  is installed with the Oracle database, the Oracle RAC functionality Fast Connection Failover (FCF) is available.  supports FCF thus the behavior from  perspective is that there will normally be some exceptions generated during RAC instance failover. When FCF is configured,   detects a lost connection, clears the database connection pool and reinitializes the connection pool.

During an RAC instance failover you might experience exceptions, for example, when database transactions such as updates and inserts are done. Database exceptions are logged in the system.

The Platform and Execution Contexts support the failover behavior. However, note that neither database collection nor forwarding agents support FCF. These agents have a different type of database connection pool implementation.