427.When exporting metadata for the transportable tablespaces, what is the correct next step after
confirming endian format?
A. Export the tablespaces using data pump.
B. Determine if the transportable set is self-contained.
C. Convert the datafiles using RMAN.
D. Copy the datafiles from source to destination.
Answer: B
解析:http://docs.oracle.com/cd/E11882_01/server.112/e25494/tspaces.htm#i1007252
-
For cross-platform transport, check the endian format of both platforms by querying the
V$TRANSPORTABLE_PLATFORM
view.Ignore this task if you are transporting your tablespace set to the same platform.
-
Pick a self-contained set of tablespaces.
-
At the source database, place the set of tablespaces in read-only mode and generate a transportable tablespace set.
A transportable tablespace set (ortransportable set) consists of data files for the set of tablespaces being transported and an export file containing structural information (metadata) for the set of tablespaces. You use Data Pump to perform the export.
If you are transporting the tablespace set to a platform with different endianness from the source platform, you must convert the tablespace set to the endianness of the destination platform. You can perform a source-side conversion at this step in the procedure, or you can perform a destination-side conversion as part of Task 4.
-
Transport the tablespace set.
Copy the data files and the export file to a place that is accessible to the destination database.
If you transported the tablespace set to a platform with different endianness from the source platform, and you have not performed a source-side conversion to the endianness of the destination platform, perform a destination-side conversion now.
-
(Optional) Restore tablespaces to read/write mode.
-
At the destination database, import the tablespace set.
Invoke the Data Pump utility to import the metadata for the tablespace set.