Migrate DBHome(s)

Migrate DBHome(s) from source VM cluster using the specified target VM cluster details.

Ensure that the target VM cluster(s) is in available state, the database input file has been generated and modified according to the target platform requirement.

The migrate_dbhomes command supports the following options:

Syntax

exacloudmigration migrate_dbhomes [-hV] [-a|-l <dbNames>] -i <inputFile> [-p <patchesFile>] [--dry-run]

Table 2-16 Exadata exacloudmigration migrate_dbhomes Commands

Command	Description
`-a, --all`	Migrates all dbhomes to the target VM cluster from the source VM cluster.
`-i, --inputFile`	Specifies the database input file name with the complete path.
`-l, --dbNames`	Specifies a comma-delimited list of source database names to migrate the database home. Examples: To migrate a database: -l dbname1 To migrate multiple databases: `-l dbname1,dbname2,dbname3`
`-p, --patchesFile`	Specifies the one-off patches file with the complete path. This file is generated by the `ecmasshutility` and is applicable only when the source is ExaDB-C@C. Use the `nopatch` option to create all target database home images with the source home base RU. For example, `-p nopatch`.
`--dry-run`	Performs dry run without creating the dbhome(s).
`-h, --help`	Displays help information about the command and its options.
`-V, --version`	Displays the version of the utility.

Examples:

To validate the database input template file and perform a --dry-run:

/home/opc>./exacloudmigration migrate_dbhomes -a -i inputs/infra_phxref/vmcluster_vmcluster1/database_inputs --dry-run

To validate a comma-delimited list of dbnames of the database input template file and perform a --dry-run:

/home/opc>./exacloudmigration migrate_dbhomes -i inputs/infra_phxref/vmcluster_vmcluster1/database_inputs -l dbname1,dbname2 --dry-run

To migrate all dbhome(s) in source (ExaDB-D) VM cluster to target (ExaDB-D) VM cluster, following successful validation and dry run:
```
/home/opc>./exacloudmigration migrate_dbhomes -a -i inputs/infra_phxref/vmcluster_vmcluster1/database_inputs
```
To migrate a comma-delimited list of dbhome(s) in the source (ExaDB-D) VM cluster to the target (ExaDB-D) VM cluster, following successful validation and dry run:
```
/home/opc>./exacloudmigration migrate_dbhomes -i inputs/infra_phxref/vmcluster_vmcluster1/database_inputs -l dbname1,dbname2
```
To migrate all dbhomes in the source (ExaDB-C@C) VM cluster to the target (ExaDB-C@C) VM cluster or source (ExaDB-C@C) VM cluster to the target (ExaDB-D) VM cluster, following successful validation and dry run:
```
/home/opc>./exacloudmigration migrate_dbhomes -a -i inputs/infra_phxref/vmcluster_vmcluster1/database_inputs -p /home/opc/patches_file
```
Generate the patches_file using the Generate patches file step and copy it to the client machine.
To migrate comma separated list of dbhomes in the source (ExaDB-C@C) VM cluster to the target (ExaDB-C@C) VM cluster or source (ExaDB-C@C) VM cluster to the target (ExaDB-D) VM cluster, following successful validation and dry run:
```
/home/opc>./exacloudmigration migrate_dbhomes -i inputs/infra_phxref/vmcluster_vmcluster1/database_inputs -l dbname1,dbname2 -p /home/opc/patches_file
```
Generate the patches_file using the Generate patches file step and copy it to the client machine.

Note:

Along with the migration, free-form tags of database dbHome(s) are also replicated to the target.

Parent topic: Exadata Cloud Infrastructure Migration Automation Utility Functionality