What is the limitation when migrating a pluggable database to Autonomous Database?

The correct answer highlights a significant limitation in the migration process of a pluggable database (PDB) to Oracle Autonomous Database. Specifically, while migrating a PDB to Autonomous Database, the typical methods such as plugging, unplugging, or cloning are not supported. This is an essential consideration because users looking to migrate databases may be accustomed to these processes in traditional Oracle Database environments.

In the context of Autonomous Database, it is designed to simplify database management and offer features like automated scaling and patching. However, these design philosophies also mean that certain traditional database migration operations are restricted. Understanding this limitation helps in effectively planning the migration strategy for organizations looking to transition to Autonomous Database while considering the constraints in the process.

Moreover, the alternatives suggest other methods that either involve creating links, archiving PDBs for uploads, or using XML formats, which do not align with the actual practices allowed in Autonomous Database migrations. This further emphasizes the importance of recognizing the unique operational model of Oracle Autonomous Database compared to traditional setups.