Archive logs always smaller in size then redo logs

Similar Questions

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

• Size archived logs

  Hello
  1. how to set the size of the logs archived in 10 g R2?
  2. how to set the size of the logs archived in 8.1.7?
  
  Thank you.

  It is not independent version.

  Size ARCHIVELOG is noramlly online redolog file size, but if the issue change you journal immediately current archiving system after a newspaper spend then archive the log size can be smaller than the redolog. This can happen if the redolog files are filled.

  You can set the size when the database was created or you can dropn and recreate newspaper members while the DB is up and running but the Logi status must be INACTIVE

• When I add text to an image that starts as a RAW file, I have no problem. When I try to add text to an image that is only a jpg file, the size of the text is extremely low. Even when I change the the font size to 72 pt, it is always small. How can I fix i

  When I add text to an image that starts as a RAW file, I have no problem. When I try to add text to an image that is only a jpg file, the size of the text is extremely low. Even when I change the the font size to 72 pt, it is always small. How can I fix it?

  You set the font size to a size that is suitable for the size of the document.   Size of the document may vary everywhere.   To resolve this problem in action, I solved in scaling the document to a known size then use a font suitable for a document of this size.  When you resize an image using size with resample Images not only checked a single pixel is change everything that is changed is the DPI image resolution setting.  So if you size a picture 8 "wide you choose a font size is good for wide image 8" the Save action.  To work around the problem of changing the size of the printing I wrote a Script to use in such an action.  The script is used twice, there is a backup and restore script.   The first time that the script is used the script records the resolution DPI images in the metadata documents.  The second time that the script is executed, it retrieves the registered PID parameter deletes the record of metadata from images and set the DPI images that had been saved.    If the use of fonts for the document 8 "will be resized to fit the print original size.

  In a script, you can calculate a correct font size to use.  Actions cannot retrieve information or use logic. They need to use the Plug-ing and Script where logic is needed.  When you make using Photoshop UI you use your eyes and brain.

  Package of shares of crafts UPDATE August 10, 2014 added conditional measures Action Palette tips.
  Contains

  • Action Actions Palette Tips.txt
  • Action creating Guidelines.txt
  • Action dealing with Image Size.txt
  • Strengthened through scripts functions.txt Photoshop action
  • CraftedActions.atn sample Action set includes an example of Watermarking action
  • Sample Photoshop Actions.txt CraftedActions the value stored in a text file.
  • More then a dozen Scripts for actions

  Example of
  Download

• Difference between redo logfiles, Undo Tablespace, Archive log data file

  Can some please highlight the difference between Undo and Redo Logs
  Also why we need to separate the archive logs when the recovery log data can be written directly in data files...
  
  Help you will be highly appreciated...

  Hello

  Ed gave you a very good answer.

  Rememeber database files are online and they are written to by DBWR process. So we have the database files, redo log files and archive logs.
  In order to avoid all the crawl log when you perform a recovery, database performs control points that summarize the State of the database. This operation of control point provides a shortcut to the recovery. At the checkpoint, the database knows that all incorrect pages were written to disk (for example, database files). At the time of recovery, the log (which includes-finished and unfinished transactions) is used to bring the database to a consistent state. The system locates the time of the last checkpoint and returned to this position in the log file. Then he restores forward all completed transactions (read committed) that occurred after the last checkpoint and rolls back all transactions that were not committed, but that began before the last checkpoint. This is where online log files are used.

  Now imagine that you need to back up your database GB 100 + all 10 minutes. It would be a waste of space! So you take a backup of your database at time t and backups of archiver process redo logs periodically to check the newspapers so that redo log files can be replaced and RMAN will use the last backup and archive the log files to recover your database at the time.

  Now, I mentioned the checkpoint process. The Checkpoint process regularly launches a control point that uses DBWR to rewrite all the blocks Sales in the data files, so synchronize the database. Imagine one dam is running and have exhausted all the redo log files. At this point, Oracle will wait until all Sales already queued blocks have been written to the buffer on disk (database files) foremost him redo log files can be considered as superfluous and available for re-use (i.e. can be overwritten). This will result in the following message in the alert.log:

  Thread 1 advanced to log sequence 17973
    Current log# 3 seq# 17973 mem# 0: /oracle/data/HAM1/log3aHAM1.dbf
    Current log# 3 seq# 17973 mem# 1: /oracle/data/HAM1/log3bHAM1.dbf
  Thread 1 cannot allocate new log, sequence 17974
  Checkpoint not complete
    Current log# 3 seq# 17973 mem# 0: /oracle/data/HAM1/log3aHAM1.dbf
    Current log# 3 seq# 17973 mem# 1: /oracle/data/HAM1/log3bHAM1.dbf
  Thread 1 advanced to log sequence 17974
  

  I am sure you have done the following:

  alter database mount;
  
  Database altered.
  

  When you mount a database, Oracle combines the instance started the database. Oracle control files are opened and read. However, no checking such as the restore/recovery is performed

  alter database open;
  
  Database altered.
  

  An open command opens the data files, recovery logs, it performs automatic and consistency of database recovery. At this point, the database is now ready to be used by all valid users.

  HTH,

  Mich

  Published by: Mich Talebzadeh on November 19, 2011 16:57

• 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

• Redo archive log file extension

  Version: 11 g
  OPERATING SYSTEM: AIX 5.3
  
  After you have enabled archiving, I noticed that archives logs files have the extension * .dbf. Is this normal?

  close the database and putting into service again.

  Then, check the setting.

  Concerning
  Asif Kabir

• 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

• Archive log file bloat - is currently out of cold back to the top of the best strategy?

  Hi friends,
  
  I have a database 10 g. / WinSvr2003 making heavy spatial processing of the Oracle.
  
  Previously, I ran the database in log mode archive and sparked a lot of files to archive log. 150 G (the worst week).
  
  I got fed up with backups (incremental) RMAN night heavy and put the database in a mode non - archive journal. (I was also worried about the time to get the data back out of band).
  
  Now, I come to launch the next nightly bat file: -.
  
  oradim-stop-sid DEV - syspwd *.
  
  del /S /Q D:\oracleBackup\DEV\*
  
  XCopy/e D:\oracle\product\10.2.0\oradata\DEV D:\oracleBackup\DEV
  
  oradim-startup-sid DEV - syspwd *.
  
  ----------------------------------------------------------------------------------------------------------
  
  1 week ago - when I arrived-in the morning the database had not restarted due to an inconsistency of data file.
  Recover the database fixed.
  
  I guess he had something that this necessary in the redo log files? (its mode no - archive).
  
  I have a DB 24/7.
  
  This cold offline backup is the best strategy to avoid the bloat of log file archive
  
  I can always use RMAN and do not back up files of newspaper Archives? How can I make sure that it is a consistent RMAN backup if she has no access to archive the log files. (I just use RMAN after an immediate stop - restart?)
  
  How instruct you RMAN is not to get the files to archive log?
  
  DATABASE INCREMENTAL LEVEL 0 BACKUP; <-this leaves archive the log file out of the backup.
  
  Thanks in advance.
  
  See you soon,.
  
  AA
  
  P.S. This is my first post on this forum. Yes!

  If you
  a. make a backup of the database CONSISTENT (that is to say in MOUNT but not OPEN) with RMAN
  b. do not save the ArchiveLogs
  c. yet the ArchiveLogs to create the database in ARCHIVELOG mode,

  You can still use the combination of consistent backup and ArchiveLogs generated since the backup database (assuming that the ArchiveLogs are still on the disk) in the method of 'Refresh '.

  In other words, RESTORE (but not RETRIEVE and OPEN) the database of the RMAN.
  Using sql RESTORE DATABASE with the HELP of BACKUP CONTROLFILE to 'Updating' then apply ArchiveLogs for what is just restored.

  See http://hemantoracledba.blogspot.com/2007/05/rollforward-from-cold-backup.html

  Hemant K Collette

• Manually apply archive logs waiting

  RDBMS Version: 11.2.0.4

  OS: RHEL 6.6

  As I understand it, if I want to manually apply archive logs, I do the 2 steps.

  But, how can I do watch DB to accept (add it as part of the eve DB) logs archiving transferred manually?

  That is to say. How can force you standby DB to add these archiving logs to its control file?

  Step 1. First stop the current recovery process (MRP) as

  ALTER database recover managed standby database cancel;

  Then transfer must all logs archiving of primary school next door waiting and apply manually using below command.

  Step 2. recover a database on hold until cancel;

  Hello

  To do this manually, you must:

  (a) manually transfer logs archived redo of primary site on backup site

  (b) lets say to the backup site, you have this path ' / archives/database / ' and in this way, there are the archived redo logs

  Then, in the backup site, you must catalog the logs archived redo with RMAN

  RMAN > CATALOGUE START WITH "/ archives/database /";

  (c) Once catalogued recovery logs archived, you can start the recovery media

  change recover managed standby database disconnect log file using current;

  or

  ALTER database recover managed standby database disconnect;

  (d) monitor the alerts log to see if this transferred manually and asking unregistered archived redo logs

  Kind regards

  Juan M

• 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

• 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

• 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
  

• 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