Which three requirements must be met before a tablespace can be transported across different platforms?

Which three requirements must be met before a tablespace can be transported across
different platforms?

Which three requirements must be met before a tablespace can be transported across
different platforms?

A.
The tablespace to be transported must be in read-only mode.

B.
The minimum compatibility level for both the source and target databases must be
10.0.0.

C.
The compatible parameter value must be the same in the source and target databases.

D.
Both the source and target databases must use the same character set.

E.
The platforms of both the source and target databases must have the same endian
format.

Show Hint

Leave a Reply 6

Your email address will not be published. Required fields are marked *

CNS

CNS

ADC

how can TTS be done if charsets don’t match ?
The TBS has to be in readonly, which a basic pre-reqs.

Reply

jack

jack

ABD
Question is about – Databases on different platforms
in this case Minimum Compatibility Setting is 10 for source – 10 for target
B is correct C is wrong (The source and target database need not have the same compatibility setting.)
E wrong. -> If you are transporting the tablespace set to a platform with different endianness from the source platform, you must convert the tablespace set to the endianness of the target platform. You can perform a source-side conversion.. or you can perform a target-side conversion.

https://docs.oracle.com/cd/B28359_01/server.111/b28310/tspaces013.htm

Reply

A1

A1

A correct
B -correct https://docs.oracle.com/database/121/ADMIN/transport.htm#ADMIN11397) ,
C – wrong (“A tablespace or table can always be transported to a database with the same or higher compatibility setting using transportable tablespaces, whether the target database is on the same or a different platform” )

D, E – both look partially wrong to me :
D – “the same character set” requirement was in 11g, in 12c it’s “The source and the target databases must use compatible database character sets” (https://docs.oracle.com/database/121/ADMIN/transport.htm#ADMIN11396) ,
E – it seems to be true only for encrypted tablespaces during full transprotable export/import (https://docs.oracle.com/database/121/ADMIN/transport.htm#ADMIN13894) : “You cannot transport an encrypted tablespace to a platform with different endianness.”

I incline to D , it appears less wrong .

Reply