Associate an Oracle Java Cloud Service Instance with a Different Database

Not Oracle Cloud Infrastructure This topic does not apply to Oracle Cloud Infrastructure. Identify the Cloud Infrastructure Used by a Service Instance.

Update an existing Oracle Java Cloud Service instance and associate it with a different Oracle Database Cloud Service deployment.

You might associate your service instance with a different database if:

  • Your service instance requires a database with a different version, edition, or capacity.

  • The current database has crashed or become corrupted, and can’t be restarted.


  • This operation is not supported for service instances running on Oracle Cloud Infrastructure regions.

  • This operation is not supported for service instances created before the Oracle Java Cloud Service release 17.4.1 (October 2017).

  • Both the original and the target Oracle Database Cloud Service deployment must be of type Single Instance. All other database types are not supported, including Database Clustering with RAC and Single Instance with Data Guard Standby.

  • Oracle Database Exadata Cloud Service is not supported.

You can only modify the association to the Infrastructure database for a service instance (the database that hosts the required Oracle WebLogic Server schemas). You cannot directly modify associations to other Application databases for a service instance. However, if the service instance’s Infrastructure database and Application database are associated with the same Oracle Database Cloud Service deployment, modifying the association for the Infrastructure database also modifies the association for the Application database.

You must enable backups on the Oracle Java Cloud Service instance prior to associating it with a different database deployment.

Before associating a service instance with a different infrastructure database, you must migrate the existing schema and data from the current database to the new database. Refer to these topics in Administering Oracle Database Cloud Service:

  1. Access your service console.
  2. Click the name of the service instance whose database association you want to change.
  3. At the bottom of the Overview page, expand Associations.
  4. From the list of associations for this service instance, identity the association with these characteristics:
    • Service Type - Oracle Database Cloud Service
    • Type - Depends On
  5. Click Manage Association Menu icon for this association, and then select Reassociate Database.

    This menu option is only available for the Infrastructure database association. It it not available for Application databases.

  6. For Database Instance Name, select the existing Oracle Database Cloud Service deployment to which you migrated the required Oracle Java Cloud Service schema and data.

    The list only includes a database deployment if it meets the following criteria:

    • Is in an active state and not currently in the process of being provisioned

    • Is not configured with a Backup Destination set to None

  7. For Association Description, describe the relationship between this Oracle Java Cloud Service instance and the selected database deployment.
  8. Enter the Database Administrator Username and Password of the database administrator that Oracle Java Cloud Service will use to connect to the selected database deployment.

    If the service instance is running Oracle WebLogic Server 12c ( version), you can specify the user SYS or any user that has been granted the SYSDBA privilege.

  9. Click Reassociate.

A new association is added to the Associations section of the Overview page. You can monitor the operation’s progress from this page or from the Activity page. After the operation completes successfully, the former database association is removed.

Prior to performing this operation, Oracle Java Cloud Service takes a backup of your service instance. If the operation fails, the service instance is automatically restored from this backup.