Exam 1z0-083 All QuestionsBrowse all questions from this exam
Go to Exam
Question 108

You want to transport the UNIVERSITY tablespace from one database to another.

The UNIVERSITY tablespace is currently open read/write.

The source and destination platforms have the same endian format.

Examine this list of steps:

1. Make the UNIVERSITY tablespace read-only on the source system.

2. Export the UNIVERSITY tablespace metadata using EXPDP.

3. Create a cross-platform backup set from the UNIVERSITY tablespace on the source system, using an RMAN command that includes the DATAPUMP clause.

4. Copy the cross-platform backup sets to the destination system.

5. Copy the Data Pump dump set from the source to the destination system.

6. Restore the cross-platform backup set on the destination system using an RMAN command that includes the DATAPUMP clause.

7. Import the UNIVERSITY tablespace metadata using IMPDP.

8. Make the UNIVERSITY tablespace read/write on the destination system.

Which are the minimum number of steps required, in the correct order, to transport the UNIVERSITY tablespace?

    Correct Answer: A

    To transport the UNIVERSITY tablespace, the steps required are: making the tablespace read-only on the source system, creating a cross-platform backup set with RMAN including the DATAPUMP clause, copying the backup sets to the destination system, restoring the backup set on the destination system using an RMAN command with the DATAPUMP clause, and making the tablespace read/write on the destination system. This ensures the tablespace is correctly prepared, transferred, and restored in the destination environment.

Discussion
RinDOption: A

A is correct https://docs.oracle.com/en-us/iaas/Content/Database/Tasks/mig-rman-cross-plat-transp-tablespace.htm

ObserverPLOption: A

Agree with RinD - A is CORRECT. It is not required to perform manually export of metadata, it is done during RMAN backup of tablespace for transport.

greenday5494Option: B

the answer is B. disagree with A. RinD's post is for transporting to the cloud, which is not what we're doing here. https://docs.oracle.com/en/database/oracle/oracle-database/12.2/bradv/rman-transporting-data-across-platforms.html#GUID-4644069A-7849-49F2-A1BF-2193EBAFFDBD according to this link, only 3 steps are necessary.

greenday5494

nevermind, its A

guretto

The endian is the same.... no cross-platform migration

antonica

your document say: Note:When you use the DATAPUMP clause, the tablespaces that are being transported must be made read-only. then b is not correct

_gio_Option: A

I agree with A

ScottLOption: A

A is correct

vkraOption: A

https://docs.oracle.com/en-us/iaas/Content/Database/Tasks/mig-rman-cross-plat-transp-tablespace.htm

hilaireOption: A

A is correct https://docs.oracle.com/en-us/iaas/Content/Database/Tasks/mig-rman-cross-plat-transp-tablespace.htm

DhanushbhOption: A

A is correct , agreed