You are about to plug a multi-terabyte non-CDB into an existing multitenant container database
(CDB).
The characteristics of the non-CDB are as follows:
Version: Oracle Database 11g Release 2 (11.2.0.2.0) 64-bit
Character set: AL32UTF8
National character set: AL16UTF16
O/S: Oracle Linux 6 64-bit
The characteristics of the CDB are as follows:
Version: Oracle Database 12c Release 1 64-bit
Character Set: AL32UTF8
National character set: AL16UTF16
O/S: Oracle Linux 6 64-bit
Which technique should you use to minimize down time while plugging this non-CDB into the
CDB?
A.
Transportable database
B.
Transportable tablespace
C.
Data Pump full export/import
D.
The DBMS_PDB package
E.
RMAN
Explanation:
* Overview, example:
– Log into ncdb12c as sys
– Get the database in a consistent state by shutting it down cleanly.
– Open the database in read only mode
– Run DBMS_PDB.DESCRIBE to create an XML file describing the database.
– Shut down ncdb12c
– Connect to target CDB (CDB2)
– Check whether non-cdb (NCDB12c) can be plugged into CDB(CDB2)
– Plug-in Non-CDB (NCDB12c) as PDB(NCDB12c) into target CDB(CDB2).
– Access the PDB and run the noncdb_to_pdb.sql script.
– Open the new PDB in read/write mode.
* You can easily plug an Oracle Database 12c non-CDB into a CDB. Just create a PDB manifest
file for the non-CDB, and then use the manifest file to create a cloned PDB in the CDB.
* Note that to plugin a non-CDB database into a CDB, the non-CDB database needs to be of
version 12c as well. So existing 11g databases will need to be upgraded to 12c before they can be
part of a 12c CDB.
Correct Answer is A, because to use DBMS_PDB both the database should be in 12c version
Then D is correct because all section A questions are based on 12C New features.
correct answer for this question is B.
http://www.oracle.com/technetwork/database/upgrade/upgrading-oracle-database-wp-12c-1896123.pdf
Not D. DBMS_PDB package does not work on 11g database
I think the question itself is wrong. Looking at explanation, if the non-cdb database is 12c, then D would be correct.
D is correct because all questions in section A in the exam are 12C New features
B
As per upgrade document B is faster option. D is possible when source DB is 12C.
D is correct because all questions in section A in the exam are 12C New features.
I have written my exam and am back here to make my comments.
85 questions are asked in the exam (51 for Oracle New Features and 34 for DBA Skill set)
Hi SisBee, Can you please confirm that these set of questions are sufficient to clear the exam. I am planning it next week. Regards.
B
B.
If the non-CDB is version 11.2.0.3 onward, you can consider using Transport Database, as described here. If the non-CDB is pre-11.2.0.3, then you can still consider using transportable tablespaces.
http://www.oracle-base.com/articles/12c/multitenant-migrate-non-cdb-to-pdb-12cr1.php
What about C? In this case you don’t need to do database upgrade.
What is faster – impdp or upgrade + transportable tablespaces?
Notice that is it asking take 11g database and put as 12c’s pdb.
So C – can be done, but it is not aster
Transport tablespace: only have to export metadata from non system tablespaces, then needs to move the TS datafile to target before plugging.
In a multi-TB database it might be faster to use Transportable Tablespaces depending on your OS and if the CDB is on another network etc. Or it might be faster to use expdp with parallel=48 again depending on your server resources.
I wish there was an answer E. It depends
B
B
export/import takes long time. Rule out C.
DBMS_PDB package can be used to plug a 12c non-CDB into an exisiting CDB. Running
the DBMS_PDB.DESCRIBE procedure on the non-CDB generates an XML file that describes
the future PDB. You can plug in the unplugged PDB in the same way that you can plug in any
unplugged PDB, using the XML file and the non-CDB data files. Therefore choice D is ruled out.
The option of an upgrade via a transport database is possible for 11.2.0.3 or later. Here the version is 11.2.0.2. If the non-CDB is version 11.2.0.3 onward, you can consider using Transport Database. If the non-CDB is pre-11.2.0.3, then you can still consider using transportable tablespaces. Hence choice A is ruled out.
There are three possible methods to plug a non-CDB database into a CDB.
Whichever method is used, you have to get the non-CDB into a transactionally-consistent state
and open it in restricted mode.
• Either use transportable tablespace (TTS) or full conventional export / import or
transportable database (TDB) provided that in the last one any user-defined object
resides in a single user-defined tablespace.
• Or use DBMS_PDBpackage to construct an XML file describing the non-CDB data files to
plug the non-CDB into the CDB as a PDB. This method presupposes that the non-CDB is
an Oracle 12cdatabase.
• Or use replication with GoldenGate.
We have already ruled out A, C, D. RMAN is not an option to plug a non-CDB into a CDB.
We can use exp/imp but it takes too long. Hence the correct answer is: B (transportable Tablespace)
B
Consider the database is too big. I will upgrade to 12c then plug into CDB database
I have written my exam and am back here to make my comments.
85 questions are asked in the exam (51 for Oracle New Features and 34 for DBA Skill set)
And what is the answer to this question?
SisBee – if you got 100% on the exam and this question was on your exam, then I’ll go with you. Otherwise I am confused between “B” and “D”.
For “D” to work: to plugin a non-CDB database into a CDB, the non-CDB database needs to be of version 12c as well. So existing 11g databases will need to be upgraded to 12c before they can be part of a 12c CDB.
B