RMAN backup for lack of archive log - Urgent

Similar Questions

• Considerations to keep the retention of RMAN backup for 1 year

  Dear all,

  We use 10 g 2 2-node CCR on Windows Server. We use Netbackup Symentec 7.5 for the backup of Oracle databases. We want to change the retention period of the RMAN backups for 1 year. Another change that the window recovery from RMAN backup at 365, what are the other considerations (any other configuration change, another point etc.), we should be aware of?

  Best regards

  Riaz

  Your controlfile would spend unusually large.  It can result in CF-queue waiting for when the generation of the archivelogs and performing backups.

  Hemant K Collette

• RMAN - RETRIEVE the backup complete and necessary archives Logs of SBT_TAPE to disk

  Hello

  I've never done this before and no one on my team seems to have idea if possible. In our environment, backups are performed using netbackup to bands using RMAN. I have a request to recover a good full backup of an oracle database (where we can restore the database, if required in the future) of January 13 and place in a way they provided for example: / dbbkup/dbName/files.

  The backup team tied the tapes required for this backup, which in this case is January 13, 2016, see below. We can only use RMAN to restore this backup, but I don't want to restore this backup on a database, instead would like to capture the full backup and zip and place it in the provided path. Is there is a possibility with RMAN?

  If yes I would appreciate the full commands necessary to capture all of the basic + archivelogs (how can I determine what archivelogs are needed?)

  I came with thisbut do not know if this will do.

  Run {}

  until ' to_date (' 01 2016 13 11:00 ', 'YYYY MM DD HH24') ";

  allocate auxiliary channels ch1 type 'sbt_tape '.

  DESTINATION FOR RESTORE GAME ' / dbbkup/dbName/files ";

  RESTORE THE DATABASE;

  }

  OPERATION STATUS OBJECT_TYPE START_TIME, END_TIME

  --------------------------------- ----------------------- ------------- ------------------- -------------------

  BACKUP COMPLETE DB FULL 01/13 / 01/13 2016:11:01:51 / 2016:11:23:03

  
  

  
  

  
  

  RMAN > backup databas list;

  Time of accomplishment BS key Type LV size device Type elapsed time

  ------- ---- -- ---------- ----------- ------------ --------------------

  1096026768 complete SBT_TAPE 4.44 G 00:11:01 January 13, 2016 23:12:47

  BP key: 1096026774 status: AVAILABLE Tablet: NO Tag: TAG20160113T230146

  Handle: e1qra7eq_1_1 Media:

  List of defined backup data files 1096026768

  Name of file LV Type cash SNA cash time

  ---- -- ---- ---------- -------------------- ----

  2 full 342817549 13 January 2016 23:01:46 /hostname/db/sid/oradata3/undotbs01.dbf

  4 integer 342817549 13 January 2016 23:01:46 /hostname/db/sid/oradata1/users01.dbf

  6 integer 342817549 13 January 2016 23:01:46 /hostname/db/sid/oradata1/_data_sid_01.dbf

  9 whole 342817549 13 January 2016 23:01:46 /hostname/db/sid/oradata1/_indx_01.DBF

  Time of accomplishment BS key Type LV size device Type elapsed time

  ------- ---- -- ---------- ----------- ------------ --------------------

  1096026769 complete SBT_TAPE 4.11 G 06:12:00 January 13, 2016 23:13:52

  BP key: 1096026775 status: AVAILABLE Tablet: NO Tag: TAG20160113T230146

  Handle: e2qra7eq_1_1 Media:

  List of defined backup data files 1096026769

  Name of file LV Type cash SNA cash time

  ---- -- ---- ---------- -------------------- ----

  342817550 full 1 January 13, 2016 23:01:46 /hostname/db/sid/oradata1/system01.dbf

  3 full 342817550 13 January 2016 23:01:46 /hostname/db/sid/oradata1/tools01.dbf

  5 integer 342817550 13 January 2016 23:01:46 /hostname/db/sid/oradata1/sysaux01.dbf

  7 full 342817550 13 January 2016 23:01:46 /hostname/db/sid/oradata1/_indx_sid_01.dbf

  8 whole 342817550 13 January 2016 23:01:46 /hostname/db/sid/oradata1/l_data_01.DBF

  
  

  
  

  
  

  
  

  
  

  Yes, we cannot copy the backupsets of a band on the disc with RMAN.

  The only option is to restore the database to a separate host computer (or we can restore the database to a filesystem separte or diskgroup within the same host of source database), and backup the database on a disk in compressed format.

  -Thank you

• RMAN > skip the file to archive log < string > already saved 1 time

  I'm trying to copy an Archivelog of ASM to the file system, but I get the following error message.
  
  How can I use the force to do? I can't understand the correct syntex. Please advise!
  

  RMAN> copy archivelog '+FRA/CCPROD/ARCHIVELOG/2011_01_31/thread_1_seq_131491.678.741834671' to '/NEW_backups/backups/thread_1_seq_131491.678.741834671';
  
  Starting backup at 31-JAN-11
  using channel ORA_DISK_1
  skipping archive log file +FRA/ccprod/archivelog/2011_01_31/thread_1_seq_131491.678.741834671; already backed up 1 time(s)
  Finished backup at 31-JAN-11

  Hello

  in RMAN, you have activated OPTIMAZTION as WE

  RMAN > SET UP OPTIMIZATION BACKUP;

  and try your previous order, it should work, if all post errors. Thank you.

• Backup the database with archiving logs lost

  How can I get a backup of the database when all archive logs have been lost?

  So, it looks that you use RMAN to back up, since all the archivelog went. You can do

  RMAN> crosscheck archivelog all;
  
  RMAN> delete archivelog all;
  

  then make a backup.

• Causing the system RMAN backups for not responding

  Need some help here. I inherited a system in which has about 65 GB memory, Linux 64 - bit - 16 processors. Whenever an RMAN backup is performed, else cannot do anything. The load average is about 10 (max). My theory is that it is the init.ora parameters, but not sure... Here's the deal:
  
  SGA_MAX_SIZE = 47GB
  SGA_TARGET = 0
  shared_pool_size = 5G
  JAVA_POOL_SIZE = 1 G
  LARGE_POOL_SIZE = 0
  db_cache_size = 38G
  
  I'll look into what I have to change. I just wanted to get other opinions since I inherited a wasp nest and need elements good enough before you can change all the settings. All documents, Metalink, etc that you can provide to support a change in these parameters would be great. Thank you.

  Hello

  You can check http://download.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmtunin.htm

  You can use the formula to set the size of the pool. If you do not install the largest basin of the rman uses memory of shared pool which can cause the problem of e/s/execution.

  LARGE_POOL_SIZE = number_of_allocated_channels * (16 MB + (4 * size_of_tape_buffer))

  Hope this will help you.

  Thank you
  Krishna

• Problem with the archive log when you use RMAN for backup and restore (11g 2)

  Hello world
  Please help me solve this problem.
  I'm just beginner in Oracle Database (11 g 2). Today, I had a problem, I tried to back up and restore my db by RMAN. I delete all the files in /u01/app/oracle/oradata/orcl / * , then I restore them easily, but the point is I have a table, I can restore Hungarian, but cannot restore anything ranks in it (something wrong with step restore database). I'll tell the detail below.
  -First, I create a 'Day' with command table create table hr.day (varchar (20)) day. Then I backup complete by this:
  run{
allocate channel bkp device type DISK FORMAT '/u01/backup/DB_FULL_%d_%T_s%s_p%p' ;
backup as compressed backupset incremental level 0 tag 'DB_FULL' database include current controlfile;
backup as compressed backupset tag 'ARCL_BKP_FULL' archivelog all delete input;
crosscheck archivelog all;
crosscheck backup;
delete noprompt obsolete;
release channel bkp;
}
  

  
  D ' other hand, I have insert 'Monday' to table. then do an incremental backup by this:

  run{
allocate channel bkp device type DISK FORMAT '/u01/backup/DB_INC_%d_%T_s%s_p%p' ;
backup as compressed backupset incremental level 1 tag 'DB_INC' database include current controlfile;
backup as compressed backupset tag 'ARCL_BKP_INC' archivelog all delete input;
crosscheck archivelog all;
crosscheck backup;
delete noprompt obsolete;
release channel bkp;
}

  Repeat 7 times (Monday-> Saturday). And I got these files:

  [oracle@rac ~]$ ls -l /u01/backup/
total 400280
-rw-r----- 1 oracle oinstall  10158080 Jan 20 07:23 c-1428943247-20160120-01
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:04 c-1428943247-20160120-02
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:05 c-1428943247-20160120-03
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:06 c-1428943247-20160120-04
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:08 c-1428943247-20160120-05
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:08 c-1428943247-20160120-06
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:09 c-1428943247-20160120-07
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:32 c-1428943247-20160120-08
-rw-r----- 1 oracle oinstall 296337408 Jan 20 07:23 DB_FULL_ORCL_20160120_s89_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 07:23 DB_FULL_ORCL_20160120_s90_p1
-rw-r----- 1 oracle oinstall   2266624 Jan 20 07:23 DB_FULL_ORCL_20160120_s91_p1
-rw-r----- 1 oracle oinstall   4073984 Jan 20 07:23 DB_FULL_ORCL_20160120_s92_p1
-rw-r----- 1 oracle oinstall  11201536 Jan 20 07:23 DB_FULL_ORCL_20160120_s93_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:05 DB_INC_ORCL_20160120_s100_p1
-rw-r----- 1 oracle oinstall    146944 Jan 20 08:05 DB_INC_ORCL_20160120_s101_p1
-rw-r----- 1 oracle oinstall    884736 Jan 20 08:06 DB_INC_ORCL_20160120_s103_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:06 DB_INC_ORCL_20160120_s104_p1
-rw-r----- 1 oracle oinstall     82432 Jan 20 08:06 DB_INC_ORCL_20160120_s105_p1
-rw-r----- 1 oracle oinstall    294912 Jan 20 08:07 DB_INC_ORCL_20160120_s107_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:07 DB_INC_ORCL_20160120_s108_p1
-rw-r----- 1 oracle oinstall     18944 Jan 20 08:08 DB_INC_ORCL_20160120_s109_p1
-rw-r----- 1 oracle oinstall    155648 Jan 20 08:08 DB_INC_ORCL_20160120_s111_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:08 DB_INC_ORCL_20160120_s112_p1
-rw-r----- 1 oracle oinstall    131584 Jan 20 08:08 DB_INC_ORCL_20160120_s113_p1
-rw-r----- 1 oracle oinstall    647168 Jan 20 08:09 DB_INC_ORCL_20160120_s115_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:09 DB_INC_ORCL_20160120_s116_p1
-rw-r----- 1 oracle oinstall      8704 Jan 20 08:09 DB_INC_ORCL_20160120_s117_p1
-rw-r----- 1 oracle oinstall   2203648 Jan 20 08:04 DB_INC_ORCL_20160120_s95_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:04 DB_INC_ORCL_20160120_s96_p1
-rw-r----- 1 oracle oinstall   1899008 Jan 20 08:04 DB_INC_ORCL_20160120_s97_p1
-rw-r----- 1 oracle oinstall    327680 Jan 20 08:05 DB_INC_ORCL_20160120_s99_p1


  And
  RMAN> list backup summary;
List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
80      B  0  A DISK        20-JAN-16       1       1       YES        DB_FULL
81      B  0  A DISK        20-JAN-16       1       1       YES        DB_FULL
82      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
83      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
84      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
85      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T072332
86      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
87      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
88      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
89      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080440
90      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
91      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
92      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
93      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080545
94      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
95      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
96      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
97      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080657
98      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
99      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
100     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
101     B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080801
102     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
103     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
104     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
105     B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080844
106     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
107     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
108     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC

  My configuration of rman:
  RMAN> show all;
RMAN configuration parameters for database with db_unique_name ORCL are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u01/backup/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/u01/backup/backup_df%t_s%s_s%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome/dbs/snapcf_orcl.f'; # default

  - Thirdly, i removed all file in /u01/app/oracle/oradata/orcl/*. then restore control file from the newest backup control file (saturday backup) + restore database. Seem nothing's wrong here.
RMAN> restore controlfile from '/u01/backup/c-1428943247-20160120-08';
Starting restore at 20-JAN-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=18 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=20 device type=DISK
channel ORA_DISK_2: skipped, AUTOBACKUP already found
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:09
output file name=/u01/app/oracle/oradata/orcl/control01.ctl
output file name=/u01/app/oracle/flash_recovery_area/orcl/control02.ctl
Finished restore at 20-JAN-16

RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
released channel: ORA_DISK_2

RMAN> restore database;
Starting restore at 20-JAN-16
Starting implicit crosscheck backup at 20-JAN-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=20 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=18 device type=DISK
Crosschecked 29 objects
Finished implicit crosscheck backup at 20-JAN-16

Starting implicit crosscheck copy at 20-JAN-16
using channel ORA_DISK_1
using channel ORA_DISK_2
Finished implicit crosscheck copy at 20-JAN-16

searching for all files in the recovery area
cataloging files...
no files cataloged

using channel ORA_DISK_1
using channel ORA_DISK_2

channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/orcl/users01.dbf
channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/orcl/example01.dbf
channel ORA_DISK_1: reading from backup piece /u01/backup/DB_FULL_ORCL_20160120_s89_p1
channel ORA_DISK_1: piece handle=/u01/backup/DB_FULL_ORCL_20160120_s89_p1 tag=DB_FULL
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:15
Finished restore at 20-JAN-16


  -Fourth, the problem here, I got the database;
.. .every oky until this line...
starting media recovery

channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=15
channel ORA_DISK_1: reading from backup piece /u01/backup/DB_INC_ORCL_20160120_s117_p1
channel ORA_DISK_1: piece handle=/u01/backup/DB_INC_ORCL_20160120_s117_p1 tag=ARCL_BKP_INC
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/u01/app/oracle/flash_recovery_area/ORCL/archivelog/2016_01_20/o1_mf_1_15_c9xsyx9k_.arc thread=1 sequence=15
unable to find archived log
archived log thread=1 sequence=1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/20/2016 08:50:22
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1 and starting SCN of 1205841

The error said that it is impossible to find the archived log thread = 1 sequence = 1. Then I check it with this command always there (oh, I'm wrong?)
RMAN> list backup of archivelog all;
List of Backup Sets
===================
BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
82      2.16M      DISK        00:00:00     20-JAN-16     
        BP Key: 82   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
        Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s91_p1

  List of Archived Logs in backup set 82
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
1    1       1154833    20-JAN-16 1177422    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
83      3.88M      DISK        00:00:00     20-JAN-16     
        BP Key: 83   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
        Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s92_p1

  List of Archived Logs in backup set 83
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
1    1       1162729    20-JAN-16 1188784    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
84      10.68M     DISK        00:00:01     20-JAN-16     
        BP Key: 84   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
        Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s93_p1

  List of Archived Logs in backup set 84
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    2       1177422    20-JAN-16 1201833    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
88      1.81M      DISK        00:00:01     20-JAN-16     
        BP Key: 88   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s97_p1

  List of Archived Logs in backup set 88
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    3       1201833    20-JAN-16 1204844    20-JAN-16
  1    4       1204844    20-JAN-16 1204893    20-JAN-16
  1    5       1204893    20-JAN-16 1204958    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
92      143.00K    DISK        00:00:00     20-JAN-16     
        BP Key: 92   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s101_p1

  List of Archived Logs in backup set 92
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    6       1204958    20-JAN-16 1205034    20-JAN-16
  1    7       1205034    20-JAN-16 1205253    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
96      80.00K     DISK        00:00:00     20-JAN-16     
        BP Key: 96   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s105_p1

  List of Archived Logs in backup set 96
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    8       1205253    20-JAN-16 1205354    20-JAN-16
  1    9       1205354    20-JAN-16 1205433    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
100     18.00K     DISK        00:00:00     20-JAN-16     
        BP Key: 100   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s109_p1

  List of Archived Logs in backup set 100
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    10      1205433    20-JAN-16 1205519    20-JAN-16
  1    11      1205519    20-JAN-16 1205559    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
104     128.00K    DISK        00:00:00     20-JAN-16     
        BP Key: 104   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s113_p1

  List of Archived Logs in backup set 104
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    12      1205559    20-JAN-16 1205624    20-JAN-16
  1    13      1205624    20-JAN-16 1205739    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
108     8.00K      DISK        00:00:00     20-JAN-16     
        BP Key: 108   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s117_p1

  List of Archived Logs in backup set 108
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    14      1205739    20-JAN-16 1205796    20-JAN-16
  1    15      1205796    20-JAN-16 1205840    20-JAN-16

  
If i ignore it and open the database, just my table in full backup come back but rows was not restored. I'm sure the problem is my archive log backup but i don't know how to solve it. Plz help me.

  Sorry for a long post.


  > 1 and from the 1205841 SNA sequence

  The SCN that indicates Oracle is above the range of SNA that you have in the ArchiveLog backups for sequence 1 to 15 (15 sequence ends at 1205840).

  The message

  channel ORA_DISK_1: restoring archives Journal

  Archives journal thread = 1 sequence = 15

  channel ORA_DISK_1: backup/u01/backup/DB_INC_ORCL_20160120_s117_p1 piece reading

  channel ORA_DISK_1: piece handle = / u01/backup/DB_INC_ORCL_20160120_s117_p1 tag = ARCL_BKP_INC

  indicates that he has restored the sequence up to 15

  You can check the log file alert database instance for messages on the fact of recovery.

  He is now asking sequence #1 it seems you did a RESETLOGS after sequence #15.

  Note: If you have NOT issued a COMMIT after the line is INSERTED in the table 'Day', the recovery of the database will have no * transactions * to retrieve.  An uncomitted transaction is cancelled.

  Hemant K Collette

• RMAN-03009 and ORA-01858 everything by backing up archiving logs

  Hello!
  
  Since today, I get the above errors to backup the fra tape archiving logs. I tried the following: error ORA-01858 in RMAN during backup backupset format ' / test/rman/%U'
  If I manually do the backup for a client, it works!
  
  environment:
  Server: windows 2008 standard server
  Oracle: 10.2.0.4.0
  
  configuration of RMAN:
  CONFIGURE RETENTION POLICY TO THE 5 DAY RECOVERY WINDOW;
  CONFIGURE BACKUP OPTIMIZATION
  SET UP DEFAULT DISK DEVICE TYPE; # by default
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
  SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
  CONFIGURE ENCRYPTION OF DATABASE # by default
  CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFAPEX. ORA'; # by default
  
  Error log:
  Recovery Manager: Release 10.2.0.4.0 - Production on Thu Oct 1 04:30 2009
  
  Copyright (c) 1982, 2007, Oracle. All rights reserved.
  
  connected to target database: APEX (DBID = 1331326226)
  connected to the recovery catalog database
  
  RMAN > sql 'alter system archive log current;
  2 > run {}
  3 > #-> drive backup
  4 > backup archivelog all;
  5 > # FRA-> band
  6 > allocate channel ch1 type 'sbt_tape '.
  7 > PARMS = "BLKSIZE = 262144, ENV = (CvClientName = ora5neu, CvInstanceName = Instance001)"; "
  8 > save the recovery area.
  {9 >}
  10 >
  SQL statement: alter system archive log current
  
  From backup 1st October 09
  Current archived log
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid = devtype 81 = DISK
  skip the log file archive D:\FRA\APEX\ARCHIVELOG\2009_09_10\O1_MF_1_2720_5BKO9BOL_. ARC; already saved 1 time
  ...
  skip the log file archive D:\FRA\APEX\ARCHIVELOG\2009_10_01\O1_MF_1_2981_5D7PZDXX_. ARC; already saved 1 time
  channel ORA_DISK_1: from archive newspaper backupset
  channel ORA_DISK_1: specification of archive log backup set
  archive log entry thread = 1 sequence = 2733 recid = 2733 stamp = 697286083
  archive log entry thread = 1 sequence = 2734 recid = 2734 stamp = 697293002
  archive log entry thread = 1 sequence = 2735 recid = 2735 stamp = 697293004
  archive log entry thread = 1 sequence = 2856 recid = 2856 stamp = 698142602
  archive log entry thread = 1 sequence = 2857 recid = 2857 stamp = 698142603
  archive log entry thread = 1 sequence = 2982 recid = 2982 stamp = 699078603
  archive log entry thread = 1 sequence = 2983 recid = 2983 stamp = 699078605
  channel ORA_DISK_1: starting piece 1 to October 1 09
  channel ORA_DISK_1: finished piece 1 to October 1 09
  piece handle = D:\FRA\APEX\BACKUPSET\2009_10_01\O1_MF_ANNNN_TAG20091001T043006_5D8520K4_. Tag BKP = comment TAG20091001T043006 = NONE
  channel ORA_DISK_1: complete set of backups, time: 00:00:03
  Backup finished on 1st October 09
  
  From control file and SPFILE Autobackup 1st October 09
  piece handle = D:\FRA\APEX\AUTOBACKUP\2009_10_01\O1_MF_S_699078626_5D8522W8_. Comment BKP = NONE
  File control finished and SPFILE Autobackup to on 1 October 09
  
  output channel: ORA_DISK_1
  allocated channel: ch1
  channel ch1: sid = 81 = SBT_TAPE devtype
  channel ch1: CommVault Systems for Oracle: Version 7.0.0 (BUILD76)
  
  From backup 1st October 09
  specification does not match any data file copy in the repository
  skip the log file archive D:\FRA\APEX\ARCHIVELOG\2009_09_10\O1_MF_1_2720_5BKO9BOL_. ARC; already saved 4 times
  ...
  jump key 5203 backupset; already saved 1 time
  channel ch1: from archive newspaper backupset
  channel ch1: specification of archive log backup set
  archive log entry thread = 1 sequence = 2982 recid = 2982 stamp = 699078603
  archive log entry thread = 1 sequence = 2983 recid = 2983 stamp = 699078605
  channel ch1: starting piece 1 to October 1 09
  channel ch1: finished piece 1 to October 1 09
  piece handle = i2kqm5vv_1_1 tag = comment TAG20091001T043031 = API 2.0, MMS Version 7.0.0.76 Version
  channel ch1: complete set of backups, time: 00:00:16
  entry count = 4670 stamp = 699064230 = creation_time backupset 1st October 09
  channel ch1: starting piece 1 to October 1 09
  RMAN-03009: failure of the backup command on channel ch1 at 2009-10-01 04:31:19
  ORA-01858: a non-digit character was found here where was waiting for a digital
  continue other job steps, not a not working will not re-run
  entry count = 4672 stamp = 699078622 = creation_time backupset 1st October 09
  channel ch1: starting piece 1 to October 1 09
  channel ch1: backup D:\FRA\APEX\BACKUPSET\2009_10_01\O1_MF_ANNNN_TAG20091001T043006_5D8520K4_ piece. BKP
  piece handle = i0kqm5uu_1_2 comment = API Version 2.0, Version MMS 7.0.0.76
  channel ch1: finished piece 1 to October 1 09
  channel ch1: complete set of backups, time: 00:00:07
  entry count = 4673 stamp = 699078626 = creation_time backupset 1st October 09
  channel ch1: starting piece 1 to October 1 09
  output channel: ch1
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03009: failure of the backup command on channel ch1 at 01/10/2009 04:31:35
  ORA-01858: a non-digit character was found here where was waiting for a digital
  
  Complete recovery manager.
  
  Thanks for your help!
  
  Ciao,.
  Christian

  See my note of the Support of Oracle:

  Subject: RMAN backup fails with RMAN-03009 ORA-01858 ORA-01861
  DOC - ID: 744047.1 Type: PROBLEM
  Modification date: 20 March 2009 status: MODERATE

  This could be a NLS_DATE_FORMAT / NLS_LANG questioned.

• RMAN alert log Message: ALTER SYSTEM ARCHIVE LOG

  Creates a new database Oracle 10.2.0.4 and now see "ALTER SYSTEM ARCHIVE LOG" in the journal of the alerts that when online RMAN backup is executed:
  Wed Sep 26 21:52:03 2009
  ALTER SYSTEM ARCHIVE LOG
  Wed Sep 26 21:52:03 2009
  Thread 1 Advanced to record the sequence of 35 (switch LGWR)
  Currently Journal # 2 seq # 35 mem # 0: /u01/app/oracle/oradata/aatest/redo02.log
  Currently Journal # 2 seq # 35 mem # 1: /u03/oradata/aatest/redo02a.log
  Wed Sep 26 21:53:37 2009
  ALTER SYSTEM ARCHIVE LOG
  Wed Sep 26 21:53:37 2009
  Thread 1 Advanced to record the sequence of 36 (switch LGWR)
  Currently Journal # 3 seq # 36 mem # 0: /u01/app/oracle/oradata/aatest/redo03.log
  Currently Journal # 3 seq # 36 mem # 1: /u03/oradata/aatest/redo03a.log
  Wed Sep 26 21:53:40 2009
  From control autobackup
  Autobackup written control disk device
  handle ' / u03/exports/backups/aatest/c-2538018370-20090826-00'.
  
  I not publish a swiitch log command. The RMAN commands, I am running are:
  CONFIGURE REDUNDANCY 2 RETENTION STRATEGY;
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT for DEVICE TYPE DISK TO ' / u03/exports/backups/aatest/%F';
  SET UP THE DEVICE TYPE DISK TYPE OF BACKUP TO COMPRESSED BACKUPSET;
  CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / u03/exports/backups/aatest/%d_%U';
  BACKUP DATABASE MORE ARCHIVELOG;
  DELETE NOPROMPT OBSOLETE;
  DELETE NOPROMPT ARCHIVELOG UNTIL ' SYSDATE-2';
  
  I do not see this message on any other 10.2.0.4 instances. Someone has seen this and if yes why it shows in the log?
  
  Thank you
  
  Curt Swartzlander

  There is no problem with the log command. Please refer to the documentation for more information on the syntax 'PLUS ARCHIVELOG '.

  http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14192/bkup003.htm#sthref377

  Adding BACKUP... MORE ARCHIVELOG causes RMAN, follow these steps:

  * 1. Executes the ALTER SYSTEM ARCHIVE LOG CURRENT command.*

  * 2. All runs THE BACKUP ARCHIVELOG. Note that if backup optimization is enabled, then RMAN passes the newspapers that he has already saved to the specified device

  * 3. Backup the rest of the files specified in BACKUP command.*

  * 4. Executes the ALTER SYSTEM ARCHIVE LOG CURRENT command.*

  * 5. Backup of all remaining archived logs generated during the backup.*

  This ensures that backups of data taken when the command file is recoverable in a consistent state.

• When ALTER SYSTEM ARCHIVE LOG happens implicitly...

  Hello
  
  When you scan the v$ archived_log SIDE primary SCHOOL, I saw below output
  
  NAME OF CREATOR REGISTR SEQUENCE # FAL
  -------------------------- ------- ------------ ----------------- ---
  /U05/prod/archivelogs/ARC_816992406_1_22885.dbf ARCH ARCH 22885 No.
  /U05/prod/archivelogs/ARC_816992406_1_22886.dbf FGRD FGRD 22886 No.
  
  
  Then I went to the alert log file and search for the sequence #, I found that
  
  When the newspaper switch happens through * ALTER SYSTEM ARCHIVE LOG *, then this sequence archive log CREATOR and REGISTRAR will be FGRD.
  What command of newspaper happens automatically (90% complete log file), then this sequence archive log CREATOR and REGISTRAR will be ARCH.
  
  
  If * ALTER SYSTEM ARCHIVE LOG * happens synchronously means control will not return to the process unless and until the underlying log file has been
  archived completely, so the CREATOR and the REGISTRAR is FGRD.
  
  My question is, under what circumstances * ALTER SYSTEM ARCHIVE LOG * happen implicitly.
  
  
  Thank you

  Hello

  user9085814 wrote:
  Thanks for the reply...

  I agree with you.

  The environment that I take abt is DATAGUARD Enviornment.

  I have not published ALTER SYSTEM ARCHIVE LOG CURRENT of any session (foreground process) of the primary DB.
  But I can still see ALTER SYSTEM ARCHIVE LOG in the log to alter.

  When you call the command ALTER SYSTEM ARCHIVE LOG CURRENT , then oracle write in the journal of the alerts as:

  On primary

  
   Wed May 15 09:16:56 2013
   Archived Log entry 789 added for thread 1 sequence 396 ID 0xf23a6e3f dest 1:
   *ALTER SYSTEM ARCHIVE LOG*
   Thread 1 cannot allocate new log, sequence 398
  

  >

  So my question on what scenario ALTER SYSTEM ARCHIVE LOG will be captured in the log of alerts.
  because it's a mistake to run foreground process ALTER SYSTEM ARCHIVE LOG .

  Have you had a logs archived backup RMAN script which is called ALTER SYSTEM ARCHIVE LOG CURRENT

   RMAN> run
             {
                sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
                backup  archivelog all delete all input;
             }
  

  If you try the command ALTER SYSTEM ARCHIVE LOG CURRENT on stanby, you get error ORA-01109: database is not open. This means database is not open READ/WRITE mode.
  Then we can use ALTER SYSTEM ARCHIVE LOG CURRENT on the standby database.

  Thanks for the interesting thread
  Mr. Mahir Quluzade
  http://www.Mahir-quluzade.com

• DB Back at a specific time with archiving logs (up to cancel or time?)

  I'll try to be as clear as possible with my goals and limits of the system, I'm working with:
  
  1. we have a test instance of our Oracle database I want to be able to update with data from the instance of production at any time, without having to close the production database or tablespaces in backup mode to warm.
  
  2. the two systems are HP Itanium boxes with different numbers of processors and RAM. These differences have been taken into account in the file init.ora for instances of the DB.
  
  3. test and production instances use a SAN to maintain the following file systems: ora_redo1, ora_redo2, ora_archlog, oradata10g. The test instance uses snapshots SAN (HP EVA SAN series) the production file systems into the data when necessary. The problem is that the single window to do it is when the production system is down for maintenance every night, which is about a 20 minute period. I want to escape this limitation.
  
  I do use the aforementioned SAN HP to take snapshots of filesystems on the production system. I'm doing this, while the production DB is running. I then import these snapshots in the test system, run a fsck to the integrity of system files, and then start the Oracle instance as follows:
  
  Startup mount
  
  Then I run the following query, I found online to determine the current redo log:
  Select Member from v$ logfile lf, v$ log l where l.status = 'CURRENT' and lf.group #= l.group #;
  
  Then I try to run a recovery as follows:
  recover database using backup controlfile until cancel;
  
  When you are prompted, enter the path to the first of the current redo logs and press ENTER. After waiting, sometimes it is said that the recovery is completed, other times it stops saying there was an error and that several files are required to standardize the DB.
  
  I took the road above because to do a recovery until the time (which is what I really want to do) kept invited me for the next archiving log in the sequence that did not exist when I took the picture of SAN. This is my back up to the order of time:
  
  recover database until time ' yyyy-mm - dd:hh:mm:ss using backup controlfile;
  
  What I want to do is to take the SAN snapshot and then retrieve the database about a minute before the snapshot by using the archive logs. I don't want to use RMAN, since it seems like overkill for this purpose. A simple recovery to a specific point in time seems to be all that is needed and I archive logs which, I suppose, SHOULD help me get there. Even if I lose the value of the last hour of trading, I could live with that. But my tests affect the recovery time even 12 hours sooner more resulted in a command prompt to the next, no archivelog.
  
  I note also that I even tried to copy the next log archiving on once there is and the recovery would then invite me to the next archive log! I recognize now that I know really much about Oracle or DBs, but it's my duty to try and make it possible to "Refresh" the DB test with the latest data with no impact on production DB.
  
  The reason why I want to use the hot backup mode, it is that I don't know the other DB schema that there probably 58 or more storage spaces. The goal is to use SAN snapshots for their speed instead of having to take RMAN files and copy them to the test instance. I don't know that I'm not the only person who has already tried that. But most of what I found online made reference on RMAN, hot backup mode, or downtime. The first two take advantage of SAN snapshots for a quick exchange of all Oracle file systems, and I can't afford downtime other than this window during the night. Is there a reason that did not retrieve it in time even if I archive logs?
  
  One last point. Recover until cancel actually worked a few times, but it seems to be sporadic. Probably has something to do with what was going on on the production DB when I created the SAN snapshots. In fact, I thought I had a solution with recover until cancel last week until he failed three times in a row.

  As I've mentioned before, I highly recommend setting the database in BACKUP mode.

  You can see a collection of papers to the
  http://www.Oracle.com/technology/deploy/availability/htdocs/oscp_papers.html
  Unfortunately, Oracle stopped the Oracle storage compliance program and now he leaves vendors to certify their memory and their file system. The documents on the site of the OSCP are now "old."

  Each storage provider has also published articles. I worked with snapshot / SnapClone / SnapView / technologies ShadowImage EMC CLARiiON, Hitachi Lightning, IBM ESS, etc. of NetApp. Only the EMC engineer did not recommend the BACKUP mode. However, when you test the EMC under high concurrency, we found corrupt index when we used the image of the snapshot. I returned to the EMC site and downloaded a specified document that we had to use the BACKUP mode and SUSPEND / SUMMARY - and why said. The main lines were "However, the operation of fracturing the clones or from sessions of snapshot with multiple devices is not atomic. Particular periods may exist as well and all of the Oracle files being backed up can seem to have lost the required I/O order sequencing. ». So it really depends on the technology. The engineer later confirmed that it was a requirement on the particular type of storage we were using, but not on the DMX class (or something like that - I don't remember all the details of a previous task a few years ago).

  (White papers of all other providers also included BACKUP mode).

  Contact the vendor for their own white papers.

  Hemant K Collette
  http://hemantoracledba.blogspot.com

• RMAN backup V1

  Hi all

  11.2.0.1

  AIX 6.1

  I have been using RMAN backup for most of our databases by using this parameter:

  run

  {

  CONFIGURE REDUNDANCY 1 RETENTION STRATEGY;

  compressed backup backupset database more archivelog;

  backup current controlfile to sleep;

  backup current controlfile;

  overlap archivelog all;

  cross-checking of backup;

  delete expired backup noprompt.

  delete noprompt expired archivelog all;

  delete noprompt obsolete;

  }

  And most of them succeeded, except this one with the error:

  RMAN-06207: WARNING: 54 items could not be removed for DISC due channels

  RMAN-06208: status do not match.  Use the OVERLAP command to set status

  RMAN-06210: list of relevant objects

  RMAN-06211: =.

  RMAN-06212: filename/Type object Handle

  RMAN-06213: --------------- ---------------------------------------------------

  RMAN-06214: copy of the data /proddata/oradata/PROD/datafile/dbs1m3a.dbf file

  RMAN-06214: copy of the data /proddata/oradata/PROD/datafile/dbs1m4b.dbf file

  RMAN-06214: copy of the data /proddata/oradata/PROD/datafile/dbs1m1b.dbf file

  RMAN-06214: copy of the data /proddata/oradata/PROD/datafile/dbs1m3b.dbf file

  I said that I have to use CROSSCHECK, but I already have this in my parameter .rcv above right?

  Help, please...

  Thank you very much

  zxy

  yxes2013 wrote:

  I'm confused with a lot of OVERLAP

  I also check above dbf files, and they are most active. Why it checks rman for deletion? Is this a bug?

  Helpppp...

  file a bug report

• How can I remove the old files of RMAN backup

  Hi all
  
  We have configured the RMAN backup for one of our customers [10.2.0.3] PROD instance in December 2010.
  
  Now my doubt is how can I delte old backup files in December and January, only this two months files backup only i need to delte.
  
  Please suggest me.
  
  The parameters are:
  CONFIGURE THE RETENTION NONE POLICY;
  CONFIGURE BACKUP OPTIMIZATION # by default
  SET UP DEFAULT DISK DEVICE TYPE; # by default
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT for DEVICE TYPE DISK TO ' / ebiz/backup/PROD-%F';
  SET UP THE DEVICE TYPE DISK BACKUP FOR PARALLELISM BACKUPSET TABLET 1 TYPE;
  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
  CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / ebiz/backup/PROD-%U';
  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
  CONFIGURE ENCRYPTION OF DATABASE # by default
  CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / ebiz/oracle/proddb/10.2.0/dbs/snapcf_PROD.f'; # by default
  
  
  Concerning
  Shaik

  Hello

  You can use this:

  DELETE BACKUP COMPLETED BEFORE TO_DATE('01/31/2011 00:00:00','MM/DD/YY HH24:MI:SS');
  

  Kind regards
  Sylvie

• With RMAN for backup, but not with the archive logs

  We run a 10.2.0.4 database and the rest 11.2.0.3. All databases are on RHEL 5.7.
  
  Our backups are via RMAN, with the data files, controlfiles and spfile saved to disk, then each day, it is copied off site to a backup server.
  
  My question is around logs archiving and RMAN.
  Our current situation is:
  -We do not save the logs to archive via RMAN. for example: backup of the list of the archivelog all; gives "specification does not match backups in the repository.
  -We set the archive_lag_target so archiving logs is produced every 30 minutes.
  -a cron job running on a remote server runs periodically to synchronize data (rsync server) the directory of archives with a remote control.
  -daily archive logs on the server host are bzip. Purge of these newspapers is scheduled for more than 3 days rman 'window of recovery '.
  
  I'm interested in feedback as to if our strategy around archiving logs is correct or not.
  
  Should we be backup logs archiving via RMAN? Are there potential problems with our approach?
  We just kept our backups in this way the DBA in the past want to see newspapers archived as opposed to it while a backupset.
  
  Curious to know what others are doing.

  Hello

  Welcome to OTN!

  Archivelogs with RMAN backup is a better option. When the archives are supported by RMAN, RMAN would be aware of the backup items which are required at the time of the recovery archives. You don't have to do it manually.

  On the disk space, you can delete the archives once they were saved by RMAN.

  RMAN > delete any backup archivelog entry;

  This supports the archivelogs and then remove the archives from the disk.

  If you have a dataguard configured, you can set the deletion policy 'applied on Eve', which removes the archives as and when they are applied to the database ensures there by the management of disk space again.

  RMAN > configure archivelog political of deletion to applied pending;

• Log of RMAN backup of files looking for bad archived newspapers

  I have an RMAN backup, which is a database called EBIZ01PD. The backup is a failure because he's trying to find the archived logs that belong to a different db named EBIZRED that is located on a different server. I'm new with RMAN and any help would be great.
  
  [run {}
  allocate channels ch1 type 'sbt_tape '.
  PARMS = "BLKSIZE = 262144, ENV = (CV_mmsApiVsn = 2, CV_channelPar = ch1, ThreadCommandLine = BACKUP jm - 45 - a 2:233 - cl 43 - ins 40 - 22-j 17828 - jt 17828:4:1 - ball 1 - bap 0 - rap 0 - SPC 0 - VMR 0 - ms 1 - newspapers - cn nvciEBIZDB - Instance001 - vm nvciebizdb.nvci.org vm)" "
  TRACE 0.
  setLimit channel ch1 maxopenfiles 8;
  SQL 'alter system archive log current;
  backup
  filesperset = 32
  diskratio = 0 (archivelog all delete input);
  }
  "exit";
  ]
  RMAN Log:]
  Recovery Manager: Release 10.2.0.4.0 - Production Thu Jan 22 04:00:49 2009
  Copyright (c) 1982, 2007, Oracle. All rights reserved.
  RMAN >
  connected to the recovery catalog database
  RMAN >
  connected to target database: EBIZ01PD (DBID = 1694328251)
  RMAN > 2 > 3 > 4 > 5 > 6 > 7 > 8 > 9 > 10 >
  allocated channel: ch1
  channel ch1: sid = 778 devtype = SBT_TAPE
  channel ch1: CommVault Systems for Oracle: Version 7.0.0 (BUILD76)
  
  
  from full resynchronization of the recovery catalog
  full complete Resync
  from full resynchronization of the recovery catalog
  full complete Resync
  from full resynchronization of the recovery catalog
  full complete Resync
  SQL statement: alter system archive log current
  from full resynchronization of the recovery catalog
  full complete Resync
  From backup 22 January 09
  Current archived log
  from full resynchronization of the recovery catalog
  full complete Resync
  archived journal D:\ORACLE\ORAARC\EBIZRED\ARC00054_0674426118.001 not found or at odds with catalog
  try another file archivelog thread 1, sequence 54
  output channel: ch1
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the backup command to 2009-01-22 04:16:23
  RMAN-06059: journal archived expected not found, lost of archived newspaper compromised recoverability
  ORA-19625: error identification of file E:\ORACLE\ORAARC\EBIZRED\ARC00054_0674426118.001
  ORA-27041: could not open the file
  04002 - OSD: could not open the file
  S/O-error: (OS 3) the system cannot find the path specified.
  RMAN >
  Complete recovery manager.

  Hi Chris,
  Could do a and retry the backup.
  Can you post setting destination arch for EBIZ01PD ?
  The dbid for the EBIZ01PD and the EBIZRED would also be intresting .
  Do you use a recovery catalog?
  Kind regards
  Tycho