Re: transportable tablespace to an ASM database

Dear DBA,

I didn't see where you got an answer to your question. Have you resolved your issue?
My assumption is that you are using the RMAN transportable tablespace feature because your two servers are not compatible (SPARC to Intel)? My understanding is that in this situation RMAN is just the way Oracle implemented the cross-platform. Even though Alejandro's example uses a full backup, that isn't needed. Perhaps this paper will show that more clearly. http://www.oracle.com/technology/deploy/availability/htdocs/xtts.htm I also don't see where Alejandro converted the tablespaces, but maybe that wasn't his point.
However, since you need to convert the tablespace to ASM, that part of Alejandro's example should be useful for you.

Dennis Williams

On 7/23/08, Dba DBA <oracledbaquestions_at_gmail.com> wrote:
>
> Oracle Version 10.2.0.4 on both databases
> The database sending the tablespace is on Solaris
> The database receiving the tablespace is on Red Hat Linux
>
> The database receiving the tablespace is on ASM, the other is not.
>
> can i do this without doing an RMAN backup of the entire source database?
>
>
> http://blogs.oracle.com/AlejandroVargas/2007/04/rman_transportable_tablespace.html
>
> They are using the SAN to do backups and not using RMAN. Its a
> multi-terabyte database, so this is not practical. I just need 1 tablespace.
>
>
>
>

--
http://www.freelists.org/webpage/oracle-l