Re: RMAN skip readonly

You'll have to remember to change the tablespace to read only (which I don't
think works) or you have to remember to modify the script.

Either way there would be manual intervention.

Or

You could dynamically create the duplicate script from the source database
after you have put the tablespaces you don't want in read only mode.


Jack van Zanen

-------------------------
This e-mail and any attachments may contain confidential material for the
sole use of the intended recipient. If you are not the intended recipient,
please be aware that any disclosure, copying, distribution or use of this
e-mail or any attachment is prohibited. If you have received this e-mail in
error, please contact the sender and delete all copies.
Thank you for your cooperation


On Wed, Oct 20, 2010 at 6:10 AM, Amit Verma (IT - Otterbase) <
averma@xxxxxxxxxxxxxxxxxxx> wrote:

>  Thanks Mayen. I knew this was an option, but I don’t want to hardcode
> these tablespace names in the script. If in future the application team
> decides to skip other archive tablespaces, I’ll (or someone will) have to
> remember to modify the script.
>
>
>
>
>  ------------------------------
>
> *From:* Mayen.Shah@xxxxxxxxxx [mailto:Mayen.Shah@xxxxxxxxxx]
> *Sent:* Tuesday, October 19, 2010 8:07 AM
> *To:* Amit Verma (IT - Otterbase)
> *Cc:* oracle-l; oracle-l-bounce@xxxxxxxxxxxxx
> *Subject:* Re: RMAN skip readonly
>
>
>
> Amit,
>
> You do not have to place tablespace in read only mode in order to skip
> during duplication.
>
> During duplicate process simply mention which tablespaces need to be
> skipped.
>
> This is what I have in my QA refresh script.
>
> $ORACLE_HOME/bin/rman <<eof
> connect target ..........
> connect catalog ............
> connect AUXILIARY .............
>
> run {
> set until ..............;
> Duplicate target database to .................
>   skip tablespace 'ARCH_TBS1','ARCH_TBS2';
> }
>
> eof
>
> HTH
>
> - Mayen
>
>
>
> From:        "Amit Verma (IT - Otterbase)" <averma@xxxxxxxxxxxxxxxxxxx>
> To:        oracle-l <oracle-l@xxxxxxxxxxxxx>
> Date:        10/18/2010 04:22 PM
> Subject:        RMAN skip readonly
> Sent by:        oracle-l-bounce@xxxxxxxxxxxxx
>  ------------------------------
>
>
>
>
> Hey guys,
>
> I need to refresh a QA database from production with the exception of 2
> archive tablespaces. These tablespaces were backed up in read-write mode
> from production and I am going to use that backup piece to restore and
> recover. Can I switch these 2 tablespaces to read only mode before issuing
> the duplicate db rman command and rman will skip these (using “skip
> readonly” ) OR do I need to first back these up as read only tablespaces for
> rman to skip these during the duplicate.
>
> In other words, where does rman “skip readonly” command check for the
> status of the tablespace, current target database or the information in the
> rman catalog?
>
> Thanks much.
>
> *Amit Verma*
>
>

Other related posts: