Which three are true about transporting databases across platforms using Recovery Manager (RMAN) image copies? (Choose three.)
Which three are true about transporting databases across platforms using Recovery Manager (RMAN) image copies? (Choose three.)
Using RMAN to transport databases across platforms involves several key aspects. Firstly, by default, the transported database will use Oracle Managed Files (OMF). Secondly, data files can be converted on the destination system using the RMAN CONVERT command before import. Thirdly, data files can also be converted on the source system before transfer to the destination platform. These steps ensure the database can be successfully transported and managed across different platforms. However, it's crucial to remember that the source and destination systems must have the same endian format for the transport to be possible, which negates options related to scenarios involving different endian formats.
A, B , C as per https://docs.oracle.com/en/database/oracle/oracle-database/18/multi/plugging-in-a-pdb.html#GUID-1691A7A2-372E-4E51-8A4F-15DAC6AB0FC3
Yes, I think this is the correct answer. https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/rman-transporting-data-across-platforms.html#GUID-65AADCB6-CC9A-4229-9AB8-805C37E4471F ABC E is wrong: You can also use RMAN to transport an entire database to a different platform so long as the two platforms have the same endian format.
E seems incorrect. Transport database needs same endian format. https://docs.oracle.com/en/database/oracle/oracle-database/18/bradv/rman-transporting-data-across-platforms.html#GUID-65AADCB6-CC9A-4229-9AB8-805C37E4471F You can use RMAN to transport tablespaces across platforms with different endian formats. You can also use RMAN to transport an entire database to a different platform so long as the two platforms have the same endian format.
B, is not possible, You can perform tablespace conversion with the RMAN CONVERT TABLESPACE command on the source host, but not on the destination host. https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/rman-transporting-data-across-platforms.html#GUID-5515B50B-2FCF-4C94-BEA3-16070E4E2334
BCE BC When you use the RMAN CONVERT command to convert data, you can either convert the data on the source platform after running Data Pump export, or you can convert the data on the target platform before running Data Pump import. In either case, you must transfer the data files from the source system to the target system. E - Converting Data Files on the Target System Before Import... The endianness of the source platform is different from the endianness of the target platform. https://docs.oracle.com/en/database/oracle/oracle-database/19/spmds/converting-data-using-rman.html#GUID-DDFA71A3-396A-440A-B9AB-E0970F843904:~:text=When%20you%20use,the%20target%20system.
https://docs.oracle.com/en/database/oracle/oracle-database/18/bradv/rman-transporting-data-across-platforms.html#GUID-D4C86E36-8EF8-489D-84CE-B8F045C8AB20 Par 28.2.2 "... 28.2.2 Overview of Database Conversion Using Image Copies To convert a whole database to a different platform, both platforms must use the same endian format..."
E: False. Note 2013540.1 (My Oracle Support): "When you transport entire database the source platform and the destination platform must use the same endian format."
A is wrong. depends on the specific configuration of the Oracle Database environment, and it’s not directly related to the process of transporting a database using RMAN. E is true. with the appropriate commands RMAN> CONVERT DATAFILE '/path/tbs_31.f', '/path/tbs_32.f', '/path/tbs_41.f' TO PLATFORM="Solaris[tm] OE (32-bit)" FROM PLATFORM="HP TRu64 UNIX" DB_FILE_NAME_CONVERT= "/path_source/", "/path_dest/" PARALLELISM=5;
ABC is correct, E is wrong since transporting DBs must have the same endian format.
A, B , C
B,C,E No doubt.
I will go for ABC for me F is wrong as it is not automatically achived you need to run the covert command on the source db reference the target db. see below https://docs.oracle.com/en/database/oracle/oracle-database/18/bradv/rman-transporting-data-across-platforms.html#GUID-E681FF6F-0927-4ED5-BF64-73926C4121DC
E: incorrect If the destination database uses an endian format that is different from that of the source database, then the required endian format conversion is performed on the destination database (This is applicable for tablespace level transport) the question is about transporting databases. You can transport a entire database only if the source and destination use the same endian format. Doc ID 2013271.1 B, C correct for sure
E is incorrect. A tablespace can be transported between different endian format, but a Database should be the same endian format to be transported.
E incorrect. ABC correct
A,B,C E is incorrect. From doc - "You can use RMAN to transport tablespaces across platforms with different endian formats. You can also use RMAN to transport an entire database to a different platform so long as the two platforms have the same endian format."
Not sure for A, I can't find anything in documentation about this. But E is surely incorrect: https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/rman-transporting-data-across-platforms.html#GUID-B0178538-6E41-455D-8166-FBB1EDC5D198
why not D? I think D is better than A
oke. ABC. transporting database cross platforms with image copies: same endian. transporting tablespace cross platforms: different endian. https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/rman-transporting-data-across-platforms.html#GUID-EF05DB57-34E6-41AA-A44A-A0A91738DDB9