You plan to perform cross-platform PDB transport using XTTS.
Which two are true? (Choose two.)
You plan to perform cross-platform PDB transport using XTTS.
Which two are true? (Choose two.)
For performing cross-platform PDB (Pluggable Database) transport using XTTS (Cross Transportable Tablespace Set), it is necessary for the source PDB to be in MOUNT state to ensure consistency and integrity during the transport process. Additionally, the source and target platforms must have the same endianness, as only then can the transport be done without the need for complex conversion processes. This ensures that the transported data remains consistent and usable on the target platform.
B and E are correct answers . to platform or for transport any of the command can be used and the source DB needs to be in mounted mode. https://blog.enmotech.com/2018/01/10/oracle-12cr2-cross-platform-pdb-transport-using-xtts/
BE correct
i agree with BE, RMAN Cross-Platform Transportable PDB This method can be used only if the on-premises platform is little endian, and the database character sets of your on-premises database and the Database service database are compatible.
D, E I will stick with one technique: Cross-Platform PDB Transport with Backup Sets – Same endian format, database mounted or opened. If we consider Cross-Platform Transport of Tablespaces in a PDB – we can have different endian formats, but the database has to be opened not mounted (not B, not D). BACKUP TO PLATFORM / BACKUP FOR TRANSPORT - both eligible for PDB or tablespace transport (Not A in every technique).
28.12.1 About Cross-Platform Transport of PDBs To transport an entire PDB to a different platform, the source platform and destination platform must use the same endian format. The PDBs must be read-only mode before the cross-platform backup is created. DE
D, E For D >> Read-Only Tablespace = Database open state https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/rman-transporting-data-across-platforms.html#GUID-7E1B3B10-CDA2-4E79-9F4C-AC8E51BCDE54
SQL> startup mount; SQL> ALTER DATABASE OPEN READ ONLY;
I change my mind to CD
I think DE. https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/rman-transporting-data-across-platforms.html#GUID-7523B82F-0DF6-4E1F-8FE6-DFDC049BA002
From this documentation I think Answer is A & B. https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/rman-transporting-data-across-platforms.html#GUID-A41CEF69-4D73-45F4-BDF8-DCCAEB20C08F Perform the following steps on the source CDB: Connect to the root as a common user with the SYSDBA or SYSBACKUP privilege. Close the PDB that needs to be transported. The following statement closes the PDB hr_pdb. Copy RMAN> ALTER PLUGGABLE DATABASE hr_pdb CLOSE IMMEDIATE; Create a cross-platform full backup of the PDB that must be transported by using the BACKUP PLUGGABLE DATABASE command. To create a cross-platform backup, include either the FOR TRANSPORT or TO PLATFORM clause. The following example creates a cross-platform backup of the PDB hr_pdb for the Linux x86 64-bit platform. The metadata required to plug this PDB into the destination CDB is specified using the UNPLUG INTO clause and stored in the XML file metadata_hrpdb.xml.
Use the FOR TRANSPORT or TO PLATFORM clause in the BACKUP command to create cross-platform backups. A - wrong
Be aware that you can also backup the PDB in (OPEN) READ ONLY mode according to 12.2 doc section 28.12.1 (About Cross-Platform Transport of PDBs).
AB, if you follow this tutorial. https://easyreliabledba.blogspot.com/2021/03/oracle-12cr2-cross-platform-pdb.html
Use one of the following techniques to transport PDBs across platforms: Connect to the root and use the BACKUP FOR TRANSPORT ... PLUGGABLE DATABASE or BACKUP TO PLATFORM ... PLUGGABLE DATABASE command to create a cross-platform backup of one or more PDBs. When you are connected to the root, the following command creates a cross-platform backup of the PDBs hr_pdb and sales_pdb. The PDBs must be read-only mode before the cross-platform backup is created. Copy BACKUP FOR TRANSPORT PLUGGABLE DATABASE hr_pdb, sales_pdb FORMAT '/tmp/backups/pdb_%U'; Connect to the PDB and use the BACKUP FOR TRANSPORT or BACKUP TO PLATFORM commands to create backup sets that can be used to transport the PDB data to another platform. Note:Performing cross-platform data transport of one or more PDBs by using the CONVERT command is not supported.
E is wrong When using Cross Platform Transportable Tablespaces (XTTS) to migrate database between systems that have different endian formats https://easyreliabledba.blogspot.com/2021/03/oracle-12cr2-cross-platform-pdb.html#google_vignette
B and E are correct answers based on https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/rman-transporting-data-across-platforms.html#GUID-27F404E2-4D45-4C99-B111-CD618F740C2B. The two alternatives are the most corrects, but alternative A also seems correct to me, can anyone tell me what is wrong with this item?
i think not A because you can also opt to use the FOR TRANSPORT clause with the BACKUP command to indicate that the backupset can be transported to any destination.
answer BE
B is confirmed with this https://docs.oracle.com/en-us/iaas/Content/Database/Tasks/mig-rman-cross-plat-transp-pdb.htm E is correct if they do not have same endian the generated xml must be formated before or after being transported.
A: is wrong because you can use "as image" mode B: No, tablespace must be in read-only E: No, this requirement is for whole database transport not TTS(Trasportable tablespaces) F: Not automatic, you must convert or backup with TO PLATFORM clause
B, E is correct
AE correct?
XTTS is a perl scripts set. Tool uses configuration file when we can define source platform and destination platform and it can have different endian, so In my opinion B and F is correct
BE https://blog.enmotech.com/2018/01/10/oracle-12cr2-cross-platform-pdb-transport-using-xtts/ B Verify the prerequisites: The source PDB must be closed in MOUNTED mode and the COMPATIBLE parameter must be set to 12.2 or higher. E For performing cross-platform PDB transport, you may need the exact name of the destination platform to which you are transporting data and may need to verify that the destination platform is of the same endian format. SQL> SELECT PLATFORM_ID, PLATFORM_NAME, ENDIAN_FORMAT FROM V$TRANSPORTABLE_PLATFORM WHERE UPPER(PLATFORM_NAME) LIKE ‘%LINUX%’;
DE run { allocate channel ch1 type disk; BACKUP to platform 'Microsoft Windows x86 64-bit' pluggable database PDB1; }
run { allocate channel ch1 type disk; BACKUP FOR TRANSPORT PLUGGABLE DATABASE PDB2; }