MAKE THE TABLESPACE(S) READ-WRITE ON BOTH SOURCE AND DESTINATION

5. Make the tablespace(s) read-write on both source and destination.

P AR T III

An additional step that may be required when transporting tablespaces from one

platform to another is to convert the endian format of the data. A big-endian platform

(such as Solaris on SPARC chips) stores a multibyte value such as a 16-bit integer with

the most significant byte first. A little-endian platform (such as Windows on Intel

chips) stores the least significant byte first. To transport tablespaces across platforms

with a different endian format requires converting the datafiles: you do this with the

RMAN command CONVERT.

To determine the platform on which a database is running, query the column

PLATFORM_NAME in V$DATABASE. Then to see the list of currently supported

platforms and their endian-ness, query the view V$TRANSPORTABLE_PLATFORM:

orcl > select * from v$transportable_platform order by platform_name;PLATFORM_ID PLATFORM_NAME ENDIAN_FORMAT--- --- --- 6 AIX-Based Systems (64-bit) Big 16 Apple Mac OS Big 19 HP IA Open VMS Little 15 HP Open VMS Little 5 HP Tru64 UNIX Little 3 HP-UX (64-bit) Big 4 HP-UX IA (64-bit) Big 18 IBM Power Based Linux Big 9 IBM zSeries Based Linux Big 13 Linux 64-bit for AMD Little 10 Linux IA (32-bit) Little 11 Linux IA (64-bit) Little 12 Microsoft Windows 64-bit for AMD Little 7 Microsoft Windows IA (32-bit) Little 8 Microsoft Windows IA (64-bit) Little 20 Solaris Operating System (AMD64) Little 17 Solaris Operating System (x86) Little 1 Solaris[tm] OE (32-bit) Big 2 Solaris[tm] OE (64-bit) Big19 rows selected.

Database Control has a wizard that takes you through the entire process of

transporting a tablespace (or several). From the database home page, select the Data

Movement tab and then the Transport Tablespaces link in the Move Database Files