Archivelog location

Hi,
I need to setup a three instance rac database.The datafiles and flash recovery area will be stored in ASM diskgroups called data and fra.
Which is the best location options for archivelogs so that they can be accessed during recovery without dba intervention ?
cluster file system with each instance writing to a shared location
or
cluster file system with each instance writing to a separate location as long as all the locations are in directories under the same mount point

each instance writing to a shared location(ASM either DATA or FRA Disk groups)
The archived redo log naming scheme that you use is important because when a node writes to a log with a specific filename on its file system, the file must be readable by any node that needs to access this archived redo log. For example, if node 1 archives a log to /oracle/arc_dest/log_1_100_23452345.arc, then node 2 can only back up this archived redo log only if it can read/oracle/arc_dest/log_1_100_23452345.arc on its own file system.
The backup and recovery strategy that you choose depends on how you configure the archiving destinations for each node. Whether only one node or all nodes perform archived redo log backups, you need to ensure that all archived redo logs are backed up. If you use RMAN parallelism during recovery, then the node that performs recovery must have read access to all archived redo logs in your cluster.
Multiple nodes can restore archived logs in parallel. However, during recovery, one one node applies the archived logs. Therefore, the node that is performing the recovery must be able to access all of the archived logs that are needed for the recovery operation. By default, the database determines the optimum number of parallel threads to use during the recovery operation. You can use the PARALLEL clause in the RECOVER command to change this number.Refer:-
http://docs.oracle.com/cd/B19306_01/rac.102/b14197/rmanops.htm

Similar Messages

Rman not reading archivelogs from all locations

Hello,
My physical standby database has two archivelog locations inside ASMFLASH. One of the location is ASMFLASH/DB/ARCHIVELOG/ where the local archivelogs of the standby database get stored. Other one is ASMFLASH/DB/archstd/ where the archivelogs are stored after getting shipped from the primary database.
I want to do maintenance task by deleting the old archivelog files. But when i connect to RMAN, it lists out archivelogs of only one location:
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
2418 1 1501 A 09-APR-11 +ASMFLASH/db/archstd/1_1501_714749644.arc
2422 1 1502 A 10-APR-11 +ASMFLASH/db/archstd/1_1502_714749644.arc
2424 1 1503 A 11-APR-11 +ASMFLASH/db/archstd/1_1503_714749644.arc
2428 1 1504 A 12-APR-11 +ASMFLASH/db/archstd/1_1504_714749644.arc
2431 1 1505 A 13-APR-11 +ASMFLASH/db/archstd/1_1505_714749644.arc
2434 1 1506 A 14-APR-11 +ASMFLASH/db/archstd/1_1506_714749644.arc
2436 1 1507 A 15-APR-11 +ASMFLASH/db/archstd/1_1507_714749644.arc
2439 1 1508 A 16-APR-11 +ASMFLASH/db/archstd/1_1508_714749644.arc
2442 1 1509 A 17-APR-11 +ASMFLASH/db/archstd/1_1509_714749644.arc
I cannot see the locally generated archivelogs of +ASMFLASH/DB/ARCHIVELOG/ . How shall i delete those archives from RMAN?

ASMCMD> cd archivelog
ASMCMD> pwd
+asmflash/db/archivelog
ASMCMD> ls
2011_02_10/
2011_02_11/
2011_02_12/
2011_02_13/
2011_02_14/
2011_02_15/
2011_02_16/
2011_02_17/
2011_02_18/
2011_02_19/
2011_02_20/
2011_02_21/
2011_02_22/
2011_02_23/
2011_02_24/
2011_02_25/
2011_02_26/
2011_02_27/
2011_02_28/
2011_04_09/
2011_04_10/
2011_04_11/
2011_04_12/
2011_04_13/
2011_04_14/
2011_04_15/
2011_04_16/
2011_04_17/
2011_04_18/
2011_04_19/
2011_04_20/
2011_04_21/
2011_04_22/
2011_04_23/
2011_04_24/
2011_04_25/
2011_04_26/
2011_04_27/
2011_04_28/
2011_04_29/
2011_04_30/
2011_05_01/
2011_05_02/
ASMCMD> cd 2011_05_02/
ASMCMD> ls
thread_1_seq_1579.1316.750079865
thread_2_seq_995.1320.750072691
thread_2_seq_996.1317.750079867
Also :
2_985_714749644.arc
2_986_714749644.arc
2_987_714749644.arc
2_988_714749644.arc
2_989_714749644.arc
2_990_714749644.arc
2_991_714749644.arc
2_992_714749644.arc
2_993_714749644.arc
2_994_714749644.arc
2_995_714749644.arc
2_996_714749644.arc
ASMCMD> pwd
+asmflash/db/archstd

How to check for archivelog backup on a particular date or time?

Dear All,
We have RMAN full database, cumulative and archivelog backup(eg location: Diskgroup A) scheduled on a regular period basis. Assume archivelog location is Diskgroup B. The diskgroup B became full and unable to archive further, since no space. Unable to connect to database, connect internal only until freed error. alert log also shows that archiver error. So the solution for this to clear some space in diskgroup B by removing some old archive logs. In our environment, everyday the archive logs are stored in a separated folder arranged in date wise. I can do that . But before clearing some space, i need to make sure that the folder( or any date folder what im going to delete) is backed up or not. How to check that? Any idea please?
eg: i have archivelogs like this in folders
01_11_2013/
02_11_2013/
03_11_2013/
04_11_2013/
05_11_2013/
06_11_2013/
If i want to remove the folder 01_11_2013/( and its contents ie archivelogs) , how to check whether the archivelogs in this folder 01_11_2013/ is backed up or not?
Regards,

Pradeepcmst wrote:
Dear All,
We have RMAN full database, cumulative and archivelog backup(eg location: Diskgroup A) scheduled on a regular period basis. Assume archivelog location is Diskgroup B. The diskgroup B became full and unable to archive further, since no space. Unable to connect to database, connect internal only until freed error. alert log also shows that archiver error. So the solution for this to clear some space in diskgroup B by removing some old archive logs. In our environment, everyday the archive logs are stored in a separated folder arranged in date wise. I can do that . But before clearing some space, i need to make sure that the folder( or any date folder what im going to delete) is backed up or not. How to check that? Any idea please?
eg: i have archivelogs like this in folders
01_11_2013/
02_11_2013/
03_11_2013/
04_11_2013/
05_11_2013/
06_11_2013/
If i want to remove the folder 01_11_2013/( and its contents ie archivelogs) , how to check whether the archivelogs in this folder 01_11_2013/ is backed up or not?
Regards,
rman> list backup;
Which begs the question .. why is the FRA getting filled in the first place? Is it seriously undersized? Are you not doing regular housekeeping with rman 'delete obsolete' and 'backup archivelog delete input'

Need 2 copies of archivelogs

I need 2 copies of my archivelogs.
1 local in my Flashback recovery area
and 1 to another server over nfs.
What oracle parameter i need to change and to which value?
Also, is this mount command is ok for the archivelog location over nfs?
I mean, do i use proper mount setting for oracle?
mount -t nfs -o hard,proto=tcp,rsize=32768,wsize=32768,intr pos:/usr/local/juk-prod/archive /mnt/pos/archive
At this moment im only using 1 archivelog location in the FRA:
archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 105767
Next log sequence to archive 105777
Current log sequence 105777
show parameter archive;
NAME TYPE VALUE
archive_lag_target integer 0
log_archive_config string
log_archive_dest string
log_archive_dest_1 string
log_archive_dest_10 string
log_archive_dest_2 string
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string enable
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string %S_%T_%r.arc
log_archive_local_first boolean TRUE
log_archive_max_processes integer 2
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
remote_archive_enable string true
standby_archive_dest string ?/dbs/arch
show parameter DB_RECOVERY_FILE_DEST;
NAME TYPE VALUE
db_recovery_file_dest string /OraArch1/
db_recovery_file_dest_size big integer 999G

Seems to work ok except for the name of the archive logs are different.
SQL> show parameter arch;
NAME TYPE VALUE
archive_lag_target integer 0
log_archive_config string
log_archive_dest string
log_archive_dest_1 string LOCATION=USE_DB_RECOVERY_FILE_
DEST MANDATORY
log_archive_dest_10 string
log_archive_dest_2 string LOCATION=/mnt/archive/ OPTIONA
L
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
NAME TYPE VALUE
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string enable
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
NAME TYPE VALUE
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string %t_%s_%r.arc
log_archive_local_first boolean TRUE
log_archive_max_processes integer 2
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
remote_archive_enable string true
NAME TYPE VALUE
standby_archive_dest string ?/dbs/arch
The name of the archivelog file in my FRA is o1_mf_1_14_3bnjm72h_.arc
And the name of the archivelog file in my second dest is 0000000014_0001_627728462.arc
Whys the archivelog name is different?
Can it be the same?
if so how?
also, the archivelog in the fra are nicely put in folder for each day like the following:
[oracle@orcltest archivelog]$ ll
total 32
drwxr-xr-x 2 oracle oinstall 4096 Jul 12 08:46 2007_07_09
drwxr-x--- 2 oracle oinstall 4096 Jul 12 15:42 2007_07_12
drwxr-x--- 2 oracle oinstall 4096 Jul 13 22:03 2007_07_13
drwxr-x--- 2 oracle oinstall 4096 Jul 16 05:00 2007_07_16
drwxr-x--- 2 oracle oinstall 4096 Jul 18 09:00 2007_07_18
drwxr-x--- 2 oracle oinstall 4096 Jul 20 10:00 2007_07_20
drwxr-x--- 2 oracle oinstall 4096 Jul 22 16:00 2007_07_22
drwxr-x--- 2 oracle oinstall 4096 Jul 27 15:17 2007_07_27
How can i do this for my second archivelog destination?

Archivelog full

Hi,
11.2.0.1
When you db encounters "archive log full waiting to be freed", is there a way to resolve it without shutting down the db? Thanks.
vk82 Oct 9, 2013 9:35 AM
In case if your DB is Production. How will you continue to operate your DB in no archivelog mode.
The solution for above mentioned problem is either:
SQL> Shutdown abort;
SQL> Startup Mount;
1) Change your Archiving Destination by :
SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST='NEW_PATH_LOCATION'
or
2) Increase the size of Archiving Destination by first determining the size of the Archiving destination which intially you have:-
SQL> SELECT NAME,(space_limit/1048576),(space_used/1048576) from v$recovery_file_dest;
And after that increase the space according to above output:-
SQL> alter system set db_recovery_file_dest_size=more_size_than_getting_size_above scope=both;
SQL> Alter database open;
Now
SQL> Shutdown immediate;
SQL> Startup;
or
3) Zip the archive logs and move it to anyother destination but be careful to preserve this you require all this archivelogs during recovery.

ozgurumut wrote:
Hi,
As I understand , you need to manage disk space of archivelog field. You can make with script or RMAN config.
Firstly, You may try RMAN Configuration like on below;
RMAN> Crosscheck archivelog all;
RMAN> Delete exprired archivelog all;
Secondly , You can use shell script (contains oracle command).
1. find <archivelog location> -name '*.log' -mtime +10 -exec rm -rf {} \;
2. RMAN> Crosscheck archivelog all;
3. RMAN> Delete exprired archivelog all;
#!/bin/sh
ORACLE_HOME=/u01/app/oracleths/product/11.2; export ORACLE_HOME
ORACLE_SID=test; export ORACLE_SID
PATH=.:$ORACLE_HOME/bin:/usr/ccs/bin:/usr/proc/lib:/usr/ucb:/usr/lib:/usr/ucblib:/opt/bin:/bin:/usr/bin:/GNU/bin/make
export PATH
find <archivelog location> -name '*.log' -mtime +10 -exec rm -rf {} \;
$ORACLE_HOME/bin/rman target / << EOF
Crosscheck archivelog all;
Delete exprired archivelog all;
exit
EOF
Finally, you should put to crontab . And it will work...
Far better would be to construct the backup procedure to let rman manage it all -- FRA or not.
rman> backup database [options]
rman> backup archivelog delete [options]
rman> delete noprompt obsolete.
and for a bit of extra insurance against 'unauthorized maintenance'
rman> crosscheck archivelog all;
rman> delete noprompt expired archivelog;
rman> crosscheck backup;
rman> delete noprompt expired backup;
schedule it however you want. All your backup, all your housekeeping, in one place, managed exclusively by rman.

Create object from a different location

I have a script object under Variables called Library. In it, I have a cat object:
function Cat(name) {
this.name = name;
this.talk = function() {
app.alert( this.name + " meow" )
I want to instantiate an instance of Cat from form.initialize.
If I do var myCat = new Library.Cat("Oscar"); I get exception.

rman target /
catalog start with '/other/archivelog/location';
backup archivelog like '/other/archivelog/location/%' ... ;

File to be put on ASM

Dear All,
db version:10.2.0.3
o/s:redhat linux4
In my production instance all configuration files(datafiles,parameterfiles,logfile,controlfiles) are on SAN filesystem .I want to migrate them to ASM hoping that i will get performance gains.i have some doubts.
1)i want to keep 2 copies of logfiles,controlfiles and archive files if i use failure groups it doesnt makes any sense coz in last underline storage is comming from san.i would like to put 1 copy in asm and 1 copy in local hardrive is it possible and no performance issues will happen?
Regards

hungry_dba wrote:
Dear All,
db version:10.2.0.3
o/s:redhat linux4
In my production instance all configuration files(datafiles,parameterfiles,logfile,controlfiles) are on SAN filesystem .I want to migrate them to ASM hoping that i will get performance gains.i have some doubts.
1)i want to keep 2 copies of logfiles,controlfiles and archive files if i use failure groups it doesnt makes any sense coz in last underline storage is comming from san.i would like to put 1 copy in asm and 1 copy in local hardrive is it possible and no performance issues will happen?
Hi,
You can put DATAFILE, CONTROLFILE,REDO and SPFILE in ASM DISKGROUP. If you setup Flash Recovery Area (FRA) to Filesystem during database creation, REDO,CONTROLFILE are automatically multiplexed in FRA and ARCHIVELOG is generate in FRA. (i.e Filesystem).
Also you can manually multiplex REDO and Controlfile and setup Archivelog Location to Filesystem and Disksgroup as you wish.
P.S REDO is always multiplexed in Main Location and FRA during creation of REDO.
The performance will depend on your hardware, if you are using the same array for both (diskgroup and filesystem) I believe it will not have performance problems.
But you must analyze performance issues and bottlenecks during the operation of your environment.
Hope this helps,
Levi Pereira

Backing up multiple archive locs

RMAN 10.2.0.2 using control file.
I have two archive log locations. I want to use RMAN to backup only one of them. The other is a long term storage area for CYA and I will back it up using non RMAN method. How do I configure RMAN to manage only the one archivelog location...
Thanks,
cd

DELETE ALL INPUT deletes every copy of each archivelog that has been backed up.
Thus if you archivelogs are in multiple destinations using log_archive_dest_1, _2 etc,
each destination copy is deleted.
DELETE INPUT deletes only the copy that did get backed up. Thus, the copy in
log_archive_dest_1 might go to the backup set and be deleted from the filesystem
but the copy in log_archive_dest_2 should still persist on disk. Right!
Then, why you said that to the OP?
Also, remember not to use "DELETE ALL INPUT" but "DELETE INPUT" if you wish RMAN to delete the archivelogs as well.

Split Brain Thinking

We are designing a RAC environment for our ERP system and have run into an interesting problem. First, I'll give you the design, then ask the question that we are puzzled over.
We have two campuses. There will be 4 nodes in the cluster, 2 per campus. We have two NetApp FAS 3070's, one per campus. Each NetApp will export voting/ocr disk, an ASM disk, and redo/archivelog locations.
Each node will use ASM's normal redundancy for fault tolerance. The nodes will see a single disk for ASM from campus A, and a single storage disk for ASM from campus B. ASM will mirror the data between the two campuses.
Each node will use normal redundancy for the voting disk and OCR.
The thought here is that we could lose an entire datacenter--2 nodes, a FAS3070, server switch--everything--and still be up on the other campus. However, here's the question: What happens when the inter-campus network links fail? In this situation, nodes 1 and 2 on campus A can still see all storage, voting disk, and ocr on its campus from its 3070, but they cannot see nodes 3 and 4, or the storage on the other campus. Nodes 3 and 4 can still see all of its storage, voting disk, and ocr on campus B, but they cannot see nodes 1 and 2 or the storage on campus A. Basically, each set of nodes (1 and 2 on campus A, and 3 and 4 on campus B) can operate independently from the other campus' nodes. Does anyone know how clusterware would handle such a situation?
Thanks for any input!

Here is what will be the final production configuration:
Definitions:
Campus A (NetApp A), and Campus B (NetApp B) will be the two sites.
We have 4 filers, two on each campus. There exists mirrored and unmirrored storage (so that we can do failovers in the case of a campus/site outage). We will be using unmirrored storage as to not duplicate data 4 times. The disks will be configured on one NetApp from each campus to use the RAID-DP feature provided by the filer, but the other campus will not do NetApp/Filer level mirroring. All mirroring will be done by Oracle's ASM. Basically, when I say "mirrored" or "unmirrored", I'm referring to filer-level mirroring, not ASM-level or Oracle "normal redundancy" mirroring. Here's how the exports look:
NA-A will export one 500GB volume for datafile storage, unmirrored.
NA-A will export one 500GB volume for archivelog storage, unmirrored.
NA-A will export one 50GB volume for redo log storage, unmirrored.
NA-A will export one 1GB volume for OCR and voting disk storage, unmirrored
NA-A will export one 1GB volume for voting disk storage, MIRRORED. This is so that if an entire site fails, and that site contains the majority of the voting disks, we can failover the mirrored voting disk volume to the other campus and bring that side up. This allows for the smallest amount of downtime.
NA-B will export one 500GB volume for datafile storage, unmirrored.
NA-B will export one 500GB volume for archivelog storage, unmirrored.
NA-B will export one 50GB volume for redo log storage, unmirrored.
NA-B will export 1GB volume for OCR and voting disk storage, unmirrored.
$ORACLE_HOME will be local to the node. We want to be able to do rolling upgrades.
Each node will have a public, private, and storage interface, all on different VLANs.
ASM will mirror the two 500GB volumes, one from each side. Oracle will use internal mechanisms to mirror the OCR disks and Voting Disks. At this point, we will remain completely online should the campus with the single voting disk fail, and be offline for a very short amount of time if the campus with two voting disks fail. Downtime length will be the time it takes for a SysAdmin to login to the filer and take over the other filer's disks. This happens very quickly, typically less than a minute.
Any other questions, feel free to ask.

Apps team uploading 114505 kbof text file,too many archives getting

the upload is going on ,too many are getting generated in archivelog location
i have increased 200gb to 900gb
please let me know how to know for 14505 kb of dataupload how many archives gettting generated
can we estimate before dataupload how many archives can generate
can you please explain clearly
thanks

Hi,
There is no specific method to calculate the number of archived log files to be generated for the particular load.
But, we may do some rough calculation by looking at the rate of archived log generation.
Check the following things,
1) How frequently the logs are getting generated and the size of the files.
2) How many data has been loaded so far.
Based on the above input, you may get some idea on number of ARCHIVED LOG files to be generated during the rest of the data load.
Also, you may do the following to avoid keep adding space to archive destination.
1) Wite a UNIX shell script to BACKUP the ARCHIVED LOG FILES and DELETE the files once backuped up; which should run for every 10 minutes.
Thanks.

Archivelogs to different locations - only with Enterprise Edition?How to?

Hello,
while searching for an answer to 'how to store my archivelogs to different locations' I came across a post, that says, that this is only possible with enterprise edition? Is that true?
In case it is not: How do I add to an online database a second or more targets? I tried it on a test database, but the new target was not accepted, the entry pointing to the FRA was deleted, and everythin stopped, of course. Is there a way to add a second target without shutting down the database? Could anyone please explain, I am afraid to crash our live database. But living without a second target makes me nervous...
Thank you very much for your help,
Chris

Did you look at the documentation for 10g?
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_transport.htm#i1265402
This was only for remote db site but there is more in the book.
5.2.2.1 Changing Destination Attributes
You can dynamically update most of the attribute values of the LOG_ARCHIVE_DEST_n and the LOG_ARCHIVE_DEST_STATE_n parameters using the ALTER SYSTEM SET statement.
The modifications take effect after the next log switch on the primary database. For example, to defer redo transport services from transmitting redo data to the remote standby database named boston, issue the following statements on the primary database:
SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=boston
2> VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)';
SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=DEFER;
Read and have fun.
I think the point you missed is that you got to set the state of the destination as well.
Regards
Tim

Backup archivelogs from different location

DB : 10.2.0.4
OS : HEHL5
due to space issue i moved the archived to different location from log_archive_dest_1.
is it possible to backup the archivelogs from different location as i moved them?
Thanks.

My bad , it's not a must! Please see,
bash-3.2$ ls
o1_mf_1_34_8jk60c7b_.arc o1_mf_1_35_8jkz3p0l_.arc o1_mf_1_36_8jlcqpky_.arc
bash-3.2$ mkdir /tmp/archivelognewloc
bash-3.2$ cp *.* /tmp/archivelognewloc
bash-3.2$ rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Jan 30 14:40:17 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
allconnected to target database: **** (DBID=1228973204)
RMAN>
RMAN> catalog start with '/tmp/archivelognewloc';
searching for all files that match the pattern /tmp/archivelognewloc
List of Files Unknown to the Database
=====================================
File Name: /tmp/archivelognewloc/o1_mf_1_36_8jlcqpky_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_35_8jkz3p0l_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_34_8jk60c7b_.arc
Do you really want to catalog the above files (enter YES or NO)? yes
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /tmp/archivelognewloc/o1_mf_1_36_8jlcqpky_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_35_8jkz3p0l_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_34_8jk60c7b_.arc
RMAN>
Update : A little better demo
SQL*Plus: Release 11.2.0.1.0 Production on Wed Jan 30 15:00:32 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining
and Real Application Testing options
SQL> alter system switch logfile;
System altered.
SQL> /
System altered.
SQL> alter system checkpoint;
System altered.
SQL> alter system switch logfile;
System altered.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining
and Real Application Testing options
bash-3.2$ ls
o1_mf_1_38_8jldnkog_.arc o1_mf_1_40_8jlfdnph_.arc
o1_mf_1_39_8jlfdmoq_.arc o1_mf_1_41_8jlff2nn_.arc
bash-3.2$ pwd
/u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30
[root@EDHDR3P0 ~]# ls /tmp/archivelognewloc/
[root@EDHDR3P0 ~]# exit
logout
bash-3.2$
bash-3.2$
bash-3.2$ pwd
/u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30
bash-3.2$ ls
o1_mf_1_38_8jldnkog_.arc o1_mf_1_40_8jlfdnph_.arc
o1_mf_1_39_8jlfdmoq_.arc o1_mf_1_41_8jlff2nn_.arc
bash-3.2$ ls /tmp/archivelognewloc/
bash-3.2$ ls -l /tmp/archivelognewloc/
total 0
bash-3.2$ cp * /tmp/archivelognewloc/
bash-3.2$ ls -l /tmp/archivelognewloc/
total 3620
-rw-r----- 1 oracle oinstall 549888 Jan 30 15:02 o1_mf_1_38_8jldnkog_.arc
-rw-r----- 1 oracle oinstall 3117568 Jan 30 15:02 o1_mf_1_39_8jlfdmoq_.arc
-rw-r----- 1 oracle oinstall    1024 Jan 30 15:02 o1_mf_1_40_8jlfdnph_.arc
-rw-r----- 1 oracle oinstall   19456 Jan 30 15:02 o1_mf_1_41_8jlff2nn_.arc
bash-3.2$ pwd
/u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30
bash-3.2$ rm -rf *
bash-3.2$ ls
bash-3.2$ rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Jan 30 15:03:13 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: AMER (DBID=1228973204)
RMAN> backup archivelog all;
Starting backup at 30-JAN-13
current log archived
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=151 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 01/30/2013 15:03:32
RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
ORA-19625: error identifying file /u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30/o1_mf_1_38_8jldnkog_.arc
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
RMAN> catalog start with '//tmp/archivelognewloc';
searching for all files that match the pattern //tmp/archivelognewloc
List of Files Unknown to the Database
=====================================
File Name: /tmp/archivelognewloc/o1_mf_1_39_8jlfdmoq_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_41_8jlff2nn_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_40_8jlfdnph_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_38_8jldnkog_.arc
Do you really want to catalog the above files (enter YES or NO)? yes
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /tmp/archivelognewloc/o1_mf_1_39_8jlfdmoq_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_41_8jlff2nn_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_40_8jlfdnph_.arc
File Name: /tmp/archivelognewloc/o1_mf_1_38_8jldnkog_.arc
RMAN> backup archivelog all;
Starting backup at 30-JAN-13
current log archived
using channel ORA_DISK_1
archived log /u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30/o1_mf_1_38_8jldnkog_.arc not found or out of sync with catalog
trying alternate file for archived log of thread 1 with sequence 38
archived log /u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30/o1_mf_1_39_8jlfdmoq_.arc not found or out of sync with catalog
trying alternate file for archived log of thread 1 with sequence 39
archived log /u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30/o1_mf_1_40_8jlfdnph_.arc not found or out of sync with catalog
trying alternate file for archived log of thread 1 with sequence 40
archived log /u01/app/oracle/flash_recovery_area/AMER/archivelog/2013_01_30/o1_mf_1_41_8jlff2nn_.arc not found or out of sync with catalog
trying alternate file for archived log of thread 1 with sequence 41
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=38 RECID=45 STAMP=806079846
input archived log thread=1 sequence=39 RECID=42 STAMP=806079846
input archived log thread=1 sequence=40 RECID=44 STAMP=806079846
input archived log thread=1 sequence=41 RECID=43 STAMP=806079846
input archived log thread=1 sequence=42 RECID=41 STAMP=806079812
input archived log thread=1 sequence=43 RECID=46 STAMP=806079851
channel ORA_DISK_1: starting piece 1 at 30-JAN-13
channel ORA_DISK_1: finished piece 1 at 30-JAN-13
piece handle=/u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T150411_8jlfmcmf_.bkp tag=TAG20130130T150411 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 30-JAN-13
RMAN> list backup of archivelog all;
List of Backup Sets
===================
BS Key Size       Device Type Elapsed Time Completion Time
1       981.94M    DISK        00:01:15     30-JAN-13
        BP Key: 1   Status: AVAILABLE Compressed: NO Tag: TAG20130130T143224
        Piece Name: /u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T143224_8jlcqs5d_.bkp
List of Archived Logs in backup set 1
Thrd Seq     Low SCN    Low Time Next SCN   Next Time
1    5       830546     25-JAN-13 841823     25-JAN-13
1    6       841823     25-JAN-13 866733     25-JAN-13
1    7       866733     25-JAN-13 889743     25-JAN-13
1    8       889743     25-JAN-13 912846     26-JAN-13
1    9       912846     26-JAN-13 931109     26-JAN-13
1    10      931109     26-JAN-13 952239     26-JAN-13
1    11      952239     26-JAN-13 979268     26-JAN-13
1    12      979268     26-JAN-13 1004465    26-JAN-13
1    13      1004465    26-JAN-13 1021707    26-JAN-13
1    14      1021707    26-JAN-13 1040437    27-JAN-13
1    15      1040437    27-JAN-13 1068031    27-JAN-13
1    16      1068031    27-JAN-13 1091450    27-JAN-13
1    17      1091450    27-JAN-13 1114656    27-JAN-13
1    18      1114656    27-JAN-13 1137779    27-JAN-13
1    19      1137779    27-JAN-13 1165125    27-JAN-13
1    20      1165125    27-JAN-13 1199499    28-JAN-13
1    21      1199499    28-JAN-13 1228282    28-JAN-13
1    22      1228282    28-JAN-13 1249640    28-JAN-13
1    23      1249640    28-JAN-13 1270613    28-JAN-13
1    24      1270613    28-JAN-13 1291570    28-JAN-13
1    25      1291570    28-JAN-13 1312497    28-JAN-13
1    26      1312497    28-JAN-13 1332622    28-JAN-13
1    27      1332622    28-JAN-13 1365097    28-JAN-13
1    28      1365097    28-JAN-13 1395297    28-JAN-13
1    29      1395297    28-JAN-13 1407058    28-JAN-13
1    30      1407058    28-JAN-13 1437549    29-JAN-13
1    31      1437549    29-JAN-13 1469773    29-JAN-13
1    32      1469773    29-JAN-13 1504608    29-JAN-13
1    33      1504608    29-JAN-13 1522578    29-JAN-13
1    34      1522578    29-JAN-13 1553706    30-JAN-13
1    35      1553706    30-JAN-13 1586954    30-JAN-13
1    36      1586954    30-JAN-13 1603625    30-JAN-13
BS Key Size       Device Type Elapsed Time Completion Time
2       538.00K    DISK        00:00:01     30-JAN-13
        BP Key: 2   Status: AVAILABLE Compressed: NO Tag: TAG20130130T144745
        Piece Name: /u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T144745_8jldnkxt_.bkp
List of Archived Logs in backup set 2
Thrd Seq     Low SCN    Low Time Next SCN   Next Time
1    38      1604067    30-JAN-13 1604680    30-JAN-13
BS Key Size       Device Type Elapsed Time Completion Time
3       3.64M      DISK        00:00:00     30-JAN-13
        BP Key: 3   Status: AVAILABLE Compressed: NO Tag: TAG20130130T150411
        Piece Name: /u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T150411_8jlfmcmf_.bkp
List of Archived Logs in backup set 3
Thrd Seq     Low SCN    Low Time Next SCN   Next Time
1    38      1604067    30-JAN-13 1604680    30-JAN-13
1    39      1604680    30-JAN-13 1606046    30-JAN-13
1    40      1606046    30-JAN-13 1606049    30-JAN-13
1    41      1606049    30-JAN-13 1606057    30-JAN-13
1    42      1606057    30-JAN-13 1606303    30-JAN-13
1    43      1606303    30-JAN-13 1606353    30-JAN-13
RMAN> crosscheck backup of archivelog all;
using channel ORA_DISK_1
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T143224_8jlcqs5d_.bkp RECID=1 STAMP=806077945
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T144745_8jldnkxt_.bkp RECID=2 STAMP=806078865
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T150411_8jlfmcmf_.bkp RECID=3 STAMP=806079851
Crosschecked 3 objects
RMAN> list backup of archivelog all;
List of Backup Sets
===================
BS Key Size       Device Type Elapsed Time Completion Time
1       981.94M    DISK        00:01:15     30-JAN-13
        BP Key: 1   Status: AVAILABLE Compressed: NO Tag: TAG20130130T143224
        Piece Name: /u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T143224_8jlcqs5d_.bkp
List of Archived Logs in backup set 1
Thrd Seq     Low SCN    Low Time Next SCN   Next Time
1    5       830546     25-JAN-13 841823     25-JAN-13
1    6       841823     25-JAN-13 866733     25-JAN-13
1    7       866733     25-JAN-13 889743     25-JAN-13
1    8       889743     25-JAN-13 912846     26-JAN-13
1    9       912846     26-JAN-13 931109     26-JAN-13
1    10      931109     26-JAN-13 952239     26-JAN-13
1    11      952239     26-JAN-13 979268     26-JAN-13
1    12      979268     26-JAN-13 1004465    26-JAN-13
1    13      1004465    26-JAN-13 1021707    26-JAN-13
1    14      1021707    26-JAN-13 1040437    27-JAN-13
1    15      1040437    27-JAN-13 1068031    27-JAN-13
1    16      1068031    27-JAN-13 1091450    27-JAN-13
1    17      1091450    27-JAN-13 1114656    27-JAN-13
1    18      1114656    27-JAN-13 1137779    27-JAN-13
1    19      1137779    27-JAN-13 1165125    27-JAN-13
1    20      1165125    27-JAN-13 1199499    28-JAN-13
1    21      1199499    28-JAN-13 1228282    28-JAN-13
1    22      1228282    28-JAN-13 1249640    28-JAN-13
1    23      1249640    28-JAN-13 1270613    28-JAN-13
1    24      1270613    28-JAN-13 1291570    28-JAN-13
1    25      1291570    28-JAN-13 1312497    28-JAN-13
1    26      1312497    28-JAN-13 1332622    28-JAN-13
1    27      1332622    28-JAN-13 1365097    28-JAN-13
1    28      1365097    28-JAN-13 1395297    28-JAN-13
1    29      1395297    28-JAN-13 1407058    28-JAN-13
1    30      1407058    28-JAN-13 1437549    29-JAN-13
1    31      1437549    29-JAN-13 1469773    29-JAN-13
1    32      1469773    29-JAN-13 1504608    29-JAN-13
1    33      1504608    29-JAN-13 1522578    29-JAN-13
1    34      1522578    29-JAN-13 1553706    30-JAN-13
1    35      1553706    30-JAN-13 1586954    30-JAN-13
1    36      1586954    30-JAN-13 1603625    30-JAN-13
BS Key Size       Device Type Elapsed Time Completion Time
2       538.00K    DISK        00:00:01     30-JAN-13
        BP Key: 2   Status: AVAILABLE Compressed: NO Tag: TAG20130130T144745
        Piece Name: /u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T144745_8jldnkxt_.bkp
List of Archived Logs in backup set 2
Thrd Seq     Low SCN    Low Time Next SCN   Next Time
1    38      1604067    30-JAN-13 1604680    30-JAN-13
BS Key Size       Device Type Elapsed Time Completion Time
3       3.64M      DISK        00:00:00     30-JAN-13
        BP Key: 3   Status: AVAILABLE Compressed: NO Tag: TAG20130130T150411
        Piece Name: /u01/app/oracle/flash_recovery_area/AMER/backupset/2013_01_30/o1_mf_annnn_TAG20130130T150411_8jlfmcmf_.bkp
List of Archived Logs in backup set 3
Thrd Seq     Low SCN    Low Time Next SCN   Next Time
1    38      1604067    30-JAN-13 1604680    30-JAN-13
1    39      1604680    30-JAN-13 1606046    30-JAN-13
1    40      1606046    30-JAN-13 1606049    30-JAN-13
1    41      1606049    30-JAN-13 1606057    30-JAN-13
1    42      1606057    30-JAN-13 1606303    30-JAN-13
1    43      1606303    30-JAN-13 1606353    30-JAN-13
RMAN> HTH
Aman....
Edited by: Aman.... on Jan 30, 2013 3:06 PM

RMAN retores archivelog to dbs location

While i test my RMAN backup in test server, I found archive log always restore to oracle_home/dbs location .rather than actual location.
I copy the whole rman bacnk to my test server from production to test..which is same folder structure. When i put the backup in exact location and set dbid and restore controlfile. And then restore datafile and start recover them ,And the problem start at this point .Archive log should restore to the same location that in production. But it restores to oracle_home/dbs. Where is the mistake that i have done??

Post the output of
log_archive_dest_1 ------ > assuming your db version > 10.1from your source DB.
Please provide the version
I know your question is about restore. Just want to let you know ; if you execute
rman > backup database;without specifying backup location using FORMAT parameter, then your backup files will end up in ORACLE_HOME/dbs

Backup via Grid Control backs up to wrong location.

When creating a backup job via CG it seems to be backing up to the default directory of $ORACLE_HOME/dbs. However, rman is configured to backup to a different location. Below is the backup script that GC created.
If I manual run backup database from RMAN the backup goes to the correct location.
$rman_script="run {
allocate channel oem_backup_disk1 type disk maxpiecesize 5 G;
backup as BACKUPSET tag '%TAG' database;
backup as BACKUPSET tag '%TAG' archivelog all not backed up delete all input;
backup tag '%TAG' current controlfile;
release channel oem_backup_disk1;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
&br_save_agent_env();
&br_prebackup($l_db_connect_string, $l_is_cold_backup, $l_use_rcvcat, $l_db_10_or_higher, $l_backup_strategy, "FALSE");
my $result = &br_backup();
exit($result);

I believe it's the one holding the rman repository. Is your rman repository on a windows box? Make sure that account has log on as batch job privilege.

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;

Archivelog location

Similar Messages

Maybe you are looking for