How to Export a Full Pluggable Database

Overview of Exporting Oracle PDB

Learn to migrate an Oracle Database 12c PDB to a DBaaS PDB using the Oracle Data Pump export and import method. This guide provides instructions for a full export and import process, taking approximately 45 minutes to complete.

Prerequisites

Before beginning the export process, ensure completion of preliminary tutorials including "Signing Up for a Database Cloud Service," "Connecting to a Database Cloud Service (DBaaS) Instance Through an SSH Tunnel," and "Creating a Database Cloud Service (DBaaS) Instance."

Preparing the Environment

Create a data pump directory object in the on-premises PDB and a new PDB within the DBaaS ORCL CDB. Set user-defined tablespaces to read-only to prepare for export.

Exporting with Data Pump

Utilize the 'expdp' command for exporting your pluggable database (PDB). The tutorial covers conventional, transportable tablespace, and full transportable network modes to accommodate your export needs.

Importing the PDB

Following the export, import the PDB into the DBaaS environment using the transportable tablespace, network, or full transportable modes as detailed in the tutorial.

Verification and Cleanup

Post-import, verify the integrity of the PDB migration and set tablespaces back to read-write mode to finalize the process.

Frequently Asked Questions

How do I prepare to export a full pluggable database in a DBCS environment?

SSH to one of the nodes in the DBCS system, list the contents to verify the environment, create an alias for the dump file path, grant a user write permissions to this path, and ensure the user has full rights to export the database.

What is the correct command to export all container databases and pluggable databases?

Use the expdp command with the include=full clause in the format: expdp username/password@root_sid directory=dir_name dumpfile=export.dmp logfile=export.log full=y include=full.

Why does using the expdp command only export the root container by default?

By default, the expdp command without the include=full clause is configured to only export the root container database.

What should I do after running the export command for a full pluggable database?

Record the dump file size to ensure there is enough space on the Oracle Cloud Infrastructure Database System for the dump file.

Common Use Cases

• 
  Migrating a complete pluggable database to a new Oracle Database environment
• 
  Backing up an entire pluggable database for disaster recovery purposes
• 
  Cloning a pluggable database to create a test or development environment
• 
  Decommissioning an old system by exporting its pluggable database to a newer architecture
• 
  Consolidating multiple pluggable databases into a single new multitenant container database

Sourcetable: The Smart Alternative to Full Database Exports

Traditional methods of exporting databases can be cumbersome and time-consuming. Sourcetable emerges as a cutting-edge alternative, enabling seamless data integration from multiple sources directly into a user-friendly spreadsheet interface. This innovative solution simplifies the process of data manipulation and analysis, offering real-time access and eliminating the need for full pluggable database exports.

With Sourcetable, users can effortlessly query and manipulate their data without the complexities of database management. Its intuitive spreadsheet-like environment is designed for efficiency, allowing for real-time data retrieval and editing. This eliminates the need for intricate export procedures, making Sourcetable a go-to choice for data handling.

Opt for Sourcetable to streamline your data processes, enhance productivity, and make informed decisions without the overhead of traditional database exports. Experience the power of immediate data access and manipulation with Sourcetable's advanced spreadsheet capabilities.