It is important to understand how to configure a supported database as part of an Oracle Fusion Middleware enterprise deployment.

Most Oracle Fusion Middleware products require a specific set of schemas that must be installed in a supported database. The schemas are installed by using the Oracle Fusion Middleware Repository Creation Utility (RCU).

In an enterprise deployment, Oracle recommends a highly available Real Application Clusters (Oracle RAC) database for the Oracle Fusion Middleware product schemas.

Before you configure the enterprise deployment topology, you have to verify that the database meets the requirements described in the following sections.

• Supported Database Versions
  
• Additional Database Software Requirements
  
• Setting the PROCESSES Database Initialization Parameter for an Enterprise Deployment
  

When multiple Oracle Fusion Middleware products are sharing the same database, each product should be configured to connect to a separate, dedicated database service. This service should be different from the default database service. Having a different service name from the default, allows you to create role based database services for Disaster Recovery and Multi-Datacenter topologies.

1. Add the service to the database and assign it to the instances by using srvctl:

   srvctl add service -db soadb -service soaedg.example.com -preferred soadb1,soadb2

   Note:

   For the Service Name of the Oracle RAC database, use lowercase letters, followed by the domain name. For example: soaedg.example.com

   If the database is a multitenant database, provide the pluggable database (PDB) name when creating the service so that the service is associated with the specified PDB. For example:

   srvctl add service -db soadb -service soaedg.example.com -preferred soadb1,soadb2 -pdb PDB1

2. Start the service:

   srvctl start service –db soadb –service soaedg.example.com

   Note:

   For complete instructions on creating and managing database services with SRVCTL, see Creating Services with SRVCTL in the Real Application Clusters Administration and Deployment Guide.

3. Modify the service so that it uses the Load Balancing Advisory and the appropriate service-level goals for runtime connection load balancing.
   Use the following resources in the Oracle Database 19c Real Application Clusters Administration and Deployment Guide to set the SERVICE_TIME and THROUGHPUT service-level goals:

   • Overview of the Load Balancing Advisory

   • Configuring Your Environment to Use the Load Balancing Advisory

   For example:

   Check the default configuration of the service by using this command:

   srvctl config service -db soadb -service soaedg.example.com

   Several parameters are shown. Check the following parameters:

   • Connection Load Balancing Goal: Long

   • Runtime Load Balancing Goal: NONE

   You can modify these parameters by using the following command:

   srvctl modify service -db soadb -service soaedg.example.com -rlbgoal SERVICE_TIME -clbgoal SHORT

4. Restart the service:

   srvctl stop service -db soadb -service soaedg.example.com
   srvctl start service -db soadb -service soaedg.example.com

5. Verify the change in the configuration:

   srvctl config service -db soadb -service soaedg.example.com
   Runtime Load Balancing Goal: SERVICE_TIME
     Service name: soaedg.example.com
     Service is enabled
     Server pool: soadb_soaedg.example.com
     ...
     Connection Load Balancing Goal: SHORT
     Runtime Load Balancing Goal: SERVICE_TIME
     ...

SecureFiles is a new LOB storage architecture introduced in Oracle Database 11g Release 1. It is recommended to use SecureFiles for the Oracle Fusion Middleware schemas, in particular for the Oracle SOA Suite schemas.

sql> alter system set db_securefile=ALWAYS scope=both;

Performing a database backup at key points in the installation and configuration of an enterprise deployment enables you to recover quickly from any issue that might occur in the later configuration steps.

At key points in the installation and configuration of an enterprise deployment, this guide recommends that you back up your current environment. For example, after you install the product software and create the schemas for a particular Oracle Fusion Middleware product, you should perform a database backup. Performing a backup allows you to perform a quick recovery from any issue that might occur in the later configuration steps.

You can choose to use your own backup strategy for the database, or you can simply make a backup by using operating system tools or RMAN for this purpose.

Oracle recommends that you use Oracle Recovery Manager for the database, particularly if the database was created using Oracle Automatic Storage Management. If possible, you can also perform a cold backup by using operating system tools such as tar.

An Oracle enterprise deployment, including Oracle SOA Suite, presents several challenges for database administrators, including managing the growth of the Oracle SOA Suite database. Underestimating the importance of managing the database can lead to issues when the database is moved to a production environment.

For information about determining an appropriate strategy and planning for capacity, testing, and monitoring, see Managing Database Growth in Administering Oracle SOA Suite and Oracle Business Process Management Suite.