FRA on ASM

I am trying to create a compressed backup on ASM using FRA setup. I have defined db_recovery_file_dest and db_recovery_file_dest_size. But the backup is not getting created and seems to simply hang.
Is there anything wrong in the below allocation while using FRA?
ALLOCATE CHANNEL C1 TYPE DISK format '+DATA01/ora_df%chr%t_s%chr%s_s%chr%p.BKP' maxopenfiles 3;

Didn't see any errors in v$rman_output.
OUTPUT
connected to target database: DB (DBID=3197251912)
using target database control file instead of recovery catalog
Starting backup at 23-MAR-09
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=202 instance=DB1 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=206 instance=DB1 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=274 instance=DB1 devtype=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: sid=205 instance=DB1 devtype=DISK
channel ORA_DISK_1: starting compressed incremental level 0 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00180 name=+DATAGRP01/DB/datafile/dbfile1.447.680717737
channel ORA_DISK_1: starting piece 1 at 23-MAR-09
channel ORA_DISK_2: starting compressed incremental level 0 datafile backupset
channel ORA_DISK_2: specifying datafile(s) in backupset
input datafile fno=00007 name=+DATAGRP01/DB/datafile/index.269.677780519
channel ORA_DISK_2: starting piece 1 at 23-MAR-09
channel ORA_DISK_3: starting compressed incremental level 0 datafile backupset
channel ORA_DISK_3: specifying datafile(s) in backupset
input datafile fno=00008 name=+DATAGRP01/DB/datafile/sdb.270.677780705
...channel ORA_DISK_3: starting piece 1 at 23-MAR-09
channel ORA_DISK_4: starting compressed incremental level 0 datafile backupset
channel ORA_DISK_4: specifying datafile(s) in backupset
input datafile fno=00116 name=+DATAGRP01/DB/datafile/lrg.378.677781499
channel ORA_DISK_4: starting piece 1 at 23-MAR-09

Similar Messages

FRA on ASM and to tape

I am using FRA and want to store backups for two days on the disk and also simultaneouly copy to tape everyday from disk. How do I achive this? Does it require a third party tape library that need to be mentioned in the rman script? I see lot of docs talks about copying from ASM to NFS and then allow sys admins to manage the tape copy. Pls advise the steps and best practice/maintenance overhead.

Hello KR,
To store backups on tape devices directly from rman (allocate a tape channel) you must use a MML (Media Management Library eg.: Backupexec, Netbackup, Legato).
But you can store it on a tape backing up you flash recovery area.
In my case to get retention policies...
RMAN> rman target / log=$SCRIPT/WHOLE_DB.log<<EOF
backup as compressed backupset
database tag=WHOLE_DB
plus archivelog tag=ARCHIVED_LOG
delete all input;
delete noprompt obsolete device type disk; #### Erase backup from file system
EOF
Regards,
Rodrigo Mufalani
http://mufalani.blogspot.com

Backing up ASM/FRA to disk via RMAN

Our 9i RAC systems were built using Veritas SFRAC. Due to an archaic tape infrastructure, we had to stream our backups to disk, then allow a nightly O/S backup job come along and backup it up to tape. We were not allowed to directly stream any backups to tape.
We are now in the process of building 10g RAC systems with Solaris 10, using ASM/Clusterware, and no 3rd party clustered file system.
My question is: if we define a FRA in ASM and stream RMAN backups there, how can I backup this area to disk so that the nightly O/S job can put it to tape. Likewise, if I have to recover and go to tape to pull an older backup, how do I restore a backup to the FRA so I can perform a restore (if it can be done)?
In other words, I still cannot directly stream to tape from the ASM FRA - I must first put it out to disk. Is this possible?
Thanks,
Jeff

AFAIK, the FRA/ASM can only be backed up to the
tape.This is correct. The FRA was created to be your on-disk backup location so that N days/copies of your backups stick around ( RMAN> CONFIGURE RETENTION POLICY TO [RECOVERY WINDOW x | REDUNDANCY x] ) to be readily available. So in RMAN's view, to backup the FRA to disk, again, would not make sense. So the only way to back it up is to a Tertiary device (tape) only.
HTH,
Layton

ASM and FRA

Installed Oracle 11g R2. Configured ASM +DATA (for data files) and FRA (for backups).
If the FRA diskgroup (which is non-raided) stops working due to the disk failure, assume all other disks (OS and DATA) are still operating normally, will the Oracle database can still be used/accessed by the user?

MORE INFO to add:
Ideally, the FRA should be on RAID 1. But due to the configuration limitation, I can only use one disk for FRA and the spare one for holding the multiplexing files such as REDO, CONTROL, and ARCHIVE.
By this way, DATA (Two ASM disks + raid 1), FRA (One ASM disk, non-raid), and Multiplexing (one regular disk, non-raid).
DATA (redo log + control + others) --> multiplexes to --> Multiplex Disk (mentioned above to hold redo log + control)
FRA (archive + all other backups) --> multiplexes to --> Multiplex Disk (mentioned above to hold archive)
Like to hear your opinion and comments.
P.S. The FRA will hold the backups only, nothing else. And DATA (Two ASM disks + raid 1) will hold the regular oracle data files + redo, control and other related files, nothing else.
Edited by: scottjhn on Aug 27, 2012 3:18 PM

FRA in use, backups written directly to a deduplication device

Oracle 11.1.0.7
An FRA is in use to store archive logs and flashback logs.
RMAN full and incremental backups write directly to EMC's Data Domain, a deduplication storage system, this appliance replicates to a secondary recovery location.
The Data Domain storage device is nfs-mounted to the database server, for our purposes it looks to be disk.
Before we nfs-mounted this storage area, we used NetBackUp SBT_TAPE.
Now that we are nfs-mounted we are removing NetBackUp and writing directly to DISK.
Storage conservation and reliability are the reasons behind the decision to move backup sets out of the FRA.
Sounds reasonable; we don't need duplicate storage of the backup in the FRA (in ASM) and then backing it up to the dedup location.
Also, the backup is immediately replicated to another location, so that intermediary time when the backup set resides only in the FRA is
eliminated, so the possibility of something happening goes away.
We are following a Best Practices document from EMC Data Domain. Another distinction this document makes is that archivelogs should be backed up separately and not with the backupset to take full advantage of dedupping rates.
While I understand the logic, from the Oracle perspective there are things that we give up by not fully utilizing the FRA. They may be a small number of things that are not impactfull, but I'm gathering a list of facts. Some things I think :
- BACKUP RECOVERY AREA can't be used
- more manual management of backup sets requiring different backup commands
- size management of the FRA considers all pieces of the backup, flashback and archivelogs
I'm sure there are things missing from this list. I am also sure that we will continue to span FRA and Dedup storage for Oracle backups, but I'd like to know all of the facts on what I'm losing by doing so.
Any insight would be appreciated.
Sherrie

Oracle 11.1.0.7
An FRA is in use to store archive logs and flashback logs.
RMAN full and incremental backups write directly to EMC's Data Domain, a deduplication storage system, this appliance replicates to a secondary recovery location.
The Data Domain storage device is nfs-mounted to the database server, for our purposes it looks to be disk.
Before we nfs-mounted this storage area, we used NetBackUp SBT_TAPE.
Now that we are nfs-mounted we are removing NetBackUp and writing directly to DISK.
Storage conservation and reliability are the reasons behind the decision to move backup sets out of the FRA.
Sounds reasonable; we don't need duplicate storage of the backup in the FRA (in ASM) and then backing it up to the dedup location.
Also, the backup is immediately replicated to another location, so that intermediary time when the backup set resides only in the FRA is
eliminated, so the possibility of something happening goes away.
We are following a Best Practices document from EMC Data Domain. Another distinction this document makes is that archivelogs should be backed up separately and not with the backupset to take full advantage of dedupping rates.
While I understand the logic, from the Oracle perspective there are things that we give up by not fully utilizing the FRA. They may be a small number of things that are not impactfull, but I'm gathering a list of facts. Some things I think :
- BACKUP RECOVERY AREA can't be used
- more manual management of backup sets requiring different backup commands
- size management of the FRA considers all pieces of the backup, flashback and archivelogs
I'm sure there are things missing from this list. I am also sure that we will continue to span FRA and Dedup storage for Oracle backups, but I'd like to know all of the facts on what I'm losing by doing so.
Any insight would be appreciated.
Sherrie

Backup - ASM vs regular cooked file system

Use Oracle 11g on Linux.
The disk system is ASM. For instance, the FRA is configured based on a ASM disk group +FRA (along withe multiplexed logs and control files). This is one place for the backup and multiplexing.
Now, I intend to place the multiplexed files also to a second location (disk). For this disk, I have two choices: 1) Use the ASM diskgroup 2) Use the regular datafile (/u01/oracle/oracdata/back).
Good thing about the cooked file system ( I can think) is that I can see the location of the file by going to the file manager and locate the directory of the files, kind of transparent.
For doing so, will it incur the opertion cost in the future? (As compared to the ASM diskgroup, though files somewhat hidden from the view, but Oracle will take care of "everything").
So, any comment on the file system of the second disk? (Oracle ASM vs regular cooked file system).
Thanks

I suggest you continue using ASM and use the ACFS feature.
From 11.2.0.3 I don't use FRA on ASM only, I'm using FRA under ASM/ACFS mount point.
Oracle Automatic Storage Management Cluster File System (Oracle ACFS) is a multi-platform, scalable file system, and storage management technology that extends Oracle Automatic Storage Management (Oracle ASM) functionality to support customer files maintained outside of Oracle Database. Oracle ACFS supports many database and application files, including executables, database trace files, database alert logs, application reports, BFILEs, and configuration files. Other supported files are video, audio, text, images, engineering drawings, and other general-purpose application file data.
Starting with Oracle Automatic Storage Management 11g Release 2 (11.2.0.3), Oracle ACFS supports RMAN backups (BACKUPSET file type), archive logs (ARCHIVELOG file type), and Data Pump dumpsets (DUMPSET file type).

How to copy out ASM storege for archivelog to normal file system

Hi Expert,
I have two node running Oracle 11gr2 11.2.3 on SUN SOLARIS 64 bit. I need to copy out the archivelog store on ASM Flash recovery area to normal file system. How can i perform this task. How to ensure that after copy this archivelog can use for recovery.
Regard
William

Hi William,
Use this guide:
Step 4. Archived Online logs (archivelogs) and BackupSet stored in FRA
http://levipereira.wordpress.com/2011/09/16/how-migrate-asm-to-non-asm-unixlinux/
As you want copy, you must replace it:
this:
BACKUP AS COPY ARCHIVELOG ALL DELETE INPUT;
to:
BACKUP AS COPY ARCHIVELOG ALL;If you can still using FRA on ASM you can copy without change parameter "db_recovery_file_dest"
e.g
BACKUP AS COPY ARCHIVELOG ALL FORMAT '/u01/app/oracle/%U';
How to ensure that after copy this archivelog can use for recovery.Try it:
VALIDATE ARCHIVELOG ALL;
Regards,
Levi Pereira
Edited by: Levi Pereira on Jan 4, 2012 5:44 PM

Copy backups back to ASM

Hi,
I am working on an oracle MAA project (2 rac with 4 nodes each using dg)
i am backing up the system using rman (to FRA on ASM) and copying the latest backup outside to local storage.
i delete the contents of all backups in the ASM and i want to copy it back in.
i used DBMS_FILE_TRANSFER to copy outside but when i want to copy back i get ORA-15046.
any expirence?
10x,

Actually, rather than email them all back to yourself, (which would lose original sender info and original timestamp data in the list viewer pane, unless you did "redirects" which will still lose original long header information), try selecting all messages in the Windoze Mail program list viewer and dragging and redropping them onto the imap account's inbox. I know I can drag and drop messages across imap servers' inboxes in my all-Macintosh world. If it were a Mac, that would for sure put them back on the imap server. Whether your Windoze Mail program will allow you to drag and drop messages onto an imap mail inbox folder, I don't know...we ARE talking about Windoze here... Of course, do what Scott suggested earlier, and change from POP/delete-from-server to IMAP on the Windoze machine first, before trying this.
If the above doesn't work, go to Mail.app's Help menubar, enter the search phrase "importing messages" and see if any of the guidance there can help you accomplish what you are trying to do with regards to cross-platform mail import. If your Windoze Mail application can export those messages into "mbox" format, do so then take the exported archive file and import it into the Mac's Mail, as Mail's Help suggests.

I need help on how to setup hardware raid for ASM.

In the « Recommendations for Storage Preparation” section in the following documentation: http://download.oracle.com/docs/cd/B28359_01/server.111/b31107/asmprepare.htm
It mentions:
--Use the storage array hardware RAID 1 mirroring protection when possible to reduce the mirroring overhead on the server.
Which is a good raid 1 configuration considering my machine setup?
“I put my Machine info below.”
Should I go for something like:
5 * raid 1 of 2 disks in each raid: disk group DATA
5 * raid 1 of 2 disks in each raid: disk group FRA
Then ASM will take care of all the striping between the 5 raids inside a disk group right?
OR, I go for:
1 * raid 1 of 10 disks: disk group DATA
1 * raid 1 of 10 disks: disk group FRA
In the second configuration, does ASM recognize that there are 10 disks in my raid configuration and stripes on those disks? Or to use ASM striping, I need to have lots of raid in a disks group?
Here is my Machine Characteristics:
O/s is Oracle Enterprise Linux 4.5 64 bit
Single instance on Enterprise Edition 10g r2
200 GIG database size.
High "oltp" environment.
Estimated growth of 60 to 80GIG per year
50-70GIG archivelogs generation per Day
Flashback time is 24 hours: 120GIG of flashback space in avg
I keep a Local backup. Then push to another disk storage, then on tape.
General Hardware Info:
Dell PowerEdge 2950
16 GIG RAM
2 * 64 bit dual core CPU's
6 * local 300G/15rpm disks
Additional Storage:
Dell PowerVault MD1000
15 * 300G/15rpm Disks
So I have 21 Disks in total.

I would personally prefer the first configuration and let ASM stripe the disks. Generally speaking, many RAID controllers will stripe then mirror (0+1) when you tell it to build a striped and mirrored RAID set on 10 disks. Some will mirror then stripe (1+0) which is what most people prefer. That's because when a 1+0 configuration has a disk failure, only a single RAID 1 set needs to be resync'd. The other members of the stripe won't have to be resynchronized.
So, I'd prefer to have ASM manage 5 luns and let ASM stripe across those 5 luns in each disk group. It also increases your ability to reorganize your storage if you need 20% more info in DATA and can afford 20% less in FRA, you can move one of your RAID 1 luns from FRA to DATA easily.
That's my 0.02.

ASM Vs asmlib

In a given scenario of having a RAC with raw devices as storage option with ASM, below is the flow.
1. If I need more data storage, I just need another raw partition of /dev/raw/rawdata4(shared) and using ASM command I can either create a new DGroup or extend the existing Dgroup.
2. Where does asmlib comes to picture?
3. OCR and Voting are directly on raw devices.
4. Exports, database instance bdump,udump, adump, software cann't be on the asm disks.
5. For the system admins, does it matter if I use the raw devices for asm or raw as it is? Isn't the prepartion part the same and only DBA's make the raw as ASM disks?
6. Flow of raw disks
LUNS --> /dev/raw/rawocr (shared)--> OCR
LUNS --> /dev/raw/rawvoting (shared)--> Voting
LUNS --> /dev/raw/rawdata1(shared) --> +DATA(using asm) --> tablespaces
LUNS --> /dev/raw/rawdata2(shared) --> +DATA(using asm) --> tablespaces
LUNS --> /dev/raw/rawdata3(shared) --> +DATA(using asm) --> tablespaces
LUNS --> /dev/raw/rawdata4(shared) --> +FRA(using asm) --> tablespaces
Please clarify if I understood right.

1, Yes - but for ASM disks it is not necessary to set up raw devices - you can give it the base block device - ensure the permissions are correct.
2, It's an optional libarary that can 'simplify management' and help improve overall performance.
3, Yes - in 10g RAW or supported CFS, inn 11g you can dispense with the Raw and use the underlying block device
4, Yes
5, Yes but as I mention it's even easier - no RAW required for ASM - just the block device
6, so it should look like
LUNS --> /dev/raw/rawocr (shared)--> OCR
LUNS --> /dev/raw/rawvoting (shared)--> Voting
LUNS --> +DATA(using asm) --> tablespaces
LUNS --> +DATA(using asm) --> tablespaces
LUNS --> +DATA(using asm) --> tablespaces
LUNS --> +FRA(using asm) --> tablespaces
Message was edited by:
PhilipRN

How to copy the ASM files on host filesystem.

Hello All,
There is a question come up in my mind that can we perform the copy/delete/move of ASM files to the host filesystem while the ASM instance is down.
For instance... To copy the file ASM file through AMCMD utility when the ASM instance is running.
ASMCMD> cp spfilenode.ora /u01
copying +DATA/NODE/spfilenode.ora -> /u01/spfilenode.ora
Now my question is, Can I copy/delete/move that file on OS filesystems when the ASM instance is down.
regards,
rohit

Hi,
1- Copy from ASM to FileSystem using cp command.
2- Copy from ASM to FileSystem using DBMS_FILE_TRANSFER.
1) In the first method, when I copy one file, I took more than 1 minute, so the following script would take me more than 1 days (I guess so).
#!/bin/ksh
# This script copies files from FRA on ASM to local disk
ORACLE_SID=+ASM2
ASMLS=/vasgatedb/app/vsgbkp/asm_ls.txt ##{ASM files list}
BKP=+data/vsgdb/vsgbkp/`date +%Y_%m_%d` ##{source location of files}
LOCALBACKUPDIR=/vasgatedb/app/vsgbkp ##{destination filesystem}
LOG=/vasgatedb/app/vsgbkp/asm_log.txt ##{log file}
# Get the list of files
$ORACLE_HOME/bin/asmcmd > $ASMLS <<EOF
ls $BKP
exit
EOF
# Clean the list by removing "ASMCMD>"
sed -i 's/ASMCMD> //g' $ASMLS
##cat $ASMLS
echo `date` > $LOG
# Copy files one by one
for FILENAME in `cat $ASMLS`
do
if [[ ! -f $LOCALBACKUPDIR/${FILENAME} ]]
then
$ORACLE_HOME/bin/asmcmd >> $LOG <<EOF
cp $BKP/$FILENAME $LOCALBACKUPDIR
EOF
fi
done
echo `date` >> $LOG
2) The second method, DBMS_FILE_TRANSFER took me less than 1 second to copy one file completely.
sys@VSGDB> set timing on
sys@VSGDB> exec dbms_file_transfer.COPY_FILE('asm_dir','level_0_vsgdb_9998_813844797.bkp','fs_dir','level_0_vsgdb_9998_813844797.bkp');
PL/SQL procedure successfully completed.
Elapsed: 00:00:00.38

11gR2 root.sh fails to copy OCR locations stored in ASM

Hi all,
I'm trying to extend an 11gR2 3-node RAC cluster to a 4th node. When trying to run the $GI_HOME/root.sh script it fails giving the following error:
/oracle/app/11.2.0/grid/root.sh
Running Oracle 11g root.sh script...
The following environment variables are set as:
ORACLE_OWNER= grid
ORACLE_HOME= /oracle/app/11.2.0/grid
Enter the full pathname of the local bin directory: [usr/local/bin]:
Copying dbhome to /usr/local/bin ...
Copying oraenv to /usr/local/bin ...
Copying coraenv to /usr/local/bin ...
Creating /etc/oratab file...
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root.sh script.
Now product-specific root actions will be performed.
2010-08-11 16:12:19: Parsing the host name
2010-08-11 16:12:19: Checking for super user privileges
2010-08-11 16:12:19: User has super user privileges
Using configuration parameter file: /oracle/app/11.2.0/grid/crs/install/crsconfig_params
Creating trace directory
-ksh: line 1: /bin/env: not found
/oracle/app/11.2.0/grid/bin/cluutil -sourcefile /etc/oracle/ocr.loc -sourcenode ucstst12 -destfile /orac le/app/11.2.0/grid/srvm/admin/ocrloc.tmp -nodelist ucstst12 ... failed
Unable to copy OCR locations
validateOCR failed for +OCR_VOTE at /oracle/app/11.2.0/grid/crs/install/crsconfig_lib.pm line 7979.
My environment is below:
OS: SLES 11.1
Database: 11.2.0.1
Grid Infrastructure: 11.2.0.1
OCR & Voting storage: ASM
DB file & FRA storage: ASM
# Nodes: 3
Any help is really appreciated.
Thanks.

Hi,
have you setup SSH for the new node (for User Oracle) in both ways, when extending it?
A common problem is to extend SSH is to do this one way only.
However especially when extending the cluster, there are some oracle tools which ssh/scp to the existing nodes (as the installation owner) to copy special files (like ocr.loc) to the new node.
If SSH is not setup both ways, then this will fail.
Check with user oracle or grid (whatever you used) that
ssh <node1> date
ssh <node2> date
ssh <node3> date
ssh <node4> date
Is working (from every node).
Note: In 11.2 you can rerun root.sh. Just do a $CRS_HOME/crs/install/rootcrs.pl –deconfig –force to deconfigure the stack and then rerun root.sh
Sebastian

How to delete the foreign archivelogs in a Logical Standby database

How do I remove the foreign archive logs that are being sent to my logical standby database. I have files in the FRA of ASM going back weeks ago. I thought RMAN would delete them.
I am doing hot backups of the databases to FRA for both databases. Using ASM, FRA, in a Data Guard environment.
I am not backing up anything to tape yet.
The ASM FRA foreign_archivelog directory on the logical standby FRA keeps growing and nothing is get deleted when
I run the following command every day.
delete expired backup;
delete noprompt force obsolete;
Primary database RMAN settings (Not all of them)
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD' CONNECT IDENTIFIER 'WMRTPRD_CWY';
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD2' CONNECT IDENTIFIER 'WMRTPRD2_CWY';
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD3' CONNECT IDENTIFIER 'WMRTPRD3_DG';
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
Logical standby database RMAN setting (not all of them)
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
How do I cleanup/delete the old ASM foreign_archivelog files?

OK, the default is TRUE which is what it is now
from DBA_LOGSTDBY_PARAMETERS
LOG_AUTO_DELETE TRUE SYSTEM YES
I am not talking about deleting the Archive logs files for the Logical database that it is creating, but the Standby archive log files being sent to the Logical Database after they have been applied.
They are in the alert log as follows under RFS LogMiner: Registered logfile
RFS[1]: Selected log 4 for thread 1 sequence 159 dbid -86802306 branch 763744382
Thu Jan 12 15:44:57 2012
*RFS LogMiner: Registered logfile [+FRA/wmrtprd2/foreign_archivelog/wmrtprd/2012_01_12/thread_1_seq_158.322.772386297] to LogM*
iner session id [1]
Thu Jan 12 15:44:58 2012
LOGMINER: Alternate logfile found. Transition to mining archived logfile for session 1 thread 1 sequence 158, +FRA/wmrtprd2/
foreign_archivelog/wmrtprd/2012_01_12/thread_1_seq_158.322.772386297
LOGMINER: End mining logfile for session 1 thread 1 sequence 158, +FRA/wmrtprd2/foreign_archivelog/wmrtprd/2012_01_12/threa
d_1_seq_158.322.772386297
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 159, +DG1/wmrtprd2/onlinelog/group_4.284.771760923

Disk are not appearing in DBCA

i have windows xp oracle 11g standard edition release one.
When i use DBCA for ASM instacne it does not show me disk within 'create disk group' page, i have raw disk and stamped wth ASM.
Initially it was showing me those raw and asm stamped disk as candidate for creating diskgroup within 'create disk group' page using DBCA , but for test purpose i have dropped those raw partion and recreat those raw partion ,stamped with ASM asmtoolg but now unable to see those candidate disk within 'create disk group' page using DBCA.
how can i reslove that issue please let me know.

### If you using RAC -> Don't Create FRA on OS/file system local, Please create on Share Storage
If you need to backup database on ASM... you have to use RMAN. You told ... you created FRA on none ASM . That's mean by default you can backup database to disk (rman) to FRA (none ASM).
And after that ... you can use 'cp' os command to copy files on FRA to anywhere.
By the way.... One way to copy datafiles(online) you have to use RMAN ....if offline but use ASM, you have to use RMAN too...
If you use 11G asm you can use "asmcmd" to copy files in ASM to none ASM.
Example:
$ asmcmd
ASMCMD> cp file01/txt /tmp/
copying +Vol1/db/file01.txt -> /tmp//file01.txt
Good Luck.

Duplicate command traying to use wrong backup

RMAN 10g (10.2.0.3). All catalog, target and auxiliary databases are exactly the same release.
The duplicate command is trying to use a backup that does not exist anymore.
"report obsolete" command listed very old backups that does not exist.
'delete obsolete" did not delete the old obsolete backups.
I dropped and created again the catalog, but after that, the old obsolete backups are still reported!!!!!
I issued "delete force obsolete" and "delete force expired..." commands. The "report obsolete" does not shows the old obsolete backups anymore.
But, duplicate command says that there are not backups of any datafile.
"list backup" command shows one available backup:
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
1057 Full 16.20M DISK 00:00:01 13-FEB-10
BP Key: 1060 Status: AVAILABLE Compressed: NO Tag: TAG20100213T182350
Piece Name: +DGB/siprod/autobackup/2010_02_13/s_710879030.714.710879031
Control File Included: Ckp SCN: 5287726942 Ckp time: 13-FEB-10
SPFILE Included: Modification time: 19-OCT-09
How can I tell to "duplicate" command, that it must use one specific backupset?

This is all the process, so you can see it complete.
'test' server cannot see the ASM DGA where the target database is. So I send the backup to a filesystem in 'siprod1' ('/ocfs2a') and I mount by NFS this filesystem in 'test' server, so that 'test' server can see the backup to use in the duplicate process. I have done this procees in the sae way twice before. Default FRA is ASM DGB (which cannot be seen by 'test').
I can send you a diagram of the servers and connections to you e-mail if you want, ahd the output of the query you asked for (it is a very long output).
When I dropped the rman catalog, I delete manually al lthe backups saved in FRA and in /ocfs2a.
This is a normal duplicate (non Data Guard). I am cloning from production to test.
===================================================================================
I tried to put here the complete output of ALL the process (command by command) but it exceedes the maximum lenght. I have sent you by e-mail that output.

FRA on ASM

Similar Messages

Maybe you are looking for