Which task would you perform to convert little-endian CLOB data to the big endian format while transporting from Oracle9i database to Oracle 10g database?
A.
Use the CHANGE command of the RMAN utility.
B.
Use the CONVERT command of the RMAN utility.
C.
Transport the data after changing the character set of the target database to big endian.
D.
Transport the data after changing the character set to be an endian-independent format in the target database.
E.
No action is required because Oracle RDBMS implicitly does the conversion in Oracle 10g database while accessing the data.
Explanation:
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.Tablespaces can be transported from one platform to another. The RMAN
CONVERT command is used to do the conversion. The tablespaces being transported can be either dictionary managed or locally managed. Starting with Oracle9 i, the transported tablespaces are not required to be of the same block size as the target database standard block size.
SQL> SELECT * FROM V$TRANSPORTABLE_PLATFORM;
PLATFORM_ID PLATFORM_NAME ENDIAN_FORMAT
———– ——————————– ————– 1 Solaris[tm] OE (32-bit) Big
2 Solaris[tm] OE (64-bit) Big
7 Microsoft Windows IA (32-bit) Little
10 Linux IA (32-bit) Little
6 AIX-Based Systems (64-bit) Big
3 HP-UX (64-bit) Big
5 HP Tru64 UNIX Little
4 HP-UX IA (64-bit) Big
11 Linux IA (64-bit) Little
15 HP Open VMS Little
8 Microsoft Windows IA (64-bit) Little
9 IBM zSeries Based Linux Big
13 Linux 64-bit for AMD Little
16 Apple Mac OS Big
12 Microsoft Windows 64-bit for AMD Little
17 Solaris Operating System (x86) LittleREF: Oracle(r) 10g Administrator Guide , 8-27