If you are taking backup to the Oracle storage classic container, make sure before you start the backup, they have to be encrypted first else you will receive the errors like below one
RMAN> backup database plus archivelog;
Starting backup at 17-AUG-18
current log archived
using target database control file instead of recovery catalog
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=56 device type=SBT_TAPE
channel ORA_SBT_TAPE_1: Oracle Database Backup Service Library VER=12.2.0.2
channel ORA_SBT_TAPE_1: starting archived log backup set
channel ORA_SBT_TAPE_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=15 RECID=1 STAMP=984399125
input archived log thread=1 sequence=16 RECID=2 STAMP=984399307
channel ORA_SBT_TAPE_1: starting piece 1 at 17-AUG-18
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 08/17/2018 12:15:37
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: non RMAN, but media manager or vendor specific failure, error text:
KBHS-01602: backup piece 01tapfeg_1_1 is not encrypted
So, to avoid the above errors, you should encrypt them first.
RMAN> set encryption on identified by "password" only;
executing command: SET encryption
RMAN> backup database plus archivelog;
Starting backup at 17-AUG-18
current log archived
using channel ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: starting archived log backup set
channel ORA_SBT_TAPE_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=15 RECID=1 STAMP=984399125
input archived log thread=1 sequence=16 RECID=2 STAMP=984399307
input archived log thread=1 sequence=17 RECID=3 STAMP=984399439
channel ORA_SBT_TAPE_1: starting piece 1 at 17-AUG-18
channel ORA_SBT_TAPE_1: finished piece 1 at 17-AUG-18
piece handle=02tapfif_1_1 tag=TAG20180817T121719 comment=API Version 2.0,MMS Version 12.2.0.2
RMAN> backup database plus archivelog;
Starting backup at 17-AUG-18
current log archived
using target database control file instead of recovery catalog
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=56 device type=SBT_TAPE
channel ORA_SBT_TAPE_1: Oracle Database Backup Service Library VER=12.2.0.2
channel ORA_SBT_TAPE_1: starting archived log backup set
channel ORA_SBT_TAPE_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=15 RECID=1 STAMP=984399125
input archived log thread=1 sequence=16 RECID=2 STAMP=984399307
channel ORA_SBT_TAPE_1: starting piece 1 at 17-AUG-18
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 08/17/2018 12:15:37
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: non RMAN, but media manager or vendor specific failure, error text:
KBHS-01602: backup piece 01tapfeg_1_1 is not encrypted
So, to avoid the above errors, you should encrypt them first.
RMAN> set encryption on identified by "password" only;
executing command: SET encryption
RMAN> backup database plus archivelog;
Starting backup at 17-AUG-18
current log archived
using channel ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: starting archived log backup set
channel ORA_SBT_TAPE_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=15 RECID=1 STAMP=984399125
input archived log thread=1 sequence=16 RECID=2 STAMP=984399307
input archived log thread=1 sequence=17 RECID=3 STAMP=984399439
channel ORA_SBT_TAPE_1: starting piece 1 at 17-AUG-18
channel ORA_SBT_TAPE_1: finished piece 1 at 17-AUG-18
piece handle=02tapfif_1_1 tag=TAG20180817T121719 comment=API Version 2.0,MMS Version 12.2.0.2
Wow, What an Outstanding post. I found this too much informatics. It is what I was seeking for. I would like to recommend you that please keep sharing such type of info.If possible, Thanks. Ultimate Encrypted Phone Solutions Chat PGP
ReplyDelete