Steps to create Cross-Platform Transportable Tablespaces

hi
what is the steps to do Cross-Platform Transportable Tablespaces.
i want to perform this in my pc, i have linux and windows in same PC, i want to migrate from linux to windows and vice versa.
so can i know complete steps and commands to perform Cross-Platform Transportable Tablespaces. to get complete knowledge i am doing this so i can implement this in my office when any migrate issues comes. so once i do this i will get confidence so that i can do the same in my office which saves my time.
veeresh s
oracle-dba
[email protected]

Hi, also you can review the Note:413586.1 into metalink site.
Good luck.
Regards.

Similar Messages

Oracle 10g - Cross-Platform Transportable Database (with or without RMAN?)

Hello guys,
i am currently on a project for migrating oracle databases from one platform to another platform (both platforms are on the same endianess):
-> From Linux 64-Bit to Windows 64-Bit
-> From HP-UX 64-Bit to AIX 64-Bit
All databases are on Oracle 10g (10.2.0.4) and i have tested two different ways:
1) The "official" way with RMAN CONVERT DATABASE
http://youngcow.net/doc/oracle10g/backup.102/b14191/dbxptrn002.htm#CHDEEEAG
2) "Copy & Paste"
- Copy & Paste of the database files
- Recreate controlfile manually on target platform (with help of "backup controlfile to trace" on source platform)
Both ways are working well and the migrated test databases are running fine.
Now i am wondering why there is a "RMAN CONVERT DATABASE" command, if it possible to copy and paste the data files and perform two steps manually afterwards.
The "RMAN CONVERT DATABASE" is time consuming and you still need to copy the RMAN output files to the target platform.
Is there any special reason, why you need the "RMAN CONVERT DATABASE"? Does the "RMAN CONVERT DATABASE" change some things in the database files internally?
Thanks and Regards

Hello,
Anurag Tibrewal wrote:
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. Of course .. in this case you can not use the "Cross-Platform Transportable Database" - you have to use the "Cross-Platform Tranportable Tablespace" (with RMAN CONVERT DATAFILE or TABLESPACE).
Anurag Tibrewal wrote:
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 oracle provides this with RMAN and the command "RMAN CONVERT DATABASE" .. as i already wrote i have already performed the two ways "RMAN CONVERT DATABASE" and "just copy & paste" and both are working fine.
So my question is if there is any special case in which you should use the RMAN way with "RMAN CONVERT DATABASE" instead of just "copy & paste" if you stay on the same endianness?
Thanks and Regards

Webinar (Aug 11): How to create Cross-Platform Automated GUI Tests for Java Apps

Join Squish expert, Amanda Burma, and learn how to create cross-platform automated GUI tests for your Java applications!
Register here (multiple time slots)
August 11th 2014
Duration: 30 minutes plus Q & A
This webinar will cover:
General Squish for Java overview
Automating BDD Scenarios
Executing Cross-Platform Automated GUI Tests
Interacting with Java application objects, properties & API
See you there!
Unable to attend? Register and we'll send links to future events and access to our webinar archive following the event.
Webinar schedule
Learn more about Squish
Evaluate froglogic squish

<property name="messaging.client.jar.path" value="Location in your local drive" />
<property name="messaging.client.jar.name" value="nameOfYourFile.jar" />

RMAN Full Database restore cross platforms

All
I have a database 10.2.0.3 running on Solaris 10 OS.
I have performed a full back up (level 0) of this database using rman utility with auto back up on. I am trying to worl on a scenario where I could restore this backup on another linux machine. so I copied over all the backup pieces into the target linux server. from a local RDBMS installation (10.2.0.3) on the linux machine I am trying to restore the database... but not successful yet..
when I issue restore spfile or restore control file from +<backup file name>+; the prompt continues to search in some location is responding back saying no back up piece found.. below is the sequece of step I am trying ..
1 set up env on the linux server
2 rman target /
(instance not started but rman allows connection)
3 set DBID=+<DB ID of the source database running on Solaris>+
it executes set dbid=
4 startup nomount
as the pfile/spfile is not available under $ORACLE_HOME/dbs on linux machine it picks up default pfile however but the instance stars no mount..
5 restore spfile from '/u01/app/oracle/product/10.2.0/rman_bkp/c-300009955'
here it is not able to restore any thing.same is the case with control file.
Any ideas please advice
Sarat

Sarat Chandra C wrote:
Thanks for the referance. I now understand that I may not be able to use transportable database command to transport the entire db. However there is a line in the +"Restrictions on Cross-Platform Transportable Database"+ which says +"The principal restriction on cross-platform transportable database is that the source and destination platform must share the same endian format. For example, while you can transport a database from Microsoft Windows to Linux for x86 (both little-endian), or from HP-UX to AIX (both big-endian), you cannot transport a whole database from HP_UX to Linux for x86 using this feature. You can, however, create a new database on a destination platform manually, and transport needed tablespaces from the source database using cross-platform transportable tablespace as described in "Cross-Platform Tranportable Tablespace: CONVERT DATAFILE or TABLESPACE"."+
I understand if we are ready to transport every tablespace from Source to Target individually, may then be able to replicate a transportable database. Does the transportable tablespace do not have any restrictions like the transport database has got in respect to Platforms and Endian? Please clarify.
Also is there a support matrix for thr transportable database and tablespaces which we could refer to ?
Regards!
SaratSarat,
The same restriction that is there for the transport of the whole database lies completely true for the transportable tablespace as well if you are going for the cross platform. Endian must match across the platforms than only you can do this otherwise, as like the database feature, you need to convert the source file to the target endian.
If you look at the reference doc for the Trasnport Tablespace command,
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta063.htm#RCMRF1919
This restriction is documented there besides other restrictions
>
Restrictions and Usage Notes
The limitations on creating transportable tablespace sets described in Oracle Database Administrator's Guide apply to transporting tablespaces from backup, with the exception of the requirement to make the tablespaces read-only.
TRANSPORT TABLESPACE does not perform endian format conversion. If the target platform has a different endian format, then you must use the RMAN CONVERT command to perform the separate step of converting the endian format of the datafiles in the transportable set.
>
HTH
Aman....

Transportable tablespace Windows to Linux different character sets

Hi,
Is it absolutely necessary to have the same character set when doing a cross platform transport tablespace from Windows to Linux? We are trying to do it on Oracle10gR2 from Windows to Linux.
Thank you.

Hi, yes is necessary that your databases have the same chracter set, please review the limitations into the Note:291024.1.
Luck.
Have a good day.
Regards.

Error in Transport Tablespace from linux to windows

I am testing the cross-Platform Transport Tablespace. As per the oracle, we can transport tablespace from linux to windows without conversion because both are using same endian (Little).
But i am fail to do Transport Tablespace from Linux to Windows.
I am performing Transport Tablespace process as following:
from Source Oracle Database server(red had linux as 4 32-bit oracle version:10.2)
Sql> alter tablespace TEST read only;
$ expdp system/pass dumpfile=test.dmp directory=export_dir transport_tablespaces=test transport_full_check=y
after this i am coping test.dmp and data file (test.dbf) to the target machine (ms windows xp 32-bit with oracle 10.1) .
on Target Machine (with Ms windows xp os) here i am giving the following command:
impdp system dumpfile=test.dmp directory=exp_dir transport_datafiles=/exp_dir/test.dbf
but it is giving following error:
ora-39001: invalid argument value
ora-39000: bad dump file specification
ora-31619: invalid dump file "c:\pks\1103.dmp"
what may by ...
Prabhaker

now for version compatibility i am inclusding version option with expdp
edpdp scott dumpfile=1103.dmp directory=pks transport_tablespaces=prabhu version=10.1.0.2.0
but now it is giving following error:
Import: Release 10.1.0.2.0 - Production on Saturday, 11 March, 2006 19:07
Copyright (c) 2003, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Master table "SCOTT"."SYS_IMPORT_TRANSPORTABLE_01" successfully loaded/unloaded
Starting "SCOTT"."SYS_IMPORT_TRANSPORTABLE_01": scott/******** DUMPFILE=1103.DMP DIRECTORY=PKS TRANSPORT_DATAFILES=C:\PKS\PRABHU version=10.1.0
Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
ORA-39123: Data Pump transportable tablespace job aborted
ORA-06550: line 2, column 2:
PLS-00306: wrong number or types of arguments in call to 'BEGINIMPORT'
ORA-06550: line 2, column 2:
PL/SQL: Statement ignored
Job "SCOTT"."SYS_IMPORT_TRANSPORTABLE_01" stopped due to fatal error at 19:07
regards
Prabhu

Transportable Tablespace in ASM

Hi all,
I want to move one tablespace from a database to another database using the 10g cross platform transportable tablespace.
My source database is running on Linux 32 bit (Little endian format) and the target database is running on AIX (Big endian format). However both databases use the ASM diskgroup as a storage option.
Do I need to convert the endian format of the source tablespace datafile to transport to the target database?
Thanks,

Because ASM diskgroup consists of one or more raw
partitions or raw devices, I am wondersing if I still
have to convert the endian format of datafiles..Interesting question.
As you said earlier:
- Linux natively uses Little endian
- AIX natively uses Big endian
You imply that perhaps Linux's ASM 'converts' to an 'Oracle neutral-endian' format whenever something is stored in the ASM disk group. Which would make it identical to AIX's ASM format, also 'converted'.
(I use 'convert' in quotes, as one or the other would not need to get switched, if a specific endian form is maintained.)
Worth investigating further. Although I am not sure why Oracle would introduce the overhead of conversion to-and-from every storage call.

Opaque Types - Cross platform TTS

When doing cross platform transportable tablespaces, there's a know limitation with "Opaque Types" which read:
Opaque Types Types(such as RAW, BFILE, and the AnyTypes) can be transported, but they are not converted as part of the cross-platform transport operation.
Their actual structure is known only to the application, so the application must address any endianness issues after these types are moved to the new platform.
Question is:
Does this also applies to standard expdp/impdp or is "Opaque Types" endiannes correctly converted when using normal expdp/impdp instead of TTS?
thanks

Hi Sulimo,
Got a link ..
Opaque Types Types(such as RAW, BFILE, and the AnyTypes) can be transported, but they are not converted as part of the cross-platform transport operation. Their actual structure is known only to the application, so the application must address any endianness issues after these types are moved to the new platform.
http://sandeepmagdum.blogspot.in/p/crossplatform-migration-using-rman.html
With expdp/impdp it should be possible but with few constrains .. please refer below
http://docs.oracle.com/cd/E11882_01/server.112/e22490/dp_overview.htm
Thanks,
Ajay More
http://www.moreajays.com

Can I use RMAN transportable database cross platform from 10g to 11g?

Hi,
I'm working on the migration plan, the source db server is solaris with 10g database while the destination server is AIX with 11g database.
Can I use RMAN transportable database for this purpose?
Coz I have read the restrictions on Cross-Platform Transportable Database, but it does not mention whether it can work for different version of database.
please help.

Hi,
Do you have metalink account? If yes please check : Cross-Platform Migration on Destination Host Using Rman Convert Database [ID 414878.1]*
RMAN Cross-Platform Transportable Databases and Tablespaces
Thank you

How to create a new TRANSPORT PACKAGE in BI 7.0

Two issues
1) How to check avaliable TRANSPORT PACKAGES in BI 7.0 and
2) How (steps) to create a new TRANSPORT PACKAGE,So that i can assign all the transport request to that package.
Thanks

Hi,
Steps for creating TRANSPORT PACKAGE
Go to SE80 and in the obj edit mode select Select DEVELOPMENT COORDINATION tab where u can giv ur PACKAGE NAME and create the package
Select your Software Component ,Transport Layer
Package Type = NOT A MAIN PACKAGE and create a request
and save it.
Assign points if useful..
Regards,
NR
Edited by: N R Pradeep Reddy on Apr 10, 2008 11:29 AM

To create a stock transport order and third party order

please explain steps to create a stock transport order and third party order with transaction code what are the pre-requisite. related to MM?

First you need a supplying plant. stock ready to transfer for a matetrial which should be created/extended at both the suppling and receiving plants.
The order type is UB
rest of the things are Pur org, Pur Grp, Company Code etc...
The most important part is Vender has been replaced by supplying plant.

Grid Control for a cross-platform migration

Is it possible to use Enterprise Manager Grid Control to execute a cross-platform migration? A co-worker suggested checking this out, but he wasn't sure if it would work or not.

Cross-Platform transportation is a complex process and done by RMAN utility. Don't rely on GridControl, better follow the roadmap in
http://download-uk.oracle.com/docs/cd/B19306_01/backup.102/b14191/dbxptrn.htm#sthref1379
Werner

Cross Platform migration employing Incremental Transportable Tablespaces

We have a VLDB that needs to be converted from a Sparc T3 Solaris Big endian to Linux small endian and there are over 6000 tables and the GoldenGate method to reduce downtime was attempted n dev and was an utter failure. Then I read in several places including metalink ( My Oracle Support ) in DOC ID 1644693.1 Entitiled "How to restore a pre 12c database backup to a cross platform cross endian 12c database", Bug 13335722 and many Oracle 12c Brochures all state that the cross platform cross endian method of using Incremental Transportable Tablespaces which used to be only supported for Exadata is now supported for ALL 12c platforms. Can anyone veriffy this and has employed this technique to migrate from Sun to Linux by first upgrading the source database to 12c then employing Incremental Transportable Tablespaces capabilities of 12c to migrate cross platform cross endian from Sun Sparc big endian 64 bit word to Linux Intel little endian 64 word. Otherwise if we migrate from 11GR2 Sun to Intel we are looking at least 5 days of Read Only downtime.
Thanks

You can also refer to Metalink note
Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup (Doc ID 1389592.1)

Why transportable tablespace for platform migration of same endian format?

RDBMS Version : 10.2.0.4
We are planning to migrate our DB to a different platform. Both platforms are of BIG endian format. From googling , I came across the following link
http://levipereira.files.wordpress.com/2011/01/oracle_generic_migration_version_1.pdf
In this IBM document, they are migrating from Solaris 5.9 (SPARC) to AIX 6 . Both are of BIG endian format.Since they both are of same endian format can't they use TRANSPORTABLE DATABASE ? Why are they using RMAN COVERT DATAFILE (Transportable tablespace ) ?

In this IBM document, they are migrating from Solaris 5.9 (SPARC) to AIX 6 . Both are of BIG endian format.Since they both are of same endian format can't they use TRANSPORTABLE DATABASE ? Why are they using RMAN COVERT DATAFILE (Transportable tablespace ) ?they are using transportable database - they are not importing data to dictionary, not creating users... - instead of using convert database, they used convert datafile to avoid of converting all datafiles (you need to convert only undo + system tablespace) - there's MOS note: Avoid Datafile Conversion during Transportable Database [ID 732053.1].
Basic steps for convert database:
1. Verify the prerequisites
2. Identify any external files and directories with DBMS_TDB.CHECK_EXTERNAL.
3. Shutdown (consistent) and restart the source database in READ ONLY mode.
4. Use DBMS_TDB.CHECK_DB to make sure the database is ready to be transported.
5. Run the RMAN convert database command.
6. Copy the converted files to the target database. Note that this implies that you will need 2x the storage on the source database for the converted files.
7. Copy the parameter file to the target database.
8. Adjust configuration files as required (parameter, listener.ora, tnsnames, etc).
9. Fire up the new database!
All other details are in:
http://docs.oracle.com/cd/B19306_01/backup.102/b14191/dbxptrn.htm#CHDFHBFI
Lukas

How could I create, force mount, and burn a read-only cross-platform .iso image?

Hello,
I am new to this group.
I want to perform the following steps as quickly as possible.
1. Create a cross-platform .iso
2. Mount the cross-platform .iso as read-only
3. Unmount the cross-platform .iso
4. Finally, burn the cross-platform read-only .iso to CD-R media
I need someone to give me an example and step-by-step instructions by using the hdiutil command in Mac Terminal.
Thanks in advance for your responses.
John P.

1. Create a cross-platform .iso
hdiutil makehybrd -o image-file source-directory -iso -iso-volume-name volume-name
2. Mount the cross-platform .iso as read-only
hdiutil attach image-file
3. Unmount the cross-platform .iso
hdiutil detach /Volumes/volume-name
4. Finally, burn the cross-platform read-only .iso to CD-R media
hdiutil burn image-file
For more information, see the man page for hdiutil(1).

Steps to create Cross-Platform Transportable Tablespaces

Similar Messages

Maybe you are looking for