You are required to migrate your 11.2.0.3 database as a pluggable database (PDB) to a
multitenant container database (CDB).
The following are the possible steps to accomplish this task:
1. Place all the user-defined tablespace in read-only mode on the source database.
2. Upgrade the source database to a 12c version.
3. Create a new PDB in the target container database.
4. Perform a full transportable export on the source database with the VERSION parameter set to
12 using the expdp utility.
5. Copy the associated data files and export the dump file to the desired location in the target
database.
6. Invoke the Data Pump import utility on the new PDB database as a user with the
DATAPUMP_IMP_FULL_DATABASE role and specify the full transportable import options.
7. Synchronize the PDB on the target container database by using the DBMS_PDS.SYNC_ODB
function.
Identify the correct order of the required steps.
A.
2, 1, 3, 4, 5, 6
B.
1, 3, 4, 5, 6, 7
C.
1, 4, 3, 5, 6, 7
D.
2, 1, 3, 4, 5, 6, 7
E.
1, 5, 6, 4, 3, 2
Explanation:
Step 0: (2) Upgrade the source database to 12c version.
Note:
Full Transportable Export/Import Support for Pluggable Databases
Full transportable export/import was designed with pluggable databases as a migration
destination.
You can use full transportable export/import to migrate from a non-CDB database into a PDB, from
one PDB to another PDB, or from a PDB to a non-CDB. Pluggable databases act exactly like
nonCDBs when importing and exporting both data and metadata.
The steps for migrating from a non-CDB into a pluggable database are as follows:
Step 1. (1) Set the user and application tablespaces in the source database to be READ ONLY
Step 2. (3) Create a new PDB in the destination CDB using the create pluggable database
command
Step 3. (5) Copy the tablespace data files to the destination
Step 4. (6) Using an account that has the DATAPUMP_IMP_FULL_DATABASE privilege, either
• (6) Export from the source database using expdp with the FULL=Y
TRANPSORTABLE=ALWAYS
options, and import into the target database using impdp, or
• Import over a database link from the source to the target using impdp
Step 5. Perform post-migration validation or testing according your normal practice
stupid question. Answer is A because there is no DBMS_PDS.SYNC_ODB thing. But step 2 (upgrade is NOT necessary with 11.2.0.3!)But there is no better answer.
You are right, I think that there are so many erros both of questions and answers in the whole test.
Did you do the exam yet?
I’m going to do it tomorrow…
•When migrating Oracle Database 11g release 2 (11.2.0.3 or later) to a CDB (or to a non-CDB) using either full database export or full transportable database export, you must set the Data Pump Export parameter VERSION=12 in order to generate a dump file that is ready for import into Oracle Database 12c. If you do not set VERSION=12, then the export file that is generated will not contain complete information about registered database options and components.
so many wrong answers consists this test paper, really dangerous who is followed this answer only, but discussion of this blog is really excellent and helpful.. people do so many testing to get the correct answer and prove that blog answer is rubbish, it’s a really nice way of knowledge sharing.
C is the correct answer
C is correct answer, while step 7 is meant by dbms_pdb.sync_pdb. Looks typo in dump.
Post plugging PDB into CDB, Verify the status, open mode, and service names of the PDBs in the CDB. If the status for a PDB shows NEEDS SYNC, you can connect to the PDB and run the DBMS_PDB.SYNC_PDB procedure to change the status to NORMAL.
C