Secondary destination for archived logs

Similar Questions

• Retention policy for archive logs.

  Retention policy is set to "REDUNDANCY 2".

  We do the complete disk backup without archive logs at 12:00.

  After that, we make full backup with newspapers to archive tape at 18:00.

  RMAN will consider newspapers to check-in after 12:00 as obsolete as it is backed up to tape?

  Thank you.

  REDUNDANCY applies only to the data files and control files. For archiving logs, there are POLICY of DELETE ARCHIVELOG. But "remove obsolete" won't use POLICY of DELETE ARCHIVELOG, so archiving logs should be removed separately if they meet this policy.

• RMAN writes two destined for archiving

  Hi all
  
  Oracle Database 10 g Express Edition Release 10.2.0.1.0 - product
  Windows XP
  
  I've implemented an rman backup, but I changed the archiving, automatic backup and data destinations:
  
  ALTER SYSTEM SET log_archive_dest='C:\oraclexe\Backup\archivelog\arch_%F' SCOPE = spfile;
  SHUTDOWN IMMEDIATE;
  BOOTABLE MEDIA;
  ALTER DATABASE ARCHIVELOG;
  ALTER DATABASE OPEN;
  alter system switch logfile;
  
  CONFIGURE RETENTION POLICY TO RECOVERY OF 2 DAYS WINDOW;
  CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT "C:\oraclexe\Backup\data\data_%U".
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK to 'C:\oraclexe\Backup\autobackup\ctl_%F ';
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  
  But what rman backup work it still says the archivelogs destination of old (flash recovery area) and the new dest.
  
  Error in the alerts log:
  ORA-17624: cannot delete the C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA directory
  \XE\ARCHIVELOG\2009_10_03
  ORA-27093: could not delete directory
  
  Here's my rman script:
  Run {}
  CROSS-CHECKING OF BACKUP;
  OVERLAP archivelog all;
  DUPLICATION OF COPY;
  Cross-CHECKING of backup of database;
  Backup DUPLICATION of the controlfile;
  delete noprompt obsolete;
  DELETE noprompt backup is complete before ' sysdate-2';
  REMOVE WINDOW OF RECOVERY 2 DAYS NOPROMPT OBSOLETE;
  # delete noprompt expired archivelog all;
  backup copy of tablespace system;
  backup database;
  delete any backup archivelog entry;
  }
  
  Help, please.

  Disable any first your region recover flash.

  To disable the flash recovery area, set the parameter DB_RECOVERY_FILE_DEST initialzation string NULL.
  For example, use this SQL * more relieved to change the setting on a database running:

  "" ALTER SYSTEM SET DB_RECOVERY_FILE_DEST = "SCOPE = THE TWO SID = ' * ';

  The database will no longer be the space of functions of management for stored files flash recovery area
  in the former location of DB_RECOVERY_FILE_DEST. The files will be always known to the RMAN Repository, however, and
  available for backup and restoration activities.

  Concerning
  Asif Kabir

• RMAN-06059: expected archived log not found

  DB version: 11.1.0.7
  Operating system: Solaris 10
  
  Our cron job RMAN has met the following error.
  -First save attempt (complete bkp more archive log) done by connecting to the catalog

  Starting backup at 14-MAR-12
  current log archived
  released channel: ch00
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of backup plus archivelog command at 03/14/2012 08:09:58
  RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
  ORA-19625: error identifying file +PQWSP_ARCH01/pqwsp_arch/pqwsp_26530_1_764525298.arc
  ORA-17503: ksfdopn:2 Failed to open file +PQWSP_ARCH01/pqwsp_arch/pqwsp_26530_1_764525298.arc
  ORA-15173: entry 'pqwsp_26530_1_764525298.arc' does not exist in directory 'pqwsp_arch'

  Because I didn't share RMAN catalog schema password, I used the control as a catalog file and run the CROSSCHECK command.
  
  -Use the control as a catalog file

  $ rman target /
  
  Recovery Manager: Release 11.1.0.7.0 - Production on Wed Mar 14 09:45:59 2012
  
  Copyright (c) 1982, 2007, Oracle.  All rights reserved.
  
  connected to target database: PQWSP (DBID=1638594930)
  
  RMAN> crosscheck archivelog all;
  
  using target database control file instead of recovery catalog
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID=429 instance=pqwsp1 device type=DISK
  validation succeeded for archived log
  archived log file name=+PQWSP_ARCH01/pqwsp_arch/pqwsp_26563_1_764525298.arc RECID=19019 STAMP=777888587
  validation succeeded for archived log
  archived log file name=+PQWSP_ARCH01/pqwsp_arch/pqwsp_26564_1_764525298.arc RECID=19022 STAMP=777890270
  validation succeeded for archived log
  .
  .
  .
  .
  .
  
  Crosschecked 14 objects

  Cannot find objects expired in the output above. I had * "validation succeeded" * message to arch all newspapers.
  
  So I ran a

  BACKUP ARCHIVELOG ALL DELETE ALL INPUT;

  and this backup was successful.
  
  No idea why the first attempt failed when there were not all logs archived expired? If I run the command of OVERLAP by connecting to the catalog, I could find out of date newspapers?

  No idea why the first attempt failed when there were not all logs archived expired?
  this case is not releated archivelog expired, however it seems the requested archivelog 26530 isn't available on destinationas, that it can be removed manually or another taking backup operation the backup and deleted if the execution of the whole.

  crosscheck updated detail that its not available for backup... Check the output of you overlap cmd to 26530 archivelog.

  Thank you
  Tylay Singh

• 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 backup for lack of archive log - Urgent

  Dear all,
  How to take backup in oracle rman for lack of logseq at logseq archiving log.
  
  Please help me urgent.
  
  Thank you
  Manas

  The SNA method before roll is easiest to get your sleep in harmony rather than completely rebuild.

  The RCS on primary continues to rise and if the archives get generated on primary at a regular stage, would be late the night before by a huge margin.

  If there is a gap of newspaper caused lack of archives and his backup is not available, then I'd rather go with the Roll Forward YVERT method.

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

• Find the archive logs generated per day (for 7.3.4 database)?

  I use a query like the one below to determine the average amount archives logs generated per day for a database for a month:
  
  Select sum (GB_USED_PER_DAY) count (GB_USED_PER_DAY) in (SELECT
  To_char(completion_time,'YYYY-mm-DD') completion_date,
  round (SUM (block_size *(blocks+1)) / 1024 / 1024 / 1024, 2) GB_USED_PER_DAY
  V $ archived_log
  WHEN TRUNC (completion_time) BETWEEN
  TRUNC(SYSDATE-30) AND TRUNC (SYSDATE)
  GROUP OF TO_CHAR(completion_time,'YYYY-MM-DD')
  order by 1 desc);
  
  This query does not work on Oracle 7.3.4 database. Anyone know how I can calculate average archive generation of newspapers per day for Oracle 7.3.4?
  
  Thanks in advance!

  Select substr(first_time,1,8), round (sum (bytes) /(1024*1024)) MB of v$ log group by substr (first_time, 1, 8);

• Copy archive logs side Eve for manual resolution of gap

  Version: 11.2 on RHEL 5.8
  Watch type: physical standby
  
  An excerpt from 11.2 Data guard Concepts and administration guide,
  
  To manually correct the gap, one can copy primary eve archivelogs and register as below
  
  

  SQL> ALTER DATABASE REGISTER LOGFILE '/physical_standby1/thread1_dest/arcr_1_7.arc';
  SQL> ALTER DATABASE REGISTER LOGFILE '/physical_standby1/thread1_dest/arcr_1_8.arc';
  SQL> ALTER DATABASE REGISTER LOGFILE '/physical_standby1/thread1_dest/arcr_1_9.arc';

  Question1.
  How is solved the gap once we register the archive above logs?
  
  
  Question2.
  We set LOG_ARCHIVE_DEST_1 physical standby? AFAIK, archive logs don't get generated in a physical standby
  because the standby DBs ORLs are never used.

  Hello

  Rebel wrote:
  Version: 11.2 on RHEL 5.8
  Watch type: physical standby

  An excerpt from 11.2 Data guard Concepts and administration guide,

  To manually correct the gap, one can copy primary eve archivelogs and register as below

  SQL> ALTER DATABASE REGISTER LOGFILE '/physical_standby1/thread1_dest/arcr_1_7.arc';
  SQL> ALTER DATABASE REGISTER LOGFILE '/physical_standby1/thread1_dest/arcr_1_8.arc';
  SQL> ALTER DATABASE REGISTER LOGFILE '/physical_standby1/thread1_dest/arcr_1_9.arc';
  

  Question1.
  How is solved the gap once we register the archive above logs?

  Yes, you can save the newspapers archived on the eve of database, which is copied manually from the primary.
  If you want to apply the archived redo logs, then you must start the recovery process - redo apply (MRP).

  If you archived redo log in the primary, he's not neccasary primary copy manually.

  If you have GAP and archived redo logs have in the primary, then it is enough to launch again apply.
  When you start MRP, if you have gap then MRP request archived redo of the FAL Server (primary) and resolve the discrepancy.
  It is the resolution of the automatic gap.

  have you started with MRP?

  select process from  v$managed_standby where process like 'MRP%';
  -- if no row selected
  alter database recover managed standby database disconnect from session;
  or
  alter database recover managed standby database using current logfile disconnect from session; -- real  time apply
  

  >
  >

  Question2.     
  We set LOG_ARCHIVE_DEST_1 physical standby? AFAIK, archive logs don't get generated in a physical standby
  because the standby DBs ORLs are never used.

  Value by default is LOG_ARCHIVE_DEST_1 - is USE_DB_RECOVERY_FILE_DEST, that means if you are not ready to LOG_ARCHIVE_DEST_1,.
  then all archived redo log store in the Flash recovery area.

  Archvied redo log isn't genereted database pending, ORL, Srl, if you add standby recovery logs.
  When you use protection MAX Performance mode and not added database SRL then sleep by using the BDL.

  Concerning
  Mr. Mahir Quluzade

• 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

• Archive log list does not sequence of current journal is awaiting data base

  Hi all

  So I tried waiting for database physical installation in my local vm.

  I apparently completed the Setup, but I am facing a problem which I cannot understand.

  OS:-Linux 6.4

  Oracle version: 12.1.0.2.0

  primary data: ORA12C

  backup database: ORASTD

  Primary database: -.

  SYS@ORA12C > list of archive logs;

  Database log mode Archive Mode

  Active AutoArchive

  Archives/u01/app/oracle/fast_recovery_area of destination

  More old sequence of journal online 14

  Log sequence archive 16

  Current log sequence 16

  SYS@ORA12C > select name, database_role, controlfile_type from v$ database;

  NAME DATABASE_ROLE CONTROL

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

  ORA12C CURRENT PRIMARY

  SYS@ORA12C > select the sequence #, first_time, next_time, applied from v$ archived_log;

  FIRST_TIM SEQUENCE NEXT_TIME # APPLIED

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

  4 15 APRIL 15 APRIL 16 15 NO.

  4 15 APRIL 15 APRIL 16, 15 YES

  5 16 APRIL 15 APRIL 16 15 NO.

  5 16 APRIL 15 APRIL 16, 15 YES

  6 16 APRIL 15 APRIL 16 15 NO.

  6 16 APRIL 15 APRIL 16, 15 YES

  7 16 APRIL 15 APRIL 16 15 NO.

  7 16 APRIL 15 APRIL 16, 15 YES

  8 16 APRIL 15 APRIL 16 15 NO.

  8 16 APRIL 15 APRIL 16, 15 YES

  9 16 APRIL 15 APRIL 16 15 NO.

  FIRST_TIM SEQUENCE NEXT_TIME # APPLIED

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

  9-16 APRIL 15 APRIL 16, 15 YES

  10 16 APRIL 15 APRIL 16 15 NO.

  10-16 APRIL 15 APRIL 16, 15 YES

  11 16 APRIL 15 APRIL 16 15 NO.

  12 16 APRIL 15 APRIL 16 15 NO.

  13 16 APRIL 15 APRIL 16 15 NO.

  11-16 APRIL 15 APRIL 16, 15 YES

  12-16 APRIL 15 APRIL 16, 15 YES

  13-16 APRIL 15 APRIL 16, 15 YES

  14 16 APRIL 15 APRIL 16 15 NO.

  15 16 APRIL 15 APRIL 16 15 NO.

  FIRST_TIM SEQUENCE NEXT_TIME # APPLIED

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

  15 16 APRIL 15 APRIL 16 15 NO.

  14-16 APRIL 15 APRIL 16, 15 YES

  Waiting for the database: -.

  Select the sequence #, first_time, next_time, applied from v$ archived_log;

  FIRST_TIM SEQUENCE NEXT_TIME # APPLIED

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

  4 15 APRIL 15 APRIL 16, 15 YES

  5 16 APRIL 15 APRIL 16, 15 YES

  6 16 APRIL 15 APRIL 16, 15 YES

  7 16 APRIL 15 APRIL 16, 15 YES

  8 16 APRIL 15 APRIL 16, 15 YES

  9-16 APRIL 15 APRIL 16, 15 YES

  10-16 APRIL 15 APRIL 16, 15 YES

  11-16 APRIL 15 APRIL 16, 15 YES

  12-16 APRIL 15 APRIL 16, 15 YES

  13-16 APRIL 15 APRIL 16, 15 YES

  15 16 APRIL 15 16 APRIL 15 IN-MEMORY

  FIRST_TIM SEQUENCE NEXT_TIME # APPLIED

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

  14-16 APRIL 15 APRIL 16, 15 YES

  SQL > select name, database_role, controlfile_type from v$ database;

  NAME DATABASE_ROLE CONTROL

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

  PHYSICAL STANDBY ORA12C STANDBY

  SQL > archive logs list;

  Database log mode Archive Mode

  Active AutoArchive

  Archives/u01/app/oracle/fast_recovery_area of destination

  More old sequence of journal online 0

  Log sequence to archive 0

  Current log sequence 0

  Now, here's my question is why the sequence of current newspapers shows 0. I tested the datas

  database primary eve happens again. I'm totally out of index.

  I tried to find it on google but nothing could help me until now.

  Any kind of help would be very appreciated.

  Thank you

  Soumya

  Hello

  I am also testing in Data Guard 12.1 configurations.

  Oracle support response is "it seems therefore that this information be removed.

  So is the best way to check on the database pending:

  SQL > select thread #, max(sequence#) ' last day before Seq received. "

  v $ archived_log val, v$ database vdb

  where val.resetlogs_change # = vdb.resetlogs_change #.

  Group thread # order by 1;

  SQL > select thread #, max(sequence#) ' last day before Seq applied.

  v $ archived_log val, v$ database vdb

  where val.resetlogs_change # = vdb.resetlogs_change #.

  and val.applied in ('YES', "IN-MEMORY")

  Group thread # order by 1;

  concerning

• Pull on the RMAN backup archive logs?

  Environment:

  Oracle 11.2.0.3 EE on Solaris

  Physical standby

  I have a gap of journal archive at the moment.  The missing archive logs have been saved on the primary and have not yet been transferred to waiting due to some maintenance work performed on the standby server.

  The database will be able to recognize that the missing archivelog files are in the RMAN backup files, restore them and send them to the update server standby for application?

  If not, will it restore manually, copy them to the standby server and save them for their application?

  Thanks a lot for your help!

  -gary

  Were the archivelogs deleted on the primary once they have been saved? If they have been deleted on the primary, then you can:

  1 manually transfer the backup to forward files

  2 replace the archivelog destination configured on the eve

  3 restart the managed recovery on the standby process, and the computer should be able to detect and apply the missing archivelogs.

  If they have not been deleted on the primary and are always available in the archivelog directory configured, then the process of Data Guard should be able to detect and automatically fix the gap.

  If you have a long interval archivelogs missing and you use + ASM, you can also try to use an incremental backup to roll forward the database pending, this article provides a good step by step: the steps for Rolling forward a standby database using RMAN incremental backup. (Doc ID 836986.1)

  Kind regards
  Oscar

• Oracle database archive logs

  Hi all

  I searched the Oracle and Internet Documents. It is really hard to get information on the management of the archive Log, so I thought to post it here:

  Now, our Database 9i (EBS 11.5.x) was in no archive mode, so I allowed him to archive mode.

  Edit the pfile $ORACLE_HOME/admin/SID/pfile who will be /oracle/proddb/9.2.0/dbs/initPROD.ora

  ############################

  # Archive Log Destinations-benr(10/15/04)

  ############################

  Log_archive_dest_1 = ' location = / Uncordon / archive.

  log_archive_start = TRUE

  
  

  then connect to the database

  
  

  
  

  
  

  
  

  SQL > shutdown normal;

  SQL > startup mount exclusive;

  SQL > alter system set log_archive_start = TRUE scope = spfile;
  SQL > alter system set log_archive_dest_1='LOCATION= /oracle/archivelog ' scope=both;
SQL > alter archivelog database;
  SQL > CHANGE the START of the SYSTEM ARCHIVE LOG;
  SQL > alter database open;
  SQL > alter system archive log all;
  SQL > change the start of the archive log system;
  SQL > archive log start;

  
  

  The next day, I checked the location of archive and sparked an archive of 1 GB even if there is no activity on the database.

  root@test4:/oracle/archivelog>ls
  1_844.dbf   1_862.dbf   1_880.dbf   1_898.dbf   1_916.dbf   1_934.dbf
  1_845.dbf   1_863.dbf   1_881.dbf   1_899.dbf   1_917.dbf   1_935.dbf
  1_846.dbf   1_864.dbf   1_882.dbf   1_900.dbf   1_918.dbf   1_936.dbf
  1_847.dbf   1_865.dbf   1_883.dbf   1_901.dbf   1_919.dbf   1_937.dbf
  1_848.dbf   1_866.dbf   1_884.dbf   1_902.dbf   1_920.dbf   1_938.dbf
  1_849.dbf   1_867.dbf   1_885.dbf   1_903.dbf   1_921.dbf   1_939.dbf
  1_850.dbf   1_868.dbf   1_886.dbf   1_904.dbf   1_922.dbf   1_940.dbf
  1_851.dbf   1_869.dbf   1_887.dbf   1_905.dbf   1_923.dbf   1_941.dbf
  1_852.dbf   1_870.dbf   1_888.dbf   1_906.dbf   1_924.dbf   1_942.dbf
  1_853.dbf   1_871.dbf   1_889.dbf   1_907.dbf   1_925.dbf   1_943.dbf
  1_854.dbf   1_872.dbf   1_890.dbf   1_908.dbf   1_926.dbf   1_944.dbf
  1_855.dbf   1_873.dbf   1_891.dbf   1_909.dbf   1_927.dbf   1_945.dbf
  1_856.dbf   1_874.dbf   1_892.dbf   1_910.dbf   1_928.dbf   1_946.dbf
  1_857.dbf   1_875.dbf   1_893.dbf   1_911.dbf   1_929.dbf   1_947.dbf
  1_858.dbf   1_876.dbf   1_894.dbf   1_912.dbf   1_930.dbf   lost+found
  1_859.dbf   1_877.dbf   1_895.dbf   1_913.dbf   1_931.dbf   test.txt
  1_860.dbf   1_878.dbf   1_896.dbf   1_914.dbf   1_932.dbf
  1_861.dbf   1_879.dbf   1_897.dbf   1_915.dbf   1_933.dbf
  

  Question

  1. How can I delete old logs archiving without using RMAN?

  2. How should I know which Archives connects to keep and delete?

  3. is there a way to know why the database generates so many newspapers to check-in?

  Hello

  Yes, you must keep this archive. You can schedule the job to compress files to archive (record use of space) and move it to another place as a backup.

  You can schedule both COLD backup once a week, in this case it is scabies archive for a week.

  HTH

• ORA-19504: failed to create the file, ORA-00270: creation of the archiving log error

  Hello
  
  Oracle 11 g 2 on windows 7, I of primary and standby on the same system (learning).
  
  When I check on status of primary and secondary use under request it gives applied log is 'NO '.
  
  SQL > select sequence #, used from v$ archived_log;
  
  SEQUENCE # APPLIED
  ---------- ---------
  516 NO.
  517 NO.
  NO. 523
  NO. 524
  525 NO.
  531 NO.
  NO. 532
  533 NO.
  NO. 541
  544 NO.
  
  When I checked error on DB primary .he give me more erro.
  SQL > SELECT 'ID', 'DB_status' STATUS DEST_ID, EXCURSION place "Archive_dest', 'ERROR' OF V$ ARCHIVE_DEST WHERE DEST_ID < = 5;
  ---------- ---------
  Error Archive_dest
  ------------------------------------------------------------------------------------------------------------------------------------------------------
  1 D:\app\kamdarvg\flash_recovery_area\test\ARCHIVELOG ORA-19504: cannot create the file «»
  
  2 STAND ORA-00270: creation of the archiving log error
  
  I checked the space on the system... is there enough free space on the disk.
  
  On primary DB (destination of the journal archive)
  
  SQL > list of archive logs
  Database log mode Archive Mode
  Active AutoArchive
  Destination of archive D:\app\kamdarvg\flash_recovery_area\test\ARCHIVELOG
  More old sequence of journal online 564
  Log sequence archive 566
  Current log sequence 566
  
  On standby DB (list of newspapers of record)
  
  SQL > list of archive logs
  Database log mode Archive Mode
  Active AutoArchive
  Destination of archive D:\app\kamdarvg\flash_recovery_area\test\ARCHIVELOG
  More old sequence of journal online 564
  Log sequence archive 566
  Current log sequence 566
  
  Please guide it's because of the destination of the journal archive even shared by the standby and primary?
  
  If yes how do I change the destination of the newspaper archive on standby DB?
  
  Thank you.
  
  Edited by: 977220 April 18, 2013 20:49

  change initialization parameter

• 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