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
A
The multiple choices are wrong. I can’t find DBMS_PDS.SYNC_ODB function.
The closest answer is either B or C
no way only A is true
in all Oracle I dont fund information abouth DBMS_PDS.SYNC_ODB
I can’t find either of DBMS_PDS nor DBMS_PDS.SYNC_ODB.
Then, we can eliminate B,C and D.
A is correct, please refers to this example,
It has to start with database upgrade to 12c using manual or DBUA methods. then use the example provided for oracle to makeit PDB.
http://www.oracle.com/technetwork/database/enterprise-edition/full-transportable-wp-12c-1973971.pdf
See example: Example: Using Full Transportable to Move a Non-CDB into a CDB
http://www.oracle.com/technetwork/database/enterprise-edition/full-transportable-wp-12c-1973971.pdf
A,D,E incorrect;
2. Upgrade the source database to a 12c version. – is wrong!
B,C – incorrect(see 7. Synchronize the PDB on the target container database by using the DBMS_PDS.SYNC_ODB
function.)
As it is 11.2.0.3 upgrade at source is not necessary. C appears to be more close. Option A also looks close if upgrade of source is required.
However the answer is quite confusing. Any more input?
There is probably typo DBMS_PDS.SYNC_ODB = DBMS_PDB.SYNC_PDB, unless that’s the catch.
Answer is C
SQL> exec dbms_pdb.sync_pdb();
PL/SQL procedure successfully completed.
C
From the link below:
http://www.oracle.com/technetwork/database/upgrade/upgrading-oracle-database-wp-12c-1896123.pdf
There is no reason why B is wrong.
I agree, C or B.
But most logical is C because with the B – you have to make readonly on source, then switch to target db to create PDB.
The answer should be A.
For 4), the export dump is performed with verion=12.
I do not think the operation is valid for B and C, as their oracle version is still 11.2.0.3
I have tested.
version=12 can be set in 11.2.0.3 during expdp.
Therefore, the answer should be B or C
Question is very ambiguous… both B and C should be correct as steps 3 & 4 are not dependent on each other. So they can be run in any order.
C B – OK but without 7 ;/
this is migration not upgrate !!!!
http://www.oracle.com/technetwork/database/upgrade/upgrading-oracle-database-wp-12c-1896123.pdf
Upgrading to Oracle Database 12c Examples of Using Full Transportable Export/Import
page 11
1 – Set user tablespaces in the source database to READ ONLY.
2 – From the Oracle Database 11gRelease 2 (11.2.0.3) environment, export the metadata and any data residing in administrative tablespaces
from the source database using the FULL=Y and TRANSPORTABLE=ALWAYS parameters.
3 – Copy the tablespace data files from the source system to the destination system.
4 – Create a CDB on the destination system, including a PDB into which you will import the source database.
5 – In the Oracle Database 12c environment, connect to the pre- created PDB and import the dump file.
In the given options, C is closest out of all!
C
There are two methods to migrate a non-CDB 11gdatabase to a 12cCDB.
The first method consists of two steps:
1. Upgrade the 11gdatabase to 12cnon-CDB.
2. Plug in the 12cnon-CDB into a CDB: Use DBMS_PDB.DESCRIBEprocedure to generate
the XML file to plug the data files into the CDB as a new PDB.
The second method consists of two steps:
1. Pre-create a PDB in the CDB from the seed PDB. This operation establishes a Oracle
Database 12cdictionary in the newly created PDB.
2. Use either export/import or replication to load the 11gdata into the newly created PDB of
the CDB.
There is no DBMS_PDS package. May be it is a typo. They may mean DBMS_PDB package. This package has only the following 3 sub programs: (i) DESCRIBE procedure, (ii) RECOVER procedure, and (iii) CHECK_PLUG_COMPATIBILITY function. This package does not have any sub program called “SYNC_PDB”. Hence all the choices with 7 can be rule out.
Then E is completely out of sequence. Therefore the correct answer is:
A
Correct answer should be B or C.
As per the following example I would select B.
https://oracle-base.com/articles/12c/upgrading-to-12c#transport-database
DB upgrade is NOT required for 11.2.0.3 when performing a full transportable export on the source database with the VERSION parameter set to 12 using the expdp utility.
Since B/C are same, then only A make sense.
We have to assume 7 is a catch (spell DBMS_PDB.SYNC_PDB() in wrong way on purpose).
Otherwise, A/B/C/D will be OK.
C
From Oracle
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.
A for sure,
http://docs.oracle.com/database/121/ADMIN/cdb_plug.htm#ADMIN13597
Creating a PDB by cloning a non-CDB
Starting with Oracle Database 12c Release 1 (12.1.0.2), you can create a PDB by cloning a non-CDB. This method is the simplest way to create a PDB using a non-CDB, but it requires copying the files of the non-CDB to a new location.
See “Creating a PDB by Cloning an Existing PDB or Non-CDB” for instructions.
Both the CDB and the non-CDB must be running Oracle Database 12c Release 1 (12.1.0.2) or later. If your current non-CDB uses an Oracle Database release before Oracle Database 12c Release 1 (12.1.0.2), then you must upgrade the non-CDB to Oracle Database 12c Release 1 (12.1.0.2) to use this technique. See Oracle Database Upgrade Guide for information about upgrading.
I don’t agree if A is correct. Question says, migrate 11g database as PDB for CDB. That means logically saying to take 11g and plug in as PBD to existing CDB.
Even if you assume inlace upgrade – it becomes non-CDB database. Isn’t it?
Regd 7 – it must be dbms_pdb.sync_pdb. This synchronizes the new pub with CDB
In 12C, u cannot perform an upgrade and migrate of database at the same time. Questions says “migrate” so options A,D,E are eliminated since it has upgrade(step 2).
We are left with answer B or C.
But i will take C.
C
C
A is correct. ( 2, 1, 3, 4, 5, 6 )
This sequence could be ( 2, 1, 4,5,3,6 )
pdb creation step could come after export and copy process.
last step import.
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
But B is correct too, it’s just that C has more appropriate order
B and C