The scenario presented here is a source environment with multiple Oracle Fusion Middleware and Oracle SOA Suite 12c (12.2.1.3) domains connecting to the same non-container database (CDB) 12.1.0.2 using different schemas prefixes (for example, DEV_WLS, DEV2_SOAINFRA, and so on) but using the same database service name (for example, orclsoa.example.com).

To migrate to a CDB that contains multiple PDBs, the approach is:

• Migrate data (using expdp and impdp, or by cloning PDBs) from the non-CDB 12.1.0.2 to a CDB 12.1.0.2 with multiple PDBs.
• Each PDB must contain a consistent set of schemas (per application), differentiated by prefixes.
• PDBs must be available under different PDB service names.

To simplify the example provided here, the setup is as follows:

• The non-CDB 12.1.0.2 (source environment) has one Oracle Fusion Middleware 12.2.1.3 domain and one Oracle SOA Suite 12.2.1.3 domain, so there are two prefix schemas:
  • DEV_WLS for the Oracle Fusion Middleware domain.
  • DEV2_SOAINFRA for the Oracle SOA Suite domain.
• In the new target CDB 12.1.0.2 (target environment), there will be two PDBs (PDB1 and PDB2), and the target system will be installed in new-target-db12c.example.com (192.168.56.93).
  • PDB1 will have DEV_WLS as prefix but will have the new service name pdb1_orclsoa.
  • PDB2 will have DEV2_SOAINFRA as prefix but will have the new service name pdb2_orclsoa.
• The Oracle Fusion Middleware and Oracle SOA Suite 12.2.1.3 domains will stay as they are (installed in soa-host01.example.com), and the JDBC connections will be reconfigured to point to the new target Oracle Database 12.1.0.2 container instance (installed in new-target-db12c.example.com).

Source Environment: Non-Container Database

The following diagram and values depict this scenario in the source environment.

Target Environment: Container Database

The following diagram and values depict this scenario in the target environment.