Transportable Tablespaces using RMAN/ASM
- From: Richard Croasmun <rac_oracledba@xxxxxxx>
- To: "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 8 Mar 2013 20:18:23 +0000
Folks,
Im trying to implement Transportable Tablespaces using Oracle 11g Enterprise
Edition Release 11.1.0.7.0 and ASM. Because the database is using ASM, its my
understanding that I must use RMAN to extract tablespace data to a physical
file for copying over to the target instance as there are not the typical O/S
database files to copy over as in a non-ASM setup. Im initially implementing
this using a development database that is in NO ARCHIVE LOG MODE. The target
tablespaces are all in read-only mode. When I execute the RMAN Transport
Tablespace command, it fails because the database is in NO ARCHIVE LOG MODE
(see below). Now, I completely understand why RMAN would want the database to
be in ARCHIVE LOG MODE if it was doing a point-in-time recovery, or something
like that, but considering the fact that all the tablespaces in my
transportable tablespace set are in read-only mode, RMAN shouldnt need prior
backups, archive logs, etc to construct a current image of the tablespaces. I
was wondering if anyone knew of any work-around without having to put the
database in ARCHIVE LOG MODE.
RMAN> TRANSPORT TABLESPACE TTS_FACT_DATA, TTS_FACT_DATA_2010,
TTS_FACT_DATA_2011, TTS_FACT_DATA_2012, TTS_FACT_DATA_2013,
TTS_FACT_INDEX_2010, TTS_FACT_INDEX_2011, TTS_FACT_INDEX_2012,
TTS_FACT_INDEX_2013
2> TABLESPACE DESTINATION '/home/spa/rick/'
3> AUXILIARY DESTINATION '/home/spa/rick/';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of transport tablespace command at 03/08/2013 14:55:35
RMAN-05004: target database log mode is NOARCHIVELOG
RMAN>
Thanks for your time and feedback,
Rick
--
//www.freelists.org/webpage/oracle-l
Other related posts:
