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).
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/
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.
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.
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
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.
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
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
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%’;
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.
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
There is more recent and more complete link:
https://docs.oracle.com/en/database/oracle/oracle-database/18/bradv/rman-transporting-data-across-platforms.html#GUID-7523B82F-0DF6-4E1F-8FE6-DFDC049BA002
Correct D, E if you choose:
About Cross-Platform Transport of PDBs, same endian , open read only, syntax without unplug:
BACKUP FOR TRANSPORT
PLUGGABLE DATABASE hr_pdb, sales_pdb FORMAT '/tmp/backups/pdb_%U';
correct B, E if you choose:
Performing Cross-Platform Transport of a Closed PDB, same endian, closed pdb, syntax with unplug:
BACKUP TO PLATFORM= 'Linux x86 64-bit'
UNPLUG INTO '/u01/oradata/backups/metadata_hrpdb.xml'
PLUGGABLE DATABASE hr_pdb
FORMAT '/u01/oradata/backups/transport_hrpdb.bck';
I wrote rubbish in my previous comment, I'm sorry.
Finally I took a look at book from official training, I suppose the same used by exam author and I found:
B (source PDB must be in MOUNT state) is CORRECT:
RMAN> RUN
{
allocate channel ch1 type disk;
BACKUP to platform 'Microsoft Windows x86 64-bit'
unplug into '/u01/oracle/BACKUPS/pdb1_manifest.xml'
pluggable database PDB1 FORMAT '/u01/oracle/BACKUPS/%d_%T_%U.DB';
}
ORA-65025: Pluggable database PDB1 is not closed on all instances.
E (source and target must have the same endianess) is CORRECT- to cross-platform transport of WHOLE PDB using XTTS:
RMAN> RUN
{
allocate channel ch1 type disk;
BACKUP to platform 'AIX-Based Systems (64-bit)'
pluggable database PDB1 FORMAT '/u01/oracle/BACKUPS/%d_%T_%U.DB';
}
ORA-19940: cannot use cross-platform backups to convert whole database to different endianess
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
mporislav
Highly Voted 3 years, 1 month agoABAJ
Highly Voted 3 years, 1 month agosaserdi
3 years, 1 month agoantonica
3 months, 2 weeks agoantonica
Most Recent 3 months, 3 weeks agodancymonkey
6 months agodancymonkey
6 months agodancymonkey
5 months, 3 weeks agoflaviogcmelo
10 months, 1 week agomamadu
4 months, 1 week agojulmis
10 months, 3 weeks agokaka321
11 months, 4 weeks ago_gio_
1 year agoHeat418
1 year, 1 month agovkra
1 year, 4 months agoBakeriiuc
1 year, 8 months agoG_C
1 year, 9 months agoegore0496
2 years, 5 months agoegore0496
2 years, 5 months agoegore0496
2 years, 5 months agoBrianG
2 years, 10 months agoAlain_t73
1 year, 2 months agofreemun05
2 years, 3 months ago5rhribar
2 years, 11 months agomporislav
3 years agoObserverPL
3 years, 1 month ago