In this part of the Hands-On Lab you will migrate the FTEX database directly into a PDB2 using Full Transportable Export/Import, an extension of Transportable Tablespaces where Data Pump takes over the manual work you’ve had to with plain TTS. It works cross-platform and cross-Endianness with at least an Oracle 188.8.131.52 source database.
In the case of the lab, you will move an Oracle 184.108.40.206 database, FTEX, directly into an 18c PDB2 which is part of CDB2.
It is important to mention that this feature works cross-platform and cross-Endianness!
- 1. Create a new PDB2
- 2. Prepare FTEX
- 3. Migrate FTEX into PDB2
- 4. Migration to Oracle Cloud or Cloud Machine
At first, as with every other Transportable Tablespace migration, we need to create a database – or in our case, a PDB – first.
Login to CDB2 and create a new PDB:
The admin user needs to exist when a PDB gets created. You can delete it later on if necessary.
Once the PDB2 is created you need to start it up and create some additional objects for the migration:
We will use the database link to allow Data Pump pulling all information via the database link. The task can be done without the database link but then two operations are necessary, an
expdp and an
Before we can transport anything, we need to prepare the FTEX database.
First of all, you need to start it up. Then you will switch the one tablespace we’ll migrate to Read-Only:
At first of course you need to transfer the file as well to the new environment:
Then you need to initiate the transport operation. In this case Data Pump will take over the usual manual steps from Transportable Tablespaces. The keywords
TRANSPORTABLE=ALWAYS and FULL=Y advice Data Pump to use the Full Transportable Export/Import feature.
VERSION=12 is needed as we use an 11g database as source.
Once the operation is completed (it takes between 2 and 3 minutes) you can shutdown
You’ll find some error messages. This particular one can be safely ignored as the object belongs to Advanced Replication:
W-1 Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/POST_SYSTEM_ACTIONS/PROCACT_SYSTEM ORA-39083: Object type PROCACT_SYSTEM failed to create with error: ORA-04042: procedure, function, package, or package body does not exist Failing sql is: BEGIN SYS.DBMS_UTILITY.EXEC_DDL_STATEMENT('GRANT EXECUTE ON DBMS_DEFER_SYS TO "DBA"');COMMIT; END; W-1 Completed 4 PROCACT_SYSTEM objects in 25 seconds
ONLY in case copy/paste does not work correctly, there’s a prepared file with all the parameters in /home/oracle/IMP. Use “
impdp parfile=/home/oracle/IMP/ft.par” instead.
You can now connect to it with:
This feature can be used of course to migrate to the Oracle Cloud or an ExaCC or OCC machine. See a real-time video here:
How to migrate an entire database with Full Transportable Export/import to the Oracle DBCS Cloud