ASM or Regular File System?

I have read few threads regarding ASM/non-ASM file system. I am thinking ASM is easy to maintain when configured, but hard to maintain when move of database to non-ASM etc. can you suggest?
Thanks.

I dont think so.. The question of chosing ASM or not dosn't depend how hard or easy it is, the main thing to know id what is the actual requirement. If you use ASM then it means its raw devices managed by oracle and definitely in order to deal with the ASM files you have to through oracle interface (RMAN) and that disks cannot be seen from OS.
There are plenty of docs available online to move database from ASM to non-ASM and vice versa, if you are good in RMAN then it shouldn't be a problem plus how many time are you gonna move your database?
Daljit Singh

Similar Messages

  • ASM vs ext3 File system(mount point)

    Please suggest which one is better for small databases.
    ASM or ext3 File system(mount point)?
    Any metalink note.

    ASM better if you do not want to play with I/O tiuning, (if you tune ext3 file system it woud be the same from performace view),
    but it more compilcated for admininstering database files in ASM then in ordinary file system.
    Oracle is recomending to use ASM for database file system.
    I woud think if you have some development database and nead a lot of cloning, moving of datafiles its better to use ordinary file system,
    so you can use copy OS comands, not so complicated.
    If you nead some striping, miroring, snapshoting from ext3 you can use LVM on unix/linux.
    I am not sure but I think what striping or miroring is better on ASM then on LVM, becouse ASM is doing it better for databse I/O.

  • ASM and ext. file system

    Hi,
    Can I use ASM for one ERP database instance and other for normal .ext file system?
    if yes, what impact would be on system?
    Thanks

    Can I use ASM for one ERP database instance and other for normal .ext file system?Please elaborate more on what you are trying to achieve.
    What is the application release? Database version? OS?
    RAC: Frequently Asked Questions [ID 220970.1] -- What storage option should I use for Oracle RAC on Linux? ASM / OCFS / Raw Devices / Block Devices / Ext3 ?
    RAC Assurance Support Team: RAC Starter Kit and Best Practices (Linux) [ID 811306.1]
    Thanks,
    Hussein

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

  • DNFS with ASM over dNFS with file system - advantages and disadvantages.

    Hello Experts,
    We are creating a 2-node RAC. There will be 3-4 DBs whose instances will be across these nodes.
    For storage we have 2 options - dNFS with ASM and dNFS without ASM.
    The advantages of ASM are well known --
    1. Easier administration for DBA, as using this 'layer', we know the storage very well.
    2. automatic re-balancing and dynamic reconfiguration.
    3. Stripping and mirroring (though we are not using this option in our env, external redundancy is provided at storage level).
    4. Less (or no) dependency on storage admin for DB file related tasks.
    5. Oracle also recommends to use ASM rather than file system storage.
    Advantages of DNFS(Direct Network File System) ---
    1. Oracle bypasses the OS layer, directly connects to storage.
    2. Better performance as user's data need not to be loaded in OS's kernel.
    3. It load balances across multiple network interfaces in a similar fashion to how ASM operates in SAN environments.
    Now if we combine these 2 options , how will be that configuration in terms of administration/manageability/performance/downtime in future in case of migration.
    I have collected some points.
    In favor of 'NOT' HAVING ASM--
    1. ASM is an extra layer on top of storage so if using dNFS ,this layer should be removed as there are no performance benefits.
    2. store the data in file system rather than ASM.
    3. Stripping will be provided  at storage level (not very much sure about this).
    4. External redundancy is being used at storage level so its better to remove ASM.
    points for 'HAVING' ASM with dNFS --
    1. If we remove ASM then DBA has no or very less control over storage. He can't even see how much is the free space left as physical level.
    2. Stripping option is there to gain performance benefits
    3. Multiplexing has benefits over mirroring when it comes to recovery.
    (e.g, suppose a database is created with only 1 controlfile as external mirroring is in place at storage level , and another database is created with 2 copies (multiplexed within Oracle level), and an rm command was issued to remove that file then definitely there will be a time difference between restoring the file back.)
    4. Now familiar and comfortable with ASM.
    I have checked MOS also but could not come to any conclusion, Oracle says --
    "Please also note that ASM is not required for using Direct NFS and NAS. ASM can be used if customers feel that ASM functionality is a value-add in their environment. " ------How to configure ASM on top of dNFS disks in 11gR2 (Doc ID 1570073.1)
    Kindly advise which one I should go with. I would love to go with ASM but If this turned out to be a wrong design in future, I want to make sure it is corrected in the first place itself.
    Regards,
    Hemant

    I agree, having ASM on NFS is going to give little benefit whilst adding complexity.  NAS will carrying out mirroring and stripping through hardware where as ASM using software.
    I would recommend DNFS only if NFS performance isn't acceptable as DNFS introduce an additional layer with potential bugs!  When I first used DNFS in 11gR1, I came across lots of bugs and worked with Oracle Support to have them all resolved.  I recommend having read of this metalink note:
    Required Diagnostic for Direct NFS Issues and Recommended Patches for 11.1.0.7 Version (Doc ID 840059.1)
    Most of the fixes have been rolled into 11gR2 and I'm not sure what the state of play is on 12c.
    Hope this helps
    ZedDBA

  • How to convert from ASM to regular filesystem

    Hi All,
    On our RHEL 5.5 machine we have one disk partition managed by ASM (11.2.0.1.0). We wan't to convert it to regular file system. How can we do it?
    Regards,
    Vinod

    Open a Terminal window and paste the following:
    # su - oracle
    $ . oraenv
    ORACLE_SID = [oracle] ? +ASM
    The Oracle base has been set to /u01/app/oracle
    $ kfod disks=all
    Disk          Size Path                                     User     Group 
    ================================================================================
       1:       9214 Mb ORCL:ASMDISK1                            <unknown> <unknown>
       2:       9214 Mb ORCL:ASMDISK2                            <unknown> <unknown>
    ORACLE_SID ORACLE_HOME                                                        
    ================================================================================
          +ASM /u01/app/oracle/product/11.2.0/grid 
    The above will either show you the device, e.g. /dev/..., or the diskname (ORCL) in case you use ASMLib
    $ su - root
    # /etc/init.d/oracleasm querydisk -p ASMDISK1
    Disk "ASMDISK1" is a valid ASM disk
    /dev/sde1: LABEL="ASMDISK1" TYPE="oracleasm"
    # /etc/init.d/oracleasm querydisk -p ASMDISK2
    Disk "ASMDISK2" is a valid ASM disk
    /dev/sdf1: LABEL="ASMDISK2" TYPE="oracleasm"
    U sing the info from the previous output, the following will permanently remove devices from ASM and create a file system (ext4) that you can mount. When using fdisk or parted, be sure to use the device name, e.g. /dev/sde and not the partition (/dev/sde1).
    # parted -s /dev/sde mklabel msdos mkpart primary 1 -- -1
    # parted -s /dev/sdf mklabel msdos mkpart primary 1 -- -1
    # mkfs.ext4 -L testdrive /dev/sde1
    # mkfs.ext4 -L testdrive /dev/sdf1
    You can then mount the file systems, for example:
    # mkdir -p /u02
    # mount /dev/sde1 /u02
    All previous information on the devices will be lost.

  • RAC - Clusterd file system

    Hi All,
    This is very basic question but if you can shed some light. I have understanding that Clustered file system gives the ability to read and write same time for a file from multinodes. Is that true ? Can you pls. explain with an example ?
    Please confirm if my understanding is correct -
    For ( database related files and VOTING Disk and OCR )
    Either we can use raw devices
    Either we can use CFS ( any other or oracle given CFS )
    ASM only for database files any of the above option for VOTING,OCR ..
    Now back to orignal question - If we really need cluster file system so that both the nodes can access database files same time then how can ASM has this capability .. Is ASM another clustered file system ?
    your response would be appreciated.
    Thanks
    Lyxx

    coming to original questions: Basic concept for allowing concurrent read/write on a file is to allow the operations on block wise locking mechanism, while usual file systems takes file lock for read write. so in cluster file system two nodes can modify two different blocks (not the same).
    ASM implements the same through its own locking mechanism, using lock manger processes and CRS architecture.
    And its absolutely true that only one ASM instance will suffice for multiple DB but we can create multiple instances if needed (probably for better grouping/isolation of storage)
    Experts please correct me if I am missing out on anything.
    Thanks
    Rajesh

  • 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 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

  • ASM RMAN backup to File System

    Hi all,
    I have a rman backup (datafile and controlfile) which was took in an ASM instance (not a RAC) ORACLE 11.2.0.2 in a Linux server, now I want restore the backup in a new database in windows/Linux OS using general File System storage (single instance rdbms) instead of ASM.
    Is this possible?
    Can I restrore an ASM rman backup in a file system storage mechanisim in a new server?
    Kindly clarify my question.
    Thanks in Advance..
    Nonuday

    Nonuday wrote:
    Hi Levi,
    Thanks for your invaluable script and blog.
    can you clarify me on this query:
    I have a RMAN backup taken from ASM and the backup is database and controlf file backup which contains datafiles and controlfiles.
    Now I need to restore this on my system and here I dont use ASM or archive log, I use single instance in no archive log mode database.
    I have restored the control file from the RMAN controfile backup.
    Before restoring the control file I have checked the orginal pfile of the backup database which had parameters like
    'db_create_file_dest',
    'db_create_online_log_dest',
    'db_recovery_file_dest_size',
    'db_recovery_dest',
    'log_archive_dest'.
    Since I am not gng to create a DB in no archive log mode, I didnt use any of the above parameters and created a database.
    Now my question is:
    If i restore the database and the datafile will get restored and after renaming all the logfiles, database will be opened.
    I want to know whether this method is correct or wrong and will the database work as it was working previously. Or do i need create the db_file_recovery and other parameters also for this database.About Parameter:
    All these parameters should reflect your current environment any reference to the old environment must be modified.
    About Filesystem used:
    Does not matter what Filesystem you are using the File (datafile/redolog/controlfile/archivelog/backuppiece) are created on Binary Format which depend on Platform only. So, The same binary file ( e.g datafile) have same format and content on raw device, ASM, ext3, ext2, and so on. So, to database it's only a location where file are stored, but the file are the same. ASM has a different architecture from Regular Filesystem and need be managed in a different manner (i.e using RMAN).
    About Database:
    Since your database files are the same even using different filesystem what you need is rename your datafiles/redofiles on controlfile during restore, the redo files will be recreated.
    So, does not matter if you database are noarchivelog or archivelog, the same way which you will do a restore on ASM is the same way to restore on Regular Filesystem. (it's only about renaming database file on controlfile during restore)
    On blog the post "How Migrate All Files on ASM to Non-ASM (Unix/Linux)" is about move the file from filesystem to another. But you can modify the script used to restore purposes;
    ## set newname tell to RMAN where file will be restored and keep this files location on memory buffer
    RMAN> set newname for datafile 1 to <location>;
    ### swich get list of files from memory buffer (rman) and rename on controlfile the files already restored.
    RMAN>switch datafile/tempfile all ;With database mounted use this script below:
    I just commented three lines that are unnecessary in your case.
    SET serveroutput ON;
    DECLARE
      vcount  NUMBER:=0;
      vfname VARCHAR2(1024);
      CURSOR df
      IS
        SELECT file#,
          rtrim(REPLACE(name,'+DG_DATA/drop/datafile/','/u01/app/oracle/oradata/drop/'),'.0123456789') AS name
        FROM v$datafile;
      CURSOR tp
      IS
        SELECT file#,
          rtrim(REPLACE(name,'+DG_DATA/drop/tempfile/','/u01/app/oracle/oradata/drop/'),'.0123456789') AS name
        FROM v$tempfile;
    BEGIN
    --  dbms_output.put_line('CONFIGURE CONTROLFILE AUTOBACKUP ON;'); ### commented
      FOR dfrec IN df
      LOOP
        IF dfrec.name  != vfname THEN
          vcount      :=1;
          vfname     := dfrec.name;
        ELSE
          vcount := vcount+1;
          vfname:= dfrec.name;
        END IF;
      --  dbms_output.put_line('backup as copy datafile ' || dfrec.file# ||' format  "'||dfrec.name ||vcount||'.dbf";');  ### commented
      END LOOP;
      dbms_output.put_line('run');
      dbms_output.put_line('{');
      FOR dfrec IN df
      LOOP
        IF dfrec.name  != vfname THEN
          vcount      :=1;
          vfname     := dfrec.name;
        ELSE
          vcount := vcount+1;
          vfname:= dfrec.name;
        END IF;
        dbms_output.put_line('set newname for datafile ' || dfrec.file# ||'  to  '''||dfrec.name ||vcount||'.dbf'' ;');
      END LOOP;
      FOR tprec IN tp
      LOOP
        IF tprec.name  !=  vfname THEN
          vcount      :=1;
          vfname     := tprec.name;
        ELSE
          vcount := vcount+1;
          vfname:= tprec.name;
        END IF;
        dbms_output.put_line('set newname for tempfile ' || tprec.file# ||'  to  '''||tprec.name ||vcount||'.dbf'' ;');
        END LOOP;
          dbms_output.put_line('restore database;');
        dbms_output.put_line('switch tempfile all;');
        dbms_output.put_line('switch datafile all;');
        dbms_output.put_line('recover database;');
        dbms_output.put_line('}');
    ---   dbms_output.put_line('alter database open;');  ### comented because you need rename your redologs on controlfile before open database
        dbms_output.put_line('exit');
    END;
    /After restore you must rename your redologs on controlfile from old location to new location:
    e.g
    ##  use this query to get current location of redolog
    SQL>  select group#,member from v$logfile order by 1;
    ## and change from <old_location> to <new_location>
    SQL > ALTER DATABASE
      RENAME FILE '+DG_TSM_DATA/tsm/onlinelog/group_3.263.720532229' 
               TO  '/u01/app/oracle/oradata/logs/log3a.rdo'  When you change all redolog on controlfile issue command below:
    SQL> alter database open resetlogs;PS: Always track database in real time using alert log file of database.
    HTH,
    Levi Pereira

  • 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

  • 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

  • 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

Maybe you are looking for