To my knowledge you have to have a catalog to make SBT_TAPE work. Its been a
while, but I think I tested something like this and it worked:
export NLS_DATE_FORMAT='DD-MON-YY HH24:MI:SS'
rman auxiliary / catalog [connection details] log=[logfile] cmdfile=[script
file] append
RMAN> startup clone nomount pfile='[pfile location]'
RMAN> set decryption identified by "[decryption password if used]";
RMAN> RUN {
set newname for database to '+DATAC1';
set newname for tempfile 2 to new;
set newname for tempfile 3 to new;
.....
set newname for tempfile 19 to new;
allocate auxiliary channel t1 type SBT_TAPE parms 'SBT_LIBRARY=[sbt library
params]';
allocate auxiliary channel t2 type SBT_TAPE parms 'SBT_LIBRARY=[sbt library
params]';
allocate auxiliary channel t3 type SBT_TAPE parms 'SBT_LIBRARY=[sbt library
params]';
allocate auxiliary channel t4 type SBT_TAPE parms 'SBT_LIBRARY=[sbt library
params]';
DUPLICATE DATABASE [source db name] dbid [dbid]] TO [target db name]
pluggable database [pluggable name], root
UNTIL TIME "TO_DATE('2016-11-15 10:07:00', 'YYYY-MM-DD HH24:MI:SS')"
PFILE [pfile location]
;
}
---
Thanks,
Shane Borden
sborden76@xxxxxxxxx
On Nov 17, 2020, at 2:24 PM, Noveljic Nenad <nenad.noveljic@xxxxxxxxxxxx>
wrote:
Thank you, Shane.
Do you know how to make it work an “sbt_tape” channel and “until” clause and
without “], root backup location”. ?
Best regards,
Nenad
From: Shane Borden <sborden76@xxxxxxxxx <mailto:sborden76@xxxxxxxxx>>
Sent: Dienstag, 17. November 2020 18:52
To: Noveljic Nenad <nenad.noveljic@xxxxxxxxxxxx
<mailto:nenad.noveljic@xxxxxxxxxxxx>>
Cc: ORACLE-L (oracle-l@xxxxxxxxxxxxx <mailto:oracle-l@xxxxxxxxxxxxx>)
<oracle-l@xxxxxxxxxxxxx <mailto:oracle-l@xxxxxxxxxxxxx>>
Subject: Re: duplicate pdb from backup
Currently the only way I am aware of to do this, is to restore a single PDB
to an auxiliary database and then plug / unplug to another destination.
Here is some sample syntax that will work for your backup:
export NLS_DATE_FORMAT='DD-MON-YY HH24:MI:SS'
rman target /
run {
allocate channel dupe1 device type disk format '[backup
location]/%d_bs%s_piece%p_%T_%U.bkp' maxopenfiles=2;
allocate channel dupe2 device type disk format '[backup
location]/%d_bs%s_piece%p_%T_%U.bkp' maxopenfiles=2;
allocate channel dupe3 device type disk format '[backup
location]/%d_bs%s_piece%p_%T_%U.bkp' maxopenfiles=2;
allocate channel dupe4 device type disk format '[backup
location]/%d_bs%s_piece%p_%T_%U.bkp' maxopenfiles=2;
allocate channel dupe5 device type disk format '[backup
location]/%d_bs%s_piece%p_%T_%U.bkp' maxopenfiles=2;
allocate channel dupe6 device type disk format '[backup
location]/%d_bs%s_piece%p_%T_%U.bkp' maxopenfiles=2;
backup as compressed backupset filesperset 4 keep until time 'sysdate+1'
tag ‘pdb_bkup' (database ROOT) (pluggable database 'pdb$seed','[pluggable
name]');
}
For the restore (you can use existing full backup if you have it.:
export NLS_DATE_FORMAT='DD-MON-YY HH24:MI:SS'
rman auxiliary / | tee /db_share/rman_migration/[container
name]/rman_auxiliary/restore_auxiliary.log
startup clone nomount pfile='/db_share/rman_migration/[container
name]/rman_auxiliary/auxcdb_pfile.ora';
set decryption identified by '[tde password if necessary]';
run {
allocate auxiliary channel dupe1 type disk;
allocate auxiliary channel dupe2 type disk;
allocate auxiliary channel dupe3 type disk;
allocate auxiliary channel dupe4 type disk;
allocate auxiliary channel dupe5 type disk;
allocate auxiliary channel dupe6 type disk;
duplicate database to auxcdb
pluggable database [pluggable name], root backup location
'/db_share/rman_migration/[container name]/rman_source'
PFILE /db_share/rman_migration/[container
name]/rman_auxiliary/auxcdb_pfile.ora;
}
---
Thanks,
Shane Borden
sborden76@xxxxxxxxx <mailto:sborden76@xxxxxxxxx>
407-963-4883
____________________________________________________
Please consider the environment before printing this e-mail.
Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.
Important Notice
This message is intended only for the individual named. It may contain
confidential or privileged information. If you are not the named addressee
you should in particular not disseminate, distribute, modify or copy this
e-mail. Please notify the sender immediately by e-mail, if you have received
this message by mistake and delete it from your system.
Without prejudice to any contractual agreements between you and us which
shall prevail in any case, we take it as your authorization to correspond
with you by e-mail if you send us messages by e-mail. However, we reserve the
right not to execute orders and instructions transmitted by e-mail at any
time and without further explanation.
E-mail transmission may not be secure or error-free as information could be
intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also
processing of incoming e-mails cannot be guaranteed. All liability of
Vontobel Holding Ltd. and any of its affiliates (hereinafter collectively
referred to as "Vontobel Group") for any damages resulting from e-mail use is
excluded. You are advised that urgent and time sensitive messages should not
be sent by e-mail and if verification is required please request a printed
version.
Please note that all e-mail communications to and from the Vontobel Group are
subject to electronic storage and review by Vontobel Group. Unless stated to
the contrary and without prejudice to any contractual agreements between you
and Vontobel Group which shall prevail in any case, e-mail-communication is
for informational purposes only and is not intended as an offer or
solicitation for the purchase or sale of any financial instrument or as an
official confirmation of any transaction.
The legal basis for the processing of your personal data is the legitimate
interest to develop a commercial relationship with you, as well as your
consent to forward you commercial communications. You can exercise, at any
time and under the terms established under current regulation, your rights.
If you prefer not to receive any further communications, please contact your
client relationship manager if you are a client of Vontobel Group or notify
the sender. Please note for an exact reference to the affected group entity
the corporate e-mail signature. For further information about data privacy at
Vontobel Group please consult www.vontobel.com <https://www.vontobel.com/>.
