Move a Database to Another Database Home

This topic provides the details and procedure to move a database to a different Database Home.

Before you begin, review the following:

• The database is moved in a rolling manner. During the move operation, each database instance is stopped on one node at a time in the current Database Home and then restarted in the destination Database Home.

• While the database is being moved, the Database Home status is displayed as Updating.

• With the default Run datapatch on the database option, datapatch is automatically executed during the move operation to complete post-patch SQL actions for all patches, including one-off patches.

• If the database move operation fails, the database status is displayed as Failed, and the Database Home field provides information about the cause of the failure.

Procedure

Perform the following steps in the Console.

1. On the Data Infrastructures list page, select the Data Infrastructure that you want to work with. If you need help finding the list page or the Data Infrastructure, see List Data Infrastructures.

2. On the Data Infrastructure details page, select the VM Cluster tab to view the list of all VM Clusters.
3. On the VM Clusters tab, select the VM Cluster that you want to work with.

4. On the VM Cluster details page, select the Databases tab to view the list of all databases.

5. On the Databases tab, select the Database that you want to work with.

6. On the Database details page, from the Actions menu, select Move Database.

7. In the Move Database to Another Home panel, provide the following details.

   • Source Database Home: Displays the details of the current Database Home.

   • Target Database Home

     • Select a target Database Home: Select a new Database Home from the list.

   • Advanced Options

     • Datapatch options: Select from the given options.

       • Run datapatch on the database: Applies datapatch to the selected database. This is the default option.

       • Skip datapatch on the database: Skips datapatch execution on the selected database.

       • Skip datapatch for closed PDBs only: Skips datapatch execution only for PDBs that are in a closed state during the update.

8. Select Move.