Oracle recommended location for archive logs in oracle 10g rac

Hello All,
We would like to know the oracle recommended location for the archive logs in oracle10g RAC .we are using ASM.
Thanks...

user4487322 wrote:
thanks. Is it the recommended setting ,if we go for a DR setup?I mean archive logs in ASM.If you can use dataguard, the archivelog copy to the standby system would be handled by Oracle and it supports ASM.
Just remember, what ever your strategy, the archivelogs must be in a SHARED location (where all nodes can read/write to this location.)

Similar Messages

No clarity on location of archive logs in Oracle 11g database

I have this query which I am not able to resolve. There is one location of archive log mentioned as /oraarch/app/oracle/oradata/snlprod/archive_logs/ in the parameter log_archive_dest_1. But the archive logs are showing in another location /orabackup/rman/snlprod/archive_logs. I am wondering how the archive logs are showing in this location, /orabackup/rman/snlprod/archive_logs.
I guess there is only one way in which location can be given which is seen from Availability->Recovery Settings->Media Recovery.
I hope, my question is clear.
Please revert with the reply to my query.
Regards

Must be
show parameter db_recovery_file_dest
If you want archived redo log send to /oraarch/app/oracle/oradata/snlprod/archive_logs
then you must set log_archive_dest_1 ='LOCATION= /oraarch/app/oracle/oradata/snlprod/archive_logs'
log_archive_dest_1 is same before then it means your all archvied redo log file will create in this directory
Regards
Mahir M. Quluzade

Specifying separate location for Archived logs in Persistent settings

DB version:11gR1
I am new to RMAN
Currently my RMAN bkp script looks like
run {
recover copy of database with tag "INCR_BKP";
     backup check logical incremental level 1 format '/data_DISK1/bkp_dir/nhprod31/data/INCR_%d_%u'
          for recover of copy with tag "INCR_BKP" database;
     backup (archivelog all format='/data_DISK2/bkp_dir/nhprod31/arch_logs/ARCH_%d_%T_%u_s%s_p%p' DELETE ALL INPUT TAG "arch_logs");
     backup format '/data_DISK1/bkp_dir/nhprod31/ctrl_file/RMAN_CTL_%s:%t:%p.bkp' current controlfile;
}I want Datafiles and Archived logs to be stored in different locations like above.
But i want to remove those lengthy path locations in the script and just use
backup database plus archivelog;For this, i need to set
configure channel device type disk format ='/u01/backup/ora_%U.bak';Question1.
Is it possible to specify a separate archive log location using CONFIGURE command?
Question2.
If it is not possible, all the backup files will have the same naming convention
ora_%U.bakhow will you identify the type of backup file. Say, i need the archive log files to be named with Log sequence number in it (like ARCH_%d_%T_%u_s%s_p%p). Shouldn't Oracle be including a provision for this?
I am not even sure that each archive log file will backed up as a single backup file. Oracle may consolidate all the archive logs in to one backup piece. Please forgive my ignorance.

783999 wrote:
Try this for datafile backup:
RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '<PATH>/rbkp/databkp/DATA_L0_QA_%d_%s_%p';
RMAN> show all;
This worked for me.
Regards,
BikramThis won't work. Re-read the question carefully.

Overheads for Archive Logs

Hi,
Not sure where I should address this but I would appreciate any helpful feedback.
I would like to find out what are the overheads (in terms of size) for managing & storing archive logs for capacity planning purposes. Is this information documented anywhere? How can I find out?
Thanks in advance.
Thanks,
Tony

Since this number is dependent on your database, it would be impossible to answer. If you have a small database with few changes/deletes, you hardly need any space for archive logs. Oracle reccommends that you size your archive logs so that they switch ~1 time per hour.

Secondary destination for Archived logs

Version: 10.2, 11.1, 11.2
We occasionally get 'archiver error' on our production DBs due to our LOG_ARCHIVE_DEST_1 being full. How can I have a secondary location for archive logs in case my 'primary' location (LOG_ARCHIVE_DEST_1) becomes full ?
I gather that LOG_ARCHIVE_DEST_2 is reserved for shipping archive logs to Dataguard standby DB in which you specify the tns entry of standby using SERVICE parameter.
Can I specify LOG_ARCHIVE_DEST_3 as my secondary location in case LOG_ARCHIVE_DEST_1 becomes full ? Is it what LOG_ARCHIVE_DEST_n meant for ? Although the documentation says you can have upto 10 locations, I am confused if they are meant to store Multiplexed copies of archive logs ? That is not what I am looking for ?

>
Hi again Tom,
I have one more question:
ALTER SYSTEM SET LOG_ARCHIVE_DEST_4 = 'LOCATION=/disk4/arch';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_3 = 'LOCATION=/disk3/arch
    ALTERNATE=LOG_ARCHIVE_DEST_4';
ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_4=ALTERNATE;
SQL> SELECT dest_name, status, destination FROM v$archive_dest;
DEST_NAME               STATUS    DESTINATION
LOG_ARCHIVE_DEST_1      VALID     /disk1/arch     -------------> Dest1
LOG_ARCHIVE_DEST_2      VALID     +RECOVERY       -------------> Dest2
LOG_ARCHIVE_DEST_3      VALID     /disk3/arch     -------------> Dest3
LOG_ARCHIVE_DEST_4      ALTERNATE /disk4/archMy understanding is (and I'm not terribly sure at the minute - don't have a test system to hand. I haven't
set up a backup/recovery strategy in a while - I just restore backups from time to time (normally every 4 weeks)
to ensure that the database recovers as it should) - my understanding is that under the scheme above
DEST_3 will be a copy of what's in DEST_1. DEST_4 on the other hand will "step in" should DEST_1
or DEST_3 fill up/fail.
As to DEST_2, I'm not sure - maybe something to do with Fast Recovery Area? I've Googled but can't
find anything - the trouble is that all the pages about this contain the word "recovery" and the "+"
sign doesn't appear to affect the search - does "+" mean something special to Google?
I don't have a system at the moment - if you do, why don't you test and see? On a test system, fill
up the file system for DEST_1 with rubbish and check to see what happens?
All of the above is to be taken with a pinch of salt - I don't have a system to hand and am not certain,
so CAVEAT EMPTOR
HTH,
Paul...
Edited by: Paulie on 21-Jul-2012 17:20

Tidying the list of archive logs in Oracle

We have been using Archive Logging for a while but manually handle the purging of them. Since we restart our 9.2 Oracle DBs daily and perform backups (cold) daily, the archive logs are currently suitable for a day.
However, in Oracle Enterprise Manager > Storage > Archive Logs, we see the entire list (history) of archive logs.
Can this be tidied and how?
Thanks

my mistake
Problem Description:
====================
When querying "v$loghist," the number of rows displayed is less than the total
number of Redo Logs created by the database.
Solution Description:
=====================
The quantity of Log History is driven by the internal parameter "maxloghistory".
When creating a database you have the option to specify the "maxloghistory"
parameter. The default value is OS dependent.
In order to alter this parameter you need to re-create the controlfile and
specify the "maxloghistory" parameter.
Explanation:
============
The setting for log history in the control file is set very low.
The Log history is stored in the controlfile. When a database is created we
specify how much Log history to store. Often, this setting is ignored or made
small so the controlfile is not too large.
References:
===========
Oracle Server SQL Reference
Note: there are some bugs about maxloghistory being ignored if you try to recreate your database.

Changing the location of archive log from flash recovery area PLZ HELP!!!

Hi All,
My archive log is being stored in flash memory area which got full and the production server went down.
alert log file details.....
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:1I removed the files and started the database,
Can someone kindly tell me as to how to avoid this problem in future by keeping archive log destination in flash recovery area.
I want to change the location of archive log files, can someone please guide me as to hiow to do that
I changed the size of flash recovery area for the time being, but i am afraid it will be full 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.regards,
Edited by: user10243788 on Apr 25, 2010 6:12 AM

user10243788 wrote:
Hi All,
My archive log is being stored in flash memory area which got full and the production server went down.
alert log file details.....
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:1I removed the files and started the database,
Can someone kindly tell me as to how to avoid this problem in future by keeping archive log destination in flash recovery area.
I want to change the location of archive log files, can someone please guide me as to hiow to do that
I changed the size of flash recovery area for the time being, but i am afraid it will be full 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.regards,
Edited by: user10243788 on Apr 25, 2010 6:12 AMPointing the archive log dest (and/or the FRA) to a new location, or enlarging them, will do no good if you are not performing regular housekeeping on the archivelogs. You will just keep knocking down the same problem over and over.
If you simply delete the archivelogs at the OS level, the database will never know about it and it will continue to think the destination is full, based on records kept in the control file.
For regular housekeeping, you need to be doing something similar to this in rman:
run {
backup archivelog all not backed up 1 times tag='bkup_vlnxora1_arch';
delete noprompt archivelog all backed up 1 times to device type disk;
run {
delete noprompt obsolete;
crosscheck archivelog all;
delete noprompt expired archivelog all;

"recover database until cancel" asks for archive log file that do not exist

Hello,
Oracle Release : Oracle 10.2.0.2.0
Last week we performed, a restore and then an Oracle recovery using the recover database until cancel command. (we didn't use backup control files) .It worked fine and we able to restart the SAP instances. However, I still have questions about Oracle behaviour using this command.
First we restored, an online backup.
We tried to restart the database, but got ORA-01113,ORA-01110 errors :
sr3usr.data1 needed media recovery.
Then we performed the recovery :
According Oracel documentation, "recover database until cancel recovery" proceeds by prompting you with the suggested filenames of archived redo log files.
The probleme is it prompts for archive log file that do not exist.
As you can see below, it asked for SMAarch1_10420_610186861.dbf that has never been created. Therefore, I cancelled manually the recovery, and restarted the database. We never got the message "media recovery complete"
ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10417_61018686
Fri Sep 7 14:09:45 2007
ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10418_610186861.dbf'
Fri Sep 7 14:09:45 2007
Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10418_610186861.dbf
ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10418_61018686
Fri Sep 7 14:10:03 2007
ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10419_610186861.dbf'
Fri Sep 7 14:10:03 2007
Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10419_610186861.dbf
ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10419_61018686
Fri Sep 7 14:10:13 2007
ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf'
Fri Sep 7 14:10:13 2007
Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf
Errors with log /oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf
ORA-308 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10420_61018686
Fri Sep 7 14:15:19 2007
ALTER DATABASE RECOVER CANCEL
Fri Sep 7 14:15:20 2007
ORA-1013 signalled during: ALTER DATABASE RECOVER CANCEL ...
Fri Sep 7 14:15:40 2007
Shutting down instance: further logons disabled
When restaring the database we could see that, a recovery of online redo log has been performed automatically, is it the normal behaviour of a recovery using "recover database until cancel" command ?
Started redo application at
Thread 1: logseq 10416, block 482
Fri Sep 7 14:24:55 2007
Recovery of Online Redo Log: Thread 1 Group 4 Seq 10416 Reading mem 0
Mem# 0 errs 0: /oracle/SMA/origlogB/log_g14m1.dbf
Mem# 1 errs 0: /oracle/SMA/mirrlogB/log_g14m2.dbf
Fri Sep 7 14:24:55 2007
Completed redo application
Fri Sep 7 14:24:55 2007
Completed crash recovery at
Thread 1: logseq 10416, block 525, scn 105140074
0 data blocks read, 0 data blocks written, 43 redo blocks read
Thank you very much for your help.
Frod.

Hi,
Let me answer your query.
=======================
Your question: While performing the recovery, is it possible to locate which online redolog is needed, and then to apply the changes in these logs
1.   When you have current controlfile and need complete data (no data loss),
      then do not go for until cancel recovery.
2.   Oracle will apply all the redologs (including current redolog) while recovery
     process is    on.
3. During the recovery you need to have all the redologs which are listed in the    view    V$RECOVERY_LOG and all the unarchived and current redolog. By querying V$RECOVERY_LOG you    can find out about the redologs required.
4. If the required sequence is not there in the archive destination, and if recovery process    asks for that sequence you can query V$LOG to see whether requested sequence is part of the    online redologs. If yes you can mention the path of the online redolog to complete the recovery.
Hope this information helps.
Regards,
Madhukar

Validation failed for archived log

Hi,
oracle database version 11.2.0.4
OS centOS 6.5
Recently i have set rman backup scripy on production Database, As we are using dbvisit for standby database for that we have set cron which run in every 10 minutes it generates archive and copy it to standby side,
but sometimes backup failed due to expected archive is not represent at location so i put "crosscheck archivelog all" in script now backup is running fine, But i have analyzed backlog file getting
"validation failed for archived log" the time stamp i have checked validation failed archive is current day and yesterday even though archives are present at the location and CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
Guys i am worried it shouldn't be a big issue for me,
please suggest what is wrong

This forum is for Berkeley DB high availability. We do not have the expertise to help you with your Oracle database 11.2.0.4 issue. You'll need to submit this question to one of the Oracle database forums to get the help you are looking for.
Paula Bingham

How to calculate storage space for archive log files and database backups?

Hi all,
I have a 1.8 terabyte Oracle 9i database and need to plan for how much additional disk space I will need to perform nightly backups and for archivelog files. Is there a script or formula available that can help me estimate how much required disk space I will need to hold a days worth of archived logs as well as a nightly export dump file and a full hot RMAN backup on disk?
Thanks!

I'm not sure how to estimate the size of your backups, especially if you use incrementals. However, the space required for archive logs will be equal to the amount of REDO your DB generates. I would count the number of log switches per day with a query like the following:
select trunc(first_time), count(*)
from v$log_history
group by trunc(first_time)
I would then take the average and multiply this count by the size of your redo log files (assuming they are all the same size).

What is the meaning of stream capture waiting for archive log ?

today I fing the oracle alert that stream capture waiting for archive log in other class,and use a lot of database time.
What is it? And Can I prevent it happening ?

today I fing the oracle alert that stream capture waiting for archive log in other class,and use a lot of database time.
What is it? And Can I prevent it happening ?

How can I set destination for archived logs?

I would like to know:
how to set destination for archived logs?
how to identify the init.ora that is used for my database?
With rman using compressed backupset by default and and making
backup database;
What does it backup exactly?

Another thing I am wondering, when I make a backup with rman : backup database.
It saves the backups in the directory autobackup from the flash_recovery_area but it seems that it only saves the data files and the control files.Isn't there a way to sava archived logs files, control files, datafiles in a single backup?
In fact I would like to make a full backup using rman on sunday of everything and a incremental backup all days of the week how can I acomplish this with a retention of 7 days?

Managing ARCHIVE Logs in Oracle 10.2.0.3

I am working with a customer who seems to think there is a way of controling the database other than a custom JOB, script or RMAN in how it creates, manages and deletes its archive logs while running in archivelog mode. He wants the database to automatically delete obsolete archive logs. He also wants to control the duration in time between each time an archive log is written in order to stop the growth of archive logs and filling up disk space.
I am saying this is not possible. You either configure RMAN to delete the obsolete or expired archive logs based on your retention policy or do it manually in the Enterprise Manager or Grid Control Console by deletenig obsolete or expired logs.
Am I correct or am I off base here?

4.1.3 Sizing Redo Log Files
The size of the redo log files can influence performance, because the behavior of the database writer and archiver processes depend on the redo log sizes. Generally, larger redo log files provide better performance. Undersized log files increase checkpoint activity and reduce performance.
Although the size of the redo log files does not affect LGWR performance, it can affect DBWR and checkpoint behavior. Checkpoint frequency is affected by several factors, including log file size and the setting of the FAST_START_MTTR_TARGET initialization parameter. If the FAST_START_MTTR_TARGET parameter is set to limit the instance recovery time, Oracle automatically tries to checkpoint as frequently as necessary. Under this condition, the size of the log files should be large enough to avoid additional checkpointing due to under sized log files. The optimal size can be obtained by querying the OPTIMAL_LOGFILE_SIZE column from the V$INSTANCE_RECOVERY view. You can also obtain sizing advice on the Redo Log Groups page of Oracle Enterprise Manager Database Control.
It may not always be possible to provide a specific size recommendation for redo log files, but redo log files in the range of a hundred megabytes to a few gigabytes are considered reasonable. Size your online redo log files according to the amount of redo your system generates. A rough guide is to switch logs at most once every twenty minutes.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/build_db.htm#sthref237
If you are talking about data guard then:
4.1.3 Sizing Redo Log Files
The size of the redo log files can influence performance, because the behavior of the database writer and archiver processes depend on the redo log sizes. Generally, larger redo log files provide better performance. Undersized log files increase checkpoint activity and reduce performance.
Although the size of the redo log files does not affect LGWR performance, it can affect DBWR and checkpoint behavior. Checkpoint frequency is affected by several factors, including log file size and the setting of the FAST_START_MTTR_TARGET initialization parameter. If the FAST_START_MTTR_TARGET parameter is set to limit the instance recovery time, Oracle automatically tries to checkpoint as frequently as necessary. Under this condition, the size of the log files should be large enough to avoid additional checkpointing due to under sized log files. The optimal size can be obtained by querying the OPTIMAL_LOGFILE_SIZE column from the V$INSTANCE_RECOVERY view. You can also obtain sizing advice on the Redo Log Groups page of Oracle Enterprise Manager Database Control.
It may not always be possible to provide a specific size recommendation for redo log files, but redo log files in the range of a hundred megabytes to a few gigabytes are considered reasonable. Size your online redo log files according to the amount of redo your system generates. A rough guide is to switch logs at most once every twenty minutes.
Automatic Deletion of Applied Archive Logs
Archived logs, once they are applied on the logical standby database, will be automatically deleted by SQL Apply.
This feature reduces storage consumption on the logical standby database and improves Data Guard manageability.
See also:
Oracle Data Guard Concepts and Administration for details
http://download.oracle.com/docs/cd/B19306_01/server.102/b14214/chapter1.htm#sthref269

New feature for Archive data in oracle database11g.

Is there any new feature in oracle database11g for archiving data?

Yes.
For example :
"optional archive log destination to be utilized in the event that the flash recovery area is inaccessible during backup"
See the document under "Archive Log Management Improvements"
http://download.oracle.com/docs/cd/B28359_01/server.111/b28279/chapter1.htm
Best Regards
mseberg

Oracle 9i request wrong archive log name during recovery

Hello all,
I am facing a problem with a database 9i Enterprise Edition running on Windows 2003 Enterprise Edition environment. According to the customer, when he takes the database offline using MSCS to take an offline backup, the database crashes when he tries to put it back online... But here a strange thing happens... when the command RECOVER DATABASE is issued, it asks for the wrong archive log... for example:
The actual sequence is 14322, but Oracle asks for the archive log SID_4322... (in this case we have to rename the original file SID_14322 to SID_4322). I don't understand why it asks for the archive incorrectly... I issued the command ARCHIVE LOG LIST and it says that the current thread is 14322 (which is correct)... every new archive is created with the correct name (SID_143XX)... why is it asking for an archive without the number 1 in this case? Rename all the files to recover a database is not very pleasent job... creating an script to do so is not a solution in my opinion, hehe. Thanks for your help in advance.
Best regards,
Bruno Carvalho
Edited by: Bruno Carvalho on Jul 5, 2010 10:08 AM

Hello Damorgan,
MSCS = Microsoft Cluster Services (it's an MMC console). The backup strategy is very old, and they use BR*Tools script to create a job on ArcServe Brigstor, and then the backup is performed via backint. (It's an SAP ERP system, which should be backed up using BR*Tools). I checked the alert log and I think that the problem is the length of the archive log name (in the alert log it gives me the error below):
ARCH: Warning. Log sequence in archive filename wrapped
to fix length as indicated by %S in LOG_ARCHIVE_FORMAT.
Old log archive with same name might be overwritten.
Media Recovery Log E:\ORACLE\SID\SAPARCH\SIDARCH\SIDARCH_43454.DBF <- this should be SIDARCH_143454.DBF
Now I'm looking for a parameter where I can set the length of the archives, your help would be very appreciated (and please let me know if I'm not going the right way).
Best regards,
Bruno Carvalho

Oracle recommended location for archive logs in oracle 10g rac

Similar Messages

Maybe you are looking for