Introduction
The Cloud Migration tool is a tool that you can run prior to moving your database into the Oracle cloud. (OCI). The tool is referred to as CPAT. The tool will significantly help those companies that want to move into OCI from their on-premise data centers.
Description
The tool will examine the source database with the target database in OCI and produce a report on the migration process. Unlike, some diagnostic tool, the CPAT tool It does not change the source database in anyway. It does not install any PLSQL or Objects into the source database. However, there are some pre-requisites required before you can run the tool,.
Its important to note this is an advisory tool. It does NOT perform the migration, instead it uses metadata collected when the tool is run which can be used by clients to help and input into their migration.
When you run the tool, you will need to specify the source database, but also a destination database. This can be an actual Oracle Autonomous Database you have running in OCI or a "generic Oracle Autonomous Database".
Pre-Requisite
There are a few pre-requisites you need to perform before the tool can be run. This are listed below
- Java 8 must be installed. (java 7 will work but not recommended).
- The following environment variables need to be set
- JAVA_HOME
- ORACLE_HOME
- ORACLE_SID
- ORACLE_HOME
- LD_LIBRARY_PATH
- The user that connects to the source database must have the following grants
- SELECT ANY DICTIONARY
- SELECT on SYSTEM.DUM$COLUMNS
- SELECT on SYSTEM.DUM$DATABASE
- Generate a CPAT properties file by running the tool with the gettargetprops parameter for the source database
- ./premigration.sh —gettargetprops -username <username> —connectstring '<connection string>
Run Types
Once the pre-requisites have been met, you are then ready to run the tool.
There are two modes you can run the tool in; FULL and SCHEMA.
In FULL mode, the tool will run checks relevant to the migration options you have chosen. All SCHEMA, INSTANCE, and UNIVERSAL checks are run.
In SCHEMA mode, SCHEMA and UNIVERSAL checks are run, but INSTANCE checks are not.
Once the tool has finished it will generate a report on the issues it has found.
Sometimes the same issue will be found for more than one object. For example, object is invalid. To avoid getting repeat messages, use the parameter —maxtextdatarows n which will limit the number of rows produced for the same error.
Further Information
Documentation
The 23c documentation for CPAT can be found here CPAT
Metalink
There master note on the tool is 2758371.1
Download the Tool
The tool can be downloaded at the following link CPAT
Published 18th October 2023
