You are required to migrate your 11.2.0.3 database to an Oracle 12c database.
Examine the list of steps that might be used to accomplish this task:
1.Place all user-defined tablespaces in read-only mode on the source database.
2.Use the RMAN convert command to convert data files to the target platform’s endian
format, if required.
3.Perform a full transportable export on the source database with the parameters
VERSI0N=I2, TRANSPORTABLE=ALWAYS, and FULL=Y.
4. Transport the data files for all the user-defined tablespaces.
5. Transport the export dump file to the target database.
6.Perform an import on the target database by using the full, network_link, and
transportable_datafiles parameters.
7.Perform an import on the target database by using the full and transportable_datafiles
parameters.
Identify the required steps in the correct order.
A.
1, 3, 5, 4, 2, and 6
B.
1, 2, 4, 6, 5, 3, and 7
C.
1, 2,4, and 7
D.
2, 4, 5, 6, and 7
B
Not A,B,C,D
http://docs.oracle.com/database/121/ADMIN/transport.htm#ADMIN13726
Transporting a Database Using an Export Dump File executing in following order:
1.Place all user-defined tablespaces in read-only mode on the source database.
3.Perform a full transportable export on the source database with the parameters
VERSI0N=12, TRANSPORTABLE=ALWAYS, and FULL=Y.
5.Transport the export dump file to the target database.
4.Transport the data files for all the user-defined tablespaces.
2.Use the RMAN convert command to convert data files to the target platform’s endian
format, if required.
7.Perform an import on the target database by using the full and TRANSPORT_DATAFILES
parameters.
OR
1.Place all user-defined tablespaces in read-only mode on the source database.
4.Transport the data files for all the user-defined tablespaces.
2.Use the RMAN convert command to convert data files to the target platform’s endian
format, if required.
~6.Perform an import on the target database by using the TRANSPORTABLE, TRANSPORT_DATAFILES,FULL,NETWORK_LINK,VERSION=12.
But I think than we should go for answer A right?
I’m not sure which answer is correct. Can you advise more?
The steps are here
http://docs.oracle.com/database/121/ADMIN/transport.htm#ADMIN13726
A
Transporting a Database Using an Export Dump File
The following list of tasks summarizes the process of transporting a database using an export dump file. Details for each task are provided in the subsequent example.
At the source database, place each of the user-defined tablespaces in read-only mode and export the database.
Ensure that the following parameters are set to the specified values:
TRANSPORTABLE=ALWAYS
FULL=Y
If the source database is an Oracle Database 11g Release 2 (11.2.0.3) or later Oracle Database 11g database, then you must set the VERSION parameter to 12 or higher.
If the source database contains any encrypted tablespaces or tablespaces containing tables with encrypted columns, then you must either specify ENCRYPTION_PWD_PROMPT=YES, or specify the ENCRYPTION_PASSWORD parameter.
The export dump file includes the metadata for objects contained within the user-defined tablespaces and both the metadata and data for user-defined objects contained within the administrative tablespaces, such as SYSTEM and SYSAUX.
Transport the export dump file.
Copy the export dump file to a place that is accessible to the target database.
Transport the data files for 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.
(Optional) Restore the user-defined tablespaces to read/write mode on the source database.
At the target database, import the database.
When the import is complete, the user-defined tablespaces are in read/write mode.
I agree with Siegfried. No correct answer for this question.
Transporting a database using an export dump file is: 1 3 5 4 2 7 (not 6)
for the transporting a database over the network, it can be either 1 4 2 6 or 1 2 4 6
When you use the RMAN CONVERT command to convert data, you can either convert
the data on the source platform after running Data Pump export, or you can convert it
on the target platform before running Data Pump import. In either case, you must
transfer the data files from the source system to the target system.
I think A too!
A
A
http://www.oracle.com/technetwork/database/upgrade/upgrading-oracle-database-wp-12c-1896123.pdf
page 11
This is yet another question with incomplete description.
this looks like an DB upgrade rather than a cross-platform migration.
Why is conversion needed at all ?
1,3,5,4,6
or
1,3,5,4,7
are correct, closes best answer for such flawed question is A.
A is correct . in new Exam dumps the first answer contains A. 1, 3, 5, 4, 2, and 7
A