Archive log backup Question

Similar Questions

• Archiving log backup RMAN

  Hi guys,.
  
  Can advise you on the syntax for the rman backup of archive logs generated in the last 2 days?
  
  Wouldn't be 1 or 2?
  
  Thank you!
  
  1 BACKUP ARCHIVELOG UNTIL ' SYSDATE-2';
  
  2 BACKUP ARCHIVELOG FROM TIME ' SYSDATE-2';

  Run the commands and see what is RMAN - it will show you what files it runs a backup of!

  OR

  Search the documentation
  http://docs.Oracle.com/CD/E11882_01/backup.112/e10643/TOC.htm

  Hemant K Collette

• The Archive Log backup retention policy

  How can I define retention policy for backups of the log of the Archives?

  The question and the answer that you have marked as "Right answer" is misleading.

  For removal of journal policy archived, see below.

  Configuration of RMAN environment

  For the real question displayed "How can I define retention policy for backups of the log of the archives?", see link below. ""

  http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmconfb.htm#i1019318

  Also, have you started the thread to clear your doubts or test other users of the forum?

  Thank you!!

• RMAN never removes the archive log backups

  Hi all
  I use Recovery Manager to back up a database (9i v2) with the following characteristics:
  The database is in mode archive, the parameter CONTROL_FILE_RECORD_KEEP_TIME = 7, I do not use a recovery catalog db (alll rman information written to the db control file) and finally, I use default CONFIGURE RETENTION POLICY to REDUNDANCY 1;
  I programmed the following to run every afternoon inside RMAN:
  run
  +{+
  View all;
  cross-checking of backup;
  delete noprompt obsolete;
  allocate channels ch1 disc type;
  backup
  tag data = "full_database_backup_and_ctl" include current controlfile
  format "d:\oracle\backup\db/fulldb_%u%s%p".
  SQL 'alter system switch logfile;
  backup
  ARCHIVELOG all delete input format 'd:\oracle\backup\db\arch_%u%s%p ';
  backup current controlfile "d:\oracle\backup\db\ctl_%u%s%p" format
  Output channel ch1.
  +}+
  Once the above script finishes executing, a tape of the whole repertoire d:\oracle\backup\db backup occurs.
  Normally I expect full *, ctl * and arch * files, since 2 days, should be deleted, but instead, I noticed that vault files are NOT removed from the directory (that is, they become never obsolete).
  This causes the player to fill up, and I'm running out of disk space.
  Does anyone have an idea why this happens?
  
  Thank you
  Yiannis

  I read not only tablespaces...

  But you have offline storage?

• Archive log deletion with no backup of the archive logs

  I suffer from enormous size archive of the newspaper. In my previous post, I asked for help. I almost 480 GB archive log every day in our database of 11 2 under redhat linux 5.8 GR. Now, if you please help me in another case.
  
  If I take backup of archive logs and run delete archivelog everything until ' sysdate-1' with each backup database of day how it affects. " In my opinion there should be no problem in that I have the last incremental backup and recovery 1 days archive log in archivelog destination. If I do not archive log backups to how it will be different. Help, please.

  >

  Hello

  Sir, I know how to remove. But in my opinion delete up to sysdate-1 and taking no backup of the Archives of newspapers will
  no effect. Is in my opinion is right or wrong, that is the question.

  What I read in your original post, is that you take a daily incremental backup - Yes? I'm assuming that you also take
  a full backup on a regular basis (Sunday?).

  I was working on the assumption that the foregoing is available? I worked on a project where installation has been similar. We
  tested regularly backups - I hope that you do the same thing?

  What we used to do was FTP (script Unix - cron job - if you Google you will find Python or Perl to do the same thing - that is)
  what I wanted to, but was cancelled - very 1980, anyway) the archived redo logs on to a specific computer that holds only these files.
  After FTP "d - they have been removed from the server, freeing up space.

  Now, you say you have TB 0.5 per day - while more than a week, you will need a machine with ~ 3 TB of disk - if you can get a kind
  the scenario as this place and running, then you will have both your incremental backup and your archived redo logs for the last
  24 hours and the full backup with recovery archived records dating back to this full backup. You can also always archive on tape if
  suits. So, you will have redundant coverage - 'belt and braces' as the Americans say.

  But, to answer your question directly, "take no backup of archive logs have no effect" - that is true - it
  will not affect the operation of the database server, but if I were you, I would hang on to enough archived redo log to return to the
  last backup. That's just my humble OPINION.

  HTH,

  Paul...

  Published by: Paulie July 21, 2012 19:28

• 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

• Backup of archive logs

  I have a cron job that backs up complete zero on Sunday.  I have an another cron job beginning level 1 backups, Monday to Saturday.  I have a 3rd cron that runs every 2 hours for each day of the week in order to safeguard the archive logs.
  
  I have concerns with the 3rd cron job.  Lets say the data in the database has not changed in the last 2 hours.  This cron job would always run this script, create another backup rman (taking more space on the server).  Is my understanding correct that rman is not smart enough to know what data has changed during backup of the Archives of newspapers so that the two components of backup are not store duplicate information? The reason why I think it's because the size of the pieces cackup for this archive log backups stop a lot of the time very similar (but not the same) in size.

  Lets say the data in the database has not changed in the last 2 hours

  That you have taken backup the archivelog at 07:00 and the next execution of the annex is at 09:00. Say that there are about 100 archives that have been backed up at 07:00. And from 07:00 until 09:00, there was that no transactions took place, in other words, that the data in the database has not changed in the last 2 hours.

  In this case, RMAN wouldn't be backup archives that have been backed up at 07:00. If there is no generated archives between 07:00 and 09:00, RMAN wouldn't save anything.

  If the archived log was not saved, it will be.
  If the archive log was not saved and is missing, you will get an error.
  If the archived log was backed up, RMAN will not back up again.

• Deletion of backups of level 1 and archive logs

  Hello
  
  Everyone knows that "the retention policy would be applicable on level 0 backups or only full backups.
  
  So how will be reported what backups and level 1 backup of archive logs are no longer needed for recovery?
  
  And after that as the command "remove obsolete", y at - it a command to remove these unwanted 1 level and archiving logs backups?
  
  Any suggestion?
  
  Thank you
  Nitesh.

  So how will be reported what backups and level 1 backup of archive logs are no longer needed for recovery?

  If you have the revoery retention strategy window 1 day and you take backup of level 0 Sat and then consecutive level until Friday 1 daily backup, again on backup sat level 0 will be obsolete previous level 0 backup sat and its seven consecutive level 1 so is found in the archived log alls before this level 0 current backup will be marked.

  Obsolete report will show you alls backup piece and the archivelogs that are marked as obsolete.

  And after that as the command "remove obsolete", y at - it a command to remove these unwanted 1 level and archiving logs backups?

  What do you mean by backups, undesirable level 1, on what basis you say that backup of level 1 are undesirable?

  Khurram

• Restore an archived log RMAN backup

  Hello
  How to restore an archived log backups RMAN? I watched it here:
  http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14191.PDF
  but can not find.
  
  Thank you.

  try something like this...

  RMAN > restore archivelog all;

  Use below if you know ru seq # for newspaper archive that you want to restore...

  RESTORE THE SEQUENCE 20 UNTIL SEQUENCE 28 ARCHIVELOG;

  Sorry if you were not looking for it... just throwing ideas out there...

• No clarity about the location of archive logs in Oracle database 11g

  I have this request which I am not able to solve. There is a location of the log archiving mentioned as /oraarch/app/oracle/oradata/snlprod/archive_logs/in the parameter log_archive_dest_1. But the archive logs appear in another location/orabackup/rman/snlprod/archive_logs. I wonder how the archive logs show at this location, / orabackup/rman/snlprod/archive_logs.

  
  

  I assume that there is only one way in what place can be given which is seen availability-> restore settings-> Media Recovery.

  
  

  Hopefully, my question is clear.

  
  

  Please get back with the answer to my query.

  
  

  Concerning

  Check the location of the archive log backup in the script. What is /orabackup/rman/snlprod/archive_logs.

• 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.

• Archive log mode off

  Hi DBA guys, have a good day all
  
  If I change the log mode archive no mode of archive log, internally, whats happen to my database?
  
  Is this old archive log backup for the future so new convert no Archives to the Archives of the journal mode?
  
  What is happen flashback if I change the log mode archive no mode of archive log?
  
  
  Concerning
  
  S.Azar

  azarmohds wrote:
  Thank you very much

  why I asked this question of means, rightnow you posted, this characteristic of 10 GB i.e flashback database configured when the log mode archive is enabled, then in this case

  What is happen flashback if I change the log mode archive no mode of archive log?

  S.Azar,

  You must be clear about the things that when you read the web notes, there may be an incompatibility of the language. The best is first, that research on the oracle documentation.

  Now on your doubt, it is a mismatch of terminology that happens here. To enable Flashback Database that is a copy more persistent undo data, stored separately in an FLB file, you must have configured in your db in archivelog mode. Without this, you cannot enable the Flashback Database feature. And you cannot switch noarchive log mode as well if you have the Flashback Database mode on.

  The other thing (that I guess Anurag mention) is the normal function of Flashback that relies on the Undo data stored in the undo tablespace. Only, this is based on the undo data and doesn't depend on the mode of journal archive / nonarchive of the database. But it is limited to these data and this period of time up to which you can store the undo data in your undo tablespace.

  HTH
  Aman...

• Data Guard - RMAN removing archive log

  Hello

  I ' v DataGuard with physical standby.

  I do a backup only on the primaries. Both sites have ther separate backup systems.

  I ' v FRA and configured archivelog deletion with RMAN configuration:

  on primary: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;

  standby: CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON STANDBY;

  It works fine but I think what if scenarios and I'v qestion on best practices for backup after the transition of role management. Let's say that for some reason, as i'v in switch mode sleep for a few days and the backup will be posible to watch (now primary) database. What would be the steps/reconfiguration appropriate to do?

  1 should I reconfigure RMAN?

  change of new primary to: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;

  change back to sleep again: CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON STANDBY;

  2. make full backup

  Hello

  1. you can refer to the oracle documentation: http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmconfb.htm#CHDCFHBG

  section: "all archived Redo Log deletion policy."

  Document provides the best algorithm to analysis of work

  You can use the CONFIGURE ARCHIVELOG DELETION POLICY BACKED UP integer TIMES TO DEVICE TYPE command to allow a policy of removal of archived newspaper. This configuration specifies that archived newspapers are eligible for deletion only when the specified number of archived log backups exist on the specified device type.

  
  

  If the deletion policy is configured with the BACKED UP integer TIMES clause, then a BACKUP ARCHIVELOG , the command copy newspapers, unless integer already exist on the specified device type backups. If integer are backups of logs, then the BACKUP ARCHIVELOG command ignores the newspapers. In this way, the deletion of archived newspaper policy works as a default NOT BACKED UP integer TIMES clause on the BACKUP ARCHIVELOG command. Note that you can override the deletion policy by specifying the FORCE option on the BACKUP command.

  The deletion of archived newspaper policy has also options specific to an environment Data Guard. , then RMAN can delete logs after they have been applied to all destinations remote mandatory. If you specify SHIPPED TO STANDBY , for example, then RMAN can remove log files when they were transferred to all destinations of mandatory relief.

  2. the paper provides good information, just to check and decide easily based on the functionality of the database role you can configure.

  It will be useful.

  -Thank you

  Pavan Kumar N

• ORA-19599: block number 1985 is corrupt in archived log + FG.

  Hi team,
  
  I couldn't take the RAC database archivelog backup. Please help me
  
  RMAN > VALIDATE the BACKUP DATABASE ARCHIVELOG ALL;
  
  From backup 24 March 13
  using channel ORA_DISK_1
  channel ORA_DISK_1: from full datafile backupset
  channel ORA_DISK_1: specifying datafile (s) in backupset
  input datafile fno = 00001 name=+DG1/kvxcprd/datafile/system.260.777756857
  input datafile fno = name=+DG1/kvxcprd/datafile/sysaux.268.777756857 00003
  input datafile fno = name=+DG1/kvxcprd/datafile/undotbs1.263.777756857 00002
  input datafile fno = 00005 name=+DG1/kvxcprd/datafile/undotbs2.264.777756983
  input datafile fno = name=+DG1/kvxcprd/datafile/users.267.777756857 00004
  channel ORA_DISK_1: complete set of backups, time: 00:00:25
  channel ORA_DISK_1: from archive newspaper backupset
  channel ORA_DISK_1: specification of archive log backup set
  archive log entry thread = 2 sequence 17 recid = 26 = 810915691 stamp =
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 24/03/2013-14:37:11
  ORA-19599: block number 1985 is corrupted in +FG/kvxcprd/archivelog/2013_03_24/thread_2_seq_17.269.810915689 archived journal
  
  RMAN > backup archivelog all;
  
  From backup 24 March 13
  Current archived log
  using channel ORA_DISK_1
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the backup to 24/03/2013-14:39:52 command
  ORA-19563: file header validation failure
  
  Thank you and best regards,
  
  
  Published by: 995796 on March 24, 2013 02:26
  
  Published by: 995796 on March 24, 2013 02:27

  You must exclude this backup archivelog. Rename the archivelog (via asmcmd) and then run OVERLAP ARCHIVELOG ALL while Oracle would mark it as 'Out of date' when it does not find the archivelog. (You can also run an ARCHIVELOG DELETE or REMOVE the ARCHIVELOG EXPIRES to logically remove).

  You should document this archivelog missing so that any required later retrieval knows this archivelog isn't available, so a point in time to recover to any point of the last backup before this archivelog to a point in time of the archivelog or as the result of it would not be possible until the next backup.

  Needless to say, take a fresh database backup.

  Hemant K Collette

• 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;