ASM failgroup

Hello

11 GR 1 material, is it possible to change the failgroup that ASM disk is assigned to the after it is created, or do I have to remove the Group and add it specifying the correct failgroup?

Thank you
Justin

Justin,

The best place to find it would be Oracle docs.
http://download.Oracle.com/docs/CD/B28359_01/server.111/b28286/statements_1006.htm#BABGCDFE

And looking at it, its clear that you must re-create the group in order to change the redundancy.

HTH
Aman...

Tags: Database

Similar Questions

Distribution of ASM & Failgroups
Hi gurus,
After Googl-ing as I had only blurry image on ASM aggregation and Fail groups.
Could you please contact intertwining of ASM 1. Concept,
2 ASM Fail group Concept. At least guide me through a URL.
udayjampani wrote:
Understand the following scenario and explain,
I chose normal redundancy and provided no one fails the group specification.
So I have two groups of disks, the DATA and the FRA, which in turn have four discs, DATA_0000, DATA_0001, FRA_0000 and FRA_0001.
1. in the document, DATA_0000, DATA_0001 will be two groups of failure automatically.is that at the time?

Yes, both discs would be in two different groups of failure and each of them would be owned by a single drive.

2. but the concept of interleaving, mirror file will be stored on discs, for example for a table, some data is stored in a disk, and remaining will be on the other disks. But this scenario will no data when there is failure of the right drive?

You mix two things. Do not combine striping and mirroring together. You have two disc mirroring would be but since you have only two disks, if we left, there will be no other drives available to support the disk group redundancy, loss of a drive would lead to term for the disassembly of the entire disk group. To confirm this, create a group of records with 3 disks and then lose one of the disks.

Aman...

Is have RAID (1 + 0) so that Failgroups for all ASM ASM starts is a well-known best practice?

Dear Experts,
Is have RAID (1 + 0) so that Failgroups for all ASM ASM starts is a well-known best practice?
Having both is the best practice
- RAID (1 + 0)
- ASM Failgroups for all ASM starts
Thank you
IVW

You can create groups of ASM disks with normal or high redundancy or specify external redundancy. It depends on your reliability requirements and storage performance. Remember that ASM is not RAID and redundancy is the base file. ASM uses alternating devices. Oracle is generally recommended to have redundancy of storage. If you have RAID redundancy at the level of hardware controller or storage, Oracle recommends to configure ASM disks with external redundancy groups. Redundancy of the DSO is only between groups of disk failure and by default, each device's own failure group. Of course, you always want to make sure that you do not rely on redundancy of data between logical devices or partitions residing on a single physical unit. Compared to external RAID redundancy redundancy ASM using will give the DBA more control and transparency on the setting of the underlying.

Question about ASM a Failgroups
Hello everyone,

I have an ASM Diskgroup that is short on space. The diskgroup has NORMAL redundancy and three groups of failure with two disks of each. All the disks are 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 recommmends Oracle for all groups of the failure of the same size. So use it means I can't do these 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 a group (if it is possible at all), this group would also have a different size.

Thanks for your thoughts.

Mario
The Diskgroup has three default groups: FG1, FG2, FG3.

in this case you have 3 discs 2 you need to add the disc in each behalf can be 36 GB but all should have the same size disc.

Seems clear, but on the other hand that means once I start with 50G disks, I always have to use 50 G discs in the future. What happens if they are out of stock etc. ?

same size of DISKGROUP not discs. so 3 disc may be 36 GB each.

Resync ASM disk in 12 c

Hello
Please can someone tell what is the difference between ASM resynchronization and consolidation of disk drive?
Are they different? If so, what is re-synchronization happens and when to rebalance?
Thank you

Fast ASM disk Resync is used to recovery failure a failure to make temporarily unavailable group is considered transient failures.

As the disconnection of the cable, controller failures or interruptions of supply disk or host bus adapter current.

You just put a time (duration) where ASM Diskgroup will be to track all the changes up to recover this failure. If records are retrieved using the last State when, down disc Resync then update all the blocks on the disk recovered from survive failgroup.

If drive failure is not picked up within the window of time, records are automatically removed from the diskgroup.

The process of adding these drive broke diskgroup start the rebalancing process.

Resynchronization occurs when updating the out-of-sync disk track.

Rebalancing occurs when data are not balanced or when to add new disc on diskgroup.

dissappearing asm space

Oracle 11.2.0.4 SE a 64-bit
Standalone ASM 11.2.0.4 - no CARS, no grouping
Oracle Linux 5.6
Database had two DGs in ASM. External redundancy, another normal redundancy with two failure groups. A group of failure was on local SSD on the server. We have been short on space and limited by these local drives, so created a third DG in order to replace the constraint... This one disc, external redundancy. Disks to look like this. The SMALL DG is the one who is forced to the internal SSD. DG DATA2 is his replacement.
GROUP_NUMBER DISK_NUMBER SIZE_GB REDUNC DISK_NAME FAILGROUP GROUP_NAME
------------ ----------- ----------- ---------- ------ -------------------- ---------------
3 LARGE EXTERN 0 950 LARGE_0000 LARGE_0000
4 SMALL 0 149.863281 NORMAL SMALL_FIOA SSD_GROUP
4 SMALL 1 149.863281 NORMAL SMALL_FIOB SSD_GROUP
4 SMALL 3 149.011719 NORMAL SMALL_FIOC SSD_GROUP
4 SMALL 6 150 NORMAL SAN_GROUP SMALL_0006
4 SMALL 7 150 NORMAL SAN_GROUP SMALL_0007
4 SMALL 8 150 NORMAL SAN_GROUP SMALL_0008
5 DATA2 EXTERN 0 500 DATA2_0000 DATA2_0000
Yesterday, I finished moving all the data and temporary files from SMALL to DATA2. The only files left on the SMALL are control files, which I hope to move today.
Now the question. I have a task that runs every morning at 0630 to gather various metrics of the use of disk file system and ASM. The result of this work is recorded and used to fill a daily tracking spreadsheet. Yesterday, I did an extra run after I finished moving all the data files (but before you move the temporary files). At this point, the SMALL DG showed 337,8 GB of usable space. After that, I created a new temp TS (TEMP2) with its files on DATA2 and dropped the old a little. I capture info use disk at this stage.
This morning I got a big surprise. The SMALL DG relates now only 74.4 GB of usable space. I double checked its contents using "asmcmd" and verified that the only file on it's a db control file and its alias.
The command to capture its use ASM is
asmcmd lsdg | awk ' {print $13 "" $2 "" $7 "" $8 "" $10}' > > $logfile
with this result:
Name Type Total_MB Free_MB Usable_file_MB
DATA2 / 512000 154640 154640 EXTERN
LARGE / EXTERN 972800 33915 33915
SMALL / NORMAL 920308 OF NTA 305895 76147
Output power of "lsdg;
State Type sector Rebal to Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files name of the block
EXTERN MOUNTED N 512 4096 1048576 512000 154640 0 154640 0 N DATA2.
EXTERN MOUNTED N 512 4096 1048576 972800 33915 0 33915 0 N GRAND.
NORMAL CLIMB N 512 4096 1048576 920308 OF NTA 305895 153600 76147 0 N SMALL.

I don't know if this will solve the problem, but perhaps that it was tyring:

ALTER DISKGROUP SMALL CHECK REPAIRS;

Redundancy of the Normal ASM - three stores, three groups of failure

Hello
I have a question about groups of failure in ASM. I have an ASM diskgroup with normal redundancy and records of three different preparations. Each storage disks are in separate groups of failure (see screen below). I know what ASM allocates to a point as it allocates a copy of copy and the primary mirror and mirror copy is placed on a different disk that is part of a group of different failure. And it is understood for the configuration with two storage (or controllers) and two different groups of failure. But what with configuration where are three storages and failure groups? My question is: If I failed three groups if new extensions are allocated are mirrored are placed on the other two discs are it is a part of a group of different failure? Or maybe this kind of configuration (with three groups of normal redundancy ASM failure) is not supported?

I know what ASM allocates to a point as it allocates a copy of copy and the primary mirror and mirror copy is placed on a different disk that is part of a group of different failure. And it is understood for the configuration with two storage (or controllers) and two different groups of failure. But what with configuration where are three storages and failure groups? My question is: if I have three groups of failure, if new extensions are allocated are mirrored are placed on the other two discs are it is a part of a group of different failure? Or maybe this kind of configuration (with three groups of normal redundancy ASM failure) is not supported?

No matter how much you failgroup. Normal redundancy requires at least 2 Failgroup.

Oracle will allocate primary measure in a failgroup and place the mirror of the scopes in an another failgroup.

The order does not matter since you always have a copy in a different failgroup.

See example below (d = data extended)

FG1 |   FG2 | FG3

========|===============|=========

d1      |   d1_copy:

|   d2          | d2_copy

d3_copy |               | d3

When you create a Diskgroup without specifying the failgroup, Oracle will automatically create a failgroup to each diskgroup. So, if you create a normal with normal redundancy Diskgroup and ASMDISK 10, ASM will create 10 failgroups.

You have 3 warehouses and 3 Failgroup

If you loss storage (h/f) ASM will tolerate because you measure mirror in any other failgroup (h, l, square).

If you loss both storage (h/f) or two different storage disk/controller at the same time ASM will not tolerate. (Need to restore a backup database)

Your point of failure: you must make sure that the two storages/controllers/disks will still be available.

If your concern is: can I have a situation where two storage can do fail (or cut) at the same time. Then, you need high redundancy, because this configuration will tolerate you two storages loss (h/f) at the same time and Diskgroup will remain active.

Syntax to drop several disks in a single command ASM

Hello
We have 11.2.0.2 with 2 RAC on AIX 7.1 knots. We have the starts in ASM with NORMAL redundancy and the diskgroup has 100 (50 for a failgroup) and 50 for an another failgroup discs.
We will drop 10 discs (5 a failgroup) and 5 from other failgroup since this diskgroup, so that all failgroups have the same number of disks (and sizes also).
So, I need the syntax to drop all ASM 10 of the same diskgroup disks in a single request. Could help me in this area, please?
I can try to use 10 commands, one for each disc to give up but, after the execution of each command/disc, the operation of rate rebalancing will take place and that will make us wait until the re - balance finish to execute the next command in the drop. To avoid time taking orders 10 running one by one, I would drop them all in a single command.
for example, the discs that we will give up are below:
Failgroup: FG1
PATH NAME
----------------------- ---------------------
/ dev/DATAM_L0203_ORCLFG1 NAME ORCL_DATOS_0150
/ dev/DATAM_L0204_ORCLFG1 NAME ORCL_DATOS_0151
/ dev/DATAM_L0205_ORCLFG1 NAME ORCL_DATOS_0152
/ dev/DATAM_L0206_ORCLFG1 NAME ORCL_DATOS_0153
/ dev/DATAM_L0207_ORCLFG1 NAME ORCL_DATOS_0154
Failgroup: FG2
PATH NAME
----------------------- ---------------------
/ dev/DATAL_L0203_ORCLFG2 NAME ORCL_DATOS_0184
/ dev/DATAL_L0204_ORCLFG2 NAME ORCL_DATOS_0184
/ dev/DATAL_L0205_ORCLFG2 NAME ORCL_DATOS_0184
/ dev/DATAL_L0206_ORCLFG2 NAME ORCL_DATOS_0184
/ dev/DATAL_L0207_ORCLFG2 NAME ORCL_DATOS_0184
Thank you very much

for example

alter diskgroup diskgroup_name drop disk ' / dev/oracle/disk197 ',' oracle/dev/disk198 ',' oracle/dev/disk199 ".

Another good resource is lower. You can also use the names of disk instead of paths

ORACLE-BASE - Automatic Storage Management (ASM) in Oracle Database 10g

Voting Quorum failgroup or regular failgroup files location?

About the notion of quorum failgroup ORACLE writes:
QUORUM of discs, or in groups of lack of quorum, cannot contain all database files,
(OCR) Oracle Cluster registry, or dynamic volumes. However, the QUORUM disks
can contain the file with voting for synchronization of Cluster Services (CSS). Oracle ASM
whenever files disk quorum uses or groups failed quorum for the vote
possible.
To sum up, I think that is the difference between a regular failgroup and a quorum quorum failgroup failgroup can only contain files of voice and an ordinary one can contains several types of files.
So I don't see any advantage to place files with right to vote on a quorum failgroup on a regular. Why Oracle has introduced the notion of quorum failgroup?
Thanks in advance.

Why Oracle has introduced the notion of quorum failgroup?

You must configure an odd number of disks with right to vote because the vote of the files are concerned, a node must be able to access more than half of the files with the right to vote at any time (simple majority). In order to be able to tolerate failure of n files in vote, need at least 2n + 1 configured. (n = number of files with voting rights) for the cluster.

If you lose 1/2 or more of all your disks with right to vote, then nodes get evicted from the cluster, or nodes to expel from the cluster.

For this reason when using Oracle for the redundancy of your discs with voting rights, Oracle recommends that customers use disks of 3 or more voting.

If you use only a 1 H/W storage and it is fail. Together the cluster falls down including all the voting disk is not serious the number configured.

The problem in an extended cluster configuration (Extended RAC) is that most of the facilities use only two storage systems (one on each site), which means that the site that hosts the majority of voting records is a potential single point of failure for the entire cluster. If the storage or the site where the files of n + 1 vote is configured fails, the entire cluster will go down, because Oracle Clusterware will lose the majority of the files.

To avoid a complete cluster failure, Oracle will support a third vote file on a cheap lowend, standard NFS mounted device somewhere in the network. Oracle recommends the file NFS vote on a dedicated server, which belongs to a production environment.

Thus, you will create a file on NFS "cooked leader" (as a disk) and present to the DSO. From this point of ASM does not know that ASMDISK between the network (wan) and it's a "cooked" file

Then, you must mark this ASMDISK as QUORUM, because Oracle will use this ASMDISK only to store the VOTEDISK. This will prevent him causing problem perfomance or dataloss store data (such as data files).

ASM with two SAN.

We are in a phase of re-architecture of our databases and all recently, we had the 4th SAN blip since a SAN has existed in our shop.
We are contemplating having two different SEM (maybe even from different vendors) to remove the single point of failure. Yes, our SAN was sold as a' double' and could never break SAN. BUT still, it shares the same firmware that of course after a firmware upgrade blew his brain when he was trying a failure more leaving us with a 'brown' failure (hum down half of the systems, a quarter in a State of funny and a quarter). 4 outages, 3 different brands of SAN.
I read some stuff on ASM but am not finding a clear answer, I can mirror all data flows to our Oracle for two different SAN databases so that doesn't break 1 SAN, SAN 2 takes over without any loss of service? Or would still need some Dataguard or something to make it work?
Thanks for any answers in advance.
Paul.

Yes you can do it with the installation of the ASM diskgroup as normal dismissal. Explain, you create two failgroups has a single call and another call B. In A failgroup you would put all the SAN disk/LUN has and in failgroup B you would put all the disk/LUN SAN B.

We had the same problem with a SAN failure we have converted our group of ASM disks in normal redundancy of questions the firm failure.

If you send me your email, I can send you a document I created during our tests, so that you can get more understand the possible configuration.

How to take database backup ASM/Instance?
Hello

I'm new with ASM. We take ASM/instance of database backup.

can we have the idea to backup ASM?

1. what components should be saved as database/Instance ASM / ASM all files?

Please do the needful.

Thank you
Nitin
Hello Nitin,

First of all, you must understand that the RDBMS & ASM instance is different but yes, both are running on the same computer.

ASM includes essentially two things: ASM instance (1) and the storage of the DSO (2).

(1) ASM instance
------------------------

That's just an instance when we do not backup but Yes if you want to keep the ASM instance configuration file then just follow these steps:

[grid@host01 ~] $. oraenv
ORACLE_SID = [+ ASM1]? + ASM1
The basic Oracle for ORACLE_HOME=/u01/app/11.2.0/grid is/u01/app/grid

SQL > create pfile='/home/grid/init+ASM1.ora' of spfile;

Created file.

(2) ASM STORAGE
-------------------------

-Storage ASM includes essentially ASM starts, namely new set of disks.

-Whenever we do not create ASM diskgroup diskgroup contains still three things:

(a) disc ASM
(b) models and metadata
(c) the ASM files (essentially datafile or all database files)

-We take backup of two things on three things in ASM diskgroup:

(1) ASM files - with RMAN because these are files of database.
(2) ASM diskgroup models & metadata - with the MD_BACKUP of ASMCMD command.

Now, MD_BACKUP will create a backup as your specified location file and this file will includes all models and metadata of the diskgroup. Benefits of taking diskgroup metadata are, if we lost the diskgroup, so we do not worry some details configuration command MD_RESTORE use to recreate the diskgroup with the same configuration. But remember that it does not restore the data file or any other file that was there on the diskgroup going to use RMAN to restore the missing files.

See the example:

ASMCMD > lsdg

State Type sector Rebal to Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files name of the block
EXTERN MOUNTED N 512 4096 1048576 11742 11643 0 11643 0 N ABC /.
NORMAL CLIMB N 512 4096 1048576 15656 10661 1259 4701 0 N DATA.
EXTERN MOUNTED N 512 4096 1048576 15656 13874 0 13874 0 N FRA.
ASMCMD >
>

ASMCMD >/home/grid/data_backup_file - G DATA md_backup
Group of disk to save metadata: DATA
Path to current directory alias: cluster01
Path to current directory alias: ORCL
Path to current directory alias: ORCL/fichier_parametres
Path to current directory alias: ORCL/DATA file
Current directory alias path: cluster01/OCRFILE
Path to current directory alias: ORCL/CONTROLFILE
Path to current directory alias: ORCL/TEMPFILE
Path to current directory alias: ORCL/ONLINELOG
Current directory alias path: cluster01/ASMPARAMETERFILE
ASMCMD >

* vim # / home/grid/data_backup_file *.

@diskgroup_set =)
{
"ATTRINFO"-ONLINE {}
"MODEL. OCRBACKUP. REDUNDANCY '-ONLINE 18',
"MODEL. FICHIER_PARAMETRES. MIRROR_REGION '-ONLINE '0',
"MODEL. TEMPORARY FILE. REDUNDANCY '-ONLINE 18',
"MODEL. TEMPORARY FILE. MIRROR_REGION '-ONLINE '0',
"MODEL. FICHIER_PARAMETRES. REDUNDANCY '-ONLINE 18',
"SECTOR_SIZE"-ONLINE '512',
"MODEL. DATAGUARDCONFIG. REDUNDANCY '-ONLINE 18',
' ACCESS_CONTROL. UMASK '-ONLINE '066'.
"MODEL. ASM_STALE. STRIPE '-ONLINE '0',
"MODEL. ARCHIVELOG. STRIPE '-ONLINE '0',
"MODEL. DATAGUARDCONFIG. PRIMARY_REGION '-ONLINE '0',
"MODEL. OCRBACKUP. STRIPE '-ONLINE '0',
"MODEL. DATA FILE. STRIPE '-ONLINE '0',
"AU_SIZE"-ONLINE '1048576',
"MODEL. ASMPARAMETERFILE. STRIPE '-ONLINE '0',
"MODEL. TRACK CHANGES. PRIMARY_REGION '-ONLINE '0',
"MODEL. CONTROLFILE. REDUNDANCY '-ONLINE 19',
"MODEL. FLASHFILE. STRIPE '-ONLINE '0',
"MODEL. BACKUPSET. PRIMARY_REGION '-ONLINE '0',
"MODEL. ARCHIVELOG. PRIMARY_REGION '-ONLINE '0',
"MODEL. TRACK CHANGES. STRIPE '-ONLINE '0',
"MODEL. ONLINELOG. PRIMARY_REGION '-ONLINE '0',
"MODEL. TRACK CHANGES. REDUNDANCY '-ONLINE 18',
"MODEL. BACKUPSET. STRIPE '-ONLINE '0',
"MODEL. OCRFILE. MIRROR_REGION '-ONLINE '0',
"DISK_REPAIR_TIME' => '3.6 h."
"MODEL. AUTOBACKUP. REDUNDANCY '-ONLINE 18',
"MODEL. DUMPSET. REDUNDANCY '-ONLINE 18',
"MODEL. RETURN OF FLAME. MIRROR_REGION '-ONLINE '0',
"MODEL. DUMPSET. MIRROR_REGION '-ONLINE '0',
"MODEL. DUMPSET. PRIMARY_REGION '-ONLINE '0',
"MODEL. ASM_STALE. REDUNDANCY '-ONLINE 19',
"MODEL. RETURN OF FLAME. PRIMARY_REGION '-ONLINE '0',
"MODEL. CONTROLFILE. STRIPE '-ONLINE 1',
"MODEL. DATA FILE. REDUNDANCY '-ONLINE 18',
"MODEL. XTRANSPORT. REDUNDANCY '-ONLINE 18',
"MODEL. AUTOBACKUP. PRIMARY_REGION '-ONLINE '0',
"MODEL. CONTROLFILE. MIRROR_REGION '-ONLINE '0',
"MODEL. DATA FILE. PRIMARY_REGION '-ONLINE '0',
"MODEL. ASMPARAMETERFILE. REDUNDANCY '-ONLINE 18',
"MODEL. FLASHFILE. MIRROR_REGION '-ONLINE '0',
"MODEL. ASM_STALE. MIRROR_REGION '-ONLINE '0',
"MODEL. RETURN OF FLAME. REDUNDANCY '-ONLINE 18',
"MODEL. DATAGUARDCONFIG. STRIPE '-ONLINE '0',
"CELL. SMART_SCAN_CAPABLE'-ONLINE 'FALSE. '
"TEMPLATE_VERSION"-ONLINE '186646528',
"MODEL. FICHIER_PARAMETRES. STRIPE '-ONLINE '0',
"MODEL. DATA FILE. MIRROR_REGION '-ONLINE '0',
"MODEL. FICHIER_PARAMETRES. PRIMARY_REGION '-ONLINE '0',
"MODEL. BACKUPSET. MIRROR_REGION '-ONLINE '0',
"MODEL. OCRBACKUP. MIRROR_REGION '-ONLINE '0',
"MODEL. ONLINELOG. REDUNDANCY '-ONLINE 18',
"MODEL. ASMPARAMETERBAKFILE. STRIPE '-ONLINE '0',
' ACCESS_CONTROL. PERMIT TO '-ONLINE 'FALSE. '
"MODEL. DATAGUARDCONFIG. MIRROR_REGION '-ONLINE '0',
"MODEL. TEMPORARY FILE. PRIMARY_REGION '-ONLINE '0',
"COMPATIBLE. RDBMS '-ONLINE '10.1.0.0.0'.
"MODEL. FLASHFILE. PRIMARY_REGION '-ONLINE '0',
"MODEL. ONLINELOG. MIRROR_REGION '-ONLINE '0',
"MODEL. FLASHFILE. REDUNDANCY '-ONLINE 18',
"MODEL. OCRBACKUP. PRIMARY_REGION '-ONLINE '0',
"MODEL. OCRFILE. STRIPE '-ONLINE '0',
"MODEL. AUTOBACKUP. MIRROR_REGION '-ONLINE '0',
"MODEL. ASM_STALE. PRIMARY_REGION '-ONLINE '0',
"MODEL. ASMPARAMETERBAKFILE. PRIMARY_REGION '-ONLINE '0',
"MODEL. XTRANSPORT. PRIMARY_REGION '-ONLINE '0',
"MODEL. DUMPSET. STRIPE '-ONLINE '0',
"MODEL. TEMPORARY FILE. STRIPE '-ONLINE '0',
"MODEL. OCRFILE. PRIMARY_REGION '-ONLINE '0',
"MODEL. ONLINELOG. STRIPE '-ONLINE '0',
"MODEL. ARCHIVELOG. REDUNDANCY '-ONLINE 18',
"MODEL. OCRFILE. REDUNDANCY '-ONLINE 18',
"MODEL. ARCHIVELOG. MIRROR_REGION '-ONLINE '0',
"MODEL. ASMPARAMETERFILE. MIRROR_REGION '-ONLINE '0',
"MODEL. RETURN OF FLAME. STRIPE '-ONLINE '0',
"MODEL. CONTROLFILE. PRIMARY_REGION '-ONLINE '0',
"MODEL. XTRANSPORT. MIRROR_REGION '-ONLINE '0',
"MODEL. BACKUPSET. REDUNDANCY '-ONLINE 18',
"MODEL. ASMPARAMETERBAKFILE. REDUNDANCY '-ONLINE 18',
"MODEL. XTRANSPORT. STRIPE '-ONLINE '0',
"MODEL. TRACK CHANGES. MIRROR_REGION '-ONLINE '0',
"COMPATIBLE. ASM '-ONLINE '11.2.0.0.0'.
"MODEL. ASMPARAMETERBAKFILE. MIRROR_REGION '-ONLINE '0',
"MODEL. ASMPARAMETERFILE. PRIMARY_REGION '-ONLINE '0',
"MODEL. AUTOBACKUP. STRIPE'-'0' ONLINE
},
"DISKSINFO"-ONLINE {}
"ASMDISK02"-ONLINE {}
"ASMDISK02"-ONLINE {}
"TOTAL_MB"-ONLINE '3914',
"FAILGROUP" => "ASMDISK02."
"NAME" => "ASMDISK02."
"DGNAME"-ONLINE "DATA."
'PATH' => 'ORCL:ASMDISK02 '.
}
},
"ASMDISK01"-ONLINE {}
"ASMDISK01"-ONLINE {}
"TOTAL_MB"-ONLINE '3914',
"FAILGROUP" => "ASMDISK01."
"NAME" => "ASMDISK01."
"DGNAME"-ONLINE "DATA."
'PATH' => 'ORCL:ASMDISK01 '.
}
},
"ASMDISK04"-ONLINE {}
"ASMDISK04"-ONLINE {}
"TOTAL_MB"-ONLINE '3914',
"FAILGROUP" => "ASMDISK04."
"NAME" => "ASMDISK04."
"DGNAME"-ONLINE "DATA."
'PATH' => 'ORCL:ASMDISK04 '.
}
},
"ASMDISK03"-ONLINE {}
"ASMDISK03"-ONLINE {}
"TOTAL_MB"-ONLINE '3914',
"FAILGROUP" => "ASMDISK03."
"NAME" => "ASMDISK03."
"DGNAME"-ONLINE "DATA."
'PATH' => 'ORCL:ASMDISK03 '.
}
}
},
"DGINFO"-ONLINE {}
"DGTORESTORE"-ONLINE 0
"DGCOMPAT"-ONLINE ' 11.2.0.0.0. "
"DGNAME"-ONLINE "DATA."
"DGDBCOMPAT"-ONLINE ' 10.1.0.0.0. "
"DGTYPE"-ONLINE "NORMAL."
"DGAUSZ"-ONLINE '1048576'
},
"ALIASINFO"-ONLINE {}
'6' => {
"DGNAME"-ONLINE "DATA."
'LEVEL'-ONLINE 1
"ALIASNAME"-online "cluster01/ASMPARAMETERFILE"
'REFERENCE_INDEX'-'16777322' ONLINE
},
'3' => {
"DGNAME"-ONLINE "DATA."
'LEVEL'-ONLINE 1
"ALIASNAME" => "ORCL/CONTROLFILE.
'REFERENCE_INDEX'-'16777534' ONLINE
},
'7' => {
"DGNAME"-ONLINE "DATA."
'LEVEL'-ONLINE 1
"ALIASNAME" => "ORCL/FICHIER_PARAMETRES,"
'REFERENCE_INDEX'-'16777693' ONLINE
},
'2' => {
"DGNAME"-ONLINE "DATA."
'LEVEL'-ONLINE 1
"ALIASNAME" => "ORCL/ONLINELOG,"
'REFERENCE_INDEX'-'16777587' ONLINE
},
'8' => {
"DGNAME"-ONLINE "DATA."
'LEVEL'-ONLINE 1
"ALIASNAME"-online "cluster01/OCRFILE"
'REFERENCE_INDEX'-'16777375' ONLINE
},
'1' => {
"DGNAME"-ONLINE "DATA."
'LEVEL'-ONLINE 0
"ALIASNAME"-online "cluster01."
'REFERENCE_INDEX'-'16777269' ONLINE
},
'4' => {
"DGNAME"-ONLINE "DATA."
'LEVEL'-ONLINE 1
"ALIASNAME" => ORCL/DATA FILE"."
'REFERENCE_INDEX'-'16777481' ONLINE
},
'0' => {
"DGNAME"-ONLINE "DATA."
'LEVEL'-ONLINE 0
"ALIASNAME" => "ORCL".
'REFERENCE_INDEX'-'16777428' ONLINE
},
'5' => {
"DGNAME"-ONLINE "DATA."
'LEVEL'-ONLINE 1
"ALIASNAME" => "ORCL/TEMPFILE"
'REFERENCE_INDEX'-'16777640' ONLINE
}
},
'TEMPLATEINFO'-ONLINE {}
'11' => {}
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE 'ROUGH. "
'TEMPNAME' => 'AUTOBACKUP.
"REDUNDANCY"-ONLINE "MIRROR."
'SYSTEM' => 'Y '.
},
'7' => {
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE 'ROUGH. "
"TEMPNAME' => 'ASMPARAMETERFILE."
"REDUNDANCY"-ONLINE "MIRROR."
'SYSTEM' => 'Y '.
},
'2' => {
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE 'ROUGH. "
"TEMPNAME' => 'ARCHIVELOG."
"REDUNDANCY"-ONLINE "MIRROR."
'SYSTEM' => 'Y '.
},
'17' => {}
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE 'ROUGH. "
"TEMPNAME' => 'OCRBACKUP."
"REDUNDANCY"-ONLINE "MIRROR."
'SYSTEM' => 'Y '.
},
'1' => {
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE 'ROUGH. "
"TEMPNAME' => 'ASM_STALE."
"REDUNDANCY"-ONLINE "HIGH."
'SYSTEM' => 'Y '.
},
'18' => {}
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE 'ROUGH. "
"TEMPNAME' => 'ONLINELOG."
"REDUNDANCY"-ONLINE "MIRROR."
'SYSTEM' => 'Y '.
},
'0' => {
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE 'ROUGH. "
'TEMPNAME' => 'DATAFILE ',.
"REDUNDANCY"-ONLINE "MIRROR."
'SYSTEM' => 'Y '.
},
'16' => {}
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE 'ROUGH. "
"TEMPNAME' => 'OCRFILE."
"REDUNDANCY"-ONLINE "MIRROR."
'SYSTEM' => 'Y '.
},
'13' => {}
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE 'ROUGH. "
"TEMPNAME'-ONLINE"TRACK CHANGES. "
"REDUNDANCY"-ONLINE "MIRROR."
'SYSTEM' => 'Y '.
},
'6' => {
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE 'ROUGH. "
"TEMPNAME' => 'ASMPARAMETERBAKFILE."
"REDUNDANCY"-ONLINE "MIRROR."
'SYSTEM' => 'Y '.
},
'3' => {
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE 'ROUGH. "
"TEMPNAME' => 'FLASHFILE."
"REDUNDANCY"-ONLINE "MIRROR."
'SYSTEM' => 'Y '.
},
'9' => {
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE 'ROUGH. "
"TEMPNAME" => "TEMPFILE"
"REDUNDANCY"-ONLINE "MIRROR."
'SYSTEM' => 'Y '.
},
'12' => {}
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE 'ROUGH. "
"TEMPNAME' => 'XTRANSPORT."
"REDUNDANCY"-ONLINE "MIRROR."
'SYSTEM' => 'Y '.
},
'14' => {}
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE 'ROUGH. "
"TEMPNAME'-ONLINE"FLASHBACK. "
"REDUNDANCY"-ONLINE "MIRROR."
'SYSTEM' => 'Y '.
},
'15' => {}
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE 'ROUGH. "
"TEMPNAME' => 'DATAGUARDCONFIG."
"REDUNDANCY"-ONLINE "MIRROR."
'SYSTEM' => 'Y '.
},
'8' => {
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE 'ROUGH. "
"TEMPNAME' => 'FICHIER_PARAMETRES."
"REDUNDANCY"-ONLINE "MIRROR."
'SYSTEM' => 'Y '.
},
'4' => {
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE "FINE."
'TEMPNAME' => 'CONTROLFILE.
"REDUNDANCY"-ONLINE "HIGH."
'SYSTEM' => 'Y '.
},
'10' => {}
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE 'ROUGH. "
"TEMPNAME' => 'BACKUPSET."
"REDUNDANCY"-ONLINE "MIRROR."
'SYSTEM' => 'Y '.
},
'5' => {
"DGNAME"-ONLINE "DATA."
"STRIPE"-ONLINE 'ROUGH. "
"TEMPNAME' => 'DUMPSET."
"REDUNDANCY"-ONLINE "MIRROR."
'SYSTEM' => 'Y '.
}
}
}
);

NOTE:

To re-create the diskgroup dropped with the same restoration of the configuration of the diskgroup even with the aid of diskgroup as:

asmcmd >/home/grid/data_backup_file - full - G DATA md_restore

Hope its clear now.

Thank you

Ashish Shukla

Quorum failgroup
Hello.
I created diskgroup with redundancy normal without specifying any failgroups and correctly migrated files in the diskgroup vote. All failgroups are normal. Then, what is "quorum failgroup" and when it should be used?
Hello

1-how votedisk is stored on ASM Diskgroup?
Discs with voting rights are placed in the header of the disk of an ASM diskgroup. The number of disks with voting rights is based on the diskgroup redundancy:
External (no mirroring) = 1 votedisk; Normal = 3 votedisk; High redundancy (triple mirrored) = 5 votedisk;
Oracle Clusterware will store the votedisk disk within a disk group that contains the files to vote.

However OCR however is saved as a normal (as any a tablespace data file) of the file inside the ASM and therefore "inherits" the diskgroup redundancy.
So while you see only 1 file, the file blocks are reflected accordingly (double or triple (High)).

Vote records can only reside in a diskgroup. You can't create another disc to vote in a separate DG.

2-how well votedisk must be configured?
You must configure an odd number of disks with right to vote because the vote of the files are concerned, a node must be able to access more than half of the files with the right to vote at any time (simple majority). In order to be able to tolerate failure of n files in vote, need at least 2n + 1 configured. (n = number of files with voting rights) for the cluster.

If you lose 1/2 or more of all your disks with right to vote, then nodes get evicted from the cluster, or nodes to expel from the cluster.
For this reason when using Oracle for the redundancy of your discs with voting rights, Oracle recommends that customers use disks of 3 or more voting.

3 - Why use voting Quorum disk?

If you use only a 1 H/W storage and it is fail. Together the cluster falls down including all the voting disk is not serious the number configured.

The problem in a stretch cluster configuration, is that most of the facilities use only two storage systems (one on each site), which means that the site that hosts the majority of voting records is a potential single point of failure for the entire cluster. If the storage or the site where the files of n + 1 vote is configured fails, the entire cluster will go down, because Oracle Clusterware will lose the majority of the files.
To avoid a complete cluster failure, Oracle will support a third vote file on a cheap lowend, standard NFS mounted device somewhere in the network. Oracle recommends the file NFS vote on a dedicated server, which belongs to a production environment.

Thus, you will create a file on NFS "cooked leader" (as a disk) and present to the DSO. From this point of ASM does not know that ASMDISK between the network (wan) and it's a "cooked" file
Then, you must mark this ASMDISK as QUORUM, because Oracle will use this ASMDISK only to store the VOTEDISK. This will prevent him causing problem perfomance or dataloss store data (such as data files).

http://levipereira.WordPress.com/2012/01/11/explaining-how-to-store-OCR-voting-disks-and-ASM-SPFile-on-ASM-diskgroup-RAC-or-RAC-extended/

storage type ASM
Hi all
database Oracle ASM with RAC RHEL 5 11g.2

I know there are 3 type of mirror 1-high three
2-normal 2 mirror
3-low no mirror on the file,

can you please share with me how to get all the details of my storage system?
Yes, you are right. External is your DATA Diskgroup isn't any failgroup, this means do not mirror.

ASM disk add query
Hello

Suppose I created one using diskgroup

CREATE DISKGROUP disk_group_1 NORMAL REDUNDANCY
FAILGROUP failure_group_1 DRIVE
"diska1/devices / ' NAME diska1,.
"diska2/devices /" NAME diska2
FAILGROUP failure_group_2 DRIVE
"diskb1/devices / ' NAME diskb1,.
"diskb2/devices / ' NAME diskb2;

now, I want to add more diskgroup disc, then we can use

ALTER DISKGROUP disk_group_1 add DISK
' / devices/disk * 3',

now my question is

(1) in which the disc failgroup * 3 will be added?
(2) how the ican maintain eqal no disc with the same size availble in each FAILGROUP for mirroring of data or redundancy of the ASM?

Please guide.
now, I want to add more diskgroup disc, then we can use

ALTER DISKGROUP disk_group_1 add DISK
' / devices/disk * 3',

It should be like:

alter diskgroup disk_group_1 add failgroup drive '';

Reference http://www.idevelopment.info/data/Oracle/DBA_tips/Automatic_Storage_Management/ASM_12.shtml

ASM HA
Hi dear experts!

I have the Infrastructure of grid 11 GR 2, RAC 2 node installed with DSO. (OEL 5.7 UEK)
ASM is configured with 3 diskgroup (normal redundancy). First diskgroup contain
5 virtual disks, and each disk is assigned its own failure group. I have also two failure
Group each have 3 virtual drives (Oracle VM 3.0.3). Virtual disks are connected to the server via NFS.
Currently I'm testing ASM behavior in a situation when this group of failure drops.
As my ASM disks are virtual and each group of failure (3 v. disks) are located in the separate machine
I simulate crash records by giving up the network interface. So after I kill the connection between
Linux and storage (NFS) my DB (with 2 groups of failure) broke down. When connection
is has become available Linux and ASM instance without rebooting can work with discs and
I *(srvctl start database-d test) * manually start DB.
My question is how can I configure (if Oracle supports of course)
ASM that DB continues to operate even after one group of disks are no longer available.
Can I set something up ASM HA?

all ideas are welcome

. / Thank you
Hello

If I understand correctly ASM does not tolerate the disk failure in this configuration, but I don't know how can this be because my
CREATE DISKGROUP statement is true... or not?

Your statament is righ... but your configuration is wrong... You can remove the diskgroup TEST and recreate with this statement (only for test purposes)
Or
You can remedy this by performing the steps above...
```
ALTER DISKGROUP TEST  DROP DISK 'DG0_ASM0' REBALANCE POWER 5 WAIT;

ALTER DISKGROUP TEST ADD FAILGROUP CONTROLLER1 DISK '/dev/oracleasm/disks/DG0_ASM0' NAME DG0_ASM0 ;

ALTER DISKGROUP TEST  DROP DISK 'DG0_ASM1' REBALANCE POWER 5 WAIT;

ALTER DISKGROUP TEST ADD FAILGROUP CONTROLLER1 DISK '/dev/oracleasm/disks/DG0_ASM1' NAME DG0_ASM1;

ALTER DISKGROUP TEST  DROP DISK 'DG1_ASM2' REBALANCE POWER 5 WAIT;

ALTER DISKGROUP TEST ADD FAILGROUP CONTROLLER2 DISK '/dev/oracleasm/disks/DG1_ASM2' NAME DG1_ASM2;
```
So, you can try your test failures.

Levi Pereira

ASM failgroup

Similar Questions

Maybe you are looking for