Create database dbHome software image

Create database dbHome software image(s) using the specified database(s) details

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

The create_dbhomeimage command supports the following options:

Syntax

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

Table 2-13 exacloudmigration create_dbhomeimage Commands

Command	Description
`-a, --all`	Creates software image for all databases in the source VM cluster.
`-i, --inputFile`	Specifies the database input file name with the complete path.
`-i, --infraInputFileName`	Specifies a comma-delimited list of database(s) to create the database software image. Examples: To create the database software image for a database: `-l dbname1` To create the database software image for 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 database software image(s).
`-h, --help`	Displays help information about the command and its options.
`-V, --version`	Displays the version of the utility.

Examples:

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

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

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

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

To create a software image(s) for each database home of the source ExaDB-D VM cluster, following successful validation and dry run:
```
/home/opc>./exacloudmigration create_dbhomeimage -a -i inputs/infra_phxref/vmcluster_vmcluster1/database_inputs
```

To create specific Database homes software image(s) of source ExaDB-D VM cluster, following successful validation and dry run:

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

To create a software image(s) for every database home of the source ExaDB-C@C VM cluster, following successful validation and dry run:
```
/home/opc>./exacloudmigration create_dbhomeimage -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 create specific Database homes software images of source ExaDB-C@C VM cluster, following successful validation and dry run:
```
/home/opc>./exacloudmigration create_dbhomeimage -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.

Parent topic: Exadata Cloud Infrastructure Migration Automation Utility Functionality