Size log Archive

Similar Questions

• 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

• 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

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

• 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

• Estimate of the size of archives (archive)

  Hello
  I want to export an archive from the applet archive with a specific query.
  I would estimate the size of archive final before running it (I want to avoid risk to reach the limit of disk space).
  You know a way to estimate the volume of files intended for export? (DB queries, tools?)
  Thanks in advance,
  Leo

  A good question, but no easy answer.

  A collection of archive may have a query to export, you could take this query, improve it with dFileSize (according to the table of Documents ) and get a report of the size of back content items. Then, you will need to add a few extra bytes for metadata. Finally, you need estimate how zip compresses the exported data.

  In addition, for really important exports, not only space, but also time can be a concern. And here, a unique experience can tell you what is best.

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

• 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

• 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

• Size of backup log archiving.

  Hello
  I want to know if each archivelog is saved in a single file. Is there any question who? I can't see it in RC_BACKUP_ARCHIVELOG_DETAILS.
  
  
  My script is:
  BACKUP
  FORMAT 'arch-s %s - p %p - t %t'
  FILESPERSET 4
  SETSIZE 300000
  ARCHIVELOG
  ALL THE
  REMOVE THE ENTRY;
  
  Our archived log is 250 MB each.
  
  Thanks a lot before.

  Hello

  You must increase the size of the backup piece in the game currently backup you create each of 300 MB (300000 SETSIZE) and each archive log size is 250 MB. You will need to create each pice of 1 GB backup to fit 4 archives.

  Please take a look at the first link I'm posting for more information in this regard.

  See you soon,.

  Francisco Munoz Alvarez
  http://www.oraclenz.com

• How long should we keep logs archived in the comic book?

  11.2.0.4 DB Oracle Linux 6.5

  We have a database whose archive generation is as follows.

  Average of generation of archive log: 400 GB/day

  Max log generation: 900 GB/day

  Archive log diskgroup size: 4 TB

  Backup strategy: we take full backups on Monday and Wednesday and Level1 for the rest of the days.

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

  Sunday-> level 0 backup

  Monday-> level 1 backup

  Tuesday-> level 1 backup

  Wednesday-> level 0 backup

  Thursday-> level 1 backup

  Friday-> level 1 backup

  Saturday-> level 1 backup

  Both Level0 and Level1 scripts have MORE ARCHIVELOG; (without a clause to DELETE all THE ENTRIES )

  We have archiveLog backup script that runs at 10:00 and 16:00 which does not REMOVE all ENTRIES either.

  We serve the archivelogs of Level0 and Level1 backup scripts, with the following command

  delete noprompt archivelog until 'SYSDATE -2";

  Question1. What is the industry standard to keep (retention period), archiving within DB logs? Is there a 'formula' / rule for this? When a restore, recovery lose us not a lot of time restore backup media archivelogs. That's why we stay 2 days now archivelog within the DB.

  Question2. We have 4 TB of space to store the archivelogs in this particular PB. With 900 GB Max generation arch daily newspapers, we can keep safe the last 3 days of the archivelogs. Right? I mean, is there a possibility of hitting the terrible archiver error if we increase the shelf life of the archive logs using the delete noprompt archivelog until 'SYSDATE -3';

  N ° DELETE OBSOLETE removes old newspapers also all the log_archive_dest.

  
  

  I could be wrong, but this is the first I hear of this and on a quick scan, I found no support in that either rman reference or guide the user to rman.  Could cite your source?

  DELETE OBSOLETE is not the same thing as REMOVE EXPIRES.

  -EDIT

  Never mind.  I found it.

  DELETE

  OBSOLETE

  Removes backups of data files and copies stored in the repository RMAN which are obsolete, in other words, is no longer required (see example 2-66). RMAN also deletes the log of the obsolete filesand archived redo log backups. RMAN determines what backups and copies of data files are no longer needed, which in turn determines what records (and backups of logs) are no longer needed. RMAN considers that the creation of a data file as a backup to decide which connects to keep.

  Post edited by: EdStevens

  Historically, I saved my archivelogs with the option to DELETE the ENTRIES, I never had reason to notice or question this behavior... a rman DELETE OBSOLETE reach out to the archivelogs themselves.   Thinking maybe it was related to the maintenance of the FRA, I just tried a little test in two ways... archivlogs wrote to FRA and archivelogs writes destined for non - FRA.  Of course, anyway DELETE OBSOLETE also deleted real archivelogs.  I don't know that I'll change my procedures as well, but it is good to know.

  I learned something new today.  Can I go home now?

• New log archiving

  Hi all

  11.2.0.1

  AIX 6.1

  Our database crashes again due to the full archive log.

  I remove all in the fast_recovery_area, so the size will be free

  and cancel the stop the database, but still the same error:

  SQL > startup

  ORACLE instance started.

  Total System Global Area 6196547584 bytes

  Bytes of size 2232952 fixed

  3657436552 variable size bytes

  2516582400 of database buffers bytes

  Redo buffers 20295680 bytes

  Mounted database.

  ORA-03113: end of file on communication channel

  Process ID: 7078052

  Session ID: 125 serial number: 5

  Please helppp.

  Thank you

  zxy

  Hello

  How much free space you have yesterday:

  / u02/oracle/fast_recovery_area/BATCHQAT /.

  / U02 is full?

  Try:

  bootable media;

  ALTER database noarchivelog

  change the database open.

  Kind regards.

• Cannot create recovery logs archived

  Oracle 11.2.0.3 in Windows Server 2008 64 bit.
  I try to put in place the mode archive in a database:
  

  C:\Users\Admin > SET ORACLE_SID = BDSPROD
  
  C:\Users\Admin > SQLPLUS/nolog
  
  SQL * more: Production of liberation 11.2.0.3.0 Thu Oct 25 12:28:59 2012
  
  Copyright (c) 1982, 2011, Oracle. All rights reserved.
  
  SQL > connect sys/oracle as a sysdba
  Connected.
  SQL > select log_mode from v database $;
  
  LOG_MODE
  ------------
  NOARCHIVELOG
  
  SQL > ALTER SYSTEM SET log_archive_start = TRUE SCOPE = spfile;
  
  Modified system.
  
  SQL > ALTER SYSTEM SET log_archive_dest = a: \oradata\BDSPROD\archivelogs\' SCOPE = spfile;
  
  Modified system.
  
  SQL > shutdown immediate;
  The database is closed.
  The database is dismounted.
  ORACLE instance stops.
  SQL > SHUTDOWN IMMEDIATE;
  ORA-01012: not connected
  SQL > STARTUP MOUNT;
  ORA-32004: outdated or obsolete parameters specified for the instance of RDBMS
  ORACLE instance started.
  
  Total System Global Area 6781128704 bytes
  Bytes of size 2268064 fixed
  3539993696 variable size bytes
  Buffers data 3221225472 bytes
  Redo buffers 17641472 bytes
  Mounted database.
  SQL > ARCHIVE LOG START;
  Statement processed.
  SQL > ALTER DATABASE ARCHIVELOG;
  
  Database altered.
  
  SQL > ALTER DATABASE OPEN;
  
  Database altered.
  
  SQL > alter system switch logfile;
  
  Modified system.
  
  SQL > select log_mode from v database $;
  
  LOG_MODE
  ------------
  ARCHIVELOG

  however, there is no archived log generated in the folder recovery: D:\oradata\BDSPROD\archivelogs\
  I also tried with log_archive_dest = SET has: \oradata\BDSPROD\archivelogs' (without the last "------"), but the same behavior, no restoring archived log is created.
  
  Published by: user521219 on October 25, 2012 10:45

  SQL > ALTER SYSTEM SET log_archive_dest = a: \oradata\BDSPROD\archivelogs\' SCOPE = spfile;

  Which shows the output when you use query below?
  SQL > select name from v$ archived_ log;

  And don't use any specific destination with the use of the attribute location below the number and try again.

  SQL > ALTER SYSTEM SET log_archive_dest_1 =' location = ' D:\oradata\BDSPROD\archivelogs;

  Thank you

• changing the location of the log archiving PLZ flash recovery area HELP!

  Hi all
  
  My journal archive is stored in an area of memory flash that got the full and the production server is down.
  
  Details of the alerts log file...
  

  ORA-19809: limit exceeded for recovery files
  ORA-19804: cannot reclaim 43432960 bytes disk space from 2147483648 limit
  *** 2010-04-25 14:22:49.777 62692 kcrr.c
  ARCH: Error 19809 Creating archive log file to 
  
  '/oracle/product/10.2.0/flash_rec
  overy_area/EDWREP/archivelog/2010_04_25/o1_mf_1_232_%u_.arc'
  *** 2010-04-25 14:22:49.777 60970 kcrr.c
  kcrrfail: dest:10 err:19809 force:0 blast:1

  I deleted the files and started the database,
  
  Can a good person kindly tell me how to avoid this problem in the future by keeping the destination of the newspaper archive in the flash recovery area.
  
  I want to change the location of the files to archive log, can someone ' a please guide me about hiow to do
  
  I changed the size of the area of recovery flash for now, but I fear that it will be again!
  

  SQL> select * from v$flash_recovery_area_usage;
  
  FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
  ------------ ------------------ ------------------------- ---------------
  CONTROLFILE                   0                         0               0
  ONLINELOG                     0                         0               0
  ARCHIVELOG                99.44                         0              57
  BACKUPPIECE                   0                         0               0
  IMAGECOPY                     0                         0               0
  FLASHBACKLOG                  0                         0               0
  
  6 rows selected.
  
  SQL> alter system set DB_RECOVERY_FILE_DEST_SIZE = 4G ;
  
  System altered.
  
  SQL> select * from v$flash_recovery_area_usage;
  
  FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
  ------------ ------------------ ------------------------- ---------------
  CONTROLFILE                   0                         0               0
  ONLINELOG                     0                         0               0
  ARCHIVELOG                49.72                         0              57
  BACKUPPIECE                   0                         0               0
  IMAGECOPY                     0                         0               0
  FLASHBACKLOG                  0                         0               0
  
  6 rows selected.

  Kind regards
  
  Published by: user10243788 on April 25, 2010 06:12

  following steps should be ok
  (1) create pfile from spfile;
  (2) remove the unnecessary params
  (3) configure log_archive_dest_1
  Note: do not remove the db_recovery_file_dest, db_recovery_file_dest_size, and parameters. they may be required at another time
  (4) stop and start your database using this new pfile
  (5) check if the archives are in one place
  (6) create spfile and bounce database to ensure that it uses spfile

  Please try all the steps test env first and go ahead in the event of success, to production