Which three requirements must be met before a tablespace can be transported across
different platforms?
A.
Both the source and target databases must use the same character set.
B.
The platforms of both the source and target databases must have the same endian format.
C.
The compatible parameter value must be the same in the source and target databases.
D.
The minimum compatibility level for both the source and target databases must be 10.0.0.
E.
The tablespace to be transported must be in read-only mode.
A, D and E.
http://docs.oracle.com/cd/B28359_01/server.111/b28310/tspaces013.htm
Thanks Vijay!
A. Confirm
The source and target database must use the same character set and national character set.
http://docs.oracle.com/cd/B28359_01/server.111/b28310/tspaces013.htm
B. Wrong. If endian is different then we need to do more step. Convert step.
http://docs.oracle.com/cd/B28359_01/server.111/b28310/tspaces013.htm
Otherwise you must do a conversion of the tablespace set either at the source or target database.
E. Correct. Need read-only tablespace
This method of generating a transportable tablespace requires that you temporarily make the tablespace read-only.
D. Correct. Differenct platform need 10.0.0 compatibility
Databases on different platforms
10.0 10.0
http://docs.oracle.com/cd/B28359_01/server.111/b28310/tspaces013.htm#i1007244
Thank you Vijay. I agree with you A, D and E
For me it’s A B D
Same link.
If transporting across different platforms, The platforms of both the source and target databases must 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.
Yes, but it is possible isnt it?
A, D, E for me…
I also agree ABD
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.
–> B
ADE
I am going to agree with ADE as well based off the Oracle Doc you guys are using. It does not say you can’t transport the tablespaces if they are different endians. It just says if they are different endians then you have to complete an additional step to use it (RMAN CONVERT command), but it does say you have to have the tablespaces in read-only mode from that Oracle Doc. So ADE for me.
E for sure correct
NOT A: The source and the target databases must use compatible database character sets.
NOT B: rman convert and get_file put_file from DBMS_FILE_TRANSFER
https://docs.oracle.com/database/121/ADMIN/transport.htm#ADMIN11396
According to ORacle Database 12c: New Features for Administrators 13 – 19, Student Guide Volume I
Transporting Tablespace: Process Steps -1
3. For performing cross-platform tablespace transport, you may need the exact name of the destination platform to which you are transporting data.
SELECT PLATFORM_ID, PLATFORM_NAME, ENDIAN_FORMAT
FROM V$TRANSPORTABLE_PLATFORM
WHERE UPPER(PLATFORM_NAME) LIKE ‘%LINUX%’;
4. Make the tablespace read-only.
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: read –>https://docs.oracle.com/database/121/ADMIN/transport.htm#ADMIN10140
Compatibility Considerations for Transporting Data
https://docs.oracle.com/database/121/ADMIN/transport.htm#ADMIN11397
General Limitations on Transporting Data
https://docs.oracle.com/database/121/ADMIN/transport.htm#ADMIN11396
ADE is the correct Answers
A.B.E
A D E
I Support Vonpire.
It’s ABD.
E could have been answer but in case had it been only solution. But it has work around,
by using backup method as well you can Transport tablespace if you do not want to make tablespace read only.
BDE
As show in this link:
http://docs.oracle.com/cd/B28359_01/server.111/b28310/tspaces013.htm
A. OK
Both the source and target databases must use the same character set.
=====
The source and target database must use the same character set and national character set.
=====
B. ONLY IN ENCRYPTED TABLESPACES, son WRONG.
The platforms of both the source and target databases must have the same endian format.
=====
You cannot transport an encrypted tablespace to a platform with different endianness.
=====
C. WRONG.
The compatible parameter value must be the same in the source and target databases.
====
Beginning with Oracle Database 11g, a tablespace can always be transported to a database with the same or higher compatibility setting
====
D. OK.
The minimum compatibility level for both the source and target databases must be 10.0.0.
=====
The question is about “tablespaces transported across different platforms”. Look in the link for “Compatibility Considerations for Transportable Tablespaces”.
=====
E. OK
The tablespace to be transported must be in read-only mode.
=====
Note:
This method for transporting tablespaces requires that you place the tablespaces to be transported in read-only mode until you complete the transporting process. If this is undesirable, you can use the Transportable Tablespaces from Backup feature, described in Oracle Database Backup and Recovery User’s Guide.
=====
So, ADE.
Here are several of the web pages we suggest for our visitors.
just beneath, are many totally not related web pages to ours, however, they are certainly worth going over
Here are a number of the web pages we suggest for our visitors
very few web sites that come about to be in depth below, from our point of view are undoubtedly very well worth checking out
ADE