Cross-platform data transmission and prerequisites in oracle11g

I. The significance of cross-platform data transmission is that you can transmit tablespaces in databases running on one platform to databases running on another platform.

 

2. Typical cross-platform portable tablespaces include the following:

1. Publish structured data as a table space that can be transferred to a non-demanding platform. You can integrate the converted table space into existing database customers.

2. migrate data from a large data warehouse server to a data center of a small computer, such as a Linux-based workstation or server

3. All Hosts share the tablespace in read-only mode on Heterogeneous clusters with the same segment-byte format.

 

Iii. There are three types of cross-platform data transmission in oracle11g:

1. If the source platform is different from the target platform and the byte format is different, you must use the RMAN convert command to operate the table space that can be transferred.

2. If some databases are converted between database platforms with the same end-byte format, you can use the operating system method to copy files from the source to the destination.

3. If you want to convert a complete database with the same end-byte format, any data file and undo must be converted. Data cannot be directly copied from the source to the target platform.

 

4. Check the database before cross-platform transmission.

1. The source and target platforms must have the same segment-byte format. For example, you can transfer a database from Microsoft Windows to Linux x86 (both in Small-end mode), or from HP-UX to Aix (both in big-end mode ), but not from HP-UX to Linux x86 (big end to low level priority )). however, even with the same byte format, a database must undergo a conversion process from one platform to another.

2. The database must be opened in read-only mode during transmission.