A container database called CDB1 is OMF-enabled.
PDB_FILE_NAME_CONVERT is not configured in CDB1.
PDB1 was unplugged from CDB1 earlier in the week.
Examine this command, which will be executed in CDB1:
CREATE PLUGGABLE DATABASE pdb1 -
USING `˜/u01/app/oracle/oradata/pdb1.xml'
SOURCE_FILE_NAME_CONVERT =
(`˜/u01/app/oracle/oradata/', `˜/u02/app/oracle/oradata/');
Which two are true? (Choose two.)
When you unplug a PDB, it remains in a mounted state and must be dropped before it can be replugged into the same CDB, hence making option E correct. The SOURCE_FILE_NAME_CONVERT clause is used to specify the new location for the data files, indicating that the current location specified in the XML file is not correct, validating option D.
The question gives the impression that the source files were held at /u01/app/oracle/oradata, but are now physically located at /u01/app/oracle/oradata. The xml description file is still at /u01/app/oracle/oradata/pdb1.xml So, for each: A: FALSE - SOURCE_FILE_NAME_CONVERT is only needed if the XML file does not accurately describe the current location of the pdb's files. B: FALSE - If pdb1 ran correctly before, it will run correctly now - assuming that no major upgrade of CDB1 has happened. C: FALSE - PDB_FILE_NAME_CONVERT is needed only when OMF is not used. The question tells us that OMF is enabled. D: TRUE - The use of the SOURCE_FILE_NAME_CONVERT parameter indicates that the DB files have been moved, so the xml file does not hold the correct locations E: TRUE - Unplugging a database will result in the PDB remaining in a MOUNT state. It is still part of the CDB and will still be backed up etc... After unplugging, a PDB needs to be dropped before a new PDB can be created with the same name. Therefore, DE are correct
The PDB must be dropped from the CDB before it can be plugged back into the same CDB. When the XML metadata file is specified, the XML file includes the full paths of the PDB files. When the .pdb archive file is specified, the XML metadata file contains the relative file names only. https://docs.oracle.com/en/database/oracle/oracle-database/21/multi/plugging-in-a-pdb.html#GUID-3132C4E5-8734-458B-8B0C-EFC77A45FFA3 I believe A, E are correct
DE correct
datafile path: /u01/app/oracle/oradata/ is in xml file. But now datafile path need to be /u02/app/oracle/oradata/
This SOURCE_FILE_NAME_CONVERT clause uses the files in the /disk2/oracle/pdb7 directory instead of the /disk1/oracle/pdb7 directory. In this case, the XML file describing a PDB specifies the /disk1/oracle/pdb7 directory, but the PDB should use the files in the /disk2/oracle/pdb7 directory. SOURCE_FILE_NAME_CONVERT = ('/disk1/oracle/pdb7/', '/disk2/oracle/pdb7/')
A and E … 100% correct
when you use SOURCE_FILE_NAME_CONVERT you convert file path written in .xml file. So you change /u01/.. to /u02/.. So xml doesn't contain the current location (D is correct) PDB1 must be dropped because is in mount state after unplug (E is correct)
OK, so three possible answers here and not two. A must be correct. The location of the data files used to be in '/u01/app/oracle/oradata/' when the PDB was unplugged, so if the SOURCE_FILE_ NAME_CONVERT clause is used we are telling the CDB that the data files are now located in '/u02/app/oracle/oradata/', i.e. "already in the correct location". B is wrong. You would only use DBMS_PDB.CHECK_PLUG_COMPATIBILITY when you use a different CDB. C is wrong. You only need to use PDB_FILE_NAME_CONVERT when not using OMF. D is correct. Hence the fact that the SOURCE_FILE_NAME_CONVERT was included. E is correct. When a PDB is unplugged from a CDB, then the STATUS column in CDB_PDBS of the unplugged PDB will be UNPLUGGED. A PDB must be dropped from a CDB before it can be plugged back into the same CDB.
AE correct
B,C looks correct
Correct answer: AE
Hi people I just did the test, the correct answers are D and E, when you try to create a pdb with an xml it gives you error if you don't delete the pdb that was unplug so E is correct and the command is executed correctly when you specify the new destination of the data files with the SOURCE_FILE_NAME_CONVERT parameter if you don't do this it is not able to find any data file you can check it if you run a cat on the xml file you will see how the old path is there, good luck!
D and E are corrects. A is false because the data files "position" is specified in the .xml file and we don't know the content. So D is true, because for sure the SOURCE_FILE_NAME_CONVERT will change the current path from u01 to u02.
I agree D,E
A is mean the new create command output but exactly the new PDB1 have not create success
WOW, not a single correct answer here )))))))))))))
do you have the correct answer?
AD is Correct. https://docs.oracle.com/en/database/oracle/oracle-database/19/multi/plugging-in-a-pdb.html#GUID-F23F5352-F456-48EE-AED7-71E3DEBAAED0
A. PDB1 data files already exist in the correct location. Correct: You use SOURCE_FILE_NAME_CONVERT to specify new correct location. B. DBMS_PDB.CHECK_PLUG_COMPATIBILITY must be run in CDB1 before executing the command. WRONG: PDB1 was unplugged from CDB1 earlier. No NEED C. PDB_FILE_NAME_CONVERT must be set before executing the command. WRONG: OMF is ENABLED.. Bust be if disabled D. /u01/app/oracle/oradata/pdb1.xml does not contain the current locations of data files for PDB1. CORRECT: We use SOURCE_FILE_NAME_CONVERT for correct path E. PDB1 must be dropped from CDB1. WRONG. PDB1 already was unplugged
Switch to DE.. A: WRONG.. "Correct Location " is note accurate... We are using CONVERT to specify new correct... E: Correct The PDB must be dropped from the CDB before it can be plugged back into the same CDB. https://docs.oracle.com/en/database/oracle/oracle-database/18/multi/removing-a-pdb.html#GUID-3D9AA767-F03C-46EB-AF8E-6808AF1C9D9F
It will be AE. PDB1 files exist even when you unplug it and it doesn't get dropped so it remained in MOUNT state post unplugging. See below: SQL> show pdbs CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 CRYPTO_PDB READ WRITE NO 4 PDB2 READ WRITE NO 5 APPCON1 READ WRITE NO SQL> alter pluggable database pdb2 close; SQL> ALTER PLUGGABLE DATABASE PDB2 UNPLUG INTO 'H:\oracle\Oracle19c\PDB2_info.xml' 2 ; Pluggable database altered. SQL> show pdbs CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 CRYPTO_PDB READ WRITE NO 4 PDB2 MOUNTED 5 APPCON1 READ WRITE NO Option A & E are correct.
It will be AE. PDB1 files exist even when you unplug it and it doesn't get dropped so it remained in MOUNT state post unplugging. See below: SQL> show pdbs CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 CRYPTO_PDB READ WRITE NO 4 PDB2 READ WRITE NO 5 APPCON1 READ WRITE NO SQL> alter pluggable database pdb2 close; SQL> ALTER PLUGGABLE DATABASE PDB2 UNPLUG INTO 'H:\oracle\Oracle19c\PDB2_info.xml' 2 ; Pluggable database altered. SQL> show pdbs CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 CRYPTO_PDB READ WRITE NO 4 PDB2 MOUNTED 5 APPCON1 READ WRITE NO Option A & E are correct.