Examine the following impdp command to import a database over the network from a pre-12c Oracle database (source):
Which three are prerequisites for successful execution of the command?
A.
The import operation must be performed by a user on the target database with the
DATAPUMP_IMP_FULL_DATABASE role, and the database link must connect to a user on the
source database with the DATAPUMP_EXD_FULL_DATABASE role.
B.
All the user-defined tablespaces must be in read-only mode on the source database.
C.
The export dump file must be created before starting the import on the target database.
D.
The source and target database must be running on the same platform with the same
endianness.
E.
The path of data files on the target database must be the same as that on the source database.
F.
The impdp operation must be performed by the same user that performed the expdp operation.
Explanation:
In this case we have run the impdp without performing any conversion if endian
format is different then we have to first perform conversion.
A,B&D
it’s AB and E.
It mentions same platform, different platforms with same endian format do not require this conversion.
Besides, E is correct. If the path for the datafiles where different in target environment, the remap_datafile clause would have to be used in the impdp since the metadata of the source specifies the required datafiles with it’s path for the exported tablespaces.
A,B&D
A B D
Why B is correct?
I think ADE
Look into documentation: ” In the source database, make the user-defined tablespaces in the database read-only”
ABE
ABD
ABD, but E is true too, not ?
A, B, D
https://docs.oracle.com/database/121/SUTIL/GUID-0871E56B-07EB-43B3-91DA-D1F457CF6182.htm#SUTIL919
http://www.oracle.com/technetwork/database/enterprise-edition/full-transportable-wp-12c-1973971.pdf
A If the USERID that is executing the import job has the DATAPUMP_IMP_FULL_DATABASE role on the target database, then that user must also have the DATAPUMP_EXP_FULL_DATABASE role on the source database.
full transportable import can be used to import a dump file or
to import directly from a source database into a destination database over a database link.
B STEP 4: Place the hr_1 and hr_2 tablespaces in read-only mode
The tablespaces to be transported must be in read-only mode for the duration of the export.
D Endian Conversion
If both the source and target platforms have the same endian format, then data files can be transported
as if they were on the same platform. If the source platform and the target platform are of different
endianness, then the data files being transported must be converted to the target platform format using
either the RMAN CONVERT command or the GET_FILE or PUT_FILE procedures in the
DBMS_FILE_TRANSFER package.
Note that encrypted tablespaces cannot be transported to a platform with different endianness.