RMAN Full Database restore cross platforms

Question

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

Answer 1

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....