You want to migrate your Oracle 11g database as a pluggable database (PDB) in 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
C
C
http://sandeepnandhadba.blogspot.pt/2014/05/migrating-from-11203-non-cdb-to-12c-pdb.html
Steps
1. Create a directory in source database to store the export dump files.
2. Set the user and application tablespace in the source database as READ ONLY
3. Export the source database using expdp with parameters version=12.0, transportable=always and full=y
4. Copy the dumpfile and datafiles for tablespaces containing user /application data.
5. Create a new PDB in the destination CDB using create pluggable database command.
6. Create a directory in the destination PDB pointing to the folder containing the dump file or create a directory for dump file and move the dump file there.
7. Create an entry in tnsnames.ora for the new PDB.
8. Import in to the target using impdp with parameters FULL=Y and TRANSPORT_DATAFILES parameters. Make sure, the account is having IMP_FULL_DATABASE.
9. Restore the tablespaces to READ-WRITE in source database.
Thans Vonpire!
Thanks Vonpire again. C
http://sandeepnandhadba.blogspot.pt/2014/05/migrating-from-11203-non-cdb-to-12c-pdb.html
1. Create a directory in source database to store the export dump files.
2. Set the user and application tablespace in the source database as READ ONLY
3. Export the source database using expdp with parameters version=12.0, transportable=always and full=y
4. Copy the dumpfile and datafiles for tablespaces containing user /application data.
5. Create a new PDB in the destination CDB using create pluggable database command.
6. Create a directory in the destination PDB pointing to the folder containing the dump file or create a directory for dump file and move the dump file there.
7. Create an entry in tnsnames.ora for the new PDB.
8. Import in to the target using impdp with parameters FULL=Y and TRANSPORT_DATAFILES parameters. Make sure, the account is having IMP_FULL_DATABASE.
9. Restore the tablespaces to READ-WRITE in source database.
I think C is wrong. Answer C and answer B are almost the same.
Answer C has the export first and creating a PDB in target database afterwards.
Answer B has creating a PDB in target database first and the export afterwards.
I believe that this order can be either one. I don’t see any dependencies between them. So why choose C instead of B ?
That being said, I will go with answer A
C
C
answer C have the last line with the option
7. Synchronize the PDB on the target container database by using the
DBMS_PDS.SYNC_ODB function.
but DBMS_PDS.SYNC_ODB does not even exists…. or i can not found any information about it..
B (and C too) were corrent without step 7.
C and B are correct (but with correct step 7 : DBMS_PDB.SYNC_PDB)
However, A is not correct, because if we upgrade the source DB to 12c (step 2), we don’t need any more to create a new PDB (step 3), just plug as non-CDB in to CDB.
C