RE: Transportable Tablespaces using RMAN/ASM
Date: Tue, 12 Mar 2013 14:09:10 +0000
Message-ID: <EC65ECF8123FEE4D8FC5B212637C30400165FDB2E606_at_EXCH1.morrisonsplc.co.uk>
I think it is a valid question you ask Rick, whether or not you have found a workaround. As I have just done a tts copy yesterday it is fresh in my mind and yes you create a flat file out of asm and the t/s has to be in read only mode first otherwise it fails. Then you copy that file to the target side and convert it back to asm.
Does the DBMS_FILE_TRANSFER option allow you to convert the Endian format as you do when using the export method as I did yesterday
RMAN> convert tablespace episys_data to platform="Linux x86 64-bit" FORMAT '/app/oracle/admin/MOMDV81A/dpdump/episys_data_convert';
John
www.jhdba.wordpress.com
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Richard Croasmun
Sent: 12 March 2013 13:05
To: oracle-l_at_freelists.org
Subject: RE: Transportable Tablespaces using RMAN/ASM
Found a document on Oracle Support describing how to do this using DBMS_FILE_TRANSFER.
How to Create Transportable Tablespaces Where the Source and Destination are ASM-Based [ID 394798.1]
Rick
> From: rac_oracledba_at_msn.com
> To: oracle-l_at_freelists.org
> Subject: Transportable Tablespaces using RMAN/ASM
> Date: Fri, 8 Mar 2013 20:18:23 +0000
>
> Folks,
>
> I'm trying to implement Transportable Tablespaces using Oracle 11g Enterprise Edition Release 11.1.0.7.0 and ASM. Because the database is using ASM, it's 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. I'm 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 shouldn't need prior backups, archive logs, etc to construct a current image of the tables
> paces. I was wondering if anyone knew of any work-around without having to put the database in ARCHIVE LOG MODE.
>
Wm Morrison Supermarkets Plc is registered in England with number 358949. The registered office of the company is situated at Gain Lane, Bradford, West Yorkshire BD3 7DL. This email and any attachments are intended for the addressee(s) only and may be confidential.
If you are not the intended recipient, please inform the sender by replying to the email that you have received in error and then destroy the email. If you are not the intended recipient, you must not use, disclose, copy or rely on the email or its attachments in any way.
This email does not constitute a contract in writing for the purposes of the Law of Property (Miscellaneous Provisions) Act 1989.
Our Standard Terms and Conditions of Purchase, as may be amended from time to time, apply to any contract that we enter into. The current version of our Standard Terms and Conditions of Purchase is available at: http://www.morrisons.co.uk/gscop
Although we have taken steps to ensure the email and its attachments are virus-free, we cannot guarantee this or accept any responsibility, and it is the responsibility of recipients to carry out their own virus checks.
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Mar 12 2013 - 15:09:10 CET