Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 

 

 

Determine Platform Endianness

Oracle RAC Cluster Tips by Burleson Consulting

This is an excerpt from the bestselling book Oracle Grid & Real Application Clusters.  To get immediate access to the code depot of working RAC scripts, buy it directly from the publisher and save more than 30%.


To transport a tablespace from one platform to another, datafiles on different platforms must be in the same endian format, byte ordering. The pattern for byte ordering in native types is called endianness.  There are only two main patterns, big endian and little endian.  Big endian means the most significant byte comes first, and little endian means the least significant byte comes first. If the source platform and the target platform are of different endianness, an additional step must be taken on either the source or target platform to convert the tablespace being transported to the target format.  If they are of the same endianness, no conversion is necessary and tablespaces can be transported as if they were on the same platform.

However, there are certain restrictions in using the transportable tablespace:

* The source and target database must use the same character set and national character set.

* A tablespace cannot be transported to a target database in which a tablespace with the same name already exists. However, the tablespace to be transported or the destination tablespace can be renamed before the transport operation. Renaming a tablespace is a new feature in 10g.

* The set should be self-containing

Transporting Tablespaces between Databases: A General Procedure

Perform the following steps to move or copy a set of tablespaces.

1. Pick a self-contained set of tablespaces. Verify this using the dbms_tts.transport_set_check package.

2. Next, generate a transportable tablespace set, using the Export utility.

3. A transportable tablespace set consists of the set of datafiles for the set of tablespaces being transported and an Export file containing metadata information for the set of tablespace and corresponding data files.

4. Transporting a tablespace set to a platform different from the source platform will require connection to the Recovery Manager (RMAN) and invoking the CONVERT command. An alternative is to do the conversion on the target platform after the tablespace datafiles have been transported.

5. Next, the tablespace datafile set is transported.  Copy the datafiles and the export file containing the metadata to the target database. This can be accomplished using any facility for copying flat files, such as the operating system copy utility, ftp, or publishing on CDs or DVDs.

6. The final step is to plug in the tablespace.  Use the Import utility to plug the set of tablespaces metadata, and hence the tablespaces themselves, into the target database.

7. If these tablespaces are being transported to a different platform, the Recovery Manager CONVERT command can be used to perform the conversion.

Note: As an alternative to conversion before transport, the CONVERT command can be used for the conversion on the target platform after the tablespace set has been transported.
 


This is an excerpt from the bestselling book Oracle Grid & Real Application Clusters, Rampant TechPress, by Mike Ault and Madhu Tumma.

You can buy it direct from the publisher for 30%-off and get instant access to the code depot of Oracle tuning scripts.

http://www.rampant-books.com/book_2004_1_10g_grid.htm


 

 
��  
 
 
Oracle Training at Sea
 
 
 
 
oracle dba poster
 

 
Follow us on Twitter 
 
Oracle performance tuning software 
 
Oracle Linux poster
 
 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright © 1996 -  2017

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.

Remote Emergency Support provided by Conversational