Size archived logs

Similar Questions

• Total combined size of archived logs

  DB version: 11.2
  Platform: AIX
  
  How can I determine the total size of the archive for a particular database logs?
  
  Search on Google and search OTN did not provide many details
  
  Don't have not the solution of the following be pass as he deviated from the subject
  
  Re: size of the journal archive
  
  
  The recovery for our database log size is 100 MB.

  SQL> select count(*) from v$archived_log where status = 'A' and name is not null;
  
    COUNT(*)
  ----------
          22
   

  So, I can multiply 22 * 100 = 2 200 MB. But there were some manual switches, the size of these files will be less. That's why I'm looking for an accurate way of determining the total size of the archive logs.

  Hello;

  V$ ARCHIVED_LOG contains BLOCKS (the size of the journal archived (in blocks)) and BLOCK_SIZE (which is the same as the size of the logical block of the newspaper online, including the archived log was copied)
  So with a little help in the query, you should be able to get it.

  ARCHIVELOG size every day

  select
    trunc(COMPLETION_TIME) TIME,
    SUM(BLOCKS * BLOCK_SIZE)/1024/1024 SIZE_MB
  from
    V$ARCHIVED_LOG
  group by
  trunc (COMPLETION_TIME) order by 1;
  

  COMPLETION_TIME is a DATE, you can add ANOTHER to the query to get exactly the total that you want for the desired date range.

  ARCHIVELOG size every hour

  alter session set nls_date_format = 'YYYY-MM-DD HH24';
  
  select
    trunc(COMPLETION_TIME,'HH24') TIME,
     SUM(BLOCKS * BLOCK_SIZE)/1024/1024 SIZE_MB
  from
    V$ARCHIVED_LOG
  group by
    trunc (COMPLETION_TIME,'HH24') order by 1;
  

  Another example

  SELECT   To_char(completion_time,'YYYYMMDD')    run_date,
           Round(Sum(blocks * block_size + block_size) / 1024 / 1024 / 1024) redo_blocks
  FROM     v$archived_log
  GROUP BY To_char(completion_time,'YYYYMMDD')
  ORDER BY 2
  /
  

  Best regards

  mseberg

  Published by: mseberg on February 23, 2012 02:30

• Why archive log file size constantly change?

  I have a question related to the size of the archive log file:
  I constantly receive a different size to the size of the log file archive, of course, they are smaller than to the size of the log file.
  A guru can explain to me: what possible reason could be?
  Thanks in advance!

  It can happen due to several reasons:

  When you perform a manual archive (via ALTER SYSTEM ARCHIVE LOG CURRENT/ALL)
  When Oracle must respect your ARCHIVE_LAG_TARGET (defined in seconds)

  Unless you do a manual check-in, your parameter ARCHIVE_LAG_TARGET is the reason why you see Archives of logs with different sizes as Oracle has archived the redo log as soon as the time ARCHIVE_LAG_TARGET is reached. Even if the redo log is not full, Oracle will always have to archive the redo log.

• Archive logs always smaller in size then redo logs

  I'm on 10.2.0.3.
  
  My recovery logs (3 groups of 2 members each) is 50 M, while my archive logs is mostly between 30 M and 40 M & never reach 50. Journal Apprently switches are too often produce.
  You guys have an idea, what could cause one - and how to fix it?
  
  TIA.
  
  GROUP # THREAD # SEQUENCE # BYTES MEMBERS OF ARC STATUS FIRST_CHANGE # FIRST_TIME
  ---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- ------------------
  YES 1 1 25679 52428800 2 INACTIVE 5176999019 5 MARCH 09
  2 1 25678 52428800 2 YES INACTIVE 5176976984 5 MARCH 09
  3 1 25680 52428800 2 NO CURRENT 5177009713 5 MARCH 09
  
  -rw - r - 1 oracle dba 36288512 5 March 10:45 arch1_25635_669756456.arc
  -rw - r - 1 oracle dba 35852288 5 March 10:45 arch1_25636_669756456.arc
  -rw - r - 1 oracle dba 38668288 5 March 10:45 arch1_25637_669756456.arc
  -rw - r - 1 oracle dba 40915968 5 March 10:45 arch1_25638_669756456.arc
  -rw - r - 1 oracle dba 35852288 5 March 10:45 arch1_25639_669756456.arc
  -rw - r - 1 oracle dba 44192768 5 March 10:45 arch1_25640_669756456.arc
  -rw - r - 1 oracle dba 46884864 5 March 10:45 arch1_25641_669756456.arc
  -rw - r - 1 oracle dba 35852288 5 March 10:46 arch1_25642_669756456.arc
  -rw - r - 1 oracle dba 35848192 5 March 10:46 arch1_25643_669756456.arc
  -rw - r - 1 oracle dba 38760448 5 March 10:46 arch1_25644_669756456.arc
  -rw - r - 1 oracle dba 35851264 5 March 10:47 arch1_25645_669756456.arc
  -rw - r - 1 oracle dba 41501696 5 March 10:47 arch1_25646_669756456.arc
  -rw - r - 1 oracle dba 44226560 5 March 10:47 arch1_25647_669756456.arc
  -rw - r - 1 oracle dba 41139200 5 March 10:47 arch1_25648_669756456.arc
  -rw - r - 1 oracle dba 35852288 5 March 10:47 arch1_25649_669756456.arc
  -rw - r - 1 oracle dba 36099072 5 March 10:47 arch1_25650_669756456.arc
  -rw - r - 1 oracle dba 43916288 5 March 10:47 arch1_25651_669756456.arc
  -rw - r - 1 oracle dba 43497472 5 March 10:47 arch1_25652_669756456.arc
  -rw - r - 1 oracle dba 36912128 5 March 10:47 arch1_25653_669756456.arc
  -rw - r - 1 oracle dba 35848192 5 March 10:53 arch1_25654_669756456.arc
  -rw - r - 1 oracle dba 36176896 5 March 10:56 arch1_25655_669756456.arc
  -rw - r - 1 oracle dba 36613120 arch1_25656_669756456.arc March 5 from 11:00
  -rw - r - 1 oracle dba 36086784 5 March 11:10 arch1_25657_669756456.arc
  -rw - r - 1 oracle dba 35859456 5 March 11:15 arch1_25658_669756456.arc
  -rw - r - 1 oracle dba 39876608 5 March 11:16 arch1_25659_669756456.arc
  -rw - r - 1 oracle dba 37593088 5 March 11:18 arch1_25660_669756456.arc
  -rw - r - 1 oracle dba 37158912 5 March 11:24 arch1_25661_669756456.arc
  -rw - r - 1 oracle dba 38323200 5 March 11:25 arch1_25662_669756456.arc
  -rw - r - 1 oracle dba 36100096 5 March 11:25 arch1_25663_669756456.arc
  -rw - r - 1 oracle dba 35860480 5 March 11:35 arch1_25664_669756456.arc
  -rw - r - 1 oracle dba 35848192 5 March 11:48 arch1_25665_669756456.arc
  -rw - r - 1 oracle dba 36048896 5 March 11:56 arch1_25666_669756456.arc
  -rw - r - 1 oracle dba 35852288 5 March 12:05 arch1_25667_669756456.arc
  -rw - r - 1 oracle dba 35990528 5 March 12:07 arch1_25668_669756456.arc
  -rw - r - 1 oracle dba 36060160 5 March 12:12 arch1_25669_669756456.arc
  -rw - r - 1 oracle dba 35888128 5 March 12:16 arch1_25670_669756456.arc
  -rw - r - 1 oracle dba 36460544 5 March 12:18 arch1_25671_669756456.arc
  -rw - r - 1 oracle dba 35857408 5 March 12:21 arch1_25672_669756456.arc
  -rw - r - 1 oracle dba 37536768 5 March 12:31 arch1_25673_669756456.arc
  -rw - r - 1 oracle dba 50753536 5 March 12:32 arch1_25674_669756456.arc
  -rw - r - 1 oracle dba 35850240 5 March 12:38 arch1_25675_669756456.arc
  -rw - r - 1 oracle dba 35854336 5 March 12:53 arch1_25676_669756456.arc
  -rw - r - 1 oracle dba 35875840 5 March 12:56 arch1_25677_669756456.arc
  -rw - r - 1 oracle dba 35873792 5 March 13:07 arch1_25678_669756456.arc
  -rw - r - 1 oracle dba 35852288 5 March 13:19 arch1_25679_669756456.arc

  Hi Grex,

  Refer to metalink Doc ID: 388627.1.

  HTH
  Anand

• 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

• DataGuard slowed db: generating the archive logs?

  Hello

  I have a 11.2.0.4 db using Data Guard to play with. I just set up and could do a failover and vice versa.

  However I have noticed there are great number of generated archive logs, one every minute. As it is an empty database, I wonder why?

  No recovery is generated by sessions:

  Select v$ session.sid, username, value/1024/1024 redo_size_MB
  v $ sesstat, v$ statname of v$ session
  where v$ sesstat. STATISTICS of # = v$ statname. STATISTICS FROM #.
  and v$ v = session.sid $sesstat.sid
  and name = "redo size."
  and > 0
  and username is not null
  2 3 4 5 6 7 8 value order;

  no selected line

  Logs are generated on the disc:

  -rw - r - 1 oracle oinstall K 77, 30 Nov 12:06 o1_mf_1_1119_c5rcg7b1_.arc

  -rw - r - 1 oracle oinstall 35K 30 Nov 12:07 o1_mf_1_1120_c5rcj3gh_.arc

  -rw - r - 1 oracle oinstall 103K 30 Nov 12:08 o1_mf_1_1121_c5rckzo0_.arc

  -rw - r - 1 oracle oinstall 36K 30 Nov 12:09 o1_mf_1_1122_c5rcmvo2_.arc

  -rw - r - 1 oracle oinstall 35K 30 Nov 12:10 o1_mf_1_1123_c5rcoqry_.arc

  -rw - r - 1 oracle oinstall 35K 30 Nov 12:11 o1_mf_1_1124_c5rcqmxm_.arc

  -rw - r - 1 oracle oinstall 35K 30 Nov 12:12 o1_mf_1_1125_c5rcsj2j_.arc

  -rw - r - 1 oracle oinstall 35K 30 Nov 12:13 o1_mf_1_1126_c5rcvd3t_.arc

  Someone has an idea of what to check?

  Concerning

  3

  Something abnormal. If this a test box, are you allowed to bounce the DB?

  If so, give it a shot and try.

  -Jonathan Rolland

• can't understand why an extract of the database restore fails (missing archive logs)

  Dear,

  I'm completely back up my database ensures every night with following statement.

  full backup AS BACKUPSET COMPRESSED ORCL_FULL_STBY format database tag ' / oradata/archive/fast_recovery_area/%d_%T_%s_%p_FULL_STBY' more tag ORCL_FULL_STBY archivelog delete all entries;

  I wanted to check with 'restore... Preview' if my backup is good enough to restore the database from scratch.
  result = failed!
  Reason:
  "any backup log archived for thread 1 with sequence 65 and YVERT departure from 49020676 found to restore."

  I have read the documentation oracle and articles for days, but I did not understand that even though I take online backup yesterday if I want to restore my database today I still need archival newspapers last month?

  can you please review my analysis and tell me where I am doing wrong?

  for example a piece from my last backup;

  Time of accomplishment BS key Type LV size device Type elapsed time
  ------- ---- -- ---------- ----------- ------------ ---------------
  1008 full 199.25 M DISK 00:04:44 October 8, 15
  BP key: 1010 situation: AVAILABLE Tablet: YES Tag: ORCL_FULL_STBY
  Item name: / oradata/archive/fast_recovery_area/QIPDB1_20151008_1057_1_FULL_STBY
  List of defined backup data files 1008
  Name of file LV Type cash SNA cash time
  ---- -- ---- ---------- --------- ----
  50570723 full 1 8 October 15 /oradata/data/qipdb1/system01.dbf
  4 integer 50570723 8 October 15 /oradata/data/qipdb1/users01.dbf

  as you can see "Cash SNA" is 50570723 so tells me that my understanding if restore these backups I need archived newspapers on top of the YVERT.
  for me the best candidate is

  Time of accomplishment time BS key size Device Type
  ------- ---------- ----------- ------------ ---------------
  65,25 M 1004 00:01 DRIVE: 24 OCTOBER 8, 15
  BP key: 1006 situation: AVAILABLE Tablet: YES Tag: ORCL_FULL_STBY
  Part name: /oradata/archive/fast_recovery_area/QIPDB1_STBY/backupset/2015_10_08/o1_mf_annnn_ORCL_FULL_STBY_c1dkfw9k_.bkp

  List of newspapers archived in backup set 1004
  The next time that THRD Seq YVERT low low time next YVERT
  ---- ------- ---------- --------- ---------- ---------
  1 79 50310555 7 OCTOBER 15 50570723 8 OCTOBER 15
  
  BUT out of "restore...". Preview' RMAN stil tells me that

  any backup log archived for thread 1 with sequence 65 and YVERT departure from 49020676 found to restore
  any backup log archived for thread 1 with sequence 66 and YVERT departure from 49020693 found to restore
  any backup log archived for thread 1 with sequence 67 and YVERT departure from 49020696 found to restore
  any backup log archived for thread 1 with sequence 68 and YVERT departure from 49020761 found to restore
  any backup log archived for thread 1 with sequence 69 and YVERT departure from 49020836 found to restore
  any backup log archived for thread 1 with sequence 70 and YVERT departure from 49020919 found to restore
  any backup log archived for thread 1 with sequence 71 and YVERT departure from 49021021 found to restore
  any backup log archived for thread 1 with sequence 72 and YVERT departure from 49155291 found to restore
  any backup log archived for thread 1 with sequence 73 and YVERT departure from 49324912 found to restore
  any backup log archived for thread 1 with sequence 74 and YVERT departure from 49498102 found to restore

  When I look at V$ ARCHIVED_LOG I see seems indeed to these archived logs removed for cause of "more tag ORCL_FULL_STBY archivelog delete all entries ' that they have been deleetd after saving.
  and because of my retention policy and script; I remove the logs also archived backups that are more than 2 days.

  S SEQUENCE # FIRST_CHANGE # NEXT_CHANGE #.
  - ---------- ------------- ------------
  65 49020676 49020693 D
  A 49020693 OF 49020676 65
  D 68 49020761 49020836
  66 49020693 49020696 D
  67 49020696 49020761 D
  69 49020836 49020919 D
  70 49020919 49021021 D
  49155291 49021021 71 D
  72 49155291 49324912 D
  D 73 49324912 49498102
  74 49498102 49632131 D

  I still don't understand why rman complains of the archived logs that are for an older sequence (SNA) as my last backup
  because I was assuming that the concerned newspapers archived should have already applied to these files of data, right?

  My final goal is to deliver below for the case that we have lost everything.

  Run {}
  restore the database;
  recover the database;
  }

  Thanks in advance,
  Halit

  Hi guys,.

  I found the root cause and workaround

  RMAN-06025 - RMAN RESTORE DATABASE OVERVIEW to the backup site asks former newspaper (Doc ID 1599013.1)

  CAUSE Checkpoint_change# standby controlfile not refreshed properly.  BUG 15876029 - RESTORE PREVIEW ASKING OLD ARCHIVE LOG IN STANDBY DATABASE  Closed as DUPLICATE of  BUG 8740124 - CURRENT STANDBY REDO LOG GROUP SHOULD BE INCLUDED IN THE DATABASE BACKUP BY RMAN SOLUTION  1) Workaround is to recreate the standby controlfile.  OR  2) upgrade to 11.2.0.4 or above where Bug 8740124  is fixed  OR  3) check for availability of patch 8740124
  

• Encryption of files to archive log...

  We have started to learn and explore the transparent encryption of the data (encryption tablespace on windows servers).  All data types appear to be encrypted in the data (watched by block dump) files, but only a few data types seem to be encrypted in the archive logs.  Is this the correct behavior?  Is there a way to well to encrypt the archive logs too?

  Discovered the problem.  We have omitted to include in our statement create tablespace. Now, the archive logs are also encrypted.

  CREATE TABLESPACE encryptedtbs

  DATAFILE ' / u01/app/oracle/oradata/d1v11201/encryptedtbs01.dbf' SIZE 100 M

  ENCRYPTION USING "AES256".

  DEFAULT STORAGE (ENCRYPT);

• Arc1: 19504 error creating archive log file... after the NFS configuration

  I use an Oracle 11.2.0.3 on RHEL 5.7 (no ASM or RAC) database
  
  We have our archiving logs off copied to a backup location external via a cron job and rsync command, and I want to switch to NFS.
  

  NAME                         TYPE      VALUE
  ------------------------------------ ----------- ------------------------------
  log_archive_format               string      RCAT_%t_%s_%r.arc
  log_archive_dest_1               string      location=USE_DB_RECOVERY_FILE_DEST
  
  SQL> !df -h
  Filesystem                 Size  Used Avail Use% Mounted on
  ...
  ...
  backups:/ARCHLOG/rman       12T  7.8T  3.5T  70% /mnt/nfs_archlog
  
  SQL> alter system set log_archive_dest_2='LOCATION=/mnt/nfs_archlog optional' scope=both;
  
  System altered.

  When I run 'alter system archive log current', I see the error message archiver in the alert below log...
  

  Wed Aug 29 14:42:08 2012
  ALTER SYSTEM ARCHIVE LOG
  Wed Aug 29 14:42:08 2012
  Thread 1 advanced to log sequence 23044 (LGWR switch)
    Current log# 4 seq# 23044 mem# 0: /u01/oradata/RCAT/redo_4a.dbf
    Current log# 4 seq# 23044 mem# 1: /u02/oradata/RCAT/redo_4b.dbf
  Wed Aug 29 14:42:14 2012
  ARC1: Error 19504 Creating archive log file to '/mnt/nfs_archlog/RCAT_1_23043_602355789.arc'
  Archived Log entry 24282 added for thread 1 sequence 23043 ID 0x165341cd dest 1:

  However, when I check the NFS location I see that the file is there.

  [oracle@rman nfs_archlog]$ ls -la
  total 72
  drwxr-x--- 14 oracle oinstall   4096 Aug 29 14:42 .
  drwxr-xr-x  3 root   root       4096 Aug 29 14:16 ..
  -rw-r-----  1 oracle oinstall 204288 Aug 29 14:42 RCAT_1_23043_602355789.arc

  On the NFS host, I see

  [root@backups archivelog]# ls -la
  total 68
  drwxr-x---. 14 500 500   4096 Aug 29 14:42 .
  drwxrwxr--.  3 500 500   4096 May  8 13:54 ..
  -rw-r-----.  1 500 500 204288 Aug 29 14:42 RCAT_1_23043_602355789.arc

  The/etc/exports on NFS host has the permissions set to read/write, no_root_squash.
  
  Is there something obvious that I'm missing?

  the folder is created by newspaper archive must have atleat authorisation from 770.

• 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

• archive log deletion pending

  Hi all
  
  I'm working on oracle database enterprise edition 10.2.0.4.I have created a database.the physical standby of the primary database name is prim and the standby database name Eve.He has 100 files of newspapers to archive are generating each size is 300 MB per day. I applied archive log political removal of watch on the primary database. So all the newspaper shifted and applied pending archive are deleted from primary. But my concern is the archive logs staggered into sleep mode. The archivelogs in the standby server must be deleted.how that it can be removed. Help, please

  use RMAN to this effect, as you do in primaries.

  It will make a backup if you need and delete the archivelogs.

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

• Archiving logs - relocation

  Good evening everyone. A bit of my environment:
  
  E-Business R12
  Oracle Enterprise DB 10.2.0.4.0
  
  Split Architecture components:
  
  Server 1 / DB Node (Redhat 5.5 32-bit)
  2 server / applications node
  
  My PROD database resides on a server that has the following specifications (those relevant to my post) about:
  
  Sheet music:
  
  / = 1 TB of total space used 99%
  
  / Backup = 1.75 TB of total space 35% used
  
  / boot = 200 MB
  
  The partitions ' / ' and ' / backup ' are physically different RAID volumes but on the same controller. / is an array of RAID 10 SAS drives the fastest available. /Backup is a RAID 1 array of two 1 TB mirrored SATA drives. I instance db PROD in the partition ' / backup ' keeping on safeguards on deep disk a few days since I backup and then against backups from disk to a tape backup library.
  
  The purpose of my post is to ask for advice on what to do to get out me of the 99% used disk space on my partition condition "/" where is the Pb of PROD. My archives logs files take up to 200 GB. How it would be difficult to move these files on my partition "/ backup" and what effect or consequences that would have the performance since the will ' / backup ' have lower performance of IO and what effect will this have on the RMAN backups?
  
  
  My database uses a PFILE file so I just change the archivelog destination it and bounce the DB? What would happen then to archive logs on the partition ' / '? Couuld I can just move these files to the same destination that I specified in the PFILE file?

  ovlz wrote:
  Thank you for your comments. I must tell you that I am relatively new to work s/n, but I was a sysadmin for a long time. In no time, I learned a lot, but I still have a way to go. At the urging of my essay, I run instead of pfile-spfile. On the PROD, I guess I got scared to make many changes because that's how the senior DBA who has contributed to the implementation done things. I did a bunch of stuff that they did; OEM, discoverer, divide the stands, etc., but I did everything quite yet. These forums are my mentor, for example, if I appreciate the help. Backups and backup strategy are not inherited something I designed, except for the part where I backup the backups on tape.

  Back to point. One of my test case that is a very recent clone works PFILE. I'll change for SPFILE and try to achieve what you have mentioned - change the destination of the archive logs. Once I have change the destination, how to maintain the archive logs existing? Is this something that happens through RMAN? If I change archivelog destination box and then delete old logs archiving? Where is the size or chronological depth of the configured archive logs?

  When an archivelog is written, the information on this specific archivelog are written in the control file. This means that during a recovery, if archive is required, the location, he wrote is known, even if the archivelog destination has been changed because it is written. In other words, destination of the newspaper archive shows the database where to write the new archivelogs. It is not used to tell rman where to find an archivelog existing.

  ' Housekeeping is done with rman '-' backup archivelog all delete input "- or a variation of that you will find in the docs. This command creates a backupset that contains a copy of the archivelogs, then deletes those that were backed up, freeing the space they occupied.

• Archiving logs fill quickly... How to find the culprit?

  Hi, all.
  
  Oracle Dabase 10.2.0.5.0 on RHEL 5
  
  I am followed by a PROD database where the archive logs fill up fast. Archive logs are generated every minute or so... Can you tell me how I can find the culprit and solve the problem... Thank you!

  Use LOGMNR.

  http://psoug.org/reference/dbms_logmnr.html

  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14215/LogMiner.htm#SUTIL019

  Go to these links.

  In addition, check the size of your redo log files. Its can be sized less now.

  # Redo size recommendation

  What should be the size of redlog in OLTP environment such as banks? (10g)

  Concerning
  Asif Kabir

• difference in the values of v$ archived_log; and list of archive logs

  HI friends,
  
  I'm in a dilemma and not able to understand why there is difference in values of:
  
  SQL > select max(sequence#) from v$ archived_log;
  
  MAX(SEQUENCE#)
  --------------
  1085
  
  
  SQL > archive logs list;
  Database log mode Archive Mode
  Active AutoArchive
  Archives/arch/IVR/arch of destination
  More old sequence of journal on line 27
  Log sequence archive 29
  Current log sequence 29
  
  
  Help, please... As it is a Production database.
  DB version:-10.2.0.3
  platform HP - UNIX 64 bit itianum

  AS FAR AS I KNOW,
  Were you running any recovery on the database?

  As said above archive log list shows current information.

  SQL> select max(sequence#) from v$archived_Log;
  
  MAX(SEQUENCE#)--------------            10
  
  SQL> archive log listDatabase log mode              Archive ModeAutomatic archival             EnabledArchive destination            F:\oracle\product\10.1.0\Db_1\RDBMSOldest online log sequence     9Next log sequence to archive   11Current log sequence           11SQL> alter system switch logfile;
  
  System altered.
  
  SQL> select max(sequence#) from v$archived_Log;
  
  MAX(SEQUENCE#)--------------            11
  
  SQL> shutdown immediate;Database closed.Database dismounted.ORACLE instance shut down.SQL> startup mountORACLE instance started.
  
  Total System Global Area  612368384 bytesFixed Size                   790624 bytesVariable Size             170127264 bytesDatabase Buffers          440401920 bytesRedo Buffers                1048576 bytesDatabase mounted.SQL> recover database until cancel;Media recovery complete.SQL> alter database openresetlogs;alter database openresetlogs                           *ERROR at line 1:ORA-02231: missing or invalid option to ALTER DATABASE
  
  SQL> alter database open resetlogs;
  
  Database altered.
  
  SQL> archive log istSP2-0718: illegal ARCHIVE LOG optionSQL> archive log listDatabase log mode              Archive ModeAutomatic archival             EnabledArchive destination            F:\oracle\product\10.1.0\Db_1\RDBMSOldest online log sequence     0Next log sequence to archive   1Current log sequence           1SQL> select max(sequence#) from v$archived_Log;
  
  MAX(SEQUENCE#)--------------            11
  

  Kind regards
  Taj