Which three statements must be true before transporting a tablespace from a database on
one platform to a database on another platform? (Choose three.)
A.
Both source and target database must be the same character set
B.
Both source and target database must have the same endian format
C.
The COMPATIBLE parameter must be the same in the source and target databases.
D.
The minimum compatibility level for both the source and target database must be 10.0.0.
E.
All read-only and offline data files that belong to the tablespace to be transported must be
platform aware.
B is wrong – you can use the rman convert to convert the datafile between endian formats
Correct answer: A,D,E
Reasoning:
Both the source and target databases need to set the COMPATIBLE initialization parameter to 10.0.0 or higher. This will cause all files opened to become platform aware.
All tablespaces that are read-only prior to Oracle 10g must be made read-write before using this feature.
I think that the correct answer is A and D only.
Why? well …
The version of oracle examined in the exam IZO-053 is 11.2.0.1 as stated here
https://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=5001&get_params=p_exam_id:1Z0-053&p_org_id=&lang=
Therefore please refer to the documentation found in
https://docs.oracle.com/cd/E11882_01/index.htm
@Anonim, what is your source? I cannot find this text in an official source. Nor can I find examples of this.
@Magwai, your last paragraph, I cannot find in a source for version 11.2.0.1.
Discussing answer A …
The 11.2.0.1 documentation in …
http://oracle.su/docs/11g/server.112/e10595/tspaces013.htm#i1007169
it says …
The source and destination database must use the same character set and national character set.
Discussing answer D …
The 11.2.0.1 documentation in …
http://oracle.su/docs/11g/server.112/e10595/tspaces013.htm#i1007169
says …
Before a tablespace can be transported to a different platform, the datafile header must identify the platform to which it belongs. In an Oracle Database with compatibility set to 10.0.0 or later, you can accomplish this by making the datafile read/write at least once.
Also at …
http://oracle.su/docs/11g/server.112/e10595/tspaces013.htm#i1007244
see section titled
“Compatibility Considerations for Transportable Tablespaces”
Discussing answer E …
correct me if I am wrong but this does not appear in the documentation found in …
https://docs.oracle.com/cd/E11882_01/index.htm
I does however appear in documentation for version 10g … hmmmmmm
I agree that ADE is correct answer.
I agree….A,D and E
You can use RMAN to transport tablespaces across platforms with different endian formats. You can also use RMAN to transport an entire database to a different platform so long as the two platforms have the same endian format.
If the source platform and the target platform are of different endianness, then an additional step must be done on either the source or target platform to convert the tablespace being transported to the target format. If they are of the same endianness, then no conversion is necessary and tablespaces can be transported as if they were on the same platform.
Read only and offline files get the compatibility advanced after they are made read/write or are brought online. This implies that tablespaces that are read only prior to Oracle Database 10g must be made read/write at least once before they can use the cross platform transportable feature.
I agree, the answers are A, D and E