Which three are true in Oracle 19c and later releases? (Choose three.)
Which three are true in Oracle 19c and later releases? (Choose three.)
In Oracle 19c and later releases, transportable tablespaces typically need to be placed in read-only mode during the operation, meaning they never remain in read/write mode throughout the process. It is possible for a transportable data pump import to leave a plugged-in tablespace in read-only mode using the KEEP_READ_ONLY clause. Additionally, the number of simultaneous data pump jobs can be limited at the pluggable database (PDB) level using the MAX_DATAPUMP_JOBS_PER_PDB parameter. Therefore, options A, B, and D are correct.
BCD "This method for transporting tablespaces requires that you place the tablespaces to be transported in read-only mode until you complete the transporting process. If this is undesirable, you can use the transportable tablespaces from backup feature" -> BC correct MAX_DATAPUMP_JOBS_PER_PDB determines the maximum number of concurrent Oracle Data Pump jobs per PDB. -> D correct https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/transporting-data.html#GUID-9304426D-9D40-4F0D-8661-F53B608A652F https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/MAX_DATAPUMP_JOBS_PER_PDB.html#GUID-E911645F-2CA4-447D-AFB7-EBD4753AA09F
C is wrong for me. The question is about import, it`s not about "backup feature". ABD
I think its ABD A: there are 2 metjods of transporting tablesapces. First, put source database live tablespace in read only mode and take metadata backup using Expdp. Second, backup based using Rman that doesn't require source database tablespace to put in read only mode. But during operation oracle create auxiliary instance restore & recover tablesapce from backup and take export of tablespace by puting them in read only mode. so tablesapces never remain in read write mode during transportable tablespace operations. B: TRANSPORTABLE = KEEP_READ_ONLY clause plugged0in tableapse can remain in read only mode. D: init parameter MAX_DATAPUMP_JOBS_PER_PDB limits simultaneous data pump job at pdb level
According to this: https://docs.oracle.com/en-us/iaas/Content/Database/Tasks/mig-data-pump-transp-tablespace.htm You MUST set thetablespaces to read-only to perfom these operations so A should be correct
BCD This is a new feature in 19c and latest https://docs.oracle.com/en/database/oracle/oracle-database/19/newft/new-features.html#GUID-8BAADCB7-F93A-48D0-BF24-369C4947C56B "You can now import tablespace files mounted on two different databases as long as the files are set as read-only." You can set read/only, so its not mandatory. D is also correct for MAX_DATAPUMP_JOBS_PER_PBD parameter
The problem with this explanation is "You can now *import* as long as set to read only" not "You can *set to read only* to import" so it does says that read only is mandatory, just the import itself is on you.
B,C,D - Look to RinD explanation.
BCD. F is tricky because with OMIT_ENCRYPTION_CLAUSE you can omit encryption clauses on exported columns but export datapump contains this clauses
BCD - see RinD
BCD is correct KEEP_READ_ONLY MAX_DATAPUMP_JOBS_PER_PDB
A, B, F
changed to BCD