Viewing assessment details for MySQL migrations

Assessment details page

On the Assessment details page, you can view a list of your Assessment in a table, which includes the following information:

  • Name of the Assessment

  • State of the Assessment resource, which can be any one of the following:

    • Creating: The new Assessment resource is being created in OCI.

    • Updating: Changes to the Assessment resource are being registered in OCI.

    • Active: The Assessment resource has finished being created or updated and is ready for use.

    • Inactive: A fallback state for unexpected errors.

    • Deleting: This state appears when you delete an Assessment resource. The resource remains in this state until deletion is completed, at which point the resource is no longer listed in the console.

    • Failed: There are problems with the Assessment resource. You can review the Assessment resource work requests to investigate the issue.

  • Migration

  • Created date and time

Assessment information page

Select an assessment from the Assessment details page to view its details.

On the Assessment information page you can view the assessment information, including:

General information:

  • OCID: The resource's unique Oracle Cloud ID.
  • Compartment: The compartment where the Connection resides.
  • Created: The date and time when the Connection was created.
  • Updated: The date and time when the Connection was updated.
Migration information:
  • Source database: The link takes you to the Database Details page. You can select Test connection to test the connectivity of the database connection.
  • Target database: The link takes you to the Database Details page. You can select Test connection to test the connectivity of the database connection.
  • Database type: For OCI co-managed databases--Autonomous Database, Database (BareMetal, VM, Exadata), VM Cluster Database (Exadata)--the display name of this Connection is also shown. The link takes you to the Database Details page in OCI. Autonomous Database, Database (BareMetal, VM, Exadata), VM Cluster Database (Exadata), Oracle, or Amazon RDS.
  • Network speed
  • Acceptable downtime
  • Data size
  • DDL changes expected

Steps

This section includes all the steps that you need to follow. The current step is displayed at the top.

The steps include the following information:

  • Name of the step
  • Description of the step along with the result.
  • Status of the step
  • Actions such as Configure, Run again

All the steps are listed as follows:

All steps:
  1. Determine recommended migration method: Based on your specific requirements, the service evaluates your inputs and recommends the most suitable migration method as offline or online.
  2. Analyze compatibility: The service evaluates that source and target databases are suitable for the OCI Database Migration Service.
  3. Complete migration configuration: Provides additional details to complete your migration configuration.
  4. Prepare source database: The service identifies and prepares your source database with the required parameters.
  5. Create Migration: Create the migration object to initiate the actual data transfer.
Here are more details about the steps that are a part of the assessment:
  1. Determine recommended migration method: Based on your inputs this step suggests the best migration method. You have the option to override this suggestion and pick a different method. You can run this step many times as required. For scenarios where you already have completed the other steps, if the migration method is changed, the progress on the steps will be lost and you will have to be complete them again.
  2. Analyze compatibility: This step identifies the incompatible objects between the source and the target database. Depending on the severity, the checks are grouped in different categories. Also, the number of issues are included beside the type, such as Review required (1), Passed checks (31), and so on:
    • Review required: Indicates migration may succeed (at least in part) but not everything is expected to work exactly as before or some work post migration must be done to bring the target instance into alignment with the source database. Checks in this category will collect your approval and apply any required change during database preparation. Checks in this section are blockers for the migration.
    • Manual action required: Checks in this category need to be manually resolved before attempting a migration as there is no automation available at the moment. Checks in this section are blockers for the migration.
    • Review is suggested: Indicates migration should succeed and applications will have no functional difference however database administrators should evaluate each check with this status to look for any unforeseen consequences. You can Acknowledge these checks and this action has no further effect. Checks in this section are not blockers for the migration. You can move to the Previous issue or the Next issue.
    • Passed checks: Checks in this section indicate the migration should succeed and applications should see no difference in behavior. Checks in this section are not blockers for the migration.
    When you click Review, then the Review issues page is displayed with the following details:
    • Name
    • Status
    • Issue
    • Impact
    • Action
    • Objects
    For Review required and Review is suggested, you can analyze Objects to review which provides the following details:
    • OWNER
    • TABLE_NAME
    • COLUMN_NAME
    • DATA_TYPE

    You can perform actions such as Cancel, go to Next issue, or Previous issue.

    You can Undo approve for Review required action, and/or Acknowledge for the Review is suggestedaction.

  3. Complete migration configuration: This step allows you to select additional migration information. This step is connected to the migration method that you select during the step 1 and the available options retains that migration method. Depending on the selected source connection and if there was a target connection selected or just a target type the following options are available:
    • Source database connection creation or selection. You need to select a transfer medium:
      • Export directory object name
      • Export directory object path
      • Source database file system SSL wallet path

        Note:

        This option is applicable only for Oracle migrations, non-Autonomous databases, when you do not create a connection with SSH details.
    • Target database connection creation or selection. You need to select a transfer medium:
      • Import directory object name
      • Import directory object path
      • Target database file system SSL wallet path

        Note:

        This option is applicable only for Oracle migrations, non-Autonomous databases, when you do not create a connection with SSH details.
    • Object storage bucket:
      • Snapshot Standby database connection selection
      • Advanced settings

      See the Editing a migration topic for more details related to editing the initial load settings.

  4. Prepare source database: This step runs the missing configurations identified during the step 2, Analyze compatibility. If you approved any check with included fixup, then it will be resolved in this step. Click Configure to start the preparation of the source database. Depending on the criticality the checks will be grouped in different categories:
    • Manual action required: You must manually resolve the checks in this category before attempting a migration as currently, there is no automation available. Checks in this category are blockers for the migration and you must resolve them before continuing the migration process. After the preparation check, apply the logic by either clicking on the Run SQL or Download SQL and for executing it on your own, click the Recheck option. This step marks the pending actions until all the blocking checks are resolved. This step identifies the required database configuration.
    • To be fixed with preparation script: Checks in this category were approved during the step 2, Analyze compatibility, these are blockers for the migration but will be fixed by the preparation script.
    • Passed: Checks in this section indicate the migration should succeed. Checks in this section are not blockers for the migration. The preparation script can either be run by the service or downloaded and applied manually by you. After the preparation check logic is applied, you can run a Recheck. This step will remain as Action required until all blocking checks are resolved. The same logic applies for the target
  5. Prepare target database: This step is quite similar to the Prepare source database however, it includes Data Pump settings validations for the source and the target databases. Depending on the result, if any of these validations fail, you can review the issue and action details, and you can also download the log. This step will prepare the target databases. The service identifies and prepares your target database with the required parameters. Click Configure to start the preparation of the target database. You can select Run again or Download log. Depending on the criticality the checks will be grouped in different categories:
    • Manual action required: Checks in this category need to be manually resolved before attempting a migration as there is no automation available at the moment. Checks in this section are blockers for the migration. Click Review to review the issues and error messages.

      For example, if you have issues in the Java Objects, Java Sources, or preparation script, review the script, and select I have reviewed the SQL script and am aware of the changes it will apply to my database. Click the Run SQL option and Close the tab.

    • Completed
  6. Advanced assessment steps (optional): The intent of these features is to offer additional functionality, these steps are not mandatory. Migrate table: This step will test the assessment. It will create a table in GGADMIN schema and transfer it to the target database. You can select to Run again as required. View details allow you to review the failure details.
  7. Create Migration: Creates a Migration object. Once an assessment has a migration object the assessment is frozen and no additional changes are allowed.

Migration workflow

From the Progress tab in Migration, click Start to initiate the actual data movement workflow. A popup window displays the different phases to require your input after completion. By default, the phase Monitor replication Lag is selected. This will enable the replication to run continuously until the migration is resumed. Select Start to begin the migration. For more details, see Viewing migration details for assessments.

Selected objects

See the following topics for information:

Work Requests

On the Assessment details page, you can find the Work requests list. Work Requests lists any work requests sent to OCI to facilitate the creation, update, or deletion of this resource. Click the work request to go to the Work Request Details page for more information about the work request.

Parent topic: Manage assessment