New log archiving

Similar Questions

• Logs archiving for the RAC ASM basics

  Hello
  
  I have a question about logs archiving on the ASM database located on a RAC. I created a database orcl who has orcl1 instance on node1 and orcl2 on Node2. For the backup of this database, I enabled for the database to archivelog.
  
  After a few transactions and backups, I noticed that there are two sets of archiving logs created on each node in the folder $ORACLE_HOME/dbs. In node 1, it starts with arch1_ * and node2 is arch2_ *.
  
  IWhy is it creates logs archiving on local disks, in which she should ideally create disks asm which is shared between the nodes. My backup application fails with journal archive not found error, because it searches newspaper archives in the other node.
  
  All entries on this will be useful.
  
  Amith

  Hello

  I have a question about logs archiving on the ASM database located on a RAC. I created a database orcl who has orcl1 instance on node1 and orcl2 on Node2. For the backup of this database, I enabled for the database to archivelog.

  After a few transactions and backups, I noticed that there are two sets of archiving logs created on each node in the folder $ORACLE_HOME/dbs. In node 1, it starts with arch1_ * and node2 is arch2_ *.

  I believe that it is missing from your configuration database and Oracle uses the default location. (i.e. your "$ORACLE_HOME/dbs")

  ARCHIVELOG must focus on a shared domain.

  You need the parameter config below:

  SQL> show parameter db_recovery_file
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ------------------------------
  db_recovery_file_dest                string
  db_recovery_file_dest_size           big integer 
  

  Or location of default config:

  SQL> show parameter log_archive_dest
  
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ------------------------------
  log_archive_dest                     string
  

  IWhy is it creates logs archiving on local disks, in which she should ideally create disks asm which is shared between the nodes. My backup application fails with journal archive not found error, because it searches newspaper archives in the other node.

  To resolve this problem see this example:

  SQL> show parameter recover
  
  NAME                                 TYPE        VALUE
  ------------------------------------ ----------- ------------------------------
  db_recovery_file_dest                string
  db_recovery_file_dest_size           big integer 1
  
  SQL> archive log list;
  Database log mode              Archive Mode
  Automatic archival             Enabled
  Archive destination            /u01/app/oracle/product/10.2.0/db_1/dbs/
  Oldest online log sequence     2
  Next log sequence to archive   3
  Current log sequence           3
  SQL>
  
  SQL> alter system set db_recovery_file_dest_size=20G scope=both sid='*';
  
  System altered.
  
  SQL> alter system set db_recovery_file_dest='+FRA' scope=both sid='*';
  
  System altered.
  
  SQL> archive log list;
  Database log mode              Archive Mode
  Automatic archival             Enabled
  Archive destination            USE_DB_RECOVERY_FILE_DEST
  Oldest online log sequence     5
  Next log sequence to archive   6
  Current log sequence           6
  SQL>
  

  With RMAN

  RMAN> CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT 'sys/oracle@db10g1';
  
  new RMAN configuration parameters:
  CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT '*';
  new RMAN configuration parameters are successfully stored
  starting full resync of recovery catalog
  full resync complete
  
  RMAN>  CONFIGURE CHANNEL 2  DEVICE TYPE DISK CONNECT  'sys/oracle@db10g2';
  
  new RMAN configuration parameters:
  CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT '*';
  new RMAN configuration parameters are successfully stored
  starting full resync of recovery catalog
  full resync complete
  
  RMAN> list archivelog all;
  
  using target database control file instead of recovery catalog
  
  List of Archived Log Copies
  Key     Thrd Seq     S Low Time  Name
  ------- ---- ------- - --------- ----
  1       1    3       A 28-FEB-11 /u01/app/oracle/product/10.2.0/db_1/dbs/arch1_3_744216789.dbf
  2       2    2       A 27-FEB-11 /u01/app/oracle/product/10.2.0/db_1/dbs/arch2_2_744216789.dbf
  
  RMAN> crosscheck archivelog all;
  
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid=127 instance=db10g1 devtype=DISK
  allocated channel: ORA_DISK_2
  channel ORA_DISK_2: sid=135 instance=db10g2 devtype=DISK
  validation succeeded for archived log
  archive log filename=/u01/app/oracle/product/10.2.0/db_1/dbs/arch1_3_744216789.dbf recid=1 stamp=744292116
  Crosschecked 1 objects
  
  validation succeeded for archived log
  archive log filename=/u01/app/oracle/product/10.2.0/db_1/dbs/arch2_2_744216789.dbf recid=2 stamp=743939327
  Crosschecked 1 objects
  
  RMAN> backup archivelog all delete input;
  
  Starting backup at 28-FEB-11
  current log archived
  using channel ORA_DISK_1
  using channel ORA_DISK_2
  channel ORA_DISK_1: starting archive log backupset
  channel ORA_DISK_1: specifying archive log(s) in backup set
  input archive log thread=1 sequence=3 recid=1 stamp=744292116
  channel ORA_DISK_1: starting piece 1 at 28-FEB-11
  channel ORA_DISK_2: starting archive log backupset
  channel ORA_DISK_2: specifying archive log(s) in backup set
  input archive log thread=2 sequence=2 recid=2 stamp=743939327
  channel ORA_DISK_2: starting piece 1 at 24-FEB-11
  channel ORA_DISK_1: finished piece 1 at 28-FEB-11
  piece handle=+FRA/db10g/backupset/2011_02_28/annnf0_tag20110228t120354_0.265.744293037 tag=TAG20110228T120354 comment=NONE
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
  channel ORA_DISK_1: deleting archive log(s)
  archive log filename=/u01/app/oracle/product/10.2.0/db_1/dbs/arch1_3_744216789.dbf recid=1 stamp=744292116
  channel ORA_DISK_2: finished piece 1 at 24-FEB-11
  piece handle=+FRA/db10g/backupset/2011_02_24/annnf0_tag20110228t120354_0.266.743940249 tag=TAG20110228T120354 comment=NONE
  channel ORA_DISK_2: backup set complete, elapsed time: 00:00:03
  channel ORA_DISK_2: deleting archive log(s)
  archive log filename=/u01/app/oracle/product/10.2.0/db_1/dbs/arch2_2_744216789.dbf recid=2 stamp=743939327
  channel ORA_DISK_1: starting archive log backupset
  channel ORA_DISK_1: specifying archive log(s) in backup set
  input archive log thread=1 sequence=4 recid=4 stamp=744293023
  input archive log thread=2 sequence=3 recid=3 stamp=743940232
  channel ORA_DISK_1: starting piece 1 at 28-FEB-11
  channel ORA_DISK_1: finished piece 1 at 28-FEB-11
  piece handle=+FRA/db10g/backupset/2011_02_28/annnf0_tag20110228t120354_0.267.744293039 tag=TAG20110228T120354 comment=NONE
  channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
  channel ORA_DISK_1: deleting archive log(s)
  archive log filename=+FRA/db10g/archivelog/2011_02_28/thread_1_seq_4.264.744293023 recid=4 stamp=744293023
  archive log filename=+FRA/db10g/archivelog/2011_02_24/thread_2_seq_3.263.743940231 recid=3 stamp=743940232
  Finished backup at 28-FEB-11
  
  Starting Control File and SPFILE Autobackup at 28-FEB-11
  piece handle=+FRA/db10g/autobackup/2011_02_28/s_744293039.263.744293039 comment=NONE
  Finished Control File and SPFILE Autobackup at 28-FEB-11
  
  SQL> alter system archive log current;
  
  System altered.
  
  RMAN> list archivelog all;
  
  using target database control file instead of recovery catalog
  
  List of Archived Log Copies
  Key     Thrd Seq     S Low Time  Name
  ------- ---- ------- - --------- ----
  5       1    5       A 28-FEB-11 +FRA/db10g/archivelog/2011_02_28/thread_1_seq_5.264.744293089
  6       2    4       A 24-FEB-11 +FRA/db10g/archivelog/2011_02_24/thread_2_seq_4.268.743940307
  
  RMAN> CONFIGURE CHANNEL 1 DEVICE TYPE DISK CLEAR;
  
  old RMAN configuration parameters:
  CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT '*';
  old RMAN configuration parameters are successfully deleted
  
  RMAN> CONFIGURE CHANNEL 2 DEVICE TYPE DISK CLEAR;
  
  old RMAN configuration parameters:
  CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT '*';
  old RMAN configuration parameters are successfully deleted
  
  RMAN> exit
  
  Recovery Manager complete.
  

  Kind regards
  Levi Pereira

  Published by: Levi Pereira on February 28, 2011 12:16

• what setting to change to avoid the "unable to allocate new log"

  Hello everyone.
  I'm on 9i r2 on windows server 2003 edition of the SD with attached ISCSI. I have the drive 1 recovery as well as DBF newspaper group in the data directory. 2 other groups redo are on the 2 local disks separated and archiving logs (in another folder).
  
  I'm getting some errors "cannot allocate new logs" every two days and in Event Viewer "process Archive error: Instance ORACLE prdps - cannot allocate Journal, check-in required.
  
  
  I do not know what setting I should change.
  
  Current configuration:
  db_writer_processes 1
  dbwr_io_slaves 0
  
  
  
  Here is the output from v$ sysstat:
  49 8 7410575 written DBWR checkpoint buffers
  50 8 7748 written DBWR transaction table
  51 DBWR undo block writes 8 4600265
  52 DBWR revisited being written 8 5313 buffer
  DBWR 53 free ask 8 26383
  54 DBWR free buffers are 8 19838373
  55 DBWR lru scans 21831-8
  56 DBWR summed scan depth 8 21265425
  57 8 21265425 scanned DBWR buffers
  58 control DBWR 8 1719 points
  59 DBWR cross instance writes 40 0
  60 fusion DBWR written 40 0
  
  
  It's alert.log:
  Fri Mar 06 00:25:52 2009
  Arc0: Complete 1 thread 1 log archiving sequence 7004
  Fri Mar 06 00:25:54 2009
  Thread 1 Advanced for you connect to sequence 7006
  Currently Journal # 3 seq # 7006 mem # 0: E:\ORACLE\ORADATA\PRDPS\REDO03A. JOURNAL
  Currently Journal # 3 seq # 7006 mem # 1: F:\ORACLE\ORADATA\PRDPS\REDO03B. JOURNAL
  Currently Journal # 3 seq # 7006 mem # 2: G:\ORACLE\ORADATA\PRDPS\REDO03C. JOURNAL
  Fri Mar 06 00:25:54 2009
  Arc1: Evaluating archive log 2 thread 1 sequence 7005
  Arc1: Begins to archive log 2 thread 1 sequence 7005
  Creating archives LOG_ARCHIVE_DEST_1 destination: "F:\ORACLE\ORADATA\PRDPS\ARCHIVE\PRDPS_001_07005.ARC."
  Fri Mar 06 00:26:03 2009
  Thread 1 Advanced for you connect to sequence 7007
  Currently journal # 1, seq # 7007 mem # 0: E:\ORACLE\ORADATA\PRDPS\REDO01A. JOURNAL
  Currently journal # 1, seq # 7007 mem # 1: F:\ORACLE\ORADATA\PRDPS\REDO01B. JOURNAL
  Currently journal # 1, seq # 7007 mem # 2: G:\ORACLE\ORADATA\PRDPS\REDO01C. JOURNAL
  Fri Mar 06 00:26:03 2009
  Arc0: Assessment of the archive log 2 thread 1 sequence 7005
  Arc0: Impossible to archive log 2 thread 1 sequence 7005
  Newspapers archived by another process
  Arc0: Assessment of the 3 thread 1 sequence 7006 log archives
  Arc0: Starts to archive log 3 thread 1 sequence 7006
  Creating archives LOG_ARCHIVE_DEST_1 destination: "F:\ORACLE\ORADATA\PRDPS\ARCHIVE\PRDPS_001_07006.ARC."
  Fri Mar 06 00:26:15 2009
  Arc1: Finished 2 thread 1 log archiving sequence 7005
  Arc1: Evaluating archive log 3 thread 1 sequence 7006
  Arc1: Impossible to archive log 3 thread 1 sequence 7006
  Newspapers archived by another process
  Fri Mar 06 00:26:16 2009
  Thread 1 cannot allot of new newspapers, sequence 7008
  All newspapers need to check-in online
  Currently journal # 1, seq # 7007 mem # 0: E:\ORACLE\ORADATA\PRDPS\REDO01A. JOURNAL
  Currently journal # 1, seq # 7007 mem # 1: F:\ORACLE\ORADATA\PRDPS\REDO01B. JOURNAL
  Currently journal # 1, seq # 7007 mem # 2: G:\ORACLE\ORADATA\PRDPS\REDO01C. JOURNAL
  Thread 1 Advanced for you connect to sequence 7008
  Currently Journal # 2 seq # 7008 mem # 0: E:\ORACLE\ORADATA\PRDPS\REDO02A. JOURNAL
  Currently Journal # 2 seq # 7008 mem # 1: F:\ORACLE\ORADATA\PRDPS\REDO02B. JOURNAL
  Currently Journal # 2 seq # 7008 mem # 2: G:\ORACLE\ORADATA\PRDPS\REDO02C. JOURNAL
  Fri Mar 06 00:26:16 2009
  Arc1: Evaluating archive log 3 thread 1 sequence 7006
  Arc1: Impossible to archive log 3 thread 1 sequence 7006
  Newspapers archived by another process
  Arc1: Evaluating archive log 1 thread 1 sequence 7007
  Arc1: Beginning to archive journal 1-wire 1 sequence 7007
  
  
  Should I just change
  db_writer_processes 1
  dbwr_io_slaves 2
  
  Thank you
  Any help appreciated.

  This message indicates that Oracle wants to re-use a redo log file, but
  the
  associated with corresponding control point is not over. In this case,.
  Oracle
  Wait for the control point is carried out entirely. This situation
  may be encountered especially when transactional activity is
  important.

  search for:
  -Background checkpoint started.
  -Control your mat point.

  These two statistics should not differ more than once. If it is

  not true, your base weighs on the control points. LGWR does not reach
  continue
  next write operations that ends the control points.

  Three reasons may explain this difference:

  -A frequency of control points which is too high.
  -A control points are starting but not filling not
  -One DBWR writing too slowly.

  How to resolve incomplete control points is through tuning
  control points and
  newspapers:

  (1) gives the checkpoint process more time to scroll through newspapers
  -Add more redo log groups
  -increase the size of the logs again
  (2) to reduce the frequency of control points
  -increase the LOG_CHECKPOINT_INTERVAL
  -increase the size of newspapers in restoration online
  (3) improve the effectiveness of the control points for the CKPT process
  CHECKPOINT_PROCESS = TRUE
  (4) set LOG_CHECKPOINT_TIMEOUT = 0. This disables the verification script
  based on
  time interval.
  (5) another way to solve this error is for DBWR to write quickly
  the dirty
  buffers to disk. The parameter associated with this task is:

  DB_BLOCK_CHECKPOINT_BATCH.

  DB_BLOCK_CHECKPOINT_BATCH specifies the number of blocks that are
  dedicated
  inside the batch size for writing the control points. When you want to
  speed up
  control points, it is necessary to increase this value.

• RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure

  Hi Oracle Community,

  I have a few databases (11.2.0.4 POWER 2 block and 12.1.0.2) with Data Guard. Back up this database with RMAN to ribbons, only on the primaries.

  During the backup, sometimes I got RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure

  By reason of this global warning to backup status is "COMPLETED WITH WARNINGS". Is it possible to remove this warning, or perhaps change RMAN configuration to avoid the appearance of this warning?

  Concerning

  J

  Where is the problem on these warnings? If you do not want to see such warnings, why not simply to perform the removal of the archivelogs in a separate step? For example:

  RMAN> backup database plus archivelog;
  RMAN> delete noprompt archivelog all completed before 'sysdate-1';
  

• Delete logs archive > 1 day

  Hi all

  9i

  RHEL5

  I posted a thread here on how to remove the log archiving liked only 1 day for both PRIMARY and standby database.

  But I don't find it anymore

  Is it possible to search all the contents of my son using Keywork "delete archive logs?

  Thank you all,

  JC

  Hello;

  You old thread:

  Remove the archivelogs and old backups

  Best regards

  mseberg

• No complete checkpoint - cannot allocate new log

  Alerts log is filled with these messages. What is the best way to solve this problem?

  Thu Apr 02 12:54:54 2015
  Thread 1 cannot allocate new log, sequence 138273
  Checkpoint not complete
    Current log# 2 seq# 138272 mem# 0: /du01/ORACLE/ORADATA/IMR1/redo02.log
  Thread 1 advanced to log sequence 138273 (LGWR switch)
    Current log# 3 seq# 138273 mem# 0: /du01/ORACLE/ORADATA/IMR1/redo03.log
  Thu Apr 02 12:55:21 2015
  Thread 1 cannot allocate new log, sequence 138274
  Checkpoint not complete
    Current log# 3 seq# 138273 mem# 0: /du01/ORACLE/ORADATA/IMR1/redo03.log
  Thread 1 advanced to log sequence 138274 (LGWR switch)
    Current log# 1 seq# 138274 mem# 0: /du01/ORACLE/ORADATA/IMR1/redo01.log
  Thu Apr 02 12:55:45 2015
  Thread 1 cannot allocate new log, sequence 138275
  Checkpoint not complete
  ...
  ...
  ...
  
  oracle@ORA3> select group#,thread#,sequence#,bytes/1024/1024 size_mb, members,status from v$log;
  
      GROUP#    THREAD#  SEQUENCE#    SIZE_MB    MEMBERS STATUS
  ---------- ---------- ---------- ---------- ---------- ----------------
           1          1     138301         25          1 ACTIVE
           2          1     138302         25          1 CURRENT
           3          1     138300         25          1 INACTIVE
  

  INCREASE the size of the REDO of a factor of 10 files!

• Purge logs archiving on things primary and Standby and for Data Guard RMAN

  
  Hi, I saw a couple of orders in regard to the purge archive records in a Data Guard configuration.

  Set UP the STRATEGY of SUPPRESSION of ARCHIVE to SHIPPED to All RELIEF;

  Set UP the STRATEGY of ARCHIVELOG DELETION to APPLIED on All RELIEF;

  Q1. The above only removes logs archiving to the primary or primary and Standby?

  Q2. If deletions above archive logs on the primary, is it really remove them (immediately) or does the FRA to delete if space is needed?

  I also saw

  CONFIGURE ARCHIVELOG DELETION POLICY TO SAVED;

  Q3. That what precedes, and once again it is something that you re primary side?

  I saw the following advice in the manual of Concepts of data protection & Admin

  Configure the DB_UNIQUE_NAME in RMAN for each database (primary and Standby) so RMAN can connect remotely to him

  Q4. Why would I want my primary ro connect to the RMAN Repository (I use the local control file) of the standby? (is this for me to say define RMAN configuration settings in the Standby) manual

  Q5. Should I only work with the RMAN Repository on the primary or should I be also in things in the deposits of RMAN (i.e. control files) of the standby?

  Q6. If I am (usually mounted but not open) Physics, of standby I able to connect to its own local repository for RMAN (i.e. control based on files) while sleep mode is just mounted?

  Q7. Similiarly if I have an old lofgical (i.e. effectively read-only), to even connect to the local RMAN Repository of Eve?

  Q8. What is the most common way to schedule a RMAN backup to such an environment? example cron, planner of the OEM, DBMS_SCHEDULER? MY instinct is cron script as Planner OEM requires running the OEM service and DBMS_SCHEDULER requires the data runs?

  Any idea greatly appreciated,

  Jim

  The above only removes logs archiving to the primary or primary and Standby?

  When CONFIGURE you a deletion policy, the configuration applies to all destinations archive

  including the flash recovery area. BACKUP - ENTRY DELETE and DELETE - ARCHIVELOG obey this configuration, like the flash recovery area.

  You can also CONFIGURE an archived redo log political suppression that newspapers are eligible for deletion only after being applied to or transferred to database backup destinations.

  If deletions above archive logs on the primary, is it really remove them (immediately) or does the FRA to delete if space is needed?

  Its a configuration, it will not erase by itself.

  If you want to use FRA for the automatic removal of the archivelogs on a database of physical before you do this:

  1. make sure that DB_RECOVERY_FILE_DEST is set to FRA - view parameter DB_RECOVERY_FILE_DEST - and - setting DB_RECOVERY_FILE_DEST_SIZE

  2. do you have political RMAN primary and Standby set - CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON ALL STANDBY;

  If you want to keep archives more you can control how long keep logs by adjusting the size of the FRA

  Great example:

  http://emrebaransel.blogspot.com/2009/03/delete-applied-archivelogs-on-standby.html

  All Oracle is worth a peek here:

  http://emrebaransel.blogspot.com/

  That what precedes, and once again it is something that you re primary side?

  I would never use it. I always had it put it this way:

  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

  I would use only 'BACKED UP' for the data protection system. Usually it tell oracle how many times to back up before removing.

  Why would I want my primary ro connect to the RMAN Repository?

  Because if you break down, you want to be able to backup there, too.

  Also if it remains idle for awhile you want.

  Should I only work with the RMAN Repository on the primary or should I be also in things in the deposits of RMAN (i.e. control files) of the standby?

  Always use a database of catalog RMAN with Data Guard.

  If I am (usually mounted but not open) Physics, of standby I able to connect to its own local repository for RMAN (i.e. control based on files) while sleep mode is just mounted?

  Same answer as 5, use a catalog database.

  Similiarly if I have an old lofgical (i.e. effectively read-only), to even connect to the local RMAN Repository of Eve?

  Same answer as 5, use a catalog database.

  What is the most common way to schedule a RMAN backup to such an environment? example cron, planner of the OEM, DBMS_SCHEDULER? MY instinct is cron script as Planner OEM requires running the OEM service and DBMS_SCHEDULER requires the data runs?

  I think cron is still, but they all work. I like cron because the database has a problem at work always reports its results.

  Best regards

  mseberg

  Summary

  Always use a database with RMAN catalog.

  Always use CRF with RMAN.

  Always set the deletion «To APPLY ON ALL STANDBY» policy

  DB_RECOVERY_FILE_DEST_SIZE determines how long to keep the archives with this configuration.

  Post edited by: mseberg

• Reg apply log archiving after the transfer of data files

  Hi all
  
  That I reinstalled the main server of the D-Drive E-reader data files using the command line.

  C:\>Move <source_path> <destination_path>

  The redo logs for the move operation will apply on the eve of the database?
  In addition, what happens if the data files are moved manually in the primary database (i.e. without using the command prompt)?
  
  
  Thank you
  Madhu

  See this doc. Keyword search Rename a data file in the primary database

  http://docs.Oracle.com/CD/B28359_01/server.111/b28294/manage_ps.htm#i1034172

  Also, you need to update primary database controlfile if some moment of the file made...

  And also close this thread

  Reg apply log archiving after the transfer of data files

  As it would help in the forum of maintenance to clean.

• Size of the huge log archive

  I have 5 redo log files. Each is 4 GB. There are huge transactions (1800-2000 per second). So we have every hour 5-6 journal of the switches. So all the hours of archives journal 20 to 24 GB and daily increase in size, the size 480 GB.
  
  I had planned to take an incremental backup of level 1 and level 0 per week daily with the option delete log archiving 'sysdate-1 '.
  
  But we have little storage if, it is impossible to the sphere 480 GB per day and take backup of these 480 GB for 7 days (480 * 7) GB = 4 TB. How can I correct this situation? Help, please.

  1 disk is cheap
  2 the onus on those who "Advanced" application
  3 you can use Log Miner to check what is happening.

  You need to this address with application developers and/or clients and/or buy the disc.
  There are no other solutions.

  -----------
  Sybrand Bakker
  Senior Oracle DBA

  Published by: sybrand_b on July 16, 2012 11:11

• Log archiving

  Dear experts,
  
  I have to test the size of the log archive every transaction. the next step needs to be done for this test
  
  1 running dml scripts in bulk
  2 need to find how the size of the log file archive created on the archive location.
  
  based on what we have to give the stats that particular transaction generated as much redo log file from archive. can you please provide the script to do this. Thanks in advance.

  Oragg wrote:
  Dear experts,

  I have to test the size of the log archive every transaction. the next step needs to be done for this test

  1 running dml scripts in bulk
  2 need to find how the size of the log file archive created on the archive location.

  based on what we have to give the stats that particular transaction generated as much redo log file from archive. can you please provide the script to do this. Thanks in advance.

  Lets assume that you have loaded data for 1 day or 1 hour as below

  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;
  

• New log files not 100% usage

  I just recently made my web app with new features to require my BDB to have at least 65% use of disk (from the default of 50%) and use of file minimum of 25% (an increase of 5% by default). At the start of my application, I temporarily coded an env.cleanLog () to force a cleanup of the logs to bring the DB up to these parameters to use.
  
  I have deployed the application and its been blowing away the clean process now for about 2.5 hours. It generates a new log file of 100 MB each minute he tries to compact the DB. However, at 2:30, I just ran DbSpace and the use of DB is only up to 51%. Perhaps more surprising are the two following facts:
  (1) newspapers newly created vacuuming files are nowhere near 100% use
  (2) some newly created log files have already been cleaned (deleted) themselves.
  
  There are 0 updates which passes to the BDB while this process is running. My understanding is that when the cleaner removed the old files and created new files, only good/valid data are written on new files. However, this is not the case. Can someone enlighten me? I am pleased to read the docs if someone can point me in the right direction.
  
  Thank you.

  The vacuum cleaner stops turning after the cleaning of several files that are in the environment, because it shows he does not progress. He wakes up again to do clean-up as more data is written by the app. If you call cleanLog, of course, he will do more cleaning.

  The FAQ contains a section of performance that you may have missed. The use of the DbCacheSize is there.
  http://www.Oracle.com/technetwork/database/BerkeleyDB/je-FAQ-096044.html#34

  In general, you need size your cache to your own performance tests. DbCacheSize gives you a guideline. Not enough memory to hold the internal nodes is strongly recommended to achieve a good performance, but your own analysis - including with cleaning of the newspaper - is the last word.

  -mark

• Cannot add the new log file for the 11g database.

  Salvation of DBA
  
  I'm not able to add the log file, I receive the error message when the database is added.
  
  SQL > alter database add logfile group 3 ('/ oracle/DEV/db/apps_st/data/log03a.dbf','/oracle/DEV/db/apps_st/data/log03a.dbf') Re-use of size of 50 m;
  alter database add logfile group 3 ('/ oracle/DEV/db/apps_st/data/log03a.dbf','/oracle/DEV/db/apps_st/data/log03a.dbf') Re-use of 50 m of size
  *
  ERROR on line 1:
  ORA-01505: Error adding log files
  ORA-01577: cannot add the log file ' / oracle/DEV/db/apps_st/data/log03a.dbf'-fichier
  already a part of the database
  
  SQL > select a.group #, a.status, a member of the journal of v$ a, v$ logfile b where a.group # order of b.group = # 1;
  
  GROUP # MEMBER STATUS
  ---------- ---------------------------------------- ----------
  1 ACTIVE /oracle/DEV/db/apps_st/data/log01a.dbf
  1 ACTIVE /oracle/DEV/db/apps_st/data/log01b.dbf
  /Oracle/DEV/db/apps_st/data/log02a.dbf CURRENT 2
  /Oracle/DEV/db/apps_st/data/log02b.dbf CURRENT 2
  
  Kindly help me to add the new log file to my database.
  
  Thank you
  SG

  PGO

  Please see (how can redo log group be dropped when it ever becomes inactive?) [ID] 730827.1).

  Thank you
  Hussein

• Cannot allocate New Log Error and transactions

  Oracle 9.2.0.4
  
  The user runs a report that executes PL/SQL. A SELECT dynamiic statement is generated and executed. This particular request is long term and ends when an error message "Unable to allocate new logs" appears in the database alert log file. The report shows no selected data. No Oracle error have been raised/caught in the trap during the course of the PL/SQL report. Immediately, the user runs the same exact report again and gets the selected data.
  
  My questions:
  
  Can the occurrence of an "Unable to allocate new logs" entry to the database alert file cause queries to long term to retrieve any data?
  Can there be a setting in the database triggers an error ORA - so that the report could identify when this happens?
  
  I know that the DBA should treat the cause. I just want to know what the report of PL/SQL can do to intercept it when it arrives.
  
  Thank you

  Can the occurrence of an "Unable to allocate new logs" entry to the database alert file cause queries to long term to retrieve any data?

  Unless there is a software bug, 'impossible to allocate new log' can freeze the instance of database for a while, but that's all.

  Can there be a setting in the database triggers an error ORA - so that the report could identify when this happens?

  As far as I know, no.

  9.2.0.4 is an Oracle either fully supported version. You must spend at least 10g.

• sleep not applying new mode do not log archiving

  I just created waiting for database... but not his newspaper archive application...
  
  When I checked the alerlog standby file...
  ORA-19527 physical standby redo log needs to be renamed

  If you use pfile to standby then do the following setting in the pfile file entry

  log_file_name_convert = 'test', 'test '.

  and follow the steps above.

  concerning

• Thread 1 cannot allocate new logs?

  Oracle 11.2.0.4 / Windows 2008 Server

  I started to notice the mistakes below in the alerts log

  Private stream flush is not complete

  Thread 1 cannot allot of new newspapers, sequence 431128-may-2015 11:54:34 CEST UNKNOWN 16

  Archived journal 4169 extra for each sequence 1 4309 0xd4e67ae9 dest ID thread entry 1:

  I checked the newspaper switching frequency which seems fine...

  27-MAY-2015 6 2 1 2 3 2 2 2 4 4 4 4 3 5 4 4 4 3 2 2 2 2 6 1

  28-MAY-2015 12 1 2 1 3 2 2 4 3 3 4 3 0 0 0 0 0 0 0 0 0 0 0 0

  I have two redo log groups made up of military record three size 51200 KB

  Don't you think that it would solve this problem to increase the size of the redo log files? thoughts would be greatly appreciated!

  Please follow the following Doc ID 435887.1, 781999.1 docs that will solve your problem. It's hard to tell you the size of your redologfile with spikes knowing anythink on your system. These DOCUMENTS will help you.