Troubleshooting Data Import

Troubleshoot the issues you find while importing data into the DB system.

Resolving Import Error: Failed opening object

You get the import error when the PAR URL, which is defined in the manifest file, expires. You cannot access the data until you redo the MySQL Shell dump to Object Storage, which regenerates the PAR URLs in the manifest file.

Using MySQL Shell

Use MySQL Shell to resolve the Import Error: Failed opening object error.

This task assumes the following:

You get an Import Error: Failed opening object error similar to the following:
```
Import Error: Failed opening object
'<ObjectStoragePath>/b/<BucketName>/o/<BucketPrefix>/@.json'
in READ mode: Not Found (404)
```

Do the following to generate new PAR URLs:

Regenerate the manifest file by running the MySQL Shell dump to Object Storage again. See MySQL Shell Dump Utility.

Note

Importing using a manifest file (@.manifest.json) is a deprecated functionality. Import from a bucket or bucket prefix PAR instead.
(Optional) If you require a longer PAR expiration period, change the value of the MySQL Shell dump parameter, ociParExpireTime. The default expiry of the MYSQL Shell-generated PAR URLs is current time plus one week. See MySQL Shell Dump Utility.

Resolving Import Error: May not be a valid URL

You get the import error because of an incorrect format in the PAR URL.

Any of the following can be a reason for the import error:

The PAR URL has expired. PARs have an expiry built in. If you have crossed the expiry date, create a new PAR URL.
You defined a filename-type prefix instead of a folder-type prefix. Filename-type prefixes are not supported.
You defined a folder-type prefix but did not add the prefix name and trailing forward slash to the PAR URL. If you are importing from a bucket prefix, add the prefix name and forward slash to the URL manually.
You specified a malformed or incorrect URL. Check your URL and confirm it is accurate. If necessary, generate a new one.

Using the Console

Use the Console to resolve the Import Error: May not be a valid URL error.

This task assumes the following:

You get an

Import Error: May not be a valid
                                    URL

error similar to the following:

attribute = {source.sourceUrl}, value =
      {https://objectstorageURL/p/alphanumericString/n/tenancyName/b/bucketName/o/prefixName/}
      - may not be a valid url

Generate a new PAR URL using the PAR generation wizard in the Console. See Using pre-authenticated requests.

Note

It is recommeded to use the Console to generate a new PAR URL.

Using the CLI

Use the command-line interface to resolve the Import Error: May not be a valid URL error.

This task assumes the following:

You get an Import Error: May not be a valid URL error similar to the following:

attribute = {source.sourceUrl}, value =
      {https://objectstorageURL/p/alphanumericString/n/tenancyName/b/bucketName/o/prefixName/}
      - may not be a valid url

Generate a new PAR URL manually using the command-line interface . See Using pre-authenticated requests.

Oracle Cloud Infrastructure Documentation Try Free Tier