Connection creation failures

In Oracle Cloud Infrastructure Database Migration, if you have a Connection (odms-connection) resource in failed state use the following steps to gather more details about the failure.

  1. Get the connection OCID.

    • Using the OCI Web Console:

      Go to the OCI Console, and open Database Migration Service/Database Connections (for example, https://console.us-phoenix-1.oraclecloud.com/odms/registrations).

      Locate the failed Connection in the list, and select Copy OCID from the Actions (three dots) menu.

    • Using Oracle Database Migration Service (database-migration) OCI Command line interface:

      The compartment OCID where the failed connection was created is required.

      • List all connection resources and find the failure:

        oci database-migration connection list -c `compartmentOCID`
      • If you know the connection display name, you can use it to filter results:

        oci database-migration connection list -c `compartmentOCID` --display-name `connectionDisplayName`
  2. Get the Work Request OCID associated with the connection creation request.

    • Using Oracle Database Migration Service (database-migration) OCI Command line interface:

      The compartment OCID where the failed connection was created is required. You can find it using database-migration >> work-request >> list as shown in the following example.

      • Use the connection OCID to list the work requests:

        oci database-migration work-request list --resource-id odms-connection-OCID --compartment-id odms-connection-compartment-OCID
      • Use the compartment OCID to list the work requests of the compartment:

        oci database-migration work-request list --compartment-id odms-connection-compartment-OCID
      • Use the sort-by option to sort the results by displayName or timeCreated:

        oci database-migration work-request list --compartment-id odms-connection-compartment-OCID --sort-by displayName
      • Use the sort-order option with asc or desc:

        oci database-migration work-request list --compartment-id odms-connection-compartment-OCID --sort-oder ASC

        Only one sort order can be specified. Default order for --sort-by timeCreated is descending.

    • Using the Database Migration REST API:

      • Use the connection OCID to list the work requests:

        See ListWorkRequests

        GET /20210929/workRequests?resourceId=odms-connection-OCID&compartmentId=odms-connection-compartment-OCID
      • Use the compartment OCID to list the work requests of the compartment:

        GET /20210929/workRequests?compartmentId=compartment-OCID-of-resource
      • Use the sort-by option to sort the results by displayName or timeCreated:

        GET /20210929/workRequests?compartmentId=compartment-OCID-of-resource&sortBy=displayName
      • Use the sort-orderoption with asc or desc:

        GET /20210929/workRequests?compartmentId=compartment-OCID-of-resource&sortOrder=ASC

        Only one sort order can be specified. Default order for --sort-by timeCreated is descending.

  3. Use the work request OCID to get details, logs, and errors related to the failure:

    • Using Oracle Database Migration Service (database-migration) OCI Command line interface:

    • Using the Database Migration REST API:

      • Use the work request identifier to get the details:

        GET /20210929/workRequests/{workRequestId}

        See GetWorkRequest

      • Use the work request identifier to get the errors:

        GET /20210929/workRequests/{workRequestId}/errors

        See ListWorkRequestErrors

      • Use the work request identifier to get the logs:

        GET /20210929/workRequests/{workRequestId}/logs

        See ListWorkRequestLogs

  4. Inspect the logs and errors in the work request and resolve the issues reported.

For more information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.