Examine the command for creating pluggable database PDB2 in container database CDB2.
Select three options, any one of which is required for it to execute successfully. (Choose three.)
Examine the command for creating pluggable database PDB2 in container database CDB2.
Select three options, any one of which is required for it to execute successfully. (Choose three.)
To execute the command for creating the pluggable database PDB2 in the container database CDB2 successfully, you can take the following actions: Add only the CREATE_FILE_DEST clause to the statement (B), set only the PDB_FILE_NAME_CONVERT parameter (C), or enable only Oracle Managed Files (OMF) (E). Adding the CREATE_FILE_DEST clause specifies a directory for the Oracle Managed Files, setting the PDB_FILE_NAME_CONVERT parameter automatically generates new file names, and enabling OMF ensures the database automatically manages the file locations. These options provide flexibility in file management during the PDB creation process.
All are valid, but i think BCE is correct because you don't require the file_name_convert in option "A" just pdb_file_name_convert, don't need pdb_file_name_convert in "D" just omf, also don't require file_name_convert in option "F" just omf. Any comment?
BCE https://docs.oracle.com/en/database/oracle/oracle-database/18/multi/overview-of-pdb-creation.html#GUID-39D2F826-7460-4439-B410-29E16C0CA0B1 not A PDB_FILE_NAME_CONVERT maps names of existing files to new file names when processing a CREATE PLUGGABLE DATABASE statement, as well as when processing the ENABLE PLUGGABLE DATABASE clause of the CREATE DATABASE statement, if the file_name_convert_clause is not specified and Oracle Managed Files is not enabled. B Enough to create OMF files C Looks good too not D Coz of using OMF not requires PDB_FILE_NAME_CONVERT E DB_CREATE_FILE_DEST? Thats enough to create PDB not F Coz of using OMF not requires FILE_NAME_CONVERT
BCE is correct
BCE sounds right.
Agree with BCE Reference: https://docs.oracle.com/database/121/SQLRF/statements_6010.htm#SQLRF55686 You can specify FILE_NAME_CONVERT = NONE, which is the same as omitting this clause. If you omit this clause, then the database first attempts to use Oracle Managed Files to generate file names. If you are not using Oracle Managed Files, then the database uses the PDB_FILE_NAME_CONVERT initialization parameter to generate file names. If this parameter is not set, then an error occurs.
Correct = ACE B = CREATE~ must enable OMF D,F = OMFdon't enable
B is correct: This CREATE_FILE_DEST lets you override the default behaviour. You can enable or disable Oracle Managed Files for the PDB and you specify a different base file system directory or Oracle ASM disk group for the PDB's files. If you specify a value other than NONE, then the database implicitly sets the DB_CREATE_FILE_DEST initialization parameter with SCOPE=SPFILE in the PDB. (https://docs.oracle.com/database/121/SQLRF/statements_6010.htm#CACFDEHC)
source: http://dbaparadise.com/2021/03/file_name_convert-vs-pdb_file_name_convert/
BCE Correct https://oracle-base.com/articles/12c/multitenant-create-and-configure-pluggable-database-12cr1
BCE For https://smarttechways.com/2019/03/05/ora-65016-file_name_convert-must-be-specified/ B C E are true F is false For https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/PDB_FILE_NAME_CONVERT.html#GUID-074F8896-D565-4139-BCDB-C81C9D741941): A D are false
see mihanik explanation
BCE is correct
I think only E is right: Version 19.6.0.0.0 SQL> show parameter CREATE_FILE NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ db_create_file_dest string +DATA SQL> show parameter file_name_convert NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ db_file_name_convert string log_file_name_convert string pdb_file_name_convert string SQL> SQL> create pluggable database pdb3 admin user pdb3_adm identified by welcome1 roles=(connect); Pluggable database created. SQL> SQL> show pdbs CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY YES 3 PDB1 READ WRITE YES 4 PDB2 READ WRITE YES 5 PDB3 MOUNTED SQL>