1. Administering Oracle SOA Cloud Service
  2. Before You Begin
  3. About Oracle SOA Cloud Service Architecture
  4. About Oracle SOA Cloud Service Architecture in Oracle Cloud Infrastructure
  5. Database

Database

Every service instance must be associated with an existing relational database in Oracle Cloud. Oracle SOA Cloud Service provisions the required infrastructure schema on the selected database.

The supported database services in Oracle Cloud vary by region. For an Oracle Cloud Infrastructure region, the infrastructure schema database options are shown in the following table.

Note:

If you specify No Preference for your region, or if you have an older Oracle Cloud account that doesn't include regions, then you can choose from the same database options as Oracle Cloud Infrastructure Classic.

Database Supported Versions Additional Information
Oracle Cloud Infrastructure database, with or without Oracle Real Application Clusters (RAC)

If you want to use RAC, you will need to create an Oracle Cloud Infrastructure database instance using the standard service level and Enterprise Edition Extreme Performance for the Oracle Database software edition.

Note: Exadata Cloud Service on Oracle Cloud Infrastructure is not supported.

  • Oracle Database 19c

  • Oracle Database 18c

  • Oracle Database 12c release 2 (12.2.0.1) and release 1 (12.1.0.2)

  • Oracle Database 11g Release 2

See Oracle Cloud Infrastructure Database Limitations and Usage Notes, below.

Oracle Autonomous Transaction Processing (ATP) database

  • Oracle Database 19c

  • Oracle Database 18c

See Oracle Autonomous Transaction Processing (ATP) Database Limitations and Usage Notes, below.

More Information:

General Usage Notes

  • All databases must be in an active state and not currently in the process of being provisioned. The WebLogic Server domain in a service instance uses Java Database Connectivity (JDBC) to access the databases.

  • To ensure that you can restore the database for an Oracle SOA Cloud Service instance without risking data loss for other service instances, Oracle recommends that you do not associate the same infrastructure schema database (or the same pluggable database) with multiple service instances. Backups of a database that is used with multiple Oracle SOA Cloud Service instances contain data for all the instances. Therefore, if you restore the database from a backup, data for all the service instances is restored, which might not be the intended result.

General Limitations

  • Database instances in Oracle Database Classic Cloud Service and Oracle Cloud Infrastructure database must be in the same region and virtual cloud network (VCN) as the Oracle SOA Cloud Service instance. The database and service instance do not need to be in the same subnet or availability domain, but it might be necessary to create and assign security rules to the subnets in order to enable communication between them. The database and service instance can be on different VCNs only if you configure VCN peering. See VCNs and Subnets in the Oracle Cloud Infrastructure Documentation.
  • When creating a service instance with the Oracle SOA Cloud Service Console, database instances in Oracle Cloud Infrastructure database and Oracle Autonomous Transaction Processing (ATP) database must be in a compartment that is directly under the root compartment. This restriction does not apply to service instances created with the REST API or CLI.

Oracle Cloud Infrastructure Database Limitations and Usage Notes

  • Oracle SOA Cloud Service uses an Oracle Cloud Infrastructure database to host the Oracle Fusion Middleware component schemas required by Oracle Java Required Files (JRF). Make sure you have quota to create an Oracle Cloud Infrastructure database.
  • Oracle SOA Cloud Service provisioned with the Oracle Cloud Infrastructure database supports only Oracle Grid Infrastructure storage management software. Oracle SOA Cloud Service is not supported with an Oracle Cloud Infrastructure database using Logical Volume Manager (LVM) storage management software.
  • To use Oracle Cloud Infrastructure database, you must assign a custom subnet to your service instance. The default subnet is not supported.
  • If you are using Oracle Real Application Clusters (RAC) with the Oracle Cloud Infrastructure database:

    • When you configure the compute shape during provisioning or scaling up a node, be sure to stay within the bounds of your available memory.

    • Note that Oracle SOA Cloud Service uses the GridLink data source to point to the RAC database.

    The following example shows a connect string used to connect to a RAC database:

    jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=vgad c01jjfrac1)(PORT=1522))(ADDRESS=(PROTOCOL=TCP)(HOST=DBHostRAC1)(PORT=1522))(LOAD_BALANCE=ON)(FAILOVER=ON))(CONNECT_DATA=(SERVICE_NAME=PDB1.sbcs.cloud.internal)))
    Name Type JNDI Name Targets

    EDNDataSource

    GridLink

    jdbc/EDNDataSource

    soaRACNo_cluster

    EDNLocalTxDataSource

    GridLink

    jdbc/EDNLocalTxDataSource

    soaRACNo_cluster

    LocalSvcTblDataSource

    GridLink

    jdbc/LocalSvcTblDataSource

    soaRACNo_adminserver

    mds-owsm

    GridLink

    jdbc/mds/owsm

    soaRACNo_cluster, soaRACNo_adminserver

    mds-soa

    GridLink

    jdbc/mds/MDS_LocalTxDataSource

    soaRACNo_cluster, soaRACNo_adminserver

    opss-audit-DBDS

    GridLink

    jdbc/AuditAppendDataSource

    soaRACNo_cluster, soaRACNo_adminserver

    opss-audit-viewDS

    GridLink

    jdbc/AuditViewDataSource

    soaRACNo_cluster, soaRACNo_adminserver

    opss-data-source

    GridLink

    jdbc/OpssDataSource

    soaRACNo_cluster, soaRACNo_adminserver

    OraSDPMDataSource

    GridLink

    jdbc/OraSDPMDataSource

    soaRACNo_cluster

    SOADataSource

    GridLink

    jdbc/SOADataSource

    soaRACNo_cluster

Oracle Autonomous Transaction Processing (ATP) Database Limitations and Usage Notes

  • To use an Oracle Autonomous Transaction Processing (ATP) database, the service instance must be running WebLogic Server 12.2.1.3 or later.
  • Oracle SOA Cloud Service supports the Database Adapter for the ATP database. See "Oracle JCA Adapter for Database" in Understanding Technology Adapters (12.2.1.4 | 12.2.1.3 ).
  • A minimum of two OCPU ATP databases is recommended.
  • Oracle SOA Cloud Service supports only serverless deployments of the ATP database. It does not support dedicated deployments.
  • DBFS is not configured when using ATP-D.
  • The Oracle Autonomous Transaction Processing database is not supported with the MFT Cluster or Business Activity Monitoring service types.
  • Oracle Enterprise Scheduler (ESS) is not included in the provisioned Oracle SOA Cloud Service instance with the Oracle Autonomous Transaction Processing database.
  • DBFS mount points are not created during provisioning for large Oracle B2B payloads.
  • Coordinated database backups with the Oracle SOA Cloud Service instance are not supported.