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.
The impdp operation must be performed by the same user that performed the expdp
operation.
C.
The path of data files on the target database must be the same as that on the source
database.
D.
All the user-defined tablespaces must be in read-only mode on the source database.
E.
The export dump file must be created before starting the import on the target database.
F.
The source and target database must be running on the same platform with the same
endianness.
ADF
Transporting a Database Over the Network
To transport a database over the network, you perform an import using the NETWORK_LINK parameter, the import is performed using a database link, and there is no dump file involved.
The following list of tasks summarizes the process of transporting a database over the network. Details for each task are provided in the subsequent example.
1.Create a database link from the target database to the source database.
The import operation must be performed by a user on the target database with DATAPUMP_IMP_FULL_DATABASE role, and the database link must connect to a user on the source database with DATAPUMP_EXP_FULL_DATABASE role. The user on the source database cannot be a user with SYSDBA administrative privilege. If the database link is a connected user database link, then the user on the target database cannot be a user with SYSDBA administrative privilege. See “Users of Database Links” for information about connected user database links.
2.In the source database, make the user-defined tablespaces in the database read-only.
3.Transport the data files for the all of the user-defined tablespaces in the database.
Copy the data files to a place that is accessible to the target database.
If the source platform and target platform are different, then check the endian format of each platform by running the query on the V$TRANSPORTABLE_PLATFORM view in “Transporting Data Across Platforms”.
If the source platform’s endian format is different from the target platform’s endian format, then use one of the following methods to convert the data files:
◦Use the GET_FILE or PUT_FILE procedure in the DBMS_FILE_TRANSFER package to transfer the data files. These procedures convert the data files to the target platform’s endian format automatically.
◦Use the RMAN CONVERT command to convert the data files to the target platform’s endian format.
See “Converting Data Between Platforms” for more information.
4.At the target database, import the database.
Invoke the Data Pump utility to import the metadata for the user-defined tablespaces and both the metadata and data for the administrative tablespaces.
Ensure that the following parameters are set to the specified values:
◦TRANSPORTABLE=ALWAYS
◦TRANSPORT_DATAFILES=list_of_datafiles
◦FULL=Y
◦NETWORK_LINK=source_database_link
Replace source_database_link with the name of the database link to the source database.
◦VERSION=12
If the source database is an Oracle Database 11g Release 2 (11.2.0.3) or later Oracle Database 11g database, then the VERSION parameter is required and must be set to 12. If the source database is an Oracle Database 12c database, then the VERSION parameter is not required.
I like this weblog so much, bookmarked.
http://www.bastcilkdoptb.com/
A
D
F