Prepare for Migration

Prepare to migrate your database environment fromOracle Cloud Infrastructure Classic to Oracle Cloud Infrastructure. You can migrate an Oracle Real Application Clusters (Oracle RAC) database or Oracle Database Exadata Cloud Service environment.

The following migration paths are available from Oracle Cloud Infrastructure Classic:

From a 1-node or Oracle RAC Oracle Database Classic Cloud Service on Oracle Cloud Infrastructure Classic to a 1-node or Oracle RAC database system on Oracle Cloud Infrastructure
From an Oracle RAC Oracle Database Classic Cloud Service on Oracle Cloud Infrastructure Classic to Oracle Database Exadata Cloud Service on Oracle Cloud Infrastructure
From Oracle Database Exadata Cloud Service on Oracle Cloud Infrastructure Classic to Oracle Database Exadata Cloud Service on Oracle Cloud Infrastructure (currently limited to a 2-node configuration)

Prepare an Oracle RAC Environment for ADMT

If you have an Oracle Real Application Clusters (Oracle RAC) single instance database environment, then prepare the cloud environment for ADMT by creating a skeleton database service, downloading the Oracle Recovery Manager (RMAN) cloud backup module, and defining files.

Log into Oracle Cloud Infrastructure and create a skeleton database service.
This skeleton database will be overwritten by the restore encoded in this automation.
Download the RMAN cloud backup module zip file and save the file in a directory.
The directory defines the opc_installer_zip_src_location variable in the setup.json file.
Define the inventory file.
Sample templates are available in the /examples subdirectory.
Use the discovery_setup_json.sh script to automatically collect some of the values for the setup.json payload file.
The script creates a file and populates some of the required information. You'll still need to provide data, such as the backup configuration for transport.
```
./discovery_setup_json.sh
```
The script creates a setup.json_discovery_datetime_stamp file.
Locate the setup.json_discovery_datetime_stamp file in the root directory of ADMT.
The file name includes a date and timestamp.
```
ls -latr 
```
Complete the missing values for the variables that are not yet discovered or configured.
```
less setup.json_discovery_datetime
```
Define the setup.json file by using the templates in the /examples subdirectory or the setup.json_discovery_datetime_stamp file as a starting point and complete the variables which have not yet been discovered or configured (oci_* and oracle_target_database_oci_*).
The setup.json_discovery_datetime_stamp file is the output from the script executed in Step 4.

Prepare an Oracle Database Exadata Environment for ADMT

If you have an Oracle Database Exadata Cloud Service environment, then you have a multi-home configuration and you need to create a database_unique_name to discovery_setup_json.sh file for ADMT. Prepare the cloud environment for the ADMT by creating a skeleton database service, downloading the Oracle Recovery Manager (RMAN) cloud backup module, and defining files.

Log into Oracle Cloud Infrastructure and create skeleton database service.
This skeleton database will be overwritten by the restore encoded in this automation. For automatic backups you should enable it in the Oracle Cloud Infrastructure Console.
Download the RMAN cloud backup module zip file and save the file in a directory.
The directory defines the opc_installer_zip_src_location variable in the setup.json file.
Define the inventory file.
Sample templates are available in the /examples subdirectory.
Use the discovery_setup_json.sh script to automatically collect some of the values for the setup.json payload file.
You must provide database_unique_name for the discovery_setup_json.sh script. The database_unique_name is available in the Oracle Cloud Infrastructure Console. Provide a value for the target (-t parameter) and the source (-s parameter) when both the source and target are an Oracle Database Exadata Cloud Service. If, for example, you're converting from an Oracle Real Application Clusters (Oracle RAC) to an Oracle Database Exadata Cloud Service system, then provide the target parameter.
```
./discovery_setup_json.sh -t database_unique_name
```
The script creates a setup.json_discovery_datetime_stamp file.
Locate the setup.json_discovery_datetime_stamp file in the root directory of ADMT.
The file name includes a date and timestamp.
```
ls -latr
```
Complete the missing values in the setup.json file for the variables that are not yet discovered or configured.
```
less setup.json_discovery_datetime
```
Define the setup.json file by using the templates in the /examples subdirectory or the setup.json_discovery_datetime_stamp file as a starting point and complete the variables which have not yet been discovered or configured (oci_* and oracle_target_database_oci_*).
The setup.json_discovery_datetime_stamp file is the output from the script executed in Step 4.