RE: RMAN duplicate RAC to single instance - how to not duplicate redo threads and temp tablespace
Date: Fri, 30 Mar 2012 09:23:00 -0500
This is attempting to create one redo group each for two instances. You must have at least two redo groups per instance - as Kathryn suggested.
Don Granaman | Phone: 402-361-3073 | Cell: 402-960-6955 | Fax: 402-361-3173 | Solutionary | Relevant . Intelligent . Security
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of neil campbell Sent: Thursday, March 29, 2012 7:20 PM
To: Oracle List
Subject: RE: RMAN duplicate RAC to single instance - how to not duplicate redo threads and temp tablespace
I know I can do this post duplicate (as you have indicated) but I really want to do it as part of the duplicate so that the redo logs dont get created if they dont have to be, and the TEMP tablespace doesn't get created if it doesn't have to.
I have a good suggestion from Chris Taylor on how to do this with the temp tablespace, and I am trying Marcins idea with the syntax for the redo logs, but I just keep getting the following error
RMAN-06136: ORACLE error from auxiliary database: ORA-01518: CREATE DATABASE must specify more than one log file
I am using the syntax
duplicate database PROD to TEST pfile='pfile.TEST' backup location='/backup/PROD' LOGFILE INSTANCE 'TEST1' GROUP 1 ('+DATA_TEST','+DATA_TEST') SIZE 1000M, INSTANCE 'TEST2' GROUP 2 ('+DATA_TEST','+DATA_TEST') SIZE 1000M;
Thanks for your help guys.
> From: DonGranaman_at_solutionary.com
> To: campbell.neil_at_hotmail.com; oracle-l_at_freelists.org
> Date: Thu, 29 Mar 2012 13:54:12 -0500
> Subject: RE: RMAN duplicate RAC to single instance - how to not
> duplicate redo threads and temp tablespace
> I do this all the time. Obviously, you cannot "skip" the redo or undo for any instance and still perform recovery, but you can duplicate the database and when it is done do (for a two-instance RAC database clone to an exclusive database)):
> alter database disable thread 2;
> alter database drop logfile group 7;
> alter database drop logfile group 8;
> drop tablespace UNDOTBS2 including contents and datafiles; ...
> (Modify as appropriate for your system, redo logs and undo
> For the temp tablespace, I haven't tried the other suggestions, but I just do something akin to (using Oracle-managed files):
> create temporary tablespace tmptmp tempfile size 100M; alter database
> default temporary tablespace TMPTMP; drop tablespace TEMP including
> contents and datafiles; create temporary tablespace TEMP tempfile size
> 1024M; alter database default temporary tablespace TEMP; drop
> tablespace TMPTMP including contents and datafiles;
> Of course there are other options...
> Don Granaman | Phone: 402-361-3073 | Cell: 402-960-6955 | Fax:
> 402-361-3173 | Solutionary | Relevant . Intelligent . Security
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of neil campbell
> Sent: Wednesday, March 28, 2012 12:01 AM
> To: Oracle List
> Subject: RMAN duplicate RAC to single instance - how to not duplicate
> redo threads and temp tablspace
> Hi all,
> Using 126.96.36.199 and trying to work out if I can do an RMAN duplicate
> from 4 node RAC to single instance without the duplicate generating the 4 threads of redo?
> Also, I wondered if it was possible to have the duplicate NOT create the TEMP tablespace as part of the duplicate?
> I am running the duplicate as part of an automated script, and it is a
> simple statement as follows
> duplicate database PROD to TEST pfile='/u01/app/oracle/test/pfile.test' backup location='/orabackup'
> This works very well, but the reason behind the requirement to not
> create additional threads and TEMP tablespace is the limited amount of
> space in the TEST environment at the moment. Removing the threads and TEMP tablespace would free up 48 Gb as the test environment doesn't run the batch jobs that use all that TEMP space.
> Open to suggestions...