Datafiles in FRA... :)

Hi All,
I would like to share my doubts about ASM and FRA(Is this section the right one to put this doubt?)...
*I know about the retention policy in FRA and that files will be deleted automatically and that production datafiles should NEVER be moved to the FRA area.
But,
Using ASM I have two diskgroups, for data and FRA. FRA area is oversized (5G normally used of 300G total,backups are not placed here...) can this area(FRA) be used temporarily to guard some datafiles(data diskgroup running low...)?Which is the risk?Or Is it better to just put the datafiles outside the diskgroups?
Can you share histories (crash?,data deletion?duh..)
Using a test environment(no-ASM,no-RAC) I put a datafile in the FRA area but the view V$FLASH_RECOVERY_AREA_USAGE did not update...Is it normal?No?How refresh it?I already use crosscheck's rman..
Which is the best way to resize the FRA diskgroup and remanage the space to the data diskgroup?(external redundacy, FRA diskgroup is listed to have 1T by Enterprise Manager, db_recovery_file_dest_size=300G...)
Oracle DB version 11.2.0.3.0(RAC)
Linux version: 2.6.32.el6
Using Oracle ASM

Using ASM I have two diskgroups, for data and FRA. FRA area is oversized (5G normally used of 300G total,backups are not placed here...) can this area(FRA) be used temporarily to guard some datafiles(data diskgroup running low...)?Which is the risk?Or Is it better to just put the datafiles outside the diskgroups?
Using a test environment(no-ASM,no-RAC) I put a datafile in the FRA area but the view V$FLASH_RECOVERY_AREA_USAGE did not update...Is it normal?No?How refresh it?I already use crosscheck's rman..
Regular datafiles are not taken into account in V$RECOVERY_AREA_USAGE. Even if you use rman "catalog recovery area", rman will skip them. Therefore database will not remove them.
Which is the best way to resize the FRA diskgroup and remanage the space to the data diskgroup?(external redundacy, FRA diskgroup is listed to have 1T by Enterprise Manager, db_recovery_file_dest_size=300G...)
You can move disks between diskgroups. Or you can temporary disable db_recovery_file_dest (putting logs and other files to new destination), remove diskgroup, resize LUN and create new diskgroup.

Similar Messages

ASM Disk preparation for Datafiles and FRA in Oracle 10g RAC Inst

Dear Friends,
Please clarify wheteher the below method is correct to confiure ASM disks for Datafiles and FRA
Partitions provided by IT team for OCR and Voting Disk
/dev/sda1 - 150 GB (For +DATA)
/dev/sda2 - 100 GB (For +FRA)
OS : RHEL 5.6 (64 Bit)
kernel version = 2.6.18-238.el5
Steps:(Node1)
1) Install the RPM's for ASM
rpm -Uvh oracleasm-support-2.1.7-1.el5.x86_64.rpm
rpm -Uvh oracleasm-2.6.18-238.el5-2.0.5-1.el5.x86_64.rpm
rpm -Uvh oracleasmlib-2.0.4-1.el5.x86_64.rpm
2) Configure ASM
/etc/init.d/oracleasm configure
Default user to own the driver interface []: oracle
Default group to own the driver interface []: dba
Start Oracle ASM library driver on boot (y/n) [n]: y
Scan for Oracle ASM disks on boot (y/n) [y]:
Writing Oracle ASM library driver configuration: done
Initializing the Oracle ASMLib driver: [ OK ]
Scanning the system for Oracle ASMLib disks: [ OK ]
3) Cretae ASM Disk
/etc/init.d/oracleasm createdisk DISK1 /dev/sda1
/etc/init.d/oracleasm createdisk DISK2 /dev/sda2
4)/etc/init.d/oracleasm status
5)/etc/init.d/oracleasm scandisks
6)/etc/init.d/oracleasm listdisks
7) Nothing to perform on Node2
8) In dbca choose ASM and map the DISK1 for datafiles and DISK2 for FRA
Please confirm the above steps are right?if not please clarify
If DBCA ->ASM doesn't discover my disk then what should be the Discovery path i have to give?
Please refer any document / Metalink ID for the above complete process
Can i have ASM and oracle DB binary in the same home
Regards,
DB

user564706 wrote:
If DBCA ->ASM doesn't discover my disk then what should be the Discovery path i have to give?for asm disk created with oracleasm discovery path variable is ORCL:*
Please refer any document / Metalink ID for the above complete processhttp://docs.oracle.com/cd/B19306_01/install.102/b14203/storage.htm#BABIFHAB
Can i have ASM and oracle DB binary in the same homeyes. unless you want job role seperation or plan to run multiple versions of oracle homes
>
Regards,
DB

After renaming data file it failes during database open

Hi,
I took RMAN full back.
Then i renamed datafile then restored and recovered. It goes fine.
But during the daabase open it fails with
ORA-01113: file 6 needs media recovery
ORA-01110: data file 6: '+OBTDG1/qa112asm/datafile/users02.dbf'
Any specific reason for that?
=======================================================
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Jul 22 01:19:30 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN> backup database;
connected to target database: QA112ASM (DBID=3746246770)
RMAN>
Starting backup at 22-JUL-10
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=145 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=+OBTDG1/qa112asm/datafile/system01.dbf
input datafile file number=00003 name=+OBTDG1/qa112asm/datafile/rbs01.dbf
input datafile file number=00002 name=+OBTDG1/qa112asm/datafile/sysaux01.dbf
input datafile file number=00004 name=+OBTDG1/qa112asm/datafile/temp01.dbf
input datafile file number=00005 name=+OBTDG1/qa112asm/datafile/tools01.dbf
input datafile file number=00006 name=+OBTDG1/qa112asm/datafile/users01.dbf
input datafile file number=00007 name=+OBTDG1/qa112asm/datafile/vindx.dbf
channel ORA_DISK_1: starting piece 1 at 22-JUL-10
channel ORA_DISK_1: finished piece 1 at 22-JUL-10
piece handle=/qa/obj/oracle/obt/output/QA112ASM/obt_standby_03_protection_tui/dttmp/back08ljcr97_1_1 tag=TAG20100722T011934 co
mment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:25
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 22-JUL-10
channel ORA_DISK_1: finished piece 1 at 22-JUL-10
piece handle=/qa/obj/oracle/obt/output/QA112ASM/obt_standby_03_protection_tui/dttmp/back09ljcra0_1_1 tag=TAG20100722T011934 co
mment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 22-JUL-10
RMAN> shutdown immediate
Oracle instance shut down
RMAN> startup mount
connected to target database (not started)
Oracle instance started
database mounted
Total System Global Area 275615744 bytes
Fixed Size 2168944 bytes
Variable Size 184551312 bytes
Database Buffers 83886080 bytes
Redo Buffers 5009408 bytes
RMAN>run(
*run {*
set newname for datafile '+OBTDG1/QA112ASM/users01.dbf' to '+OBTDG1/QA112ASM/users02.dbf' ;
restore datafile '+OBTDG1/QA112ASM/users01.dbf';
recover datafile '+OBTDG1/QA112ASM/users01.dbf' noredo;
switch datafile '+OBTDG1/QA112ASM/users02.dbf' ;
RMAN>
2> 3> 4> 5> 6>
executing command: SET NEWNAME
Starting restore at 22-JUL-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=137 device type=DISK
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00006 to +OBTDG1/QA112ASM/datafile/users02.dbf
channel ORA_DISK_1: reading from backup piece /qa/obj/oracle/obt/output/QA112ASM/obt_standby_03_protection_tui/dttmp/back08ljc
r97_1_1
channel ORA_DISK_1: piece handle=/qa/obj/oracle/obt/output/QA112ASM/obt_standby_03_protection_tui/dttmp/back08ljcr97_1_1 tag=T
AG20100722T011934
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
Finished restore at 22-JUL-10
Starting recover at 22-JUL-10
using channel ORA_DISK_1
Finished recover at 22-JUL-10
datafile 6 switched to datafile copy
input datafile copy RECID=2 STAMP=724987222 file name=+OBTDG1/qa112asm/datafile/users02.dbf
RMAN> alter database open;
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 07/22/2010 01:20:23
ORA-01113: file 6 needs media recovery
ORA-01110: data file 6: '+OBTDG1/qa112asm/datafile/users02.dbf'
=======================================================
Edited by: user13310502 on Jul 23, 2010 4:49 AM

as you can see..
RMAN> sql "alter tablespace andreas offline";
sql statement: alter tablespace andreas offline
RMAN> run
2> {
3> set newname for datafile 8 to '+FRA';
4> restore datafile 8;
5> recover datafile 8;
6> switch datafile 8;
7> }
executing command: SET NEWNAME
Starting restore at 23-JUL-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00008 to +FRA
channel ORA_DISK_1: reading from backup piece +FRA/remtest/backupset/2010_07_23/nnndf0_tag20100723t135242_0.3112.725118763
channel ORA_DISK_1: restored backup piece 1
piece handle=+FRA/remtest/backupset/2010_07_23/nnndf0_tag20100723t135242_0.3112.725118763 tag=TAG20100723T135242
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
Finished restore at 23-JUL-10
Starting recover at 23-JUL-10
using channel ORA_DISK_1
starting media recovery
media recovery complete, elapsed time: 00:00:00
Finished recover at 23-JUL-10
datafile 8 switched to datafile copy
input datafile copy recid=7 stamp=725118807 filename=+FRA/remtest/datafile/andreas.3113.725118805
RMAN> sql "alter tablespace andreas online";
sql statement: alter tablespace andreas online
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 07/23/2010 13:53:33
RMAN-11003: failure during parse/execution of SQL statement: alter tablespace andreas online
ORA-01113: file 8 needs media recovery
ORA-01110: data file 8: '+FRA/remtest/datafile/andreas.3113.725118805'
RMAN> run
2> {
3> set newname for datafile 8 to '+FRA';
4> restore datafile 8;
5> switch datafile 8;
6> recover datafile 8;
7> }
executing command: SET NEWNAME
Starting restore at 23-JUL-10
using channel ORA_DISK_1
channel ORA_DISK_1: restoring datafile 00008
input datafile copy recid=8 stamp=725118807 filename=+DATA/remtest/datafile/andreas.349.725036143
destination for restore of datafile 00008: +FRA
channel ORA_DISK_1: copied datafile copy of datafile 00008
output filename=+FRA/remtest/datafile/andreas.3114.725118849 recid=9 stamp=725118849
Finished restore at 23-JUL-10
datafile 8 switched to datafile copy
input datafile copy recid=10 stamp=725118850 filename=+FRA/remtest/datafile/andreas.3114.725118849
Starting recover at 23-JUL-10
using channel ORA_DISK_1
starting media recovery
media recovery complete, elapsed time: 00:00:01
Finished recover at 23-JUL-10
RMAN> sql "alter tablespace andreas online";
sql statement: alter tablespace andreas online

Shared file system recomended for OCR and voting Disk in 10g R2

Dear Friends,
For Oracle 10g R2 (10.2.0.5) 64 bit which shared file system is recomended for OCR and voting Disk (NFS / raw devices / OCFS2)
For Datafiles and FRA i planned to use ASM
Regards,
DB

Hi,
If your using standard edition then you got no choice but raw devices
http://docs.oracle.com/cd/B19306_01/license.102/b14199/options.htm#CJAHAGJE
for ocfs2 you need to take extra care
Heartbeat/Voting/Quorum Related Timeout Configuration for Linux, OCFS2, RAC Stack to Avoid Unnecessary Node Fencing, Panic and Reboot [ID 395878.1]

CRS not starting

OS: OEL 5 U4 x86_64
DB: Oracle 11.2.0.1 EE
Grid Infrastructure: Oracle 11.2.0.1
CRS and Voting disk Storage: ASM
Datafile and FRA storage: ASM
I'm not sure exactly what caused this, but anyways, I changed MTU from 1500 to 900 online. After some time, 3 out of 4 nodes in the cluster went down and CRS refuses to start on these nodes after trying the switch back from MTU 9000 to 1500, reboots, and making sure disk permissions and ownership are correct. The logs are not too helpful (and cryptic) so I'm at a loss and appreciate any ideas or help.
The installation was successful, the RAC was up for a few days while running some tests (including restart of a node). Currently only a single node has everything up and functional, the others are not working. Below are some output that might help:
[root@ucstst11 bin]# ./crsctl check cluster -n ucstst11
ucstst11:
CRS-4535: Cannot communicate with Cluster Ready Services
CRS-4530: Communications failure contacting Cluster Synchronization Services daemon
CRS-4533: Event Manager is online
[root@ucstst11 bin]# ./crsctl start cluster -n ucstst11
CRS-2672: Attempting to start 'ora.cssd' on 'ucstst11'
CRS-2672: Attempting to start 'ora.diskmon' on 'ucstst11'
CRS-2676: Start of 'ora.diskmon' on 'ucstst11' succeeded
CRS-4404: The following nodes did not reply within the allotted time:
ucstst11
[root@ucstst11 bin]# ./crsctl check crs
CRS-4638: Oracle High Availability Services is online
CRS-4535: Cannot communicate with Cluster Ready Services
CRS-4530: Communications failure contacting Cluster Synchronization Services daemon
CRS-4533: Event Manager is online
[root@ucstst11 bin]# ./crsctl start crs
CRS-4640: Oracle High Availability Services is already active
CRS-4000: Command Start failed, or completed with errors.
[root@ucstst11 bin]# oracleasm querydisk -p CRSVOL01
Disk "CRSVOL01" is a valid ASM disk
/dev/sdz1: LABEL="CRSVOL01" TYPE="oracleasm"
/dev/sdcj1: LABEL="CRSVOL01" TYPE="oracleasm"
[root@ucstst11 bin]# ll /dev/sdz1 /dev/sdcj1
brw-rw---- 1 oracle dba 69, 113 Mar 27 19:00 /dev/sdcj1
brw-rw---- 1 oracle dba 65, 145 Mar 27 19:00 /dev/sdz1
[root@ucstst11 bin]# oracleasm querydisk -d CRSVOL01
Disk "CRSVOL01" is a valid ASM disk on device [65, 145]
From the functional node:
[root@ucstst12 bin]# ./crsctl check cluster -all
ucstst12:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
Cluster verification now hangs when it tries to contact the other nodes.
Please help!

For the most part this issue has been resolved. The SA partially changed to jumbo frames (OS, but not the switch), we reverted all the jumbo frame changes and the system is back online, except for one node (the one which was working ironically) not being reported via "crsctl check cluster -all", and one instance not starting due to it not seeing an interconnect (weird).
We did attempt to fully implement jumbo frames but that did not work hence the reversion.

FRA´s datafile directory and tape backups

Hi again,
I have tried to find relevant information for my question, but instead of finding answers (again) which may or may not be helpful I hope someone can explain me.
We are running 10Gr2 databases with FRA´s enabled, currently backupping all using Oracle´s suggested backup to Disk devices.
Since we have copies of the datafiles in the FRA which takes up quite some (productional) storage space we are asked to stop the Disk backups, and backup things up to the tape device, which underwater is a TSM library.
How would this affect the occupance of the FRA? Will the datafile directory in the FRA be moved to the "tape" device if we implement (solely) tape backups; or is it only the backupsets and autobackups which would then be moved to tape?
I have tried several setups for which I wanted to set the datafile, backupset and autobackup directory out of the FRA, but I have not found a (working) way yet to set the datafile directory apart from it.
Advice or help are greatly appreciated.
Robin

Changing the backup location from FRA to an external device will only effect backups (backupsets or image copies of datafiles,controlfiles,spfile,archivelogs). Possible (but not mandatory) components of FRA are archivelogs,backup pieces,controlfiles,online logs,image copies and flashback logs.
For performance reasons it's better to continue using the FRA as first backup device. Extend your backup strategy by backing the FRA itself to tape in regular intervals.
'BACKUP RECOVERY AREA' backs up recovery files created in the current and all previous flash recovery area destinations. Recovery files are full and incremental backup sets, control file autobackups, archived logs, and datafile copies. Flashback logs, the current control file, and online redo logs are not backed up.
The backup must go to a tape device, so RMAN issues an error if no sbt channels are allocated or configured.
Or use
'BACKUP RECOVERY FILES'. It backs up all recovery files on disk, whether they are stored in the flash recovery area or another locations on disk. Recovery files include full and incremental backup sets, control file autobackups, archived logs, and datafile copies.
Werner

Backup file getting generated on FRA insted of format path

Hi,
I have below script to generate RMAN full backup on given path in FORMAT directory, still RMAN genarate one .bkp file on FRA.
We require to generate all backup files on given format path only.
below file was generated on FRA
o1_mf_nnndf_TAG20100804T043926_65l9t06h_.bkpBelow is the code for generating full backup.
backup database plus archivelog FORMAT '/export/home/nfs_bak/lims/backup/ndb/backup_%d_DB_%D%M%Y_%U_%s' delete all input;
resync catalog;
report schema;
list backup;
CROSSCHECK BACKUP;
CROSSCHECK BACKUPSET;
DELETE NOPROMPT EXPIRED BACKUP;
DELETE NOPROMPT OBSOLETE DEVICE TYPE DISK;
CROSSCHECK ARCHIVELOG ALL;
DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;Oracle : 11gR2
OS:Solaris

Output for old command:
RMAN> backup database plus archivelog FORMAT '/export/home/nfs_bak/lims/backup/ndb/backup_%d_DB_%D%M%Y_%U_%s' delete all input;
Starting backup at 05-AUG-10
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=194 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=225 device type=DISK
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=26 RECID=24 STAMP=726199910
channel ORA_DISK_1: starting piece 1 at 05-AUG-10
channel ORA_DISK_1: finished piece 1 at 05-AUG-10
piece handle=/export/home/nfs_bak/lims/backup/ndb/backup_NDB_DB_05082010_16lkhrj8_1_1_38 tag=TAG20100805T021152 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/export/home/nfs_bak/lims/backup/ndb/NDB/archivelog/2010_08_05/o1_mf_1_26_65nok6fb_.arc RECID=24 STAMP=726199910
Finished backup at 05-AUG-10
Starting backup at 05-AUG-10
using channel ORA_DISK_1
using channel ORA_DISK_2
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=+DATA/lims/ndb/system01.dbf
input datafile file number=00002 name=+DATA/lims/ndb/sysaux01.dbf
input datafile file number=00006 name=+DATA/lims/ndb/datafile/ndb_cellmap_idx_tbs_01.dbf
input datafile file number=00008 name=+DATA/lims/ndb/datafile/ndb_fingerprint_tbs_idx_01.dbf
input datafile file number=00010 name=+DATA/lims/ndb/datafile/ndb_sys_idx_tbs_01.dbf
channel ORA_DISK_1: starting piece 1 at 05-AUG-10
channel ORA_DISK_2: starting full datafile backup set
channel ORA_DISK_2: specifying datafile(s) in backup set
input datafile file number=00005 name=+DATA/lims/ndb/datafile/ndb_cellmap_tbs_01.dbf
input datafile file number=00007 name=+DATA/lims/ndb/datafile/ndb_fingerprint_tbs_01.dbf
input datafile file number=00009 name=+DATA/lims/ndb/datafile/ndb_sys_tbs_01.dbf
input datafile file number=00003 name=+DATA/lims/ndb/undotbs01.dbf
input datafile file number=00004 name=+DATA/lims/ndb/users01.dbf
channel ORA_DISK_2: starting piece 1 at 05-AUG-10
channel ORA_DISK_1: finished piece 1 at 05-AUG-10
piece handle=/export/home/nfs_bak/lims/backup/ndb/backup_NDB_DB_05082010_17lkhrj9_1_1_39 tag=TAG20100805T021153 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:06:46
channel ORA_DISK_2: finished piece 1 at 05-AUG-10
piece handle=/export/home/nfs_bak/lims/backup/ndb/NDB/backupset/2010_08_05/o1_mf_nnndf_TAG20100805T021153_65nokdyo_.bkp tag=TAG20100805T021153 comment=NONE
channel ORA_DISK_2: backup set complete, elapsed time: 00:06:56
Finished backup at 05-AUG-10
Starting backup at 05-AUG-10
current log archived
using channel ORA_DISK_1
using channel ORA_DISK_2
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=27 RECID=25 STAMP=726200330
channel ORA_DISK_1: starting piece 1 at 05-AUG-10
channel ORA_DISK_1: finished piece 1 at 05-AUG-10
piece handle=/export/home/nfs_bak/lims/backup/ndb/backup_NDB_DB_05082010_19lkhs0b_1_1_41 tag=TAG20100805T021851 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/export/home/nfs_bak/lims/backup/ndb/NDB/archivelog/2010_08_05/o1_mf_1_27_65noyb7m_.arc RECID=25 STAMP=726200330
Finished backup at 05-AUG-10
Starting Control File and SPFILE Autobackup at 05-AUG-10
piece handle=/export/home/nfs_bak/lims/backup/ndb/db11g_c-1074407344-20100805-01 comment=NONE
Finished Control File and SPFILE Autobackup at 05-AUG-10output for updated command:
RMAN> RUN
2> {
3> allocate channel channel1 device type disk format '/export/home/nfs_bak/lims/backup/ndb/backup_%d_DB_%D%M%Y_%U_%s';
4> backup database plus archivelog delete all input;
5> release channel channel1;
6> }
7> resync catalog;
8> report schema;
9> list backup;
10> crosscheck backup;
11> crosscheck backupset;
12> delete noprompt expired backup;
13> delete noprompt obsolete;
14> crosscheck archivelog all;
15> DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;
16>
starting full resync of recovery catalog
full resync complete
allocated channel: channel1
channel channel1: SID=98 device type=DISK
Starting backup at 05-AUG-10
current log archived
channel channel1: starting archived log backup set
channel channel1: specifying archived log(s) in backup set
input archived log thread=1 sequence=20 RECID=18 STAMP=726148869
input archived log thread=1 sequence=21 RECID=19 STAMP=726175480
input archived log thread=1 sequence=22 RECID=20 STAMP=726185922
input archived log thread=1 sequence=23 RECID=21 STAMP=726195156
input archived log thread=1 sequence=24 RECID=22 STAMP=726197409
channel channel1: starting piece 1 at 05-AUG-10
channel channel1: finished piece 1 at 05-AUG-10
piece handle=/export/home/nfs_bak/lims/backup/ndb/backup_NDB_DB_05082010_12lkhp52_1_1_34 tag=TAG20100805T013010 comment=NONE
channel channel1: backup set complete, elapsed time: 00:00:07
channel channel1: deleting archived log(s)
archived log file name=/export/home/nfs_bak/lims/backup/ndb/NDB/archivelog/2010_08_04/o1_mf_1_20_65m3p0rz_.arc RECID=18 STAMP=726148869
archived log file name=/export/home/nfs_bak/lims/backup/ndb/NDB/archivelog/2010_08_04/o1_mf_1_21_65mxonbz_.arc RECID=19 STAMP=726175480
archived log file name=/export/home/nfs_bak/lims/backup/ndb/NDB/archivelog/2010_08_04/o1_mf_1_22_65n7vtog_.arc RECID=20 STAMP=726185922
archived log file name=/export/home/nfs_bak/lims/backup/ndb/NDB/archivelog/2010_08_05/o1_mf_1_23_65njwhld_.arc RECID=21 STAMP=726195156
archived log file name=/export/home/nfs_bak/lims/backup/ndb/NDB/archivelog/2010_08_05/o1_mf_1_24_65nm31ko_.arc RECID=22 STAMP=726197409
Finished backup at 05-AUG-10
Starting backup at 05-AUG-10
channel channel1: starting full datafile backup set
channel channel1: specifying datafile(s) in backup set
input datafile file number=00005 name=+DATA/lims/ndb/datafile/ndb_cellmap_tbs_01.dbf
input datafile file number=00001 name=+DATA/lims/ndb/system01.dbf
input datafile file number=00002 name=+DATA/lims/ndb/sysaux01.dbf
input datafile file number=00007 name=+DATA/lims/ndb/datafile/ndb_fingerprint_tbs_01.dbf
input datafile file number=00006 name=+DATA/lims/ndb/datafile/ndb_cellmap_idx_tbs_01.dbf
input datafile file number=00008 name=+DATA/lims/ndb/datafile/ndb_fingerprint_tbs_idx_01.dbf
input datafile file number=00009 name=+DATA/lims/ndb/datafile/ndb_sys_tbs_01.dbf
input datafile file number=00003 name=+DATA/lims/ndb/undotbs01.dbf
input datafile file number=00010 name=+DATA/lims/ndb/datafile/ndb_sys_idx_tbs_01.dbf
input datafile file number=00004 name=+DATA/lims/ndb/users01.dbf
channel channel1: starting piece 1 at 05-AUG-10
channel channel1: finished piece 1 at 05-AUG-10
piece handle=/export/home/nfs_bak/lims/backup/ndb/backup_NDB_DB_05082010_13lkhp5a_1_1_35 tag=TAG20100805T013018 comment=NONE
channel channel1: backup set complete, elapsed time: 00:06:55
Finished backup at 05-AUG-10
Starting backup at 05-AUG-10
current log archived
channel channel1: starting archived log backup set
channel channel1: specifying archived log(s) in backup set
input archived log thread=1 sequence=25 RECID=23 STAMP=726197834
channel channel1: starting piece 1 at 05-AUG-10
channel channel1: finished piece 1 at 05-AUG-10
piece handle=/export/home/nfs_bak/lims/backup/ndb/backup_NDB_DB_05082010_14lkhpia_1_1_36 tag=TAG20100805T013714 comment=NONE
channel channel1: backup set complete, elapsed time: 00:00:01
channel channel1: deleting archived log(s)
archived log file name=/export/home/nfs_bak/lims/backup/ndb/NDB/archivelog/2010_08_05/o1_mf_1_25_65nmj9y9_.arc RECID=23 STAMP=726197834
Finished backup at 05-AUG-10
Starting Control File and SPFILE Autobackup at 05-AUG-10
piece handle=/export/home/nfs_bak/lims/backup/ndb/db11g_c-1074407344-20100805-00 comment=NONE
Finished Control File and SPFILE Autobackup at 05-AUG-10
released channel: channel1

Restore FRA from tape backup

I have got a 2 node RAC cluster.
I am running RMAN backup connecting to one of the nodes and then running RMAN backups to FRA.
Since I cannot backup ASM to tapes just like a normal file system, I have configured the MML to backup the FRA to tapes using "backup recovery area" command.
The FRA backup to tapes is successful.
Now if ever I need to restore / recover the database, how do I restore my backups from tape.
ie: I dont see a command to say -> restore recovery area , which will restore the backups to FRA.Or is there a way ?
If it cannot restore , then what is the point of backing up the FRA to tapes using the above command.
Any thoughts ?
AU

Just try to restore database/tablespace/datafile using usual RMAN commands: RMAN will check if FRA is used and check if related backup is on disk or on tape. If backup is on tape, RMAN will read it using Media Manager Layer (MML) in a transparent way.

ORA-19612: datafile 0 not restored due to missing data

Hello,
I'm testing a restore of the controlfile. The database is in archivelog mode and autobackup is set to ON. I successfully did a full backup and backup as copy database.
To test I did the following:
- note the DBID
- shutdown the database
- renamed both controlfiles:
$ mv /u02/rcat/control01.ctl /u02/rcat/control01.ctl_old
$ mv /u02/fra/rcat/control02.ctl /u02/fra/rcat/control02.ctl_old
When I try to restore the controlfile form autobackup I receive the following error. What could be reason please?
[rcat@oel54]$ rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Dec 10 00:07:41 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: RCAT (not mounted)
RMAN> set dbid 502889862;
executing command: SET DBID
RMAN> restore controlfile from autobackup;
Starting restore at 10-DEC-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=19 device type=DISK
recovery area destination: /u02/fra
database name (or database unique name) used for search: RCAT
channel ORA_DISK_1: AUTOBACKUP /u02/fra/RCAT/autobackup/2010_12_09/o1_mf_s_737336682_6j2pyv2l_.bkp found in the recovery area
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20101210
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20101209
channel ORA_DISK_1: restoring control file from AUTOBACKUP /u02/fra/RCAT/autobackup/2010_12_09/o1_mf_s_737336682_6j2pyv2l_.bkp
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 12/10/2010 00:09:55
ORA-19870: error while restoring backup piece /u02/fra/RCAT/autobackup/2010_12_09/o1_mf_s_737336682_6j2pyv2l_.bkp
ORA-19612: datafile 0 not restored due to missing data
$ ll /u02/fra/RCAT/autobackup/2010_12_09/o1_mf_s_737336682_6j2pyv2l_.bkp
-rw-r----- 1 oracle dba 10354688 Dec 9 23:44 /u02/fra/RCAT/autobackup/2010_12_09/o1_mf_s_737336682_6j2pyv2l_.bkpThanks!

The file was indeed corrupted as below will show.
Very strange. Perhaps something with the latest Virtualbox or the SSD/hybrid harddrive. (host MacOSX 10.6, guest Oracle Linux 5.5 UEK)
$ mv /u02/rcat/control01.ctl_old /u02/rcat/control01.ctl
$ mv /u02/fra/rcat/control02.ctl_old /u02/fra/rcat/control02.ctl
SQL> startup mount
ORACLE instance started.
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-00264: no recovery required
SQL> alter database open;
Database altered.
$ rman target /
connected to target database: RCAT (DBID=502889862)
RMAN> backup current controlfile;
piece handle=/u02/fra/RCAT/backupset/2010_12_10/o1_mf_ncnnf_TAG20101210T012420_6j2wsoko_.bkp
Finished backup at 10-DEC-10
Starting Control File and SPFILE Autobackup at 10-DEC-10
piece handle=/u02/fra/RCAT/autobackup/2010_12_10/o1_mf_s_737342662_6j2wspvf_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 10-DEC-10
RMAN> restore validate controlfile;
piece handle=/u02/fra/RCAT/autobackup/2010_12_10/o1_mf_s_737342662_6j2wspvf_.bkp tag=TAG20101210T012422
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: validation complete, elapsed time: 00:00:02
Finished restore at 10-DEC-10
SQL> shutdown immediate
$ mv /u02/rcat/control01.ctl /u02/rcat/control01.ctl_old
$ mv /u02/fra/rcat/control02.ctl /u02/fra/rcat/control02.ctl_old
SQL> startup nomount
$ rman target /
connected to target database: RCAT (not mounted)
RMAN> set dbid 502889862;
RMAN> restore controlfile from autobackup;
Starting restore at 10-DEC-10
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=19 device type=DISK
recovery area destination: /u02/fra
database name (or database unique name) used for search: RCAT
channel ORA_DISK_1: AUTOBACKUP /u02/fra/RCAT/autobackup/2010_12_10/o1_mf_s_737342662_6j2wspvf_.bkp found in the recovery area
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20101210
channel ORA_DISK_1: restoring control file from AUTOBACKUP /u02/fra/RCAT/autobackup/2010_12_10/o1_mf_s_737342662_6j2wspvf_.bkp
channel ORA_DISK_1: control file restore from AUTOBACKUP complete
output file name=/u02/rcat/control01.ctl
output file name=/u02/fra/rcat/control02.ctl
Finished restore at 10-DEC-10

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

Best practice: managing FRA

I was not sure this was the most appropriate forum for this question; if not, please feel free to make an alternative suggestion.
For those of us who run multiple databases on a box with shared disk for FRA, I am finding the extra layer of ASM and db_recovery_file_dest_size to be a minor inconvenience. The Best Practice white papers I have found so far say that you should use db_recovery_file_dest_size, but they do not specify how you should set it. Currently, we have been setting db_recovery_file_dest_size rather small, as the databases so far are small and even at 3x the database size, the parameter is still significantly smaller than the total disk available in that diskgroup.
So, my question; is there any downside to setting db_recovery_file_dest_size equal to the total size of the FRA diskgroup for all databases? Obviously, this means that the amount of free space in the diskgroup may be consumed even if db_recovery_file_dest_size is not yet full (as reflected in the instance V$RECOVERY_FILE_DEST). But is that really a big deal at all? Can we not simply monitor the FRA diskgroup, which we have to do anyway? This eliminates the need to worry about an additional level of disk management. I like to keep things simple.
The question is relevant to folks using other forms of volume management (yes, I know, ASM is "not a volume manager"), but seems germane to the ASM forum because most articles and DBAs that I have talked to are using ASM for FRA.
Most importantly, what ramifications does "over-sizing" db_recovery_file_dest_size have? Aside from the scenario above.
TIA

As a general rule, the larger the flash recovery area(db_recovery_file_dest_size ), the more useful it becomes. Ideally, the flash recovery area should be large enough to hold a copy of all of your datafiles and control files, the online redo logs, and the archived redo log files needed to recover your database using the datafile backups kept under your retention policy.
Setting the size of DB_FILE_RECOVERY_DEST_SIZE must be based on following factors.
1) your falshback retention target,
2) what all files you are storing in flashback and
3) if that inclueds backup then the retention policy for them or how often you move them to tape
The bigger the flash recovery area, the more useful it becomes. Setting it much larger or equal to you FRA disk group does not cause any [b]overhead that is not known to Oracle.
But there are reasons why Oracle lets you define a disk limit, which is the amount of space that Oracle can use in the flash recovery area out of your FRA disk group.
1) A disk limit lets you use the remaining disk space for other purposes and not to dedicate a complete disk for the flash recovery area.
2)Oracle does not delete eligible files from the Flash Recovery Area until the
space must be reclaimed for some other purpose. So even though your database size is 5GB your restention target is very small but if your recovery_dest_size is much larger it will just keep filling.
3)Say in my case I have one FRA disk group of 150GB shared by 3 different databases. Based on the nature and criticaly of the database I have different size requirement of flashback recovery area for these databases. So I use varrying db_file_recovery dest_size (30GB, 50GB,70GB) respectively for meeting my retention target or the kind of files and backup I want to store them in FRA for these databases.
Oracle Internal Space management mehcanism for Falshback recovery area itself is designed in such way that if you define your db_recovery_file_dest_size and DB_FLASHBACK_RETENTION_TARGET at a optimal value, you wont need any further administration or management. If a Flash Recovery Area is configured, then the database uses an internal algorithm to delete files from the Flash Recovery Area that are no longer needed because they are redundant, orphaned, and so forth. The backups with status OBSOLETE form a subset of the files deemed eligible for deletion by the disk quota rules. When space is required in the Flash Recovery Area, then the following files are deleted:
a) Any backups which have become obsolete as per the retention policy.
b) Any files in the Flash Recovery Area which has been already backed up
to a tertiary device such as tape.
c) Flashback logs may be deleted from the Flash Recovery Area to make space available for other required files.
NOTE: If your FRA is 100GB and 3 databases have thier DB_RECOVERY_FILE_DEST set FRA then logically the total of db_recovery_file_dest_size for these 3 databases should not exceed 100GB. Even though practically it allows you to cross this limit.
Hope this helps.

RAC instance, trying to recover UNDO datafile, RMAN gives RMAN-06054

Hello all,
This has been a troublesome instance..a quick bit of background. This was created awhile back by someone else, I inherited this 3 mode RAC clusterof instance1.
I'm exporting out of one database (10G) into this instance1 (11G). When I was about to start the import..I found this instance wouldn't start. Turned out no backup had been going on of this empty instance. I backed up the archive logs to tape to free up the FRA..and things fired up.
I began the import, and found a bunch of errors...basically tellling me that I couldn't access one of the undo tablespaces...datafile problems.
I went to look and saw:
SQL> select a.file_name, a.file_id, b.status, a.tablespace_name
     2 from dba_data_files a, v$datafile b
     3 where a.file_id = b.file#
     4 order by a.file_name;
     FILE_NAME FILE_ID STATUS TABLESPACE_NAME
     +DATADG/instance1/datafile/sysaux.270.696702269              2 ONLINE                SYSAUX
     +DATADG/instance1/datafile/system.263.696702253              1 SYSTEM                SYSTEM
     +DATADG/instance1/datafile/undotbs1.257.696702279            3 ONLINE                UNDOTBS1
     +DATADG/instance1/datafile/undotbs2.266.696702305            4 ONLINE                UNDOTBS2
     +DATADG/instance1/datafile/undotbs3.269.696702313            5 RECOVER               UNDOTBS3
     +DATADG/instance1/datafile/users.268.696702321               6 ONLINE                USERS
     +DATADG/instance1/l_data_01_01                              11 ONLINE                L_DATA_01
     +DATADG/instance1/s_data_01_01                               7 ONLINE                S_DATA_01
     +DATADG/instance1/s_data_01_02                               8 ONLINE                S_DATA_01
     +INDEXDG/instance1/l_index_01_01                            12 ONLINE                L_INDEX_01
     +INDEXDG/instance1/s_index_01_01                             9 ONLINE                S_INDEX_01
     FILE_NAME FILE_ID STATUS TABLESPACE_NAME
     +INDEXDG/instance1/s_index_01_02                            10 ONLINE                S_INDEX_01
There is is, file #5.
So, I went into RMAN to try to restore/recover:
RMAN> restore datafile 5;
Starting restore at 06-APR-10
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=222 instance=instance1 device type=SBT_TAPE
channel ORA_SBT_TAPE_1: NMO v4.5.0.0
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=222 instance=instance1 device type=DISK
creating datafile file number=5 name=+DATADG/instance1/datafile/undotbs3.269.696702313
restore not done; all files read only, offline, or already restored
Finished restore at 06-APR-10
RMAN> recover datafile 5;
Starting recover at 06-APR-10
using channel ORA_SBT_TAPE_1
using channel ORA_DISK_1
starting media recovery
RMAN-06560: WARNING: backup set with key 343546 will be read 2 times
available space of 8315779 kb needed to avoid reading the backup set multiple times
unable to find archived log
archived log thread=1 sequence=1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/06/2010 14:33:07
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1 and starting SCN of 16016
This is all on ASM, and am a bit of a newb with that. I bascially have no data I'm worried about losing, I just need to get everything 'on the air' so I can import successfully, and let users on this instance. I've set up the backups in GRID now....so, it will be backed up on the future, but what is the quickest, most efficient way to get this UNDO tablespace datafile recovered?
Thank you,
cayenne

Hemant K Chitale wrote:
SET UNTIL SEQUENCE 27wouldn't work if the Recovery requires Sequence 1 and it is missing.
Hemant K ChitaleOops...meant to have start and set until both to "1"
However, I see what you mean. It seems I cannot find the file on tape.
Since the RAC instance hasn't yet had any data put into it, I'm thinking it might be best to just blow it away, and recreate everything.
Trouble is, I'm a bit new at RAC and ASM. I was thinking the best route might be to use DBCA to remove the database...? Would this not take care of removing all the datafiles from all the ASM instances on the RAC..as well as all the other directories, etc on all 3x nodes?
I've already used the dbca to create templates of this instance, so recreation shouldn't be too difficult (although it will be my first RAC creation)...
Thank you in advance for the advice so far,
cayenne

Duplicating a database using FRA

Hello,
I'm trying to duplicate a database using a backupset stored in FRA.
However, I thought rman would go take the most recently backupset that I'd backed up but isn't what's happening.
It's trying read backup piece from tape and this is what I don't want to.
How can I do to rman read backupset stored in FRA ?
Here a excerpt from script I'm using:
[oracle@oradell01 scripts]$ rman target / rcvcat rman10g_pd01@sf01 auxiliary sys@bpd01
Recovery Manager: Release 10.2.0.4.0 - Production on Seg Fev 8 09:41:41 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: PD01 (DBID=4238933412)
recovery catalog database Password:
connected to recovery catalog database
auxiliary database Password:
connected to auxiliary database: BPD01 (not mounted)
RMAN>
run {
allocate auxiliary channel c1 type sbt;
set newname for datafile 1 to '+DG1/bpd01/datafile/system.441.699983113';
set newname for datafile 2 to '+DG1/bpd01/datafile/undotbs1.442.699983125';
set newname for datafile 3 to '+DG1/bpd01/datafile/sysaux.443.699983133';
set newname for datafile 4 to '+DG1/bpd01/datafile/users.432.699983141';
set newname for datafile 5 to '+DG1/bpd01/datafile/drsys.430.699985041';
set newname for datafile 6 to '+DG1/bpd01/datafile/ifsdados.428.699985051';
set newname for datafile 7 to '+DG1/bpd01/datafile/ifsindex.429.699985179';
set newname for datafile 8 to '+DG1/bpd01/datafile/pergaindex.427.699985261';
set newname for datafile 9 to '+DG1/bpd01/datafile/pergamarc.426.699985397';
duplicate target database to bpd01
logfile
group 1 ('+DG1/bpd01/onlinelog/redo01a.log','+DG1/bpd01/onlinelog/redo01b.log') size 50m reuse,
group 2 ('+DG1/bpd01/onlinelog/redo02a.log','+DG1/bpd01/onlinelog/redo02b.log') size 50m reuse;
Thank you very much
Marcelo Sinni

It's trying read backup piece from tape and this is what I don't want to.That's because you allocate manually a tape channel inside the RUN block:
allocate auxiliary channel c1 type sbt;For Duplicate use the same settings you used for the backup to the FRA.
Werner

Files in FRA

Hi oracle's guru!
I need some advices and directions to learn.
I'm going to use FRA.
1. can i specific file formats for database backup files and control files? I run backup database plus archivelogs and there are 5 files with random names (rman generates itself). Can i add any tag for them?
2. Why i have 4 files instead 2? my database is not big enough. XE with default schemas.
regards,
rustam

Hi Jörg,
that depends on several settings. Thanks, i got it now.
For example: If you use filesperset 1 than only 1 file will be included in a backupset.If you have 4 tablespaces it will > create 4 backupsets. XE per default has system, sysaux, undo, users - 4 tablespaces. In addition if you open > channels then 4 backupsets are generated.I didnt change this value so i think default value is 3, coz created new tablespace and even add new datafiles and always got 3 backupsets. I read in oracle document that:
Specifies the maximum number of input files in each backup set. If you set FILESPERSET = n, then RMAN never includes more than n files in a backup set. The default for FILESPERSET is the lesser of these two values: 64, number of input files divided by the number of channels. For example, if you back up 100 datafiles by using two channels, RMAN sets FILESPERSET to 50.
RMAN always attempts to create enough backup sets so that all allocated channels have work to do. An exception to the rule occurs when there are more channels than files to back up. For example, if RMAN backs up two datafiles+ when three channels are allocated and FILESPERSET = 1, then one channel is necessarily idle.+
So i can manage the number of backupsets, right? How much should i have? many files with min sizes or some files with big size?
Hi Hemant K Chitale,
Ok, thanks a lot. I didnt know that i can create controlfile in FRA. What is the benefit of this strategy?
controlfile backups / autobackups would be in BACKUPPIECE.but in another folder and not with backupsets folder, right? coz my database backupsets are in ...\FRA\XE\BACKUPSET\ and backupset of controlfiles are in ...\FRA\XE\AUTOBACKUP\
regards and thanks,
rustam

Add datafile dataguard from physical RAC to standby RAC

Hello we have a 3 node cluster RAC 10g on the primary and RAC 10g on the standby.We use as db storage ASM wich is configured over raw devices and file management omf.The same groups DATA and FRA on both servers.STANDBY_FILE_MANAGEMENT is manual.
We need to add a datafile on the primary safely.Can you offer me some ideeas?
Thank you!

Hello;
Change STANDBY_FILE_MANAGEMENT to "auto" before you add the file and then leave it set to "auto". ( set this to AUTO on both Primary and Standby )
STANDBY_FILE_MANAGEMENT enables or disables automatic standby file management.
If you leave it set to MANUAL you may create unwanted file in $ORACLE_HOME/dbs and cause issues with the MRP process.
Best Regards
mseberg
Edited by: mseberg on Jun 7, 2013 9:02 AM

Datafiles in FRA... :)

Similar Messages

Maybe you are looking for