Oracle Cloud Infrastructure Documentation

Troubleshooting Classic Migration

Use troubleshooting information to identify and address common issues that can occur while working with Classic Migration Service.

If a migration fails, then the status of the migration changes to Migration failed and the status of the migrate application work request is Failed. The work request that is associated with migration is the Migrate Application work request. View the errors associated with this work request to identify the issues. For information about the different work requests that are associated with the operations that you perform on sources and migrations, see Work Requests in Classic Migration Service.

To view logs and errors associated with a work request:

  1. Open the navigation menu on the Oracle Cloud Infrastructure Console, click OCI Classic Services, and then click either Sources or Migrations in the Classic Migration section to display either the Sources in compartment or Migrations in compartment page and a list of sources or migrations in the compartment.
  2. Choose a compartment from the Compartment menu in which you have permission to work. The page updates to display only the resources in that compartment. If you are not sure which compartment to use, then contact an administrator. For more information, see Access Control.
  3. Click the name of the resource for which you want to view work requests to display the details page for that resource.
  4. In the Resources section, click Work Requests to display a list of work requests and their statuses.
  5. Click a work request to display its details page and view log messages and other details about the work request.

    For example, if a migration fails, then click the Migrate Application work request to view the logs and errors to identify the issues associated with migration of the application.

  6. In the Resources section of the work request details page, click Logs to view the activity logs.
  7. In the Resources section of the work request details page, click Errors to view error messages.

After resolving the issues, you can retry the process. If issues occurred while migrating the application, then click the Migrate Application work request to view the logs and errors to identify the issues. After resolving the issues, you can start the migration.

Stack Creation Failed

Troubleshoot a failed Oracle WebLogic Server domain that you attempted to create with Oracle WebLogic Server for Oracle Cloud Infrastructure or Oracle SOA Suite on Marketplace.

Use the Terraform job logs in Resource Manager to identify the cause of the failure.

  1. From the navigation menu on the Oracle Cloud Infrastructure Console, select Resource Manager, and then click Jobs.
  2. Identify and click the job for your stack.
    • The type is Apply.
    • The state is Failed.
    • The stack is the name of your target instance stack.
  3. In the Logs section, search the log for error messages.

    You can optionally Download the log files and search the files offline.

Unable to Access the Domain

Troubleshoot problems accessing the application console after it's successfully migrated.

To check port access to the application console:

  1. From the navigation menu on the Oracle Cloud Infrastructure Console, select Networking, and then click Virtual Cloud Networks.
  2. Select the compartment in which you created the domain.
  3. Select the virtual cloud network in which you created the domain.
  4. Select the subnet where the Oracle WebLogic Server compute instance is provisioned.
  5. Select the security list assigned to this subnet.

  6. For a domain that is not on a private subnet, make sure the following ingress rule exists to permit traffic to the application console:

    Source: 0.0.0.0/0
IP Protocol: TCP
Source Port Range: All
Destination Port Range: port_to_access_application_console

    For example, by default the Oracle WebLogic Server Administration Console is accessed through port 7001 or 7002. To permit traffic to port 7001, create the following ingress rule:

    Source: 0.0.0.0/0
IP Protocol: TCP
Source Port Range: All
Destination Port Range: 7001

Missing Integrations in Target Instance

In some cases, you successfully migrate an application to the target Oracle Integration instance but all the integrations from the source environment did not migrate to the target.

After a migration completes, log into your target instance to verify that all integrations from the source instance successfully migrated to the target. If any integrations are missing, then view the log files. The log files provide details about the resources that were exported from the source environment, the status of the resources imported to the target environment, and import errors, if any.

To identify the missing integrations, view the log files and search for OIC Export Report log and Integration Import Log from Archive log entries.

When you start a migration, Classic Migration Service archives all the resources on the source instance into a storage bucket. The OIC Export Report log lists all the resources that are available in the storage bucket. View this report to identify the components that Classic Migration Service migrated from the source environment.

After exporting the resources in the source instance to a storage bucket, Classic Migration Service imports the individual resources to the target instance. The Integration Import Log from Archive lists the components that are imported to the target instance.

  1. Open the navigation menu on the Oracle Cloud Infrastructure Console, click OCI Classic Services, and then click Sources in the Classic Migration section to display the Sources in compartment page and a list of sources in the compartment.
  2. Select the compartment from the Compartment drop-down that contains your migration, if you are not already in the correct compartment.
  3. Click the name of the source you want to troubleshoot to display the details page for that source.
  4. In the Resources section, click Work Requests to display a list of work requests and their statuses.
  5. Click the Migrate Application work request to display the details page for that work request and view the logs and errors to identify the issues associated with migration of the application.
  6. In the Resources section, click Logs to view the messages and identify the cause of the issue.
  7. In the list of logs, search for logs that begin with OIC Export Report and Integration Import Log from Archive.