Generate input templates

Syntax

exacloudmigration generate_template [-hV] [command]

Oracle Exadata Cloud Infrastructure Migration Utility discovers and captures the configuration of the source environment as input templates for the Exadata Infrastructure, VM clusters, databases, and PDBs. These templates are then used to create or migrate the infrastructure, VM clusters, databases, and PDBs in the target environment.

Table 3-6 Oracle Exadata Cloud Infrastructure Migration Utility Generate Template Options

Option	Description
`-h, --help`	Displays help information about the command and its options.
`-V, --version`	Displays the version of the utility.

Table 3-7 Oracle Exadata Cloud Infrastructure Migration Utility Generate Template Commands

Command	Description
`all`	Generates input template for Infrastructure, VM cluster(s) and Databases.
`infra`	Generates input template for Exadata infrastructure.
`vmcluster`	Generates input template for VM cluster(s)
`database`	Generates input template for database(s).
`pdb`	Generates input template for PDBs.

Parent topic: Oracle Exadata Cloud Infrastructure Migration Utility Functionality

Generate input templates for Infrastructure, VM cluster(s), and database(s)

Syntax

exacloudmigration generate_template all [-hV] -t <targetType> -s <sourceExadataInfraOCID> [-i <infraInputFileName>] [-v <vmClusterInputFileName>] [-d <dbInputFileName>] [-p <profile>]

Table 3-8 Oracle Exadata Cloud Infrastructure Migration Utility Generate Template All Commands

Command	Description
`-t, --targetType`	Target System Type (`exadbd`, `exadbcc`).
`-s, --sourceExadataInfraOCID`	Source Exadata Infrastructure OCID.
`-i, --infraInputFileName`	Sets the infrastructure input template file name. Default: `infrastructure_inputs`
`-v, --vmClusterInputFileName`	Sets the VM cluster input template file name. Default: `cloudvmcluster_inputs`
`-d, --dbInputFileName`	Sets the database input template file name. Default: `database_inputs`
`-p, --profile`	OCI user profile name. Default profile: `DEFAULT`
`-h, --help`	Displays help information about the command and its options.
`-V, --version`	Displays the version of the utility.

Examples:

To generate all input template files (Infrastructure, VM cluster(s) and database(s)) if the migration target is ExaDB-D:
```
/home/opc>./exacloudmigration generate_template all -t exadbd -s <OCID>
```
To generate all input template files (VM cluster(s) and database(s)) if the migration target is ExaDB-C@C:
```
/home/opc>./exacloudmigration generate_template all -t exadbcc -s <OCID> -t exadbcc
```

Sample contents of input template for ExaDB-D Infrastructure (/home/opc/inputs/infra_phxref/infrastructure_inputs)

Note:

phxref refers to the infrastructure name

!-------------- CLOUD-EXADATA-INFRASTRUCTURE-INPUTS --------------!
## For details on these parameters refer readme which is shipped with this utility
## Modify these values for new infrastructure creation with different specifications
=================== START: GLOBAL PARAMETERS ===================
sourceProfile=DEFAULT
targetProfile=
sourceExadataInfraOCID=<OCID>
=================== END: GLOBAL PARAMETERS ===================

## The below values are retrieved based on the source infrastructure ocid.
## By default it will create new infra having same region, compartment, availability domain, display name, exadata infra model, compute count and storage count.
## Allowed values for exadataInfraModel: Exadata.X8M | Exadata.X9M | Exadata.X11M | Exadata.Base.48 and default is Exadata.X11M
## Allowed values for databaseServerType: X11M (required only for creating X11M infrastructure)
## Allowed values for storageServerType: X11M-HC (required only for creating X11M infrastructure)
## computeCount and storageCount is required only for Elastic models
=================== START: phxref ===================
compartmentOCID=<OCID>
region=us-phoenix-1
displayName=phxref
availabilityDomain=OLou:PHX-AD-2
exadataInfraModel=Exadata.X11M
databaseServerType=X11M
computeCount=2
storageServerType=X11M-HC
storageCount=3
=================== END: phxref ===================

Sample contents of input template for ExaDB-D VM cluster(s) (/home/opc/inputs/infra_phxref/cloudvmcluster_inputs)

Note:

phxref refers to the infrastructure name

!-------------- CLOUD-VMCLUSTER-INPUTS --------------!
## For details on these parameters refer readme which is shipped with this utility.
## Modify these values for new cloud VM cluster creation with different specifications.
=================== START: GLOBAL PARAMETERS ===================
sourceProfile=DEFAULT
targetProfile=
sourceExadataInfraOCID=<OCID>
targetExadataInfraOCID=
==================== END: GLOBAL PARAMETERS ===================

## The below values are retrieved based on the source infrastructure ocid.
## By default it will create new cluster having values same as source VM cluster.
=================== START: vmcluster1 ===================
create=no
createAppVIP=no
sourceVmClusterOCID=<OCID>
compartmentOCID=<OCID>
displayName=examig
giVersion=19.0.0.0
exadataImageVersion=23.1.13.0.0.240410.1
dbServers=dbServer-1, dbServer-2
cpuModel=ocpu
cpuCountPerVM=6
memorySizeInGBsPerVM=720
u02SizeInGBsPerVM=175
fileSystemSizesInGBsPerVM={/=15, /var=5, /home=4, /tmp=3, /u01=20, /var/log=18, /var/log/audit=3}
dataStorageSizeInTBs=180
dataStoragePercentage=80
clientSubnetOCID=<OCID>
backupSubnetOCID=<OCID>
hostnamePrefix=examig
privateZoneOCID=
=================== END: vmcluster1 ===================

Sample contents of input template for ExaDB-C@C VM cluster(s) (/home/opc/inputs/infra_phxref/cloudvmcluster_inputs)

Note:

phxref refers to the infrastructure name

!-------------- VMCLUSTER-INPUTS --------------!
## For details on these parameters refer readme which is shipped with this utility.
## Modify these values for new ExaDb-C@C VM cluster creation with different specifications.
=================== START: GLOBAL PARAMETERS ===================
sourceProfile=DEFAULT
targetProfile=
sourceExadataInfraOCID=<OCID>
targetExadataInfraOCID=
==================== END: GLOBAL PARAMETERS ===================

## The below values are retrieved based on the source infrastructure ocid.
## By default it will create new cluster having values same as source VM cluster.
=================== START: vmcluster1 ===================
create=no
sourceVmClusterOCID=<OCID>
compartmentOCID=<OCID>
displayName=examig
giVersion=19.0.0.0
exadataImageVersion=23.1.13.0.0.240410.1
dbServers=dbServer-1, dbServer-2
cpuModel=ocpu
cpuCountPerVM=6
memorySizeInGBsPerVM=720
u02SizeInGBsPerVM=175
fileSystemSizesInGBsPerVM={/=15, /var=5, /home=4, /tmp=3, /u01=20, /var/log=18, /var/log/audit=3}
dataStorageSizeInTBs=180
dataStoragePercentage=80
vmClusterNetworkOCID=
=================== END: vmcluster1 ===================

Sample contents of input template for ExaDB-D database(s) (/home/opc/inputs/infra_phxref/vmcluster_vmcluster1/database_inputs)

Note:

phxref refers to the infrastructure name and vmcluster1 refers to the VM cluster name

!-------------- DATABASE-INPUTS --------------!
## For details on these parameters refer readme which is shipped with this utility.
## Modify these values for new dg association creation with different specifications.
=================== START: GLOBAL PARAMETERS ===================
sourceProfile=DEFAULT
targetProfile=
sourceVmClusterOCID=<OCID>
targetVmClusterOCID=
=================== END: GLOBAL PARAMETERS ===================

## The below values are retrieved based on the source infrastructure or VM cluster ocid.
## By default it will create dg association having default values.
## Allowed values for dataGuardType: dataGuard | activeDataGuard and default is dataGuard
## Multidg supports only MAXIMUM PERFORMANCE for protection mode
=================== START: DBNAME1 =======================
create=no
sourceDatabaseOCID=<OCID>
dbName=DBNAME1
databaseSoftwareImageOCID=
dataGuardType=dataGuard
dbUniqueName=
oracleSidPrefix=DBNAME1
standbyDatabaseOCID=
=================== END: DBNAME1 ==========================

=================== START: DBNAME2 =========================
create=no
sourceDatabaseOCID=<OCID>
dbName=DBNAME2
databaseSoftwareImageOCID=
dataGuardType=dataGuard
dbUniqueName=
oracleSidPrefix=DBNAME2
standbyDatabaseOCID=
=================== END: DBNAME2 ===========================

Sample contents of input template for ExaDB-C@C database(s) (/home/opc/inputs/infra_phxref/vmcluster_vmcluster1/database_inputs)

Note:

phxref refers to the infrastructure name and vmcluster1 refers to the VM cluster name

!-------------- DATABASE-INPUTS --------------!
## For details on these parameters refer readme which is shipped with this utility.
## Modify these values for new dg association creation with different specifications.
=================== START: GLOBAL PARAMETERS ===================
sourceProfile=DEFAULT
targetProfile=
sourceVmClusterOCID=<OCID>
targetVmClusterOCID=
=================== END: GLOBAL PARAMETERS ===================

## The below values are retrieved based on the source infrastructure or VM cluster ocid.
## By default it will create dg association having default values.
## Allowed values for dataGuardType: dataGuard | activeDataGuard and default is dataGuard
## Multidg supports only MAXIMUM PERFORMANCE for protection mode

=================== START: DBNAME1 =======================
create=no
sourceDatabaseOCID=<OCID>
dbName=DBNAME1
databaseSoftwareImageOCID=
dataGuardType=dataGuard
dbUniqueName=
oracleSidPrefix=DBNAME1
standbyDatabaseOCID=
=================== END: DBNAME1 ==========================

=================== START: DBNAME2 =========================
create=no
sourceDatabaseOCID=<OCID>
dbName=DBNAME2
databaseSoftwareImageOCID=
dataGuardType=dataGuard
dbUniqueName=
oracleSidPrefix=DBNAME2
standbyDatabaseOCID=
=================== END: DBNAME2 ===========================

Parent topic: Generate input templates

Generate input template for Infrastructure only

Syntax

exacloudmigration generate_template infra [-hV] -s <sourceExadataInfraOCID> [-i <inputFileName>] [-p <profile>]

Table 3-9 Oracle Exadata Cloud Infrastructure Migration Utility Generate Template Commands

Command	Description
`-s, --sourceExadataInfraOCID`	Source Exadata Infrastructure OCID.
`-i, --inputFileName`	Sets the infrastructure input template file name. Default: `infrastructure_inputs`
`-p, --profile`	OCI user profile name. Default profile: `DEFAULT`
`-h, --help`	Displays help information about the command and its options.
`-V, --version`	Displays the version of the utility.

Examples:

To generate input template for ExaDB-D infrastructure only:

/home/opc>./exacloudmigration generate_template infra -s <OCID>

Parent topic: Generate input templates

Generate input template for VM cluster(s) only

Syntax

exacloudmigration generate_template vmcluster [-hV] -t <targetType> -s <sourceExadataInfraOCID> [-i <inputFileName>] [-p <profile>]

Table 3-10 Oracle Exadata Cloud Infrastructure Migration Utility Generate Template VM Clusters Commands

Command	Description
`-t, --targetType`	Target System Type (`exadbd`, `exadbcc`).
`-s, --sourceExadataInfraOCID`	Source Exadata Infrastructure OCID.
`-i, --inputFileName`	Sets the VM cluster input template file name. Default: `cloudvmcluster_inputs`
`-p, --profile`	OCI user profile name. Default profile: `DEFAULT`
`-h, --help`	Displays help information about the command and its options.
`-V, --version`	Displays the version of the utility.

Examples:

To generate input template for VM cluster(s) if the migration target is ExaDB-D:
```
/home/opc>./exacloudmigration generate_template vmcluster -t exadbd -s <OCID>
```
To generate input template for VM cluster(s) if the migration target is ExaDB-C@C:
```
/home/opc>./exacloudmigration generate_template vmcluster -t exadbcc -s <OCID>
```

Parent topic: Generate input templates

Generate input template for database(s) only

Syntax

exacloudmigration generate_template database [-hV] -s <sourceVmClusterOCID> [-i <inputFileName>] [-p <profile>]

Table 3-11 Oracle Exadata Cloud Infrastructure Migration Utility Generate Template Database(s) Commands

Command	Description
`-s, --sourceVmClusterOCID`	Source VM cluster OCID.
`-i, --inputFileName`	Set the database(s) input template file name. Default: `database_inputs`
`-p, --profile`	OCI user profile name. Default profile: `DEFAULT`
`-h, --help`	Displays help information about the command and its options.
`-V, --version`	Displays the version of the utility.

Examples:

To generate input template for ExaDB-D database(s) only:

/home/opc>./exacloudmigration generate_template database -s <OCID>

To generate input template for ExaDB-C@C database(s) only:

/home/opc>./exacloudmigration generate_template database -s <OCID>

Parent topic: Generate input templates

Generate input template for PDBs only

Syntax

exacloudmigration generate_template pdb [-hV] -s <sourceDatabaseOCID> [-i <inputFileName>] [-p <profile>]

Table 3-12 Oracle Exadata Cloud Infrastructure Migration Utility Generate Template PDBs Command

Command	Description
`-s, --sourceDatabaseOCID`	Source Database OCID.
`-i, --inputFileName`	Set the pdb(s) input template file name. Default: `<dbName>_pdb_inputs`
`-p, --profile`	OCI user profile name. Default profile: `DEFAULT`
`-h, --help`	Displays help information about the command and its options.
`-V, --version`	Displays the version of the utility.

Examples:

To generate input template for PDBs only:

/home/opc>./exacloudmigration generate_template pdb -s <OCID>

Example content of input template for PDBs

(/home/opc/inputs/infra_text-infra/vmcluster_vmcluster1/DBNAME1_pdb_inputs)

Note: text-infra refers to the infrastructure name, vmcluster1 refers to the VM cluster name and database dbName is DBNAME1

!-------------- PDB-INPUTS --------------!
## For details on these parameters, refer to the README.txt shipped with this utility.
## Modify these values for PDB relocation according to the requirements

=================== START: GLOBAL PARAMETERS ===================
sourceProfile=DEFAULT
targetProfile=
sourceDatabaseOCID=<OCID>
=================== END: GLOBAL PARAMETERS ===================

## The below values are retrieved based on the source Database ocid.
## By default, the PDB is relocated with the same name as the source. Update the PDB name if a different name is required

=================== START: PDB2 ===================
create=no
sourcePDBOCID=<OCID>
pdbName=PDB2
targetDatabaseOCID=<OCID>
=================== END: PDB2 ===================

=================== START: PDB1 ===================
create=no
sourcePDBOCID=<OCID>
pdbName=PDB1
targetDatabaseOCID=
=================== END: PDB1 ===================

Parent topic: Generate input templates