CPAT runs by default and provides you with the following features and benefits:

• Warns you about any features used by your database that aren't supported in the target environment

• Makes suggestions for remedial changes and/or parameters to use for the Data Pump export and import operations

• Generates remedial scripts for failing checks that you can run against the source database

After a validation job runs, the job output displays the checks performed, descriptions of any problems, and actions you can take to resolve the issues.

To view or download the CPAT results

1. On a migration resource detail page, click Jobs, then the job name, then Phases.

2. Click the Validate pre-migration advisor phase name to open the Validation pre-migration advisor detail page.

   From this page you can download the CPAT report, view the report statistics, and drill down in the Checks list.

Checks List Operations

Filters: You can filter the checks listed using the Filters checkboxes on the left side.

Drill down on individual checks: Click a check name in the list to display details about that check from the CPAT report.

Check Details

The View check details panel shows you

• Information about the check, including the issue that caused the result shown, its potential impact on the migration, any action you can take to mitigate the issue, and if applicable, the location of a fixup script you can run on the source database.

• A Reviewed indicator, which lets you mark a check as "reviewed" so that you can see in the Validate premigration advisor list of checks whether you have completed whatever tasks you wanted to do with the check.

  Click the link in the check details to change it to a No or Yes value. The indicator does not have any impact on how the checks are processed; it is available for your convenience.

• A list of Objects that were flagged by the check as problematic.

  Some checks will show a read-only list of objects and some checks let you interactively update the objects listed.

Running Fixup Scripts

The location of the fixup script is shown on the View check details panel for an individual check.

The Fixup script location specifies where the script is located on the source database.

Running the fixup script against the source database requires sys admin privileges.

In multitenant architecture, fixup scripts should be run on the CDB. Running them on the PDB will produce an error.

Excluding Problematic Objects

After a validation run, every object listed in the View check details pane shows a No in the Is excluded column.

To exclude objects from the next validation run, you can check the boxes next to objects in the list and click Exclude selected, or you can choose Exclude all to exclude all objects that were listed in the check.

Any objects you choose to exclude will show a Yes in the Is excluded column. Objects marked Yes are ignored by CPAT in the next validation run, and they will not appear in the Objects list the next time you run the validation.

The migration's Selected Objects configuration is also updated to reflect this change. You will see a new row with the exclusion rule in the Selected Objects on the Migration details page. If you want to include this object again you must remove the rule in the Selected Objects list.

Note that Exclude all will exclude all of the objects on the page displayed, plus any objects from pages not displayed. However, if you check the first box in the checkbox column and click Exclude all, only the objects listed on the current page are excluded.

See Selecting objects for Oracle migration for information about explicitly including and excluding objects.