RAC_OCR and VD files in asm.

Hi All,
    From 11g r2 onwards we can keep OCR and voting disk files in ASM +DG in that case,
1. if ocr and VD files are in ASM DG then which process needs to start first ? how can we start asm dg first before cluster?
2. why we need to keet VD files in odd numbers ?
Please give me some link or way to understand this.
Thanks,

1. if ocr and VD files are in ASM DG then which process needs to start first ? how can we start asm dg first before cluster?
Oracle Clusterware does not rely on ASM to access the Voting Files because the voting disks are placed directly on ASMDISK (not in a Diskgroup).
Voting files not depend of Diskgroup (with state mounted) to be accessed, does not mean that we don’t need the diskgroup, diskgroup and voting file are linked by their settings.
CSSD identifies the vote disks based on the discovery string in the gpnp profile and at this point after the discovery of the vote disks has direct access to it.
Within the disk header of ASM disks with Voting files there is markers that define the starting AU (vfstart) and ending AU (vfend) for the voting disk.
On startup, CSSD will scan all ASM disks (using the ASM discovery string from the GPnP profile) for these markers once found, CSSD use them without any direct relationship to an ASM instance
2. why we need to keet VD files in odd numbers ?
You should configure odd number of voting disks because far as voting files are concerned, a node must be able to access more than the half of the voting files at any time (simple majority).
In order to be able to tolerate a failure of n voting files, one must have at least 2n+1 configured. (n= number of voting files) for the cluster.
If a node in cluster lost majority of disk heartbeat they must be kicked from cluster.
To ensure that will lost the majority (i.e greater than 50% of disks) you must have odd number, because you can't lost a half disk.
If you have a even number of disk you can't apply quorum concept and it is not acceptable in a cluster.

Similar Messages

  • How to create redlog and control file at ASM in linux RAC

    Hi Experts,
    I will to maintance a oracle 10g database at ASM as RAC iin linux red hat.
    i am a new person with some question.
    nornally speaking, oracle recommadition for oracle 10g database as
    create 3 copy fills for control file
    create at least 2 redo log with mirror files in system.
    However, I checked find
    redlog file is at FRA place +FLSdisk1 and no mirror
    control file is at FRA place--+FLSDISK1/
    datebase file at ‘+DATA1/
    There are no mirror for relog.
    Go to EM, I also could not find place to enter file name.
    We use ASM to hold database to support RAC.
    Do i need to create redlog file as
    ALTER DATABASE ADD LOGFILE GROUP 1 ('+FLSdisk1/sale/onlinelog/REDO01.LOG','+FLSdisk1/sale/onlinelog/REDO01_mirror.LOG') SIZE 1000M reuse;
    my boss told me that ASM is reliable.
    Do you need to creat more directory to arrange redlog and control files in ASM for RAC system?
    FRA is a good place to store control file and redlog file ?
    Thanks
    JIM
    Edited by: user589812 on Jul 3, 2009 3:03 PM

    ASM is reliable but a smart DBA is very careful. If ASM is doing mirroring this is like RAID doing mirroring. What happens if you accidentally delete one copy ... the other one disappears instantly. Not a good idea.
    With respect to redo logs you need a minimum of three groups, two members, and one thread per instance. So a 2 node cluster should, at a minimum have 12 physical files.
    Not mirroring the redo logs, assuming multiple members, is not as critical.

  • 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

  • How to create parameter and control file like filename + date

    Hello there
    I am trying to create parameter and control file with following command
    in SQLPLUS
    create pfile='/u03/oradata/WEBDB/backup/initWEBDB.ora' from spfile;
    In RMAN
    copy current controlfile to '/u03/oradata/WEBDB/backup/cf_longterm.cpy';
    how can I put date at the end of filename like
    initWEBDB8jan06.ora and cf_longterm8jan06.cpy
    Thanks in advance
    Lionel

    ASM is reliable but a smart DBA is very careful. If ASM is doing mirroring this is like RAID doing mirroring. What happens if you accidentally delete one copy ... the other one disappears instantly. Not a good idea.
    With respect to redo logs you need a minimum of three groups, two members, and one thread per instance. So a 2 node cluster should, at a minimum have 12 physical files.
    Not mirroring the redo logs, assuming multiple members, is not as critical.

  • OCR and voting disks on ASM, problems in case of fail-over instances

    Hi everybody
    in case at your site you :
    - have an 11.2 fail-over cluster using Grid Infrastructure (CRS, OCR, voting disks),
    where you have yourself created additional CRS resources to handle single-node db instances,
    their listener, their disks and so on (which are started only on one node at a time,
    can fail from that node and restart to another);
    - have put OCR and voting disks into an ASM diskgroup (as strongly suggested by Oracle);
    then you might have problems (as we had) because you might:
    - reach max number of diskgroups handled by an ASM instance (63 only, above which you get ORA-15068);
    - experiment delays (especially in case of multipath), find fake CRS resources, etc.
    whenever you dismount disks from one node and mount to another;
    So (if both conditions are true) you might be interested in this story,
    then please keep reading on for the boring details.
    One step backward (I'll try to keep it simple).
    Oracle Grid Infrastructure is mainly used by RAC db instances,
    which means that any db you create usually has one instance started on each node,
    and all instances access read / write the same disks from each node.
    So, ASM instance on each node will mount diskgroups in Shared Mode,
    because the same diskgroups are mounted also by other ASM instances on the other nodes.
    ASM instances have a spfile parameter CLUSTER_DATABASE=true (and this parameter implies
    that every diskgroup is mounted in Shared Mode, among other things).
    In this context, it is quite obvious that Oracle strongly recommends to put OCR and voting disks
    inside ASM: this (usually called CRS_DATA) will become diskgroup number 1
    and ASM instances will mount it before CRS starts.
    Then, additional diskgroup will be added by users, for DATA, REDO, FRA etc of each RAC db,
    and will be mounted later when a RAC db instance starts on the specific node.
    In case of fail-over cluster, where instances are not RAC type and there is
    only one instance running (on one of the nodes) at any time for each db, it is different.
    All diskgroups of db instances don't need to be mounted in Shared Mode,
    because they are used by one instance only at a time
    (on the contrary, they should be mounted in Exclusive Mode).
    Yet, if you follow Oracle advice and put OCR and voting inside ASM, then:
    - at installation OUI will start ASM instance on each node with CLUSTER_DATABASE=true;
    - the first diskgroup, which contains OCR and votings, will be mounted Shared Mode;
    - all other diskgroups, used by each db instance, will be mounted Shared Mode, too,
    even if you'll take care that they'll be mounted by one ASM instance at a time.
    At our site, for our three-nodes cluster, this fact has two consequences.
    One conseguence is that we hit ORA-15068 limit (max 63 diskgroups) earlier than expected:
    - none ot the instances on this cluster are Production (only Test, Dev, etc);
    - we planned to have usually 10 instances on each node, each of them with 3 diskgroups (DATA, REDO, FRA),
    so 30 diskgroups each node, for a total of 90 diskgroups (30 instances) on the cluster;
    - in case one node failed, surviving two should get resources of the failing node,
    in the worst case: one node with 60 diskgroups (20 instances), the other one with 30 diskgroups (10 instances)
    - in case two nodes failed, the only node survived should not be able to mount additional diskgroups
    (because of limit of max 63 diskgroup mounted by an ASM instance), so all other would remain unmounted
    and their db instances stopped (they are not Production instances);
    But it didn't worked, since ASM has parameter CLUSTER_DATABASE=true, so you cannot mount 90 diskgroups,
    you can mount 62 globally (once a diskgroup is mounted on one node, it is given a number between 2 and 63,
    and other diskgroups mounted on other nodes cannot reuse that number).
    So as a matter of fact we can mount only 21 diskgroups (about 7 instances) on each node.
    The second conseguence is that, every time our CRS handmade scripts dismount diskgroups
    from one node and mount it to another, there are delays in the range of seconds (especially with multipath).
    Also we found inside CRS log that, whenever we mounted diskgroups (on one node only), then
    behind the scenes were created on the fly additional fake resources
    of type ora*.dg, maybe to accomodate the fact that on other nodes those diskgroups were left unmounted
    (once again, instances are single-node here, and not RAC type).
    That's all.
    Did anyone go into similar problems?
    We opened a SR to Oracle asking about what options do we have here, and we are disappointed by their answer.
    Regards
    Oscar

    Hi Klaas-Jan
    - best practises require that also online redolog files are in a separate diskgroup, in case of ASM logical corruption (we are a little bit paranoid): in case DATA dg gets corrupted, you can restore Full backup plus Archived RedoLog plus Online Redolog (otherwise you will stop at the latest Archived).
    So we have 3 diskgroups for each db instance: DATA, REDO, FRA.
    - in case of fail-over cluster (active-passive), Oracle provide some templates of CRS scripts (in $CRS_HOME/crs/crs/public) that you edit and change at your will, also you might create additionale scripts in case of additional resources you might need (Oracle Agents, backups agent, file systems, monitoring tools, etc)
    About our problem, the only solution is to move OCR and voting disks from ASM and change pfile af all ASM instance (parameter CLUSTER_DATABASE from true to false ).
    Oracle aswers were a litlle bit odd:
    - first they told us to use Grid Standalone (without CRS, OCR, voting at all), but we told them that we needed a Fail-over solution
    - then they told us to use RAC Single Node, which actually has some better features, in csae of planned fail-over it might be able to migreate
    client sessions without causing a reconnect (for SELECTs only, not in case of a running transaction), but we already have a few fail-over cluster, we cannot change them all
    So we plan to move OCR and voting disks into block devices (we think that the other solution, which needs a Shared File System, will take longer).
    Thanks Marko for pointing us to OCFS2 pros / cons.
    We asked Oracle a confirmation that it supported, they said yes but it is discouraged (and also, doesn't work with OUI nor ASMCA).
    Anyway that's the simplest approach, this is a non-Prod cluster, we'll start here and if everthing is fine, after a while we'll do it also on Prod ones.
    - Note 605828.1, paragraph 5, Configuring non-raw multipath devices for Oracle Clusterware 11g (11.1.0, 11.2.0) on RHEL5/OL5
    - Note 428681.1: OCR / Vote disk Maintenance Operations: (ADD/REMOVE/REPLACE/MOVE)
    -"Grid Infrastructure Install on Linux", paragraph 3.1.6, Table 3-2
    Oscar

  • ORA-15017 and ORA-15013 on ASM start

    Grid Infrastructure 12.1.0.1
    Oracle Linux 6.5 
    Standalone -   NOT RAC
    I have two diskgroups:    ASM_DATA and ASM_FRA
    SYS@+ASM AS SYSDBA> show parameter diskgroup
    NAME_COL_PLUS_SHOW_PARAM            VALUE_COL_PLUS_SHOW_PARAM
    asm_diskgroups                                         ASM_FRA, ASM_DATA
    My spfile is in asm:
    asmcmd -p
    ls +asm_data/asm/asmparameterfile
    REGISTRY.253.840373079
    On reboot (we use Oracle Restart) or startup of ASM the alert log shows:
    WARNING: Disk Group ASM_DATA containing spfile for this instance is not mounted
    ORA-15032: not all alterations performed
    ORA-15017: diskgroup "ASM_FRA" cannot be mounted
    ORA-15013: diskgroup "ASM_FRA" is already mounted
    ORA-15017: diskgroup "ASM_DATA" cannot be mounted
    ORA-15013: diskgroup "ASM_DATA" is already mounted
    It's like ASM needs to spfile to startup and it's in ASM whose diskgroup is not yet mounted, so it can't find it.
    But then it does, but by that time something else already has it mounted.
    Is this perhaps a chicken-and-egg thing and I don't have something set right?  I've searched and searched but see nothing.
    A lot of documentation for GI which is where our ASM resides is for RAC, but we are standalone.  That shouldn't make a difference, but it does with the crs commands.
    Any insight is appreciated.
    Sherrie

    Hi,
    If you see those diskgroup resource ,they have startup_dependencies on ora.asm resource .
    It will wait for asm instance to be online within startup_timeout value and then mount those diskgroup.
    At startup ,it reads OLR file and get the spfile location of ASM in standalone .
    And starts up the system.
    Generally ,this does not take much time.
    But from the error it seems ,it is taking few more seconds .
    This depends upon the the OS level disk  response too ,as ASM opens all disks at the time of startup.
    you  can ignore these errors.
    Regards,
    Aritra

  • How to add other 2 control files at ASM in linux RAC

    Hi Experts,
    I am new for RAC .
    the vendor build a RAC for us. I found there are only one control file in system.
    we use oracle 10.2.0.4 at ASM with RAC in redhat linux 5.
    how to add 2 additional control file to ASM for RAC ?
    Please provide a procedur in detail.
    Thanks
    Jim

    Hi damorgan & Friends,
    I could not find some infomration to add control into ASM . I can do this job( see below procedure) in no ASM .
    My question, our database locates at ASM and control file with a system auto-number ( fully qualified filename ) as
    +DATA1/SALE/controlfile/current.256.690290159
    How do I physical copy and rename other 2 contril file in directory and modify location in pfile?
    I saw some paper to use request as an alias (such as +dgroup2/control/ctl.f). i can not image to copy/rename control.
    Please help me!!
    Thanks
    Jim
    ========added control file for no ASM database and works=====================
    1)
    SQL> create pfile from spfile;
    File created.
    2)
    SQL> show parameter control_file
    NAME TYPE VALUE
    control_file_record_keep_time integer 7
    control_files string C:\ORADATA\ORCL\CONTROL01.CTL
    3)
    SQL> shutdown immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    4) modify pfile add additional control file2/3 as
    control_files='C:\Oradata\ORCL\control01.ctl','C:\Oradata\ORCL\control02.ctl','C:\Oradata\ORCL\control03.ctl'
    and physical copy control01.ctl and raname as control02.ctl,control03.ctl
    5)
    SQL> startup pfile='C:\oracle\product\10.2.0\db_2\database\initORCL.ora';
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 1247900 bytes
    Variable Size 62915940 bytes
    Database Buffers 100663296 bytes
    Redo Buffers 2945024 bytes
    Database mounted.
    Database opened.er database mount;
    6)
    SQL> Create spfile from pfile='C:\oracle\product\10.2.0\db_2\database\initORCL.ora';
    File created.
    7) check control file info under pfile environment
    SQL> show parameter control_file
    NAME TYPE VALUE
    control_file_record_keep_time integer 7
    control_files string C:\ORADATA\ORCL\CONTROL01.CTL,
    C:\ORADATA\ORCL\CONTROL02.CTL
    , C:\ORADATA\ORCL\CONTROL03.CT
    L
    8)SQL> shutdown immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    9) startup as spfile environment.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 1247900 bytes
    Variable Size 62915940 bytes
    Database Buffers 100663296 bytes
    Redo Buffers 2945024 bytes
    Database mounted.
    Database opened.
    10) check control info for spfile environment
    SQL> show parameter spfile
    NAME TYPE VALUE
    spfile string C:\ORACLE\PRODUCT\10.2.0\DB_2\
    DATABASE\SPFILEORCL.ORA
    SQL> show parameter control_file
    NAME TYPE VALUE
    control_file_record_keep_time integer 7
    control_files string C:\ORADATA\ORCL\CONTROL01.CTL,
    C:\ORADATA\ORCL\CONTROL02.CTL
    , C:\ORADATA\ORCL\CONTROL03.CT
    L

  • How to delete archive log files from ASM through Grid Control

    Hi
    Anybody suggest me how to delete archive log files from ASM through Grid Control.
    Thanks

    It is important to specify both, the oracle version and os version when posting, so confusions can be avoided.
    In this particular case, since you are referring to asm and grid control you could be talking about either 10gR1, 10gR2 or 11gR1; but I strongly suggest you to avoid us to be guessing. In either case, you sould go to the maintenance tab of the target database and program a scheduled 'delete noprompt obsolete;' procedure. This will purge the information stored at the Flash recovery area, which I assume you have declared inside the ASM.
    ~ Madrid
    http://hrivera99.blogspot.com/

  • Multiplexing redo logs and control files to a separate diskgroup

    General question this one...
    I've been using ASM for a few years now and have always installed a new system with 3 diskgroups
    +DATA - for datafiles, control files, redo logs
    +FRA - for achive logs, flash recovery. RMAN backup
    Those I guess are the standards, but I've always created an extra (very small) diskgroup, called +ONLINE where I keep multiplexed copies of the redo logs and control files.
    My reasoning behind this is that if there are any issues with the +DATA diskgroup, the redo logs and control files can still be accessed.
    In the olden days (all those 5 years ago!), on local storage, this was important, but is it still important now? With all the striping and mirroring going on (both at ASM and RAID level), am I just being overtly paranoid? Does this additional +ONLINE diskgroup actually hamper performance? (with dual write overheads that are not necessary)
    Thoughts?

    Some of the decision will probably depend on your specific environment's data activity, volume, and throughput.
    Something to remember is that redo logs are sequential write, which benefit from a lower RAID overhead (RAID-10, 2 writes per IOP vs RAID-5, 4 writes per IOP). RAID-10 is often not cost-effective for the data portion of a database. If your database is OLTP with a high volume of random reads/writes, you're potentially hurting redo throughput by creating contention on the disks sharing data and redo. Again, that depends entirely on what you're seeing in terms of wait events. A low volume database would probably not experience any noticeable degraded performance.
    In my environment, I have RAID-5 and RAID-10 available, and since the RAID-10 requirement from a capacity perspective for redo is very low, it makes sense to create 2 diskgroups for online redo, separate from DATA, and separate from each other. This way, we don't need to be concerned with DATA transactions impacting REDO performance, and vice versa, and we still maintain redo redundancy.
    In my opinion, you can't be too paranoid. :)
    Good luck!
    K

  • Copying files from ASM to Remote ASM, Fails.

    Dear All,
    I am trying to copy files from ASM to Remote ASM disk groups, failing with the following error,
    ASMCMD-8201: (Bad argc for RDBMS:ASMCMD-8201) , any idea.
    Syntax: cp -- port 1521 +RECO_ABC/ABC/BKP/xyz.dbf sys@hostname.+ASM1:+RECO_XYZ/XYZ/xyz.dbf
    Thanks.

    cp -ifr <source file name> <user_name>@<host_name>.<Port Number>.<SID>:<targer path>/<target file name>
    user_name@host_name.<Port Number>.<SID>
    The user_name, host_name, and SID are required. The default port number is 1521.
    reason for error :
    It could be due to following reason.
    * not able to reach remote host.
    * Remote host listener is down.
    * Remote ASM Instance is not registered with listener and running non-default port.
    * sysasm remote connection does not work.
    * Incorrect password given for sys user.
    * Remote ASM Instance password file missing.
    We need to enable additional tracing for asmcmd connection to get a exact failure message.
    ++ set DBI_TRACE environment variable for asmcmd perl tracing.
    export DBI_TRACE=1
    ++ Now connect using asmcmd and re-produce the issue.

  • ASM lost disk, rebuilt disk grp. No dbid, how to copy ctl file to ASM?

    Hi all,
    I'm trying to help out on what is turning out to be a real challenge.
    This looks to be Oracle 10.1.0.4.0 (version showed by rman and sqlplus).
    There is ASM...but it was set to redundancy of EXTERN, but not really external redundancy. This is a test box, and I guess they were just trying to use what disks they had....I dunno, it was set up long before I got here.
    Out of all the instances I've had to look at....for this one server, I have no DBID's documented.
    This is a HP-UX box....they replaced the bad ASM drive, and I rebuilt the DATADG disk group.
    RMAN settings...well, show all just gives defaults, as that I don't have a control file in place. This was, however, set up to autobackup control files and spfiles...but I don't know the DBID, and can't figure how to find the DBID....
    I did, however, find the snapshot controlfile...and hoping I could use that.
    I am, however, stumped as to how to copy this copy of the control file, into ASM.
    I have found and old pfile that I can use to start the instance. I have started it nomount with this.
    I looked at the parameter for control file and found:
    SQL> show parameter control_file
    NAME TYPE VALUE
    control_file_record_keep_time integer 7
    control_files string +DATADG/instance/control01.ctl
    , +DATADG/instance/control02.c
    tl, +DATADG/instance/control03
    .ctl, +DATADG/instance/control
    04.ctl
    So, I know where they are to go. This is such an old version, I guess there was no ASMCMD...I can't find that command.
    I'm thinking, if I could find a way to copy this snapshot of the control file onto ASM in the old places it was, I could startup up the database, and it would then be able to restore and recover with the RMAN backups?
    Any suggestions?
    cayenne

    Just a quick update on this.
    I was able to find a snapshot of the controlfile on disk....
    I went into asm and recreated the directory where the controlfiles were kept, and used rman to copy the snapshot controlfile to where the originals were kept:
    export ORACLE_SID=+ASM
    connect with sqlplus and do:
    SQL> alter diskgroup DATADG add directory '+DATADG/instance';
    Diskgroup altered.
    Then in RMAN:
    restore controlfile to '+DATADG/instance/control01.ctl' from '/u01/app/oracle/product/10.1.0/Db_1/dbs/snapcf_INSTANCE.f';
    restore controlfile to '+DATADG/instance/control02.ctl' from '/u01/app/oracle/product/10.1.0/Db_1/dbs/snapcf_INSTANCE.f';
    restore controlfile to '+DATADG/instance/control03.ctl' from '/u01/app/oracle/product/10.1.0/Db_1/dbs/snapcf_INSTANCE.f';
    restore controlfile to '+DATADG/instance/control04.ctl' from '/u01/app/oracle/product/10.1.0/Db_1/dbs/snapcf_INSTANCE.f';
    I then got out of RMAN...back into sqlplus and mounted the database instance:
    SQL> connect / as sysdba
    Connected.
    SQL> alter database mount;
    Database altered.
    Checking to see backups:
    RMAN> run {
    2> allocate channel vh1 type sbt_tape;
    3> restore database preview;
    4> }
    allocated channel: vh1
    channel vh1: sid=321 devtype=SBT_TAPE
    channel vh1: NMO v4.1.0.0
    Starting restore at 30-SEP-11
    Starting implicit crosscheck backup at 30-SEP-11
    Finished implicit crosscheck backup at 30-SEP-11
    Starting implicit crosscheck copy at 30-SEP-11
    Finished implicit crosscheck copy at 30-SEP-11
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    no files cataloged
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    33235 Incr 0 9G SBT_TAPE 00:23:51 11-AUG-11
    List of Datafiles in backup set 33235
    File LV Type Ckp SCN Ckp Time Name
    1 0 Incr 330744282 11-AUG-11 +DATADG/instance/datafile/system.413.573936825
    2 0 Incr 330744282 11-AUG-11 +DATADG/instance/datafile/undotbs1.409.573936855
    3 0 Incr 330744282 11-AUG-11 +DATADG/instance/datafile/sysaux.406.573936867
    4 0 Incr 330744282 11-AUG-11 +DATADG/instance/datafile/users.432.573936895
    5 0 Incr 330744282 11-AUG-11 +DATADG/instance/datafile/rcv_cat.437.573987643
    6 0 Incr 330744282 11-AUG-11 +DATADG/instance/datafile/mgmt_tablespace.448.574422259
    7 0 Incr 330744282 11-AUG-11 +DATADG/instance/datafile/mgmt_ecm_depot_ts.844.574422261
    8 0 Incr 330744282 11-AUG-11 +DATADG/instance/datafile/oem_repository.533.574022071
    Backup Set Copy #1 of backup set 33235
    Device Type Elapsed Time Completion Time Compressed Tag
    SBT_TAPE 00:23:51 NO WEEKLY_INSTANCE_081111040003
    List of Backup Pieces for backup set 33235 Copy #1
    BP Key Pc# Status Media Piece Name
    34399 1 AVAILABLE server.003 fjmjmnmo_1_1
    34400 2 AVAILABLE server.003 fjmjmnmo_2_1
    34401 3 AVAILABLE server.003 fjmjmnmo_3_1
    34402 4 AVAILABLE server.003 fjmjmnmo_4_1
    34403 5 AVAILABLE server.003 fjmjmnmo_5_1
    Finished restore at 30-SEP-11
    released channel: vh1
    I think I'm ready to try to figure out the restore and recover parts now....
    I tried to recover the spfile from autobackup...but that didn't work:
    RMAN> restore spfile from autobackup;
    Starting restore at 30-SEP-11
    allocated channel: ORA_SBT_TAPE_1
    channel ORA_SBT_TAPE_1: sid=321 devtype=SBT_TAPE
    channel ORA_SBT_TAPE_1: NMO v4.1.0.0
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=320 devtype=DISK
    channel ORA_SBT_TAPE_1: looking for autobackup on day: 20110930
    channel ORA_SBT_TAPE_1: looking for autobackup on day: 20110929
    channel ORA_SBT_TAPE_1: looking for autobackup on day: 20110928
    channel ORA_SBT_TAPE_1: looking for autobackup on day: 20110927
    channel ORA_SBT_TAPE_1: looking for autobackup on day: 20110926
    channel ORA_SBT_TAPE_1: looking for autobackup on day: 20110925
    channel ORA_SBT_TAPE_1: looking for autobackup on day: 20110924
    channel ORA_SBT_TAPE_1: no autobackup in 7 days found
    recovery area destination: +RECOVERYDG
    database name (or lock name space) used for search: INSTANCE
    channel ORA_DISK_1: no autobackups found in the recovery area
    channel ORA_DISK_1: looking for autobackup on day: 20110930
    channel ORA_DISK_1: looking for autobackup on day: 20110929
    channel ORA_DISK_1: looking for autobackup on day: 20110928
    channel ORA_DISK_1: looking for autobackup on day: 20110927
    channel ORA_DISK_1: looking for autobackup on day: 20110926
    channel ORA_DISK_1: looking for autobackup on day: 20110925
    channel ORA_DISK_1: looking for autobackup on day: 20110924
    channel ORA_DISK_1: no autobackup in 7 days found
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 09/30/2011 10:01:09
    RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
    Anyway...further along than I was.....
    Suggestions welcome....
    cayenne

  • How to organize RAC database files on ASM

    How to Organize RAC database files on ASM.
    Say,
    DISK Group = DATA
    DISK Group= FLASH
    Instance = prod1, prod2
    '+DATA/PROD/datafiles/'
    or
    Need to Organize sepratly for each instance specific db files.
    as
    '+DATA/PROD1/datafiles'
    '+DATA?PROD2/datafiles'
    Thanks in Advance,
    Regards
    Satish

    It would be just PROD - since that's the database name...and BTW, when you use DBCA to create a database using ASM, it organizes data files under PROD and it doesn't use instance names.
    HTH
    Thanks
    Chandra

  • Send and Receive Files

    I found that on my desktop computer I cannot send or receive any files (pictures, documents, etc). However if I log into skype on my Android phone i can receive and send files. Why is this happening and how can I fix it?
    I'm on Skype Version 7.2.59.103
    Solved!
    Go to Solution.

    Try to reset all Internet Explorer settings:
    http://support.microsoft.com/kb/923737
    Next reset LAN settings:
    Open Internet Explorer. Go to Tools -> Internet Options -> Connections -> LAN settings. Make sure that the only option selected is “Automatically detect settings”.
    Next clear all Temporary Internet Files:
    Open Internet Explorer -> Tools -> Internet Options -> General. In the section “Browsing history” press the “Settings” button and in the next window the “View files” button. Delete all files from the Temporary Internet Files folder.
    Reboot your computer and test now what happens when you open this link in your Internet Explorer.
    https://api.asm.skype.com/s/i

  • What is the failure group in ASM  and the meaning of ASM assigns each disk

    Hi
    Please help me in understanding
    what is the failure group in ASM and the meaning of "ASM assigns each disk to it's own failure group, by default"

    As you may have known ASM uses mirroring and striping of files. Mirroring is storing same compies/parts of files in different disks/controllers. When creating disk group which could consist of several disks, you have to assign disks at least to separate failure groups for normal redundancy , or three failure groups for High redundancy. This means that ASM will never assign mirrode copies/pieces of files to the same failure group. So, assigning disks to different failure groups you make sure mirrored copies are not on the same physical storage. Saying with other words, failure group gives your more abstract meaning based on which you can organize your physical disks contained in disk group.
    That is why for normal redundancy at least two failure groups are needed, because there are one mirrored copy of each extent(allocation unit, to be exact) and for high redundancy the requirement is at least 3 failure groups, because each allocation unit has 2 mirrored copies, which should be on different failure group, consequently.
    Hope, this explanation is helpful.

  • Strange .nfs file in ASM storage

    Hello
    I'm using ASM in a RAC environment over NFS. I've noticed that where I've raw files for ASM I've also some .nfsXXXXXXXxx files:
    [oracle@itsm-cldb1c oradata]$ ls -al
    total 29417868
    drwxrwxrwx 3 root root 4096 Aug 28 11:31 .
    drwxr-xr-x 27 root root 4096 Aug 27 19:20 ..
    drwxr-x--- 2 oracle oinstall 4096 Aug 28 08:58 dbs
    -rw-r--r-- 1 oracle oinstall 10737418240 Aug 28 10:36 .nfs0011a52600000001
    -rw-r--r-- 1 oracle oinstall 5368709120 Aug 28 11:21 .nfs0011a52700000002
    -rw-r--r-- 1 oracle oinstall 4294967296 Aug 28 11:40 tdwdisk1
    -rw-r--r-- 1 oracle oinstall 4294967296 Aug 28 11:40 tdwflash1
    -rw-r--r-- 1 oracle oinstall 5368709120 Aug 28 11:39 tdwstorage1
    [oracle@itsm-cldb1c oradata]$ rm -rf .nfs0011a52*
    rm: cannot remove `.nfs0011a52600000001': Device or resource busy
    rm: cannot remove `.nfs0011a52700000002': Device or resource busy
    And these files are busy. Anyone knows what kind of files are them?
    Thanks
    Stefano

    This usually happens if you are using NFS...and I think you are using NFS. If you remove a file that is currently/actively being used or open by running process , the file isn't really removed and it would manifest itself as a .nfsxxxx files.
    HTH
    Thanks
    Chandra Pabba

Maybe you are looking for