Overlapped RMAN processes

Question

Hi Guys,
I have a problem with rman full backups and archivelog backups. The problem occurs when the full backup schedule is run and in the middle is started an archivelog backup schedule. Both run properly, but this generates a problem. With this behavior, the archives backed up with the archivelog backup schedule are not included with the backupset of full backup, and more, because both schedules has different expiration time, our archivelog backup schedule have an expiration time lower than our weekly full backup schedule.
Then, sometimes, when we try to restore a weekly full backup, we find that some needed archives are not in the backupset of the full backup, they are in the backupset of archives , with the lower expiration time, and sometimes expired. Therefore, the recover  is not possible.
The question is:
Is there are any way to lock, at RMAN level, to avoid the start of the archives backup schedule, until the full backup is finished?
Thank you very much for your help.

Answer 1

Hello saurabh,
The script of full backup is the one that comes with the Netbackup Enterprise tool, and is:
RUN {
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
BACKUP
    $BACKUP_TYPE
    SKIP INACCESSIBLE
    TAG hot_db_bk_level0
    FILESPERSET 5
    FORMAT 'bk_%s_%p_%t'
    DATABASE;
    sql 'alter system archive log current';
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
BACKUP
   filesperset 20
   FORMAT 'al_%s_%p_%t'
   ARCHIVELOG ALL DELETE INPUT;
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
BACKUP
    FORMAT 'cntrl_%s_%p_%t'
    CURRENT CONTROLFILE;
RELEASE CHANNEL ch00;
And the script for the archives that we run every 4 hours and when the archives filesystem reaches % of use, is:
RUN {
sql 'alter system archive log current';
ALLOCATE CHANNEL ch00
    TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch01
    TYPE 'SBT_TAPE';
SEND 'NB_ORA_CLIENT=terra01,NB_ORA_POLICY=ORACLE_REDO_CRMAX,NB_ORA_SERV=mserver1,NB_ORA_SCHED=Default-Application-Backup';
BACKUP
    FORMAT 'arch_u%u_s%s_p%p_t%t'
    ARCHIVELOG
        ALL
    DELETE INPUT;
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
ALLOCATE CHANNEL ch00
    TYPE 'SBT_TAPE';
SEND 'NB_ORA_CLIENT=terra01,NB_ORA_POLICY=ORACLE_REDO_CRMAX,NB_ORA_SERV=mserver1,NB_ORA_SCHED=Default-Application-Backup';
BACKUP
    FORMAT 'ctrl_u%u_s%s_p%p_t%t'
    CURRENT CONTROLFILE;
RELEASE CHANNEL ch00;
Seems that RMAN don't have any mechanism that prevent the delete of one archive needed by an previous rman process in running state.