Known issues

Refer to the Known Issues for OCI Database Migration.

Known issue: If you have a source database as Standard Edition Oracle Database and if you are not using DB link as the transfer medium, then the export fails with the following error:

PRGZ-1464 : PRGZ-1464 : Oracle Data Pump dump encryption feature is not available for Oracle Standard Edition Database

Known issue:

Currently, editions for editionable objects are not migrated, the export is done according to the current object edition that you have in the source database.

Editionable views are not currently migrated and you need to manually create them in the target database.

Known issue

Issue: PRGZ-3808 | The specified directory path {0} in the parameter "DATAPUMPSETTINGS.EXPORTDIRECTORYOBJECT.PATH" does not match with the path {0 } that the database directory object {0 } points to.

Solution: You can either update the directory object on the database to match the directory object path that you provide in the migration. Alternatively, you can update the migration with the correct directory object path and the directory object name. Analyze the following query:

SELECT directory_name, directory_path
FROM dba_directories
WHERE directory_name = '<DIRECTORY_OBJECT_NAME>';

Known issue

Issue: While creating a migration from an Autonomous database to an Autonomous database, evaluation job fails whenever the ADMIN user is configured for initial load and has an insufficient privileges error.

Solution: As a workaround, when performing an online migration, you must set the value of the GOLDENGATESETTINGS_SKIPRELOADQUERYADVISOR advanced parameter in the migration configuration to true.

Ensure to add the following permissions:

GRANT SELECT ON SYS.V_$SESSION TO ggadmin;
GRANT SELECT ON SYS.V_$TRANSACTION TO ggadmin;
GRANT SELECT ON SYS.V_$DATABASE TO ggadmin;
ALTER SYSTEM SET GLOBAL_NAMES=FALSE;
ALTER PLUGGABLE DATABASE ADD SUPPLEMENTAL LOG DATA;
GRANT PDB_DBA to ggadmin;

• Migration Method 1: Using a Network File System (NFS):

  This method uses a shared OCI File Storage (NFS) file system to transfer the Data Pump files. The service performs the mounting and unmounting of this file system directly on the ADB instances.

  1. Before you begin, you must unmount the specific file system that you select for the migration.

  2. Unmount File System: On both the source and target ADB instances, ensure the OCI File Storage (NFS) you plan to use for the migration is unmounted.

  3. Clean Source Directory: On the source ADB instance, you must clean up ALL files within the DATA_PUMP_DIR directory. ZDM automatically uses this directory path to mount the NFS share, and the mount operation will fail if the directory is not empty.

  4. Prepare Target Directory: On the target ADB instance, you can either specify an existing empty directory or let ZDM create one. Oracle recommends to let ZDM create the directory, as it will automatically handle mounting the file system for you.

  5. After completing the prerequisites, run the migration job. ZDM manages the attachment of the NFS file system for the data transfer.

• Migration Method 2: Using a Database Link (DBLINK)

  1. Create Database Links: You must create a database link on both the source and target ADB shared instances. Important: The database links on the source and target must have the exact same name. For detailed instructions, see Create Database Links from Autonomous AI Database to Another Autonomous AI Database.

  2. When defining the migration job using the API or SDK, you must specify the name of the database link in the migration transfer medium parameters.

  3. After completing the prerequisites, you can run the migration job.

Known issue

Issue: The online migrations fail when using IPv4+IPv6 subnet. PE (Private Endpoint) and RCE (Remote Code Execution) do not yet support IPv6.

Solution: Currently, when you attempt an online migration and the connections are assigned to a subnet that contains IPv6 CIDR blocks, the migration fails because it would not be able to create the GGS Connection. This is because both PE and RCE do not yet support IPv6. PE has only rolled out IPv6 support to a few regions and the tenancies are yet to be enabled.

Related Topics

• Known Issues for Oracle Cloud Infrastructure Database Migration Service