1. Administering Oracle Database Exadata Cloud at Customer (Gen 1/OCI-C)
  2. The dbaascli Utility
  3. dbaascli database move

dbaascli database move

The database move subcommand of the dbaascli utility moves a database to another Oracle Home directory location.

Connect to the compute node as the opc user and execute this command as the root user. 

dbaascli database move --dbname dbname --ohome oracle_home [--precheck] [--standby]

In the preceding command:

  • --dbname dbname — specifies the name of the database that you want to move.

  • --ohome oracle_home — specifies the path to an existing Oracle Home directory location, which you want the specified database to use.

  • --precheck — optionally performs a prerequisite check. You can use this option to test the environment prior to performing a move.
  • --standby — optionally specifies that you are moving a standby database. Specify this option if you are moving a standby database in an Oracle Data Guard configuration.

Before performing a move operation, ensure that all of the database instances associated with the database deployment are up and running.

You can use this command to move a database to an Oracle Home with a different patch level. For example, you can move in either direction between 12.2.0.1.200414 and 12.2.0.1.200714 or between 19.3 and 19.7. You can also use this command to move a standby database in an Oracle Data Guard configuration to an Oracle Home with a different release level. For example, 12.2.X to 19.Y.

However, for a standalone database (not in an Oracle Data Guard configuration) or an Oracle Data Guard primary database, you cannot use this command to move between major release versions, such as 12.2.X to 19.Y. For such cases, see dbaascli database upgrade. See also, Upgrading to 19c Oracle Database on Gen 1 Exadata Cloud at Customer.

When performing a move operation to an Oracle Home with a different patch level, if the database is part of an Oracle Data Guard configuration, then ensure that you move the standby database to the new patchset before you move the primary database.

The command automatically patches the data dictionary (also known as SQL patching or data patching) as required. Specifically, data dictionary patching automatically occurs when you move a database to an Oracle Home with a different patch level. The exception is for standby databases, where data dictionary patching flows from the primary.