As part of archiving the historical data, you want to transfer data from one database to another database, which
is on another server. All tablespaces in the source database are read/write and online. The source and target
databases use the same compatibility level and character sets. View the Exhibit and examine the features in
the source and target database.
Which of the following steps are required to transport a tablespace from the database to the target database:
1. Make the tablespace read-only at the source database.
2. Export metadata from the source database.
3. Convert data filed by using Recovery Manager (RMAN).
4. Transfer the dump file and data filed to the target machine.
5. Import metadata at the target database.
6. Make the tablespace read/write at the target database.
Exhibit:
A.
2, 4, and 5
B.
All the steps
C.
2, 3, 4 and 5
D.
1, 2, 4, 5 and 6
Explanation:
Generate a Transportable Tablespace Set
read_only–expdp–4-import-read_wrtie
1, 2, 4, 5, 6 (optional)
If both platforms have the same endianness, no conversion is necessary. Otherwise you must do a conversion
of the tablespace set either at the source or destination database.
Transport the dump file to the directory pointed to by the DATA_PUMP_DIR directory object, or to any other
directory of your choosing.
Run the following query to determine the location of DATA_PUMP_DIR:
SELECT * FROM DBA_DIRECTORIES WHERE DIRECTORY_NAME = ‘DATA_PUMP_DIR’;
Transport the data files to the location of the existing data files of the destination database.
On the UNIX and Linux platforms, this location is typically /u01/app/oracle/oradata/SID/ or +DISKGROUP/SID/
datafile/.
