Asm vs Fil system

Hi all
i saw this has been discussed here already,
well I think I will try and go for the Asm,
the machine is linux OS red hat.
my question is:
does asm uses async io ? - or do I need to use file system in order to use async io?
do I need on 10g to relink oracle to get async io as was in 9i ?
Thanks
Sahar

ASM uses asyncIO if your OS supports async (most do). ASM is far superior to filesystem with respect to manageability.
Use ASM !

Similar Messages

Asmca has grayed out Volumes and ASM Cluster File Systems 11.2.0.3

I've got a two node cluster which is up and running with the latest 11.2.0.3 grid install on Oracle Linux 6.3
I need to get a shared storage location I can use for File I/O testing, ASM looks like the solution with an ASM Cluster File System.
When I run asmca I do not have the ability to create these volumes or file systems as they are Grayed out.
I found some instructions on how to get it to work, and they said to use acfsload to start up the required daemons:
[root@oracleA bin]# ./acfsload start -s
ACFS-9459: ADVM/ACFS is not supported on this OS version: '2.6.39-300.17.3.el6uek.x86_64'
I installed Patches: 13146560, 14596051 - Which I thought would fix the problem. Rebooted after successfully applying the patches, but asmca still shows them greyed out
and not supported on this OS error persists.
I see some posts online saying to edit osds_acfslib.pm and update it to allow for the supported ORACLE version
Right now it shows: ($release =~ /^oraclelinux-release/))) # Oracle Linux
under /etc it only has oracle-release - could that have something to do with it not passing the check?
uname -r
2.6.39-300.17.3.el6uek.x86_64
From what I can tell this kernal should support asm..
Any help in getting these shared storage asm disks setup would be very helpful, oracleasm creates them and sees them fine for databases. Thanks.

Turns out the Kernel version 2.6.39 does not have support for the ASM Drivers for the ACFS mounting.
I'm going to have to use Oracle Linux 6.2 (instead of Oracle Linux 6.3) and rebuild my RAC to get a supported version of the drivers -> Kernel version 2.6.32
http://docs.oracle.com/cd/E11882_01/install.112/e16763/oraclerestart.htm#BGBGEDGA

Advantages of Oracle ASM Cluster File Systems (ACFS)

Hi
configured 11g Rel 2 Grid Infr , ASM instance and the database on linux x86_64 bit
when I started asmca, i noticed that there are no volumes configured
Need to know what are the advantages of configuring volumes,
[root@vmorarac2 init.d]# lsmod
Module Size Used by
oracleacfs 1613902 0
oracleadvm 220326 0
oracleoks 279693 2 oracleacfs,oracleadvm
oracleasm 48660 1
thanks

Need to know what are the advantages of configuring volumes,ACFS files system will available once you'll configure volume.
http://docs.oracle.com/cd/E11882_01/server.112/e18951/asmfs_util002.htm#CACGFHAA

ASM Vs File System - Who is best, Why and How ..

How the ASM is better than traditional file system ..? What is the reason behind oracle recommends ASM when we can achieve the same performance in traditional file system ...? Can some one throw some lights on this to understand the purpose of ASM in a better ways when comparing traditional file system.

ASM is better for two basic reasons.
Management and administration. It allows the DBA far better control, with features not found, when using a cooked file system. For example - you need to move the database from an old drive to a newly installed drive on the server. With ASM you can do this while the database is up, running and in-use.
Performance. ASM disks are block devices that are accessed using direct I/O. This bypasses a lot of moving parts that you will typically find in a cooked file system. Raw/direct disk I/O is faster than doing I/O via a kernel file system driver (that may or may not write that data to file on disk).
The con is that ASM is another s/w layer that needs to be installed, and which needs server resources to run. On the modern server, that is not a problem. It's not like running on a couple of sub Ghz CPUs with only 4Gb of system RAM. PCs today have more resources and faster resources than servers of a decade ago.
So there is not much reason for not using ASM.
I'm using ASM on all my database servers. From very small (dual core standalone) to large (12 node RAC). ASM has numerous times saved the proverbial day when there was storage issues, and required storage changes. I would need a lot of sound and hard convincing not to use ASM by default for an Oracle database in today's environment.

ASM Vs File system

1. With file system, we were able to set some threshold alerts at the OS mount point level. Is this possible with ASM since it is a raw device at the OS level?
2. The ASM directories are logical and is visible ONLY at the oracle ASM level. True?
3. Is cold backup an option with ASM?
4. Is RMAN the only solution with ASM disks?
5. Are there any suggested Hardware snap/clone available for ASM storage?
Thanks for your insight on this.

KR wrote:
1. With file system, we were able to set some threshold alerts at the OS mount point level. Is this possible with ASM since it is a raw device at the OS level?
2. The ASM directories are logical and is visible ONLY at the oracle ASM level. True?
3. Is cold backup an option with ASM?
4. Is RMAN the only solution with ASM disks?
5. Are there any suggested Hardware snap/clone available for ASM storage?1. Not possible from an OS point-of-view. See earlier reply for workaround;
2. Yep, or use asmcmd (from the ASM ORACLE_HOME) or ftp
3. If you use RMAN to cold-backup: yes. You cannot use a regular backup to back up your devices, unless you have designated files as 'disks' to ASM (But who would want that?). In this case you should shut down ASM and backup the file system where these files reside.
4. Yes, it is.
5. That depends on your hardware configuration. It is possible to run ASM on concurrent/shared, host based mirrored volume groups/volumes. If you use SAN technology, you can always verify whether these options are available from the storage manufacturer. However, I would be really careful with these, always taking things down before taking snapshots/flashcopies/clones/whatever you call them.
HTH.
Arnoud Roth

Why would anyone want to use ASM Clustered File system?

DB Version: 11gR2
OS : Solaris, AIX, HP-UX
I've read about the new feature ACFS.
http://www.oracle-base.com/articles/11g/ACFS_11gR2.php
But why would anyone want to store database binaries in a separate Filesystem created by Oracle?

Hi Vitamind,
how do these binaries interact with the CPU when they want something to be done?
ACFS should work with Local OS (Solaris) to communicate with the CPU . Isn't this kind of double work?ACFS dont work with .... but provide filesystem to Local S.O
There may be extra work, but that's because there are more resources that a common filesystem.
Oracle ACFS executes on operating system platforms as a native file system technology supporting native operating system file system application programming interfaces (APIs).
ACFS is a general purpose POSIX compliant cluster file system. Being POSIX compliant, all operating system utilities we use with ext3 and other file systems can also be used with Oracle ACFS given it belongs to the same family of related standards.
ACFS Driver Model
An Oracle ACFS file system is installed as a dynamically loadable vendor operating system (OS) file system driver and tool set that is developed for each supported operating system platform. The driver is implemented as a Virtual File System (VFS) and processes all file and directory operations directed to a specific file system.
It makes sense you use the ACFS if you use some of the features below:
• Oracle RAC / RAC ONE NODE
• Oracle ACFS Snapshots
• Oracle ASM Dynamic Volume Manager
• Cluster Filesystem for regular files
ACFS Use Cases
• Shared Oracle DB home
• Other “file system” data
• External tables, data loads, data extracts
• BFILES and other data customer chooses not to store in db
• Log files (consolidates access)
• Test environments
• Copy back a previous snapshot after testing
• Backups
• Snapshot file system for point-intime backups
• General purpose local or cluster file system
• Leverage ASM manageability
Note : Oracle ACFS file systems cannot be used for an Oracle base directory or an Oracle grid infrastructure home that contains the software for Oracle Clusterware, Oracle ASM, Oracle ACFS, and Oracle ADVM components.
Regards,
Levi Pereira

RMAN copies to ASM and file system

I am on 11g Rel 1 trying to do an RMAN backup with 2 copies of my backup. One copy should go to ASM storage and the other should go to a regular file system.
My RMAN script is:
run {
configure default device type to disk;
set backup copies 2;
configure device type disk parallelism 16 backup type to compressed backupset;
configure channel device type disk format = '+ASMDG2/backups/%d_%T_%U_dump0.bck, /orabackups/oracle/%d_%T_%U_dump0_offload.bck' MAXPIECESIZE 60G;
configure controlfile autobackup on;
backup incremental level=0 database plus archivelog;
delete noprompt obsolete redundancy 1;
exit;
When the backup runs I get:
RMAN-03009: failure of backup command ....etc.
ORA-15124: ASM file name '+ASMDG2/backups/%d_%T_%U_dump0.bck, /orabackups/oracle/%d_%T_%U_dump0_offload.bck' containd invalid alias name...
What is the correct syntax to get the copies to be able to go to ASM disk and regular disk locations?

OK, I see that in the documentation this time. I'll try that for tonights backup and let you know how it works. I'm a bit concerned still because it looks like it wrote fine to the +ASMDG2 location. I would have thought the whole backup would fail but I guess it was able to read the first path...

ASM and file system combination

Hi everyone -
OK, this may sound a bit crazy, but it's the situation I'm facing and I really need your help and opinion before I do something stupid.
I am using ASM on a SAN to manage my DATA tablespace (contains all the user data, including BLOBs). The ASM takes up all the disk space on the SAN except for what's left over from the disks allocated for the SAN OS. Basically, I have 941GB free space on the disks allocated the the SAN OS. Now, I need more space for my DATA tablespace, but can't afford to buy more disks at the moment (spent all my money on this SAN). I want to use the 941GB of unused disk space from the SAN OS disks for my DATA tablespace. But these disks are obviously not using ASM, and my current DATA tablespace is completely inside ASM.
So the 6 million dollar question is . . . Can I add a "filesystem" datafile to an existing ASM tablespace? For example:
Tablespace DATA is currently managed by ASM. Can I do
SQL> alter tablespace DATA add datafile '/ora1/oradata/orcl/DATA_FS_01.DBF' size 1024M;
So essentially I'll have part of the tablespace managed by ASM and another part residing on a traditional file system datafile.
What do you think? Is this possible? Advisable? The worst thing I could do? Ok to do?
Thanks in advance
a

OK, I see that in the documentation this time. I'll try that for tonights backup and let you know how it works. I'm a bit concerned still because it looks like it wrote fine to the +ASMDG2 location. I would have thought the whole backup would fail but I guess it was able to read the first path...

Which is better ASM or file system storage

Hi all, I need a urgent help from all u gr8 DBAs.
I have to give justification to my client that which is better to use between file based option ASM and why??
So can anyone give me some write up in this line?

Ok, how about this
Today's large databases demand minimal scheduled downtime, and DBAs are often required to manage multiple databases with an increasing number of database files. Automatic Storage Management lets you be more productive by making some manual storage management tasks obsolete.
The Oracle Database provides a simplified management interface for storage resources. Automatic Storage Management eliminates the need for manual I/O performance tuning. It simplifies storage to a set of disk groups and provides redundancy options to enable a high level of protection. Automatic Storage Management facilitates non-intrusive storage allocations and provides automatic rebalancing. It spreads database files across all available storage to optimize performance and resource utilization. It also saves time by automating manual storage tasks, which thereby increases their ability to manage more and larger databases with increased efficiency. Different versions of the database can interoperate with different versions of Automatic Storage Management. That is, any combination of release 10.1.x.y and 10.2.x.y for either the Automatic Storage Management instance or the database instance interoperate transparently.
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14220/mgmt_db.htm

ASM Cluster File System

Hi Xperts
I have a two nodes RAC and I need to create a Shared filesystem between the nodes, so I think in using ACFS, the problem is when I open ASMCA the ACFS tab is disable and I´m not able to start the ACFS driver. So I want to be sure that I won´t be able to use ACFS or if I am missing something.
I execute this:
[root@MPE66 bin]# ./acfsload start -s
ACFS-9459: ADVM/ACFS is not supported on this OS version: '2.6.39-300.26.1.el5uek'
[root@MPE66 bin]#
[root@MPE66 bin]# ./acfsdriverstate -orahome /u01/app/11.2.0.3/grid installed
ACFS-9204: false
[root@MPE66 bin]#
My configuration:
[root@ MPE66 bin]# cat /etc/*-release
Enterprise Linux Enterprise Linux Server release 5.9 (Carthage)
Oracle Linux Server release 5.9
Red Hat Enterprise Linux Server release 5.9 (Tikanga)
[root@ MPE66 bin]#
[root@ MPE66 bin]# uname -a
Linux MPE66.xxxxx.net 2.6.39-300.26.1.el5uek #1 SMP Thu Jan 3 18:31:38 PST 2013 x86_64 x86_64 x86_64 GNU/Linux
[root@ MPE66 bin]#
Grid and RDBMS= 11.2.0.3
Regards

Hi
I read the metalink Note but I still have the same problem:
[root@MPE66bin]#
[root@MPE66bin]# ./acfsroot install
ACFS-9459: ADVM/ACFS is not supported on this OS version: '2.6.39-300.26.1.el5uek'
[root@MPE66bin]# ./acfsroot enable
ACFS-9459: ADVM/ACFS is not supported on this OS version: '2.6.39-300.26.1.el5uek'
[root@MPE66bin]#
I think I am going to install and configure OCFS
Regards

How to converrt files on RAW devices in ASM to non ASM file system.

Hi all,
I have on problem .
Is that possible to migrate ASM raw files system to non ASM file .
If possible plzz describe them.
If not also please tell y not?
Thanks in addvance
Regards
Krishna

Hi,
I totally agree with Mahir. And I just want to share one thing:
Use %U to generate guaranteed unique names :
For backupsets, %U means: %u_%p_%c
For an image copy of a datafile, %U means: data-D-%d_id-%I_TS-%N_FNO-%f_%u
For an image copy of an archived redolog, %U means: arch-D_%d-id-%I_S-%e_T-%h_A-%a_%u
For an image copy of a control file, %U means: cf-D_%d-id-%I_%u
Thank you

Difference between ASM Disk Group, ADVM Volume and ACFS File system

Q1. What is the difference between an ASM Disk Group and an ADVM Volume ?
To my mind, an ASM Disk Group is effectively a logical volume for Database files ( including FRA files ).
11gR2 seems to have introduced the concepts of ADVM volumes and ACFS File Systems.
An 11gR2 ASM Disk Group can contain :
ASM Disks
ADVM volumes
ACFS file systems
Q2. ADVM volumes appear to be dynamic volumes.
However is this therefore not effectively layering a logical volume ( the ADVM volume ) beneath an ASM Disk Group ( conceptually a logical volume as well ) ?
Worse still if you have left ASM Disk Group Redundancy to the hardware RAID / SAN level ( as Oracle recommend ), you could effectively have 3 layers of logical disk ? ( ASM on top of ADVM on top of RAID/SAN ) ?
Q3. if it is 2 layers of logical disk ( i.e. ASM on top of ADVM ), what makes this better than 2 layers using a 3rd party volume manager ( eg ASM on top of 3rd party LVM ) - something Oracle encourages against ?
Q4. ACFS File systems, seem to be clustered file systems for non database files including ORACLE_HOMEs, application exe's etc ( but NOT GRID_HOME, OS root, OCR's or Voting disks )
Can you create / modify ACFS file systems using ASM.
The oracle toplogy diagram for ASM in the 11gR2 ASM Admin guide, shows ACFS as part of ASM. I am not sure from this if ACFS is part of ASM or ASM sits on top of ACFS ?
Q5. Connected to Q4. there seems to be a number of different ways, ACFS file systems can be created ? Which of the below are valid methods ?
through ASM ?
through native OS file system creation ?
through OEM ?
through acfsutil ?
my head is exploding
Any help and clarification greatly appreciated
Jim

Q1 - ADVM volume is a type of special file created in the ASM DG. Once created, it creates a block device on the OS itself that can be used just like any other block device. http://docs.oracle.com/cd/E16655_01/server.121/e17612/asmfilesystem.htm#OSTMG30000
Q2 - the asm disk group is a disk group, not really a logical volume. It combines attributes of both when used for database purposes, as the database and certain other applications know how to talk "ASM" protocol. However, you won't find any general purpose applications that can do so. In addition, some customers prefer to deal directly with file systems and volume devices, which ADVM is made to do. In your way of thinking, you could have 3 layers of logical disk, but each of them provides different attributes and characteristics. This is not a bad thing though, as each has a slightly different focus - os file system\device, database specific, and storage centric.
Q3 - ADVM is specifically developed to extend the characteristics of ASM for use by general OS applications. It understands the database performance characteristics and is tuned to work well in that situation. Because it is developed in house, it takes advantage of the ASM design model. Additionally, rather than having to contact multiple vendors for support, your support is limited to calling Oracle, a one-stop shop.
Q4 - You can create and modify ACFS file systems using command line tools and ASMCA. Creating and modifying logical volumes happens through SQL(ASM), asmcmd, and ASMCA. EM can also be used for both items. ACFS sits on top of ADVM, which is a file in an ASM disk group. ACFS is aware of the characteristics of ASM\ADVM volumes, and tunes it's IO to make best use of those characteristics.
Q5 - several ways:
1) Connect to ASM with SQL, use 'alter diskgroup add volume' as Mihael points out. This creates an ADVM volume. Then, format the volume using 'mkfs' (*nix) or acfsformat (windows).
2) Use ASMCA - A gui to create a volume and format a file system. Probably the easiest if your head is exploding.
3) Use 'asmcmd' to create a volume, and 'mkfs' to format the ACFS file system.
Here is information on ASMCA, with examples:
http://docs.oracle.com/cd/E16655_01/server.121/e17612/asmca_acfs.htm#OSTMG94348
Information on command line tools, with examples:
Basic Steps to Manage Oracle ACFS Systems

Unix shell: Environment variable works for file system but not for ASM path

We would like to switch from file system to ASM for data files of Oracle tablespaces. For the path of the data files, we have so far used environment variables, e.g.,
CREATE TABLESPACE BMA DATAFILE '${ORACLE_DB_DATA}/bma.dbf' SIZE 2M AUTOEXTEND ON;
This works just fine (from shell scripts, PL/SQL packages, etc.) if ORACLE_DB_DATA denotes a file system path, such as "/home/oracle", but doesn’t work if the environment variable denotes an ASM path like "\+DATA/rac/datafile". I assume that it has something to do with "+" being a special character in the shell. However, escaping "\+" didn’t work. I tried with both bash and ksh.
Oracle managed files (e.g., set DB_CREATE_FILE_DEST to +DATA/rac/datafile) would be an option. However, this would require changing quite a few scripts and programs. Therefore, I am looking for a solution with the environment variable. Any suggestions?
The example below is on a RAC Attack system (http://en.wikibooks.org/wiki/RAC_Attack_-OracleCluster_Database_at_Home). I get the same issues on Solaris/AIX/HP-UX on 11.2.0.3 also.
Thanks,
Martin
==== WORKS JUST FINE WITH ORACLE_DB_DATA DENOTING FILE SYSTEM PATH ====
collabn1:/home/oracle[RAC1]$ export ORACLE_DB_DATA=/home/oracle
collabn1:/home/oracle[RAC1]$ sqlplus "/ as sysdba"
SQL*Plus: Release 11.2.0.1.0 Production on Fri Aug 24 20:57:09 2012
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, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
SQL> CREATE TABLESPACE BMA DATAFILE '${ORACLE_DB_DATA}/bma.dbf' SIZE 2M AUTOEXTEND ON;
Tablespace created.
SQL> !ls -l ${ORACLE_DB_DATA}/bma.dbf
-rw-r----- 1 oracle asmadmin 2105344 Aug 24 20:57 /home/oracle/bma.dbf
SQL> drop tablespace bma including contents and datafiles;
==== DOESN’T WORK WITH ORACLE_DB_DATA DENOTING ASM PATH ====
collabn1:/home/oracle[RAC1]$ export ORACLE_DB_DATA="+DATA/rac/datafile"
collabn1:/home/oracle[RAC1]$ sqlplus "/ as sysdba"
SQL*Plus: Release 11.2.0.1.0 Production on Fri Aug 24 21:08:47 2012
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, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
SQL> CREATE TABLESPACE BMA DATAFILE '${ORACLE_DB_DATA}/bma.dbf' SIZE 2M AUTOEXTEND ON;
CREATE TABLESPACE BMA DATAFILE '${ORACLE_DB_DATA}/bma.dbf' SIZE 2M AUTOEXTEND ON
ERROR at line 1:
ORA-01119: error in creating database file '${ORACLE_DB_DATA}/bma.dbf'
ORA-27040: file create error, unable to create file
Linux Error: 2: No such file or directory
SQL> -- works if I substitute manually
SQL> CREATE TABLESPACE BMA DATAFILE '+DATA/rac/datafile/bma.dbf' SIZE 2M AUTOEXTEND ON;
Tablespace created.
SQL> drop tablespace bma including contents and datafiles;

My revised understanding is that it is not a shell issue with replacing +, but an Oracle problem. It appears that Oracle first checks whether the path starts with a "+" or not. If it does not (file system), it performs the normal environment variable resolution. If it does start with a "+" (ASM case), Oracle does not perform environment variable resolution. Escaping, such as "\+" instead of "+" doesn't work either.
To be more specific regarding my use case: I need the substitution to work from SQL*Plus scripts started with @script, PL/SQL packages with execute immediate, and optionally entered interactively in SQL*Plus.
Thanks,
Martin

DB_UNIQUE_NAME vs DB_NAME in standby databases of ASM file systems

Question : Do we need to have the db_unique_name paramter set differently in standby database compared to db_name in standby .
Problem we are facing :
Here is the little background
Primary Server     : SERVER1
db_name          : VENKAT
db_unique_name     : VENKAT
Standby server     : SERVER2
db_name          : VENKAT
db_unique_name     : VENKAT_stb
Sever          : Linux
Database Version: 11.20.3
File system type: ASM ( 11.2.0.3)
stanby type     : Physical
Disk group names: Identical on both primary and standby servers
Data          : +DATA_OP01027_128
FRA          : +FRA_VENKAT_128
How datafiles are layed out on primary server:
sample datafile name location : +DATA_VENKAT_128/VENKAT/datafile/venkat.277.789579565
How standby was build : using Active duplicte command
Once we have the standby database build we have the datafiles created under this location
Sample datafile name location on standby server : +DATA_VENKAT_128/VENKAT_stb/datafile/venkat.280.789579597
with this we have learnt that the directory VENKAT_stb is getting created in standby ASM off the db_unique_name that
was given in the database , we have not seen this issue in the normal file system even we are using db_unique_name different that
the db_name in standby database .
Can you please help us how we can prevent this situation of having datafiles getting created under differnt direction in standby compared to prod.
Can you also let us know what impacts we might be having if we don't specify the db_unique_name different than db_name in standby database.
Hope this explains the problem what we are facing currently .
What steps i follwed to fix this issues :
I have db_unique_name set to the same name as db_name and when i did the restore all datafiles are in the identical location to prod standby server .
Note : We do fully understand the need for having the db_unique_name set different to db_name in standby db in standby and primary db's are residing on the same physical server .
Thanks
Venkat

first of all, this is not an issue or problem
works as intended
Question : Do we need to have the db_unique_name paramter set differently in standby database compared to db_name in standby .yes
Sample datafile name location on standby server : +DATA_VENKAT_128/VENKAT_stb/datafile/venkat.280.789579597
with this we have learnt that the directory VENKAT_stb is getting created in standby ASM off the db_unique_name that
was given in the database , we have not seen this issue in the normal file system even we are using db_unique_name different that
the db_name in standby database .
Can you please help us how we can prevent this situation of having datafiles getting created under differnt direction in standby compared to prod.well, dont use OMF then
OMF format for datafiles in ASM is: +DISKGROUP/DB_UNIQUE_NAME/DATAFILE/TABLESPACE_NAME.FILE.INCARNATION
datafiles will be created this way no matter what you do
the difference is, that if you dont use OMF, there will be an alias created referencing the file, with the path you gave
for example:
OMF:
create tablespace test size 10M;
a datafile is created: +DATA_VENKAT_128/VENKAT/DATAFILE/test.280.789581212 (i wrote some random numbers here)
non-OMF:
create tablespace test datafile '+DATA_VENKAT_128/dummy/test01.dbf' size 10M;
what actually happens:
a datafile is created: +DATA_VENKAT_128/VENKAT/DATAFILE/test.280.789581212 (i wrote some random numbers here)
and an ASM alias is created: +DATA_VENKAT_128/dummy/test01.dbf
and this alias is used by the database
while OMF files have their specified path format, and their path (db_unique_name) and even name (numbers at the end) will change when duplicated, aliases dont necessarily do this
however this is just extra work and administration, OMF is your friend

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

Asm vs Fil system

Similar Messages

Maybe you are looking for