Question on ASM an Failgroups

Hello everybody,
I am having a ASM Diskgroup that is running out of space. The diskgroup has redundancy NORMAL and has three failure groups with two disks each. All of the disks have the same size (50G).
Now the diskgroup is almost full and I have to add space. And I have two raw devices of 36G each available.
I read that Oracle recommmends to have all the failure groups of the same size. So does that mean I can not make use of those two free disks for ASM ?
Because if I create another Failgroup with them, the group would have a different size than the others. And if I add them to an existing group (if that is possible at all), this group would also have a different size.
Thanks for your thoughts.
Mario

Hello Kuljeet Pal Singh,
thank you for your quick reply. Maybe I have not made clear what my exact problem/question is:
I have one Diskgroup: DG1.
This Diskgroup has three Failure Groups: FG1,FG2,FG3.
Each Failure Group has two disks DISK1A (belongs to FG1) , DISK1B (belongs to FG1) , DISK2A (belongs to FG2) ,DISK2B (FG2) , DISK3A (FG3) ,DISK3B (FG3).
Each of this disks 50G in size.
Now I have two more disks to add, let's say DISK4A and DISK4B, but they are only 36G each.
If I create a new failure group FG4, it would not have the same size as the other FGs.
If I add it to FG1,FG2 or FG3 there would also be a misbalance in the size.
I am not sure if I interpret the statement from Oracle "Failure groups should all be of the same size" correct.
Sounds clear, but on the other hand that would mean once I start with 50G disks, I always have to use 50G disks in the future. What if they are out of stock etc. ?
Mario

Similar Messages

Questions on asm disk discovery:

Questions on asm disk discovery:
1）What is the relationship btween asm_diskstring in the init.ora and DiscoveryString in the GPNP profile.xml?
2) Which one of the above two finally accounts for the disk discovery process?
3) We know that asmlib disks are self describing at the disk header. This overcomes the disk name/path persistency issue as we no long need to rely on the path to discover the asm disks, by setting asm_diskstring='ORCL:*' , ASM instance will identify the right disks automatically. However, I am not sure if setting asm_diskstring='ORCL:*' is the most economic way to do the discovery as I am not sure if Oracle will have to probe all the disks on the OS to determine the right disks. If Oracle has to screen all the disks in this way, then I think setting asm_diskstring='<path_to_asmlib_disk>' will be much faster, although this will be open to the persistent problem. Is my understanding correct?
Thanks.

From my understanding all disk you see in /dev/oracleasm/disks are the disks in your system that been discovered by asmlib at discovery stage.
Currently, due to bug 13465545, ASM instance will discover disks from both locations, ASM_DISKSTRING and gpnp profile, which can cause some mess in disk representation for asm. You can check the settings using asmcmd command: dsget, and set to be the same using dsset.
I think its more secure to set ASM_DISKSTRING to only the disks used by asm instance.
ASMCMD> dsget
Regards
Ed

Questions on asm disk discover:

Questions on asm disk discover:
1）What is the relationship btween asm_diskstring in the init.ora and DiscoveryString in the GPNP profile.xml?
2) which one finally accounts for the disk discovery process?
3) We know that asmlib disks are self describing at the disk header. This overcomes the disk name/path persistency issue as we do not rely on the path the discover the asmlib
disks. asm_diskstring='ORCL:*' will identify the right disks. I am not sure if setting 'ORCL:*' is the most economic way as I am not sure if Oracle will have to scan all the disks
on the OS and probe the disks that it has rigths to determine which disks belong to ASM. If Oracle has to screen all the disks in this way, then I think setting
asm_diskstring='<path_to_asmlib_disk>' will be much faster. However, this will be open to the persistent problem. Is my understanding correct?
Thanks.

Questions on asm disk discovery:
1）What is the relationship btween asm_diskstring in the init.ora and DiscoveryString in the GPNP profile.xml?
2) Which one of the above two finally accounts for the disk discovery process?
3) We know that asmlib disks are self describing at the disk header. This overcomes the disk name/path persistency issue as we no long need to rely on the path to discover the asm disks, by setting asm_diskstring='ORCL:*' , ASM instance will identify the right disks automatically. However, I am not sure if setting asm_diskstring='ORCL:*' is the most economic way to do the discovery as I am not sure if Oracle will have to probe all the disks on the OS to determine the right disks. If Oracle has to screen all the disks in this way, then I think setting asm_diskstring='<path_to_asmlib_disk>' will be much faster, although this will be open to the persistent problem. Is my understanding correct?
Thanks.

Question about ASM

Hi dears,
I am planning the installation of G.I 11R2 and have a question regarding ASM.
If I have ASM diskgroup with normal or high redundancy for my DB need I create multiplex redologs and
multiplex controlfiles ? If I understood correctly the multiplex redologs and controlfile is another HA and DR option.
From Oracle documentation
*"To protect against a failure involving the redo log itself, Oracle Database allows a multiplexed redo log, meaning that two or more identical copies of the redo log can be automatically maintained in separate locations."*
Question rised when I checked my old G.I with RACcheck and got the following....
The online redo logs of an Oracle database are critical to availability and recoverability and should always be multiplexed even in cases where fault tolerance is provided at the storage level.
The controlfile of an Oracle database is critical to availability and recoverability and should always be multiplexed even in cases where fault tolerance is provided at the storage level.
"should always be multiplexed even in cases where fault tolerance is provided at the storage level"
WHY ????
Please share your experience.
./thanks

Ilmar Kerm wrote:
Redo logs and controlfile are very critical for database, and if something happened with one copy of them (like file is deleted or corrupted) you can quickly recover by copying over the damaged file with the contents from the surviving file (copies are identical). So copies should be located on separate LUNs/disks/diskgroups/filesystems.Thanks Ilmar for reply.
I understand what you said its obvious. My questions is that if I already have 2 copies or 3 copies of redolog files with ASM nigh or normal redundancy why I need to do it also with creating multiplex redo file.....

Few Questions on ASM

Hi,
I am new to ASM and I have few questions regarding ASM.
1.In a RAC environment I understand there will be 2 ASM instanace for a 2 node RAC.If one of the node crashes for ASM what will happen to
the other instance and How will other instance will know about crash of one of the instance.
2.How can I backup ASM database through RAMN and How can I recover to a different new machine without ASM.
3.Where should I keep my archive logs,can I keep my archive logs on ASM if so how can I configure the database for that.
4.Usually companies keep 4-5 instance on each node and with ASM it will be one more instance.what will happen to cache fusion for the instances(ASM also uses cache fusion if so how we can query if there is bottleneck on the cache fusion).
5.How can we administor ASM instances.(ASMCMD OR SRVCTL OR BOTH).
6.If I want to duplicate the database through RMAN how can i do it if I am using ASM.
7.ASM instances do we have to take backup or how can I recreate them.
Regards
MMU

MMU,
ASM is a volume manager like other volume manger available in the market. ASM does not have any data dictionary and there is no need to take backup of ASM instance as this will have only metadata about ASM disks and ASM instance itslef keep mirrored copy of this metadata internally.
Regarding your questionsa about backup, I would suggest you to go thru Oracle Backup and Recovery Advanced User Guide available from OTN.
For administration of ASM instance, there are database views starting with v$ASM* that can be very useful. Following are few of ASM views:
V$ASM_DISK
V$ASM_DISKGROUP
V$ASM_OPERATION
V$ASM_FILE
V$ASM_ALIAS
Thanks & Regards

ASM Quorum Failgroup Setup is Mandatory for Normal and High Redundancy?

Hi all,
Since I have worked with version 11.2 I had a concept about Quorum Failgroup and its purpose, now reading the documentation 12c I'm confuse about some aspect and want your views on this subject.
My Concept About Quorum Failgroup:
The Quorum Failgroup was introduced in 11.2 for setup with Extended RAC and/or for setup with Diskgroups that have only 2 ASMDISK using Normal redundancy or 3 ASMDISK using High redundancy.
But if we are not using Extended RAC and/or have a Diskgroup Normal Redundancy with 3 or more ASMDISK or Diskgroup High Redundancy with 5 or more ASMDISK the use of Quorum Failgroup is optional, most like not used.
==============================================================================
Documentation isn't clear about WHEN we must to use Quorum Failgroup.
https://docs.oracle.com/database/121/CWLIN/storage.htm#CWLIN287
7.4.1 Configuring Storage for Oracle Automatic Storage Management
2. Choose the Oracle ASM redundancy level to use for the Oracle ASM disk group.
Except when using external redundancy, Oracle ASM mirrors all Oracle Clusterware files in separate failure groups within a disk group. A quorum failure group, a special type of failure group, contains mirror copies of voting files when voting files are stored in normal or high redundancy disk groups. If the voting files are in a disk group, then the disk groups that contain Oracle Clusterware files (OCR and voting files) have a higher minimum number of failure groups than other disk groups because the voting files are stored in quorum failure groups.
A quorum failure group is a special type of failure group that is used to store the Oracle Clusterware voting files. The quorum failure group is used to ensure that a quorum of the specified failure groups are available. When Oracle ASM mounts a disk group that contains Oracle Clusterware files, the quorum failure group is used to determine if the disk group can be mounted in the event of the loss of one or more failure groups. Disks in the quorum failure group do not contain user data, therefore a quorum failure group is not considered when determining redundancy requirements in respect to storing user data.
As mentioned in documentation above, I could understand that in ANY diskgroup that use Normal or High Redundancy MUST have a Quorum failgroup. (does not matter what setup)
In my view, if a Quorum Failgroup is used to ENSURE that a quorum of the specified failure groups are available, then we must use it, in other words is mandatory.
What's your view on this matter?
==============================================================================
Another Issue:
Suppose the following scenario (example using NORMAL Redundancy).
Example 1
Diskgroup Normal Redundancy with 3 ASMDIKS.
DSK_0000 - FG1 (QUORUM FAILGROUP)
DSK_0001 - FG2 (REGULAR FAILGROUP)
DSK_0002 - FG3 (REGULAR FAILGROUP)
The ASM will allow create only one Quorum Failgroup, and two Regular Failgroup ( a failgroup to each asm disk)
Storing Votedisk on this diskgroup the all three asmdisk will be used one votedisk in each asm disk.
Storing OCR on this diskgroup the two Regular Failgroup will be used, only one OCR and primary extents and mirror of its extents accross two failgroup. (quorum failgroup will not be used to OCR)
Example 2
Diskgroup Normal Redundancy with 5 ASMDIKS.
DSK_0000 - FG1 (REGULAR FAILGROUP)
DSK_0001 - FG2 (REGULAR FAILGROUP)
DSK_0002 - FG3 (QUORUM FAILGROUP)
DSK_0003 - FG4 (QUORUM FAILGROUP)
DSK_0004 - FG5 (QUORUM FAILGROUP)
The ASM will allow create up to three Quorum Failgroup, and two Regular Failgroup.
Storing Votedisk on this diskgroup the all three QUORUM FAILGROUP will be used. REGULAR FAILGROUP will not be used.
Storing OCR on this diskgroup the two Regular Failgroup will be used, only one OCR and primary extents and mirror of its extents accross two failgroup. (none quorum failgroup will not be used to OCR).
This right here below is confuse to me.
https://docs.oracle.com/database/121/CWLIN/storage.htm#CWLIN287
7.4.1 Configuring Storage for Oracle Automatic Storage Management
2. Choose the Oracle ASM redundancy level to use for the Oracle ASM disk group.
The quorum failure group is used to determine if the disk group can be mounted in the event of the loss of one or more failure groups.
Normal redundancy: For Oracle Clusterware files, a normal redundancy disk group requires a minimum of three disk devices (two of the three disks are used by failure groups and all three disks are used by the quorum failure group) and provides three voting files and one OCR and mirror of the OCR. When using a normal redundancy disk group, the cluster can survive the loss of one failure group.For most installations, Oracle recommends that you select normal redundancy disk groups.
High redundancy: For Oracle Clusterware files, a high redundancy disk group requires a minimum of five disk devices (three of the five disks are used by failure groups and all five disks are used by the quorum failure group) and provides five voting files and one OCR and two mirrors of the OCR. With high redundancy, the cluster can survive the loss of two failure groups.
Documentation says:
minimum of three disk devices: two of the three disks are used by failure groups and all three disks are used by the quorum failure group for normal redundancy.
minimum of five disk devices: three of the five disks are used by failure groups and all five disks are used by the quorum failure group for high redudancy.
Questions :
What this USED mean?
How the all disk are USED by quorum failgroup?
This USED mean used to determine if the disk group can be mounted?
How Quorum Failgroup determine if a diskgroup can be mounted, what is the math?
Consider following scenery:
Diskgroup Normal Redundancy with 3 ASM Disks. (Two Regular failgroup and One Quorum Failgroup)
If we lost the Quorum failgroup group. We can mount that diskgroup using force option.
If we lost one Regular failgroup group. We can mount that diskgroup using force option.
We can't lost two Failgroup at same time.
If I don't use Quorum failgroup (i.e only Regular Failgroup) the result of test is the same.
I see no difference between use Quorum Failgroup and only Regular Failgroup on this matter.
======================================================================================
When Oracle docs says:
one OCR and mirror of the OCR for normal redundancy
one OCR and two mirrors of the OCR for high redundancy
What this means is we have ONLY ONE OCR File and mirror of its extents, but oracle in documentation says 1 mirror of OCR (normal redundancy) and 2 mirror of OCR (high redudancy).
What is sound like? a single file or two or more files ?
Please don't confuse it with ocrconfig mirror location.

Hi Levi Pereira,
Sorry for the late answer. And as per 12c1 documentation, yes you are right, only the VD will be placed on the quorum fail groups:
The redundancy level that you choose for the Oracle ASM disk group determines how Oracle ASM mirrors files in the disk group, and determines the number of disks and amount of disk space that you require. If the voting files are in a disk group, then the disk groups that contain Oracle Clusterware files (OCR and voting files) have a higher minimum number of failure groups than other disk groups because the voting files are stored in quorum failure groups.
Managing Oracle Cluster Registry and Voting Files
Regarding your question "I want answer about is mandatory to use Quorum Failgroup when use Normal or High Redundancy?" No it isn't, I have a normal redundancy diskgroup that I store VD with no Quorum Failgroup, indeed, it would prevent you to store data on the disks within this kind of failgroup as per the documentation:
A quorum failure group is a special type of failure group that is used to store the Oracle Clusterware voting files. The quorum failure group is used to ensure that a quorum of the specified failure groups are available. When Oracle ASM mounts a disk group that contains Oracle Clusterware files, the quorum failure group is used to determine if the disk group can be mounted if there is a loss of one or more failure groups. Disks in the quorum failure group do not contain user data, therefore a quorum failure group is not considered when determining redundancy requirements in respect to storing user data.
Managing Oracle Cluster Registry and Voting Files
And as per the documentation, my answer are with red color:
Could you explain what documentation meant:
minimum of three disk devices: two of the three disks are used by failure groups and all three disks are used by the quorum failure group for normal redundancy.
how all three disk are used by the quorum failgroup? [I don't think this is correct, sounds a bit strange and it is the opposite for what is right before...]
Regards.

Looking for information on the below questions on ASM

Scenario: (Oracle 10g on Windows 2003 with EMC storage)
ASM Partition table crashed for LUN 20 on 18th July
DB was up and running till 23rd July (New LUN (LUN 36) was presented and the RMAN backup used to restore the data that were residing on the corrupt LUN)
End of the day everything screwed up and the complete grid (4 nodes) was rebuild.
Links:
As mentioned in the link: http://www.exforsys.com/forum/oracle-database/487-what-asm-instance-oracle.html
"The ASM instance is only involved during the creation or deletion of files and when disk configurations change (such as dropping or adding a disk). When these types
of changes occur, the ASM instance automatically rebalanced the disks and provides the necessary information to refresh the extent map in the SGA of the database
instance. Of course, this process requires that the ASM instance run concurrently with the database instance, and only shut down after the database instance is
closed."
As mentioned in the link: http://www.orafaq.com/wiki/ASM_FAQ#ASM_disk_header.2Fsuperblock_backups.3F
"ASM disk headers (super-blocks) cannot be backed up and restored in Oracle 10g. By implication, if you use EXTERNAL REDUNDANCY and a single disk's header is
accidentally overwritten, the entire disk group will have to be restored."
As mentioned in the link: http://www.datadisk.co.uk/html_docs/oracle/asm.htm
"ASM is a special instance that does not have any data files, there is only ASM instance one per server which manages all ASM files for each database. The instance
looks after the disk groups and allows access to the ASM files. Databases access the files directly but uses the ASM instance to locate them. If the ASM instance is
shutdown then the database will either be automatically shutdown or crash. "
With the above scenario and the documents provided in the links above, I am unable to get the complete picture of what went wrong. Will be great if some one could
through more light on the below questions. (Note: we have multiple vendor engaged managing different part of this outage and unable to get the real fact of what went
wrong)
1, The ASM had given the details of the disk to the DB, and the DB is managing the disk directly. Also the DB and the ASM instance were up and running till 23rd is
what i understand going by the details given in the above links, in this scenario how can we confirm that the partition table is corrupt / missing. Is their a way to
check the same?
2, ASM disk headers (super-blocks) cannot be backed up, that means that it can not be read directly. Then is it possible to say that the ASM disk header is corrupt /
missing?
3, If the ASM disk header / partition table of LUN 20 is corrupt on 18th, can the DB run till 23rd without any issue? will the ASM & DB does not crash?
4, ASM will strip the data across the available LUN's, will it not be able to rebuild the data on the newly presented LUN 36 instead of using RMAN backup to rebuild the
data? or is the ASM not configured as it should be done. (WE have multiple LUN's presented to this Grid)
Edited by: 880333 on Aug 19, 2011 12:35 AM

What relation with the Oracle Forms product ?
Francois

Question on Asm Disk Groups

Hello,
I have five 200gb (Total 1 TB) disks on my prod rac environment and we are using 11g 11.1.0.6. These disks have been mounted a while back and the db is currently 50gb full.
My question is i need to unmount one of the disks of 200gb since we are having a shortage of disks at the moment, so i can use it as the flash recovery drive. My understanding with asm is that even if once disk fails the rebalnce act would happen and it would stripe data across four disks without any loss of data or downtime.
We are using external redudancy on these disks and they use Raid 5.
Can i attempt this, if this is possible could you guys give me the best command i can use to do this.
Thx All

Just do an
alter diskgroup <name> drop disk <name>;The documentation states:
DROP DISK The DROP DISK clause lets you drop one or more disks from the disk group and automatically rebalance the disk group. When you drop a disk, Automatic Storage Management relocates all the data from the disk and clears the disk header so that it no longer is part of the disk group.
Note:
If you need to drop more than one disk i strongly recommend to do it in a single step, e.g.
alter diskgroup <name> drop disk <nameA>,<nameB>;Thsi will do the rebalance only once.
Ronny Egner
My Blog: http://blog.ronnyegner-consulting.de

Two questions on ASM for Grid Installation

Grid Infrastructure version : 11.2.0.3
Platform : Oracle Enterprise Linux 5.6
Question1.
oracle:dba will be owner of our Grid software (not grid user). What should be permission set for LUNs ( /dev/sda1, ..) before the grid installation ?
Question2.
Currently, the shared LUNs appear as
/dev/sdb ,
/dev/sdc,
/dev/sdd
does a single partition need to be created before presenting LUN to ASM ?
For example, I should choose p (primary partition ) below. Right ?
# fdisk /dev/sdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0x8b157fd2.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
         switch off the mode (command 'c') and change display units to
         sectors (command 'u').
Command (m for help): c
DOS Compatibility flag is not set
Command (m for help): u
Changing display/entry units to sectors
Command (m for help): n
Command action
   e   extended
p   primary partition (1-4)

Check the step 5 here.You use oracleasm utility which changes permission.
Installing Grid Infrastructure for a Standalone Server
Ta
Jag

ASM striping & Failgroups

Hi Gurus,
After Googl-ing also i got only blur image about ASM striping and Fail groups.
Could you please expalin 1.ASM striping Concept,
2.ASM Fail Group Concept. At least guide me through some URL.

udayjampani wrote:
Understand the following scenario and explain me,
I have chosen normal redundancy level and didn't provided any fail group specification .
So I have two disk groups,DATA and FRA , which in turn having four disks, DATA_0000,DATA_0001,FRA_0000,FRA_0001.
1.From the document, DATA_0000,DATA_0001 will be two failure groups automatically.is that right?Yes, both the disks would be in two different fail groups and each one would be owned by one disk.
2.But from striping concept,mirror file will be stored across disks,say for a table some data is stored in one disk,and remaining will be on the other disks.But this scenario will not serve data when there is disk failure right?You are mixing two things. Don't combine striping and mirroring together. You have got two disks over which the mirroring would be done but since you have just two disks, if one is gone, there won't be any other disks available to support the redundancy level of the disk group, loss of one disk would eventually lead to the dismounting of the entire disk group. To confirm this, create a disk group with 3 disks and then lose one of the disks .
Aman....

Question on ASM operation

Hi,
i am using oracle 11gR1 and ASM as storage option. user sys is ASM admin but i am not able to access ASM instance with sys user. if i do su oracle then i can access asm instance , do asm dg operation etc. i thought ASM admin is the one who can do execute some operation on asm instance and asm dg etc. should i always use "oracle" user for ASM operation . cant i use "sys" user for this. Please share your view on this.
Thanks for your help,

user11305560 wrote:
is it possible to make one OS user owner of crs and make one OS user admin of ASM instance. i believe the CRS owner will have permission to do ASM administration also. Following is the error message, i am getting when i am doing su sys.
$ export ORACLE_SID="+ASM1"
$ su sys
$ sqlplus '/ as sysdba'
SQL*Plus: Release 11.1.0.6.0 - Production on Thu Nov 5 20:19:45 2009
Copyright (c) 1982, 2007, Oracle. All rights reserved.
ERROR:
ORA-01031: insufficient privileges
Enter user-name: sys
Enter password:
ERROR:
ORA-15000: command disallowed by current instance type
############################################3
when i do su oracle it works fine.
$ su oracle
$ sqlplus '/ as sysdba'
SQL*Plus: Release 11.1.0.6.0 - Production on Thu Nov 5 20:21:05 2009
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options
SQL>If you install ASM by "oracle" user, you should use "oracle" to connect ASM as sysdba

Question about ASM Online log files

Hi All,
Wondering if this setup is desirable?
SQL> show parameter db_create
NAME TYPE VALUE
db_create_file_dest string +SYS1
db_create_online_log_dest_1 string +SYS1
db_create_online_log_dest_2 string +SYS2
db_create_online_log_dest_3 string +SYS3
db_create_online_log_dest_4 string +SYS4
db_create_online_log_dest_5 string
SQL>
Looks like logs are being sent to 4 DG's....

HI,
DB_CREATE_ONLINE_LOG_DEST_n (where n = 1, 2, 3, ... 5) specifies the default location for Oracle-managed control files and online redo logs. If more than one DB_CREATE_ONLINE_LOG_DEST_n parameter is specified, then the control file or online redo log is multiplexed across the locations of the other DB_CREATE_ONLINE_LOG_DEST_n parameters. One member of each online redo log is created in each location, and one control file is created in each location.
Specifying at least two parameters provides greater fault tolerance for the control files and online redo logs if one of the locations should fail.
If a file system directory is specified as the default location, then the directory must already exist; Oracle does not create it. The directory must have appropriate permissions that allow Oracle to create files in it. Oracle generates unique names for the files, and a file thus created is an Oracle Managed File.
Cheers

Is the Use of ASM Mandatory in 11g Rel 2

Hello.
I am currently using Oracle DB server 11g Rel 1 (11.1.0.7.0). We are planning on going to Release 2 soon. We do not use ASM at the moment, but have a NAS implemetation instead. An associate of mine who is also on Rel 1 of 11g told me that I will be REQUIRED to use ASM when I go to 11g Rel 2. I have not ever heard this before and not found it in any documentation that I have ever looked at. My simple question: is ASM required when going to Oracle DB 11g Release 2? Thank you.
Matt

Matt,
From 11g onwards, the support of raw devices is removed by oracle. So what your colleague probably wanted to mention that if you are having a use of raw devices in the current set up of yours, it won't be supported in 11.2. This is partially correct since if you are already on raw, after upgrading as well, oracle would support it at least for 11.2 . In 12g, this won't be possible at all and you would need to migrate to the ASM on a mandatory basis. The file system support(cooked) remains as it is and thus is available in both previous versions and in 11.2 as well. This also would remain as a supported option in the next releases as well.
Hope that helps.
Aman....

ASM instance migration from non-asm in windows

hi,
i am looking for migration steps to asm from non-asm in windows platform. oracle version is 10.2.0.2.0 any metalink id's or Docs would be great.
i just had raw disk allocated in my windows but asmtoolg could not find the disk while configuring ?

had better post your question in ASM forum, you will get better guidance/reply there.
Forum Home » Grid Computing » Automatic Storage Management
Automatic Storage Management

ASM instance backup

Hello All,
I am using Oracle RAC 11g R2 + ASM.
I have basic below 2 questions concerning ASM and OCR and voting disks data
1. Is there any way to backup the ASM instance? Is that needed in a production environment? What is the best way to do that ? is it through RMAN ?
2. My OCR and Voting disks info are stored on ASM diskgroup +OCR, should I backup that? I am seeing md_backup command in asmcmd help
Regards,

>
I have basic below 2 questions concerning ASM and OCR and voting disks data
1. Is there any way to backup the ASM instance? Is that needed in a production environment? What is the best way to do that ? is it through RMAN ?with the help of md_backup you can backup the metadata of the ASM instance .
Nice articles from arup on this
http://www.oracle.com/technetwork/articles/sql/11g-asm-083478.html
2. My OCR and Voting disks info are stored on ASM diskgroup +OCR, should I backup that? I am seeing md_backup command in asmcmd help
OCR backup detail -http://docs.oracle.com/cd/E11882_01/rac.112/e16794/votocr.htm#i1012456
The voting disk data is automatically backed up in OCR as part of any configuration change.

Question on ASM an Failgroups

Similar Messages

Maybe you are looking for