recommendation of the number of ASM disks on 11 GR 2

Similar Questions

• How to solve the problem of 'ASM disk group is inaccessible' slave VM rac2?

  People,
  
  Hello. I want to install Oracle 11 g RAC 2 using 2 virtual machines (VM main rac1 and rac2 VM slave) with Oracle Linux 5.6 according to the website http://appsdbaworkshop.blogspot.com/2011/10/11gr2-rac-on-linux-56-using-vmware.html
  
  Grid and data base RAC have been installed successfully for VMS rac1 and rac2.
  I use the slave rac2 VM test data grid and CARS because rac1 disk is full.
  The problem is that the OCR file is not available or currupted in the rac2 VM slave. To know his reasons, I check permission on disc ocr as below:
  
  [ora11g@rac2 bin] $ pwd
  / U02/11g_db/ora11g/racdb/bin
  
  [ora11g@rac2 bin] $ srvctl start asm
  
  RPRC-1070: could not verify if the ora.asm resource is registered
  Cannot communicate with crsd
  
  [ora11g@rac2 rac2] $ pwd
  / u01/app/Grid/log/Rac2
  
  [ora11g@rac2 rac2] $ cat alertrac2.log
  
  Last lines:
  [/ u01/app/grid/bin/cssdagent (5779)] CRS - 5822:Agent ' / u01/app/grid/bin/cssdagent_root "disconnected from the server. Details at (: CRSAGF00117 :) in u01/app/grid/log/rac2/agent/ohasd/oracssdagent_root/oracssdagent_root.log.)
  2012-03-20 13:44:55.914
  [ohasd (5149)] CRS-2112: the service ODE started on node rac2.
  2012-03-20 13:44:58.588
  [ohasd (5149)] CRS - 8017:location: / etc/oracle/lastgasp has 72 Advisory reboot log files, 0 were announced and 0 errors
  2012-03-20 13:45:07.555
  [ohasd (5149)] CRS - 2772:Server "rac2" was awarded to 'Free' the pool.
  2012-03-20 13:45:10.108
  [ohasd (5149)] CRS-2302: failed to get profile negotiators. Error CLSGPNP_NO_DAEMON (the demon GPNPD does not work).
  2012-03-20 13:45:10.251
  [gpnpd (5368)] CRS - 2328:GPNPD began the rac2 node.
  2012-03-20 13:45:13.037
  [cssd (5443)] CRS - 1713:CSSD daemon is launched in cluster mode
  2012-03-20 13:45:37.132
  [cssd (5443)] CRS - 1707:Lease acquisition for node rac2 number 2 completed
  2012-03-20 13:45:37.727
  [cssd (5443)] CRS - 1605:CSSD file to vote is online: ORCL:ASMDISK3; details in u01/app/grid/log/rac2/cssd/ocssd.log.
  2012-03-20 13:45:37.986
  [cssd (5443)] CRS - 1625:Node rac1, number 1, was closed manually
  2012-03-20 13:45:37.991
  [cssd (5443)] CRS - 1605:CSSD file to vote is online: ORCL:ASMDISK2; details in u01/app/grid/log/rac2/cssd/ocssd.log.
  2012-03-20 13:45:38.633
  [cssd (5443)] CRS - 1605:CSSD file to vote is online: ORCL:ASMDISK1; details in u01/app/grid/log/rac2/cssd/ocssd.log.
  2012-03-20 13:45:56.956
  [cssd (5443)] CRS - 1601:CSSD Reconfiguration is complete. Active nodes are rac2.
  2012-03-20 13:46:00.557
  [ctssd (5834)] CRS-2403: the time synchronization Service on rac2 host Cluster is in observer mode.
  2012-03-20 13:46:00.576
  [ctssd (5834)] CRS-2407: the new Cluster Time Synchronization Service reference node is host rac2.
  2012-03-20 13:46:01.000
  [ctssd (5834)] CRS-2401: time synchronization Service Cluster started on host rac2.
  2012-03-20 13:46:11.097
  [crsd (5856)] CRS-1013: the location of the OCR in ASM disk group is inaccessible. Details in u01/app/grid/log/rac2/crsd/crsd.log.
  2012-03-20 13:46:12.085
  [ohasd (5149)] CRS - 2765:Resource 'ora.crsd' failed on the server "rac2.
  2012-03-20 13:46:13.338
  [crsd (5925)] CRS-1013: the location of the OCR in ASM disk group is inaccessible. Details in u01/app/grid/log/rac2/crsd/crsd.log.
  2012-03-20 13:46:14.217
  [ohasd (5149)] CRS - 2765:Resource 'ora.crsd' failed on the server "rac2.
  2012-03-20 13:46:15.438
  [crsd (5940)] CRS-1013: the location of the OCR in ASM disk group is inaccessible. Details in u01/app/grid/log/rac2/crsd/crsd.log.
  2012-03-20 13:46:16.313
  [ohasd (5149)] CRS - 2765:Resource 'ora.crsd' failed on the server "rac2.
  2012-03-20 13:46:17.539
  [crsd (5955)] CRS-1013: the location of the OCR in ASM disk group is inaccessible. Details in u01/app/grid/log/rac2/crsd/crsd.log.
  2012-03-20 13:46:18.392
  [ohasd (5149)] CRS - 2765:Resource 'ora.crsd' failed on the server "rac2.
  2012-03-20 13:46:19.537
  [crsd (5988)] CRS-1013: the location of the OCR in ASM disk group is inaccessible. Details in u01/app/grid/log/rac2/crsd/crsd.log.
  2012-03-20 13:46:20.468
  [ohasd (5149)] CRS - 2765:Resource 'ora.crsd' failed on the server "rac2.
  2012-03-20 13:46:22.636
  [crsd (6003)] CRS-1013: the location of the OCR in ASM disk group is inaccessible. Details in u01/app/grid/log/rac2/crsd/crsd.log.
  2012-03-20 13:46:23.615
  [ohasd (5149)] CRS - 2765:Resource 'ora.crsd' failed on the server "rac2.
  2012-03-20 13:46:24.781
  [crsd (6022)] CRS-1013: the location of the OCR in ASM disk group is inaccessible. Details in u01/app/grid/log/rac2/crsd/crsd.log.
  2012-03-20 13:46:25.713
  [ohasd (5149)] CRS - 2765:Resource 'ora.crsd' failed on the server "rac2.
  2012-03-20 13:46:26.885
  [crsd (6037)] CRS-1013: the location of the OCR in ASM disk group is inaccessible. Details in u01/app/grid/log/rac2/crsd/crsd.log.
  2012-03-20 13:46:27.799
  [ohasd (5149)] CRS - 2765:Resource 'ora.crsd' failed on the server "rac2.
  2012-03-20 13:46:29.021
  [crsd (6052)] CRS-1013: the location of the OCR in ASM disk group is inaccessible. Details in u01/app/grid/log/rac2/crsd/crsd.log.
  2012-03-20 13:46:29.925
  [ohasd (5149)] CRS - 2765:Resource 'ora.crsd' failed on the server "rac2.
  2012-03-20 13:46:31.136
  [crsd (6067)] CRS-1013: the location of the OCR in ASM disk group is inaccessible. Details in u01/app/grid/log/rac2/crsd/crsd.log.
  2012-03-20 13:46:32.040
  [ohasd (5149)] CRS - 2765:Resource 'ora.crsd' failed on the server "rac2.
  2012-03-20 13:46:33.247
  [crsd (6082)] CRS-1013: the location of the OCR in ASM disk group is inaccessible. Details in u01/app/grid/log/rac2/crsd/crsd.log.
  2012-03-20 13:46:34.172
  [ohasd (5149)] CRS - 2765:Resource 'ora.crsd' failed on the server "rac2.
  2012-03-20 13:46:34.173
  [ohasd (5149)] CRS - 2771:Maximum attempts to restart the resource 'ora.crsd '; does not restart.
  [ora11g@rac2 rac2] $
  
  The output of alertrac2.log, we have seen disk group ASM is inaccessible. So my question is:
  
  How to solve the problem of "ASM disk group is inaccessible" in the rac2 VM slave?
  
  
  Thank you.

  user8860348 wrote:
  People,

  Hello. Thanks much for the reply.

  Yes. I put the entry "SQLNET. AUTHENTICATION_SERVICES = (NTS)"input file sqlnet.ora.

  I ran the commands below:

  [ora11g@rac2 bin] $ pwd
  / u01/app/Grid/bin

  [ora11g@rac2 bin] $ ps - ef | grep pmon

  16219 ora11g 8602-0 12:29 pts/2 00:00:00 grep pmon

  [ora11g@rac2 bin] $

  [ora11g@rac2 bin] $ export ORACLE_SID = + ASM2
  [ora11g@rac2 bin] $. / sqlplus / as sysdba

  SQL * more: Production version 11.2.0.1.0 Fri Mar 23 12:33:15 2012

  Copyright (c) 1982, 2009, Oracle. All rights reserved.

  Connect to an instance is idle.

  SQL > startup pfile = ' / u01/app/grid/dbs/pfile ".
  ORA-01031: insufficient privileges
  SQL >

  Sign in as SYSASM as

  . / sqlplus / as sysasm
  >

  As we see above shows the command $ ps - ef | grep pmon, my question is:

  First of all, are ' 16219 8602 ora11g 0 "process ID?

  Secondly, we need to kill one by one? For examples: kill-9 ora11g? Kill-9 16219?

  Laughing out loud. It's not the running process.

• ASM disk added without scan on the second node

  Hi all

  Oracle Version: 11.2.0.3

  I need a help for a problem with the addition of ASM disks.

  It is a node two CARS and a disk group was filled.

  A drive was available as UNUSED001 and so we renamed it ran scan disk and disk added to the diskgroup on node1.

  But, as we have not run scan disk on the second node, the name is still the poster as UNUSED001 and assigned to diskgroup showing as a MEMBER.

  In addition, the renamed disk shows as a MEMBER but not attributed with any diskgroup.

  Usually, when this heppens we have to restart the node to solve the problem, but would like to get idea if this can be fixed without bouncing nodes.

  I restarted node and that fixed the issue.

  Closing this thread.

  Thank you guys.

• Question about the use of size mixed with ASM disk groups

  I support a RAC 10 g 10.2.0.3 running and using ASM cluster. We currently have a group of data disks, which is 600 GB in size, consisting of 3 individual raw disk 200 GB devices. The RAC cluster runs on a server pSeries IBM using AIX 5.3
  
  I need to add more space, but the system administrator can give me only 100 GB in the new raw device. What will be the impact, if any, the addition of this feature of smaller crude disk in the same data ASM disk group? I understand that ASM is trying to "balance" the general use of each raw device. ASM still works very well, or will he constantly try to rebalance the disk group because the a raw device is only half of the other three? Any help and advice would be greatly appreciated. Thank you!

  It works, I do the same thing in a production database. What happens is, asm will distribute data on the size of the disks. 200 GB drives will get two times more data than the 100 GB drive. The downside is that it will also result in an unequal distribution of the IOPS / s: adults discs will be achieved more often.

  Bjoern

• CREATION OF THE ASM DISK

  All the
  
  I created asm disk on single instance.when autonomous system using dbca I can't find disk to stamp. I need to
  create disk dynamic disk to basic disk?
  
  init parameter file, I mentioned ASM_DISKSTRING = "e:\asmdisks\*."
  
  
  e:\asm_disks > asmtool - create e:\asm_disks\asmdisk1 512
  
  e:\asm_disks > asmtool - create e:\asm_disks\asmdisk2 512
  
  Concerning
  Belli

  Could query you v$ asm_disk and v$ asm_diskgroup if groups exist with good records?

• How card ASM disk path to the physical drive on AIX?

  Hello world
  I work on a plug-in for Oracle Enterprise Manager 10 g 2 on AIX 5.3 which monitors storage bays and supports databases in addition to the "emrep" database ASM One of the metrics of this plug-in is populated by the result of a korn shell script. Directly, the script runs on the AIX host (connected to the storage array cable CF via HBA ports) and retrieves the mapping for - disk - logical disk - LUN - ASM.
  
  Now, I was able to get the mapping to physical disk - logical disk - LUN, but could not map drive ASM. I googled a lot for no idea, but did not find the answer to this specific problem.
  
  Now, I have the list of physical disks used for the DSO by the command:
  
  LSPV
  
  hdisk0 0001c22ac8d664ca rootvg active
  hdisk1 0001c22aa51f496a Oracle active
  hdisk2 0001c22ac478263a zero active
  hdisk3 0001c22ac472549a Oracle active
  hdisk4 0001c22ac4725d6a Oracle active
  hdisk5 none None
  hdisk6 none None
  hdisk7 none None
  hdisk8 none None
  hdisk9 none None
  hdisk10 none None
  hdisk11 none None
  hdisk12 none None
  hdisk13 none None
  hdisk14 none None
  hdisk15 none None
  hdisk16 none None
  
  Hdisk5-16 discs are ASM disks and there are currently of no PVID.
  
  I also have the list of ASM disks by the command:
  
  ls-l/dev | grep oracle
  
  CRW - rw - 1 oracle dba 22, 6 12 may 00:02 asm_rd10_1a
  CRW - rw - 1 oracle dba 22, 10 Apr 21 07:27 asm_rd10_1b
  CRW - rw - 1 oracle dba 22, 7 May 09 13:53 asm_rd10_1c
  CRW - rw - 1 oracle dba 22, 8 May 09 13:53 asm_rd5_1a
  CRW - rw - 1 oracle dba 22, 4 12 may 00:02 asm_rd5_1b
  CRW - rw - 1 oracle dba 22, 9 APR 21 07:28 asm_rd5_1c
  CRW - rw - 1 oracle dba 22, 12 12 may 00:02 asm_xbb2_rd10_1a
  CRW - rw - 1 oracle dba 22: 11 Apr 24 07:34 asm_xbb2_rd10_1b
  CRW - rw - 1 oracle dba 22, 13 May 09 13:53 asm_xbb2_rd10_1c
  CRW - rw - 1 oracle dba 22, 16 12 may 00:02 asm_xbb2_rd5_1a
  CRW - rw - 1 oracle dba 22, 14 Apr 24 07:34 asm_xbb2_rd5_1b
  CRW - rw - 1 oracle dba 22, 15 May 09 13:54 asm_xbb2_rd5_1c
  
  Now, I'm looking for a way to map these two lists with each other and had no luck so far.
  Oracle provides this information somewhere in the OEM installation structure or y at - it a command in AIX that could provide a way to map the ASM disks on the physical disks?
  
  Any help on this is greatly appreciated. Thanks in advance...
  
  
  FYI: ASMLib driver is not present on the system.

  I am not familiar with aix, but I think you can get the major and minor numbers as follows:

  ls-l/dev/asm_rd_10_1a
  CRW - rw - 1 oracle dba 22, 6 12 may 00:02 asm_rd10_1a
  ls-l/dev/hdisk5
  CRW - rw - 1 root root 22, 6 12 may 00:02 hdisk5

  the numbers would be 22 and 6.

  That's just a guess, on HP - UX, it's like that, but it will be a little tricky

• 11 GR 2 Grid Infrastructure install - with normal redundancy ASM disk group requires 3 disks?

  
  Hello

  I want to install 11 GR 2 grid Infrastructure in a new environment in cluster - 2 nodes). I use the 11.2.0.4 GI Installer on Oracle Linux 6.5 x 86-64

  However when it is in the installer of GI, it comes to choose the storage Option - I choose ASM disk groups.

  Then change the path of discovery to pick up my candidate ASM disks.

  I enter the disk group name SIR give Normal redundancy, choose 2 discs of candidate and then press < next > to Setup.

  However, I gives me the message

  [INS-30510] Insufficient number of ASM disks selected

  The number of selected disks was inadequate for the level of redundancy selected

  For a disk group with redundancy level "Normal" disks at least "3" are recommended

  I always thought that Redunancy Normal required only 2 discs and high redundancy requires 3 disks?

  No idea what is gpoing?

  Thank you

  Jim

  Consult the following notes for how to move:

  Note 1638177.1 and 428681.1

  Concerning

  Thomas

• ASM disk - based SAN LUN expansion

  Hi all
  I'm learning a bit about the ASM and best practices to follow properly set up/use it at its best.
  
  Using an external FC SAN storage, if I create a logical volume with a LUN number and expose this LUN to my server ASM, I can see it properly and add it to an ASM disk group.
  
  So far so good. After that, if I develop this LUN on the external storage (using the tools), I'm not able to see the new space of the DSO. Looks like Oracle somehow "partitioned" originally the LUN when I first added it to the instance of the DSO, and after the "marking" it, even if I increase the Volume, the "expansion" is not seen.
  
  Is there a way to tell ASM as ther IS actually more space available? If I "fdisk-l", I see the amount of space on the device. But the 'blocks' are always the old value...
  
  I know that the creation of another logic unit number and adding to the disk group, there is no problem, but I would rather be able to expand an existing LUN on my external storage to create new LUNS on it all the time... Please help me understand if what I have in mind is correct or not on a best practices perspective.
  
  Thanks for any help.

  Yes you're right. Add the 20 GB lun, you can with 0 downtime and then remove the old 10GB of the diskgroup lun (assuming that you don't change the 10 GB to 20 GB :)) If you hold rebalance low power, Re-balance I/O will be even not worth the performance system IO too muchl.) But the problem here is that hesitate to use only a single lun 20 GB as the entire disk to ASM diskgroup. If you increase the number of LUNs (disks asm) even by creating separate volumes on the same physical disks you will increase the number of logical I/O paths which contributes to the homogeneity of distrubution of I/O.

  Kind regards
  Hüsnü
  http://husnusensoy.WordPress.com

• degree of parallelism and the number of files in the tablespace

  Hello
  
  I'm trying to find the relationship between the number of files in a tablespace and the degree of parallelism. because of the number of files in a tablespace effect dop in parallel query. because if several files are in the tablespace/o of the system has increased and the system became more feverable for a query parallel.
  
  But I looked in the dop formulas I can't find any settings that specify how the file is there in a tablespace. Please give me the formula for calculting dop in oracle.
  
  
  concerning
  Nick

  Hi Nick,

  It is not easy to determine the optimum degree of parallelism for the tasks of the Oracle.

  Oracle says that the best degree of parallelism for a query is based on several factors. These factors are presented in order of importance:

  -The number of processors on the server.

  -The number of physical disks located in the tables.

  -For parallelization of the partition, the number of partitions that will be available, based on the size of partition (if any).

  I can't find any settings that specify how the file is there in a tablespace.

  This is the number of physical spindles that matters, is not at the level of the tablespace.

  If I have diploma = 8, cpu_count = 8 and data are on 8 discs, there is no pretense.

  It's one of the problems with big great drives today, too few concurrency...

  I hope this helps...

  Donald K. Burleson
  Oracle Press author
  Author of "Oracle Tuning: the definitive reference".
  http://www.rampant-books.com/book_2005_1_awr_proactive_tuning.htm

• Why can't I drop the ASM disks and stop ASMLib?

  Hi, I wanted to remove the disc, but this operation has failed:
  
  1.
  
  /etc/init.d/oracleasm deletedisk DATA1
  Remove ASM disk "DATA1" [NOT]
  
  I know there is the solution to replace header ASM on a disc information
  DD if = / dev/zero of = < your_raw_device > bs = 1024 count = 100
  
  and then droping is successful
  
  but I've also seen resources who said that it should be count = 50
  
  If someone could confirm count = 100 or 50?
  
  2.
  
  In addition to this I tried to stop ASMLib and she doesn't have too:
  
  stop /etc/init.d/oracleasm
  Drop Oracle ASMLib discs: [OK]
  Close the driver Oracle ASMLib: [FAILURE]
  
  OK, so using dd will help me to get rid of the disks, but I'm worried about ASMLib in general, why can't you stop it? All instances of the ASM have been removed before. There is no software installed ASM, in addition to ASMLib.

  There are several things not clear

  1 as most of the people here you forgot to display four-digit version number, assuming that Oracle never changes, or we can guess that you are running.
  The two statements are false. To stop asmlib, you use exit oracleasm

  2 you use the root account or another account? You must use the root account

  3. Why do you not use the oracleasm command?

  ----------
  Sybrand Bakker
  Senior Oracle DBA

• 1 the ASM disk group are several DBs CARS?

  DB version: 11 GR 2
  Platform: Sun OS 5.10
  Number of nodes: 2
  
  We currently have a 2 DB RAC node called PMDB1 running with a group of disks called 1 tera bytes DG1_DATA.
  We would like to add another data base of this group.
  This DB allows the same group of disks (DG1_DATA) whose use PMDB1?

  Hi Haiti

  This DB allows the same group of disks (DG1_DATA) whose use PMDB1?

  Yes. No problem.

  An instance of ASM to the CCR can be associated with instances of the several DBs. right?

  Right

  Kind regards
  Levi Pereira

• the ASM disks can be in a different Partition for a database

  Hi all
  I have 2 datababase on the server. I save the data file on MDMDISK1 for the MDM and DWHDISK1 database to the DWH database.
  I can add/dev/sdd5, / dev/sdd6, / dev/sdd7 to DWHDG1 disk group to give more space to the DWH database.
  
  Table of Partition disk configuration
  Group name size GB ASM Disk Disk drive
  / dev/SDS (MON) 107
  / dev/sdd1 7 CRSDISK1
  / dev/sdd2 7 CRSDISK2
  / dev/SDS3 7 CRSDISK3
  / dev/SDS4 8
  / dev/sdd5 24
  / dev/SDD6 24
  / dev/sdd7 24
  / dev/sde (MON) 107
  / dev/SDE1 24 MDMDISK1 + MDMDG1
  / dev/SDE2 24 MDMDISK2
  / dev/SDE3 24 MDMDISK3
  / dev/sde4 24 MDMDISK4
  / dev/sdf (MON) 107
  / dev/SDF1 24 DWHDISK1 + DWHDG1
  / dev/sdf2 24 DWHDISK2
  / dev/SDF3 24 DWHDISK3
  / dev/sdf4 24 DWHDISK4

  user5846399 wrote:

  but I wanted insurance with people with experience as you go this drive on differnet LUN will not impede performance.

  A LUN is a logical unit - it may be a single physical disk. It may consists of 20 physical drives. If the LUN itself does not determine the performance. Performance is determined by the parts in movement under it.

  Multiple LUNS to the same diskgroup using or the volume of file system is a common practice. If this would be a problem (performance or otherwise) depends on the cloth under the LUN.

  For example, a logic unit number could be RAID5 and another logic unit number can be RAID0 + 1. Mixture of different RAID levels is not really a good idea.

  A LUN can be a storage on a San and accessible via the fiber channel. Another logic unit number could be an iScsi device, accessed through intellectual property. Mix very different storage architecture and storage protocols are not a good idea.

  A LUN can be RAID0, through fiber double channels connected to a switch, for the storage of 1 storage server. Another logic unit number can also be RAID0 and accessible through the same fiber channels and switch, but since the storage server 2. Whereby the RAID levels are the same and the storage Protocol and infrastructure the same - and that will not only make a compatible mix, but can actually increases the redundancy if you use these as disk mirrors ASM (which means that ASM can lose the server storage 1 or 2 and still works).

• Narrowing of the ASM disks

  I just tried to resize an ASM disk and although the reaction was "successful", it does not appear to have been any change.
  
  I was trying to shrink DATA_0001 from 200G to 100G. Am I missing something obvious?
  

  SQL> select group_number, name, path, os_mb, total_mb, free_mb from v$asm_disk;
  
  GROUP_NUMBER NAME                 PATH                                OS_MB   TOTAL_MB    FREE_MB
  ------------ -------------------- ------------------------------ ---------- ---------- ----------
            0                      /dev/iscsi/rman11                   20489          0          0
            0                      /dev/iscsi/rmanB11                 102398          0          0
            0                      /dev/iscsi/rman1                    20490          0          0
            0                      /dev/iscsi/vote3                      300          0          0
            0                      /dev/iscsi/vote1                      300          0          0
            0                      /dev/iscsi/rmanP11                 204805          0          0
            0                      /dev/iscsi/vote2                      300          0          0
            0                      /dev/iscsi/rmanP1                  204810          0          0
            0                      /dev/iscsi/rmanB1                  102405          0          0
            1 DATA_0000            /dev/iscsi/db1                      10245      10245      10109
            2 FRA_0000             /dev/iscsi/flshbk1                  20490      20490      20465
  
  GROUP_NUMBER NAME                 PATH                                OS_MB   TOTAL_MB    FREE_MB
  ------------ -------------------- ------------------------------ ---------- ---------- ----------
            2 FRA_0001             /dev/iscsi/flshbkR1                409605     409605     409262
            1 DATA_0001            /dev/iscsi/dbR1                    204810     204810     202297
  
  13 rows selected.
  
  SQL> alter diskgroup data resize disk 'data_0001' size 100g;
  
  Diskgroup altered.
  
  SQL> select group_number, name, path, os_mb, total_mb, free_mb from v$asm_disk;
  
  GROUP_NUMBER NAME                 PATH                                OS_MB   TOTAL_MB    FREE_MB
  ------------ -------------------- ------------------------------ ---------- ---------- ----------
            0                      /dev/iscsi/rman11                   20489          0          0
            0                      /dev/iscsi/rmanB11                 102398          0          0
            0                      /dev/iscsi/rman1                    20490          0          0
            0                      /dev/iscsi/vote3                      300          0          0
            0                      /dev/iscsi/vote1                      300          0          0
            0                      /dev/iscsi/rmanP11                 204805          0          0
            0                      /dev/iscsi/vote2                      300          0          0
            0                      /dev/iscsi/rmanP1                  204810          0          0
            0                      /dev/iscsi/rmanB1                  102405          0          0
            1 DATA_0000            /dev/iscsi/db1                      10245      10245      10004
            2 FRA_0000             /dev/iscsi/flshbk1                  20490      20490      20465
  
  GROUP_NUMBER NAME                 PATH                                OS_MB   TOTAL_MB    FREE_MB
  ------------ -------------------- ------------------------------ ---------- ---------- ----------
            2 FRA_0001             /dev/iscsi/flshbkR1                409605     409605     409262
            1 DATA_0001            /dev/iscsi/dbR1                    204810     204810     202402
  
  13 rows selected.

  The free_mb seems to have increased, but otherwise I do not see the effect of my change. Maybe I'm looking in the wrong place?
  
  I tried to restart the ASM instance, but it made no difference.
  
  After the resizing of the ASM disk, I have narrowed the disk volume in our storage array. ASM was naturally down at the time.
  
  When I tried to restart ASM I saw...
  

  SQL> startup
  ASM instance started
  
  Total System Global Area  283930624 bytes
  Fixed Size                  2158992 bytes
  Variable Size             256605808 bytes
  ASM Cache                  25165824 bytes
  ORA-15032: not all alterations performed
  ORA-15036: disk '/dev/iscsi/dbR1' is truncated

  No of my starts are mounted...
  

  SQL> select group_number, name, state from v$asm_diskgroup;
  
  GROUP_NUMBER NAME            STATE
  ------------ --------------- ---------------------------------
            0 DATA            DISMOUNTED
            0 FRA             DISMOUNTED

  Here is the log of the ASM instance alert messages...
  

  SQL> ALTER DISKGROUP ALL MOUNT
  NOTE: cache registered group DATA number=1 incarn=0x5f5e3343
  NOTE: cache began mount (not first) of group DATA number=1 incarn=0x5f5e3343
  NOTE: cache registered group FRA number=2 incarn=0x5f5e3344
  NOTE: cache began mount (not first) of group FRA number=2 incarn=0x5f5e3344
  WARNING::ASMLIB library not found. See trace file for details.
  NOTE: Assigning number (1,0) to disk (/dev/iscsi/db1)
  NOTE: cache dismounting group 1/0x5F5E3343 (DATA)
  NOTE: dbwr not being msg'd to dismount
  NOTE: lgwr not being msg'd to dismount
  NOTE: cache dismounted group 1/0x5F5E3343 (DATA)
  NOTE: cache ending mount (fail) of group DATA number=1 incarn=0x5f5e3343
  kfdp_dismount(): 1
  kfdp_dismountBg(): 1
  NOTE: De-assigning number (1,0) from disk (/dev/iscsi/db1)
  ERROR: diskgroup DATA was not mounted
  NOTE: Assigning number (2,1) to disk (/dev/iscsi/flshbkR1)
  NOTE: Assigning number (2,0) to disk (/dev/iscsi/flshbk1)
  NOTE: cache dismounting group 2/0x5F5E3344 (FRA)
  NOTE: dbwr not being msg'd to dismount
  NOTE: lgwr not being msg'd to dismount
  NOTE: cache dismounted group 2/0x5F5E3344 (FRA)
  NOTE: cache ending mount (fail) of group FRA number=2
  incarn=0x5f5e3344
  kfdp_dismount(): 2
  kfdp_dismountBg(): 2
  NOTE: De-assigning number (2,0) from disk (/dev/iscsi/flshbk1)
  NOTE: De-assigning number (2,1) from disk (/dev/iscsi/flshbkR1)
  ERROR: diskgroup FRA was not mounted
  ORA-15032: not all alterations performed
  ORA-15036: disk '/dev/iscsi/dbR1' is truncated
  ERROR: ALTER DISKGROUP ALL MOUNT

  Clues?
  
  Thank you
  
  Steve

  Hi Steve,.

  I think what happened occurred due to certain steps in your initial procedure, a corruption of ASM header that cannot be repaired automatically more. Therefore, check if ML Note 553319.1 - ORA-15036 when to start an ASM Instance - can be used to solve your problem, too.

  Now, in order to avoid such things, I would make the following the next time:

  Stop all except 1 ASM instance.
  CHANGE Diskgorup RESIZE DISK - the disk that you want to resize.
  Wait for the rebalancing that may occur finally.
  stop this ASM instance
  change the size of the disk to the disk level
  restart all instances of the DSO.

  This seems to be the safest way to do it. A perspective HA, some optimization might be possible, I think.

  Hope that helps. Thank you
  Markus

• Installation of Oracle 11 g R2 grid does not detect the ASM disks

  Hi guys,.

  I'm trying to install Oracle 11 g R2 RAC and as part of the installation of the grid, the Setup program does not detect the ASM disks.

  Here are the outputs for some commands.

  [root@rac1 ~] # oracleasm scandisks

  Reload from disk partitions: fact

  Cleaning up stale ASM disks...

  ASM disks scanning system...

  Instantiation of disk 'ASMDATA2 '.

  Instantiation of disk 'ASMDATA1 '.

  [root@rac1 ~] # oracleasm listdisks

  ASMDATA1

  ASMDATA2

  [root@rac1 ~] # ls - ls/dev/oracleasm/disks

  Total 0

  0 brw - rw - 1 grid asmadmin 252, 3 14 May 17:18 ASMDATA1

  0 brw - rw - 1 grid asmadmin 252, 2 14 May 17:18 ASMDATA2

  I already tried to reconfigure Oracleasm (oracleasm configure - i) but no luck.

  I would be really grateful for the help here as its been a few days now and want to complete the installation as soon as possible

  Concerning

  Praveen

  Thank you Ricardo, I see now the disks after you change the path from discovery to/dev/oracleasm/disks

  

• Analyze the index on the machine of Dataguard and redundancy of ASM disks

  Dear friends,

  I have two questions regarding disc Dataguard and ASM.

  (> > 1) for best performance, periodically, we rebuild the index index and analysis analyze table. What is the best periodic steps to do to get better performance?

  I mean, first of all is rebuilding of index, is second index analysis and so on......

  (> > 2) if I run analyze the index or the table on my PRODUCTION system he replicated this effect on statndby dataguard automatic system? If so, how it is replicated?

  (> > 3) my last question related with high redundancy of the ASM disk. I have some confusion on this area.

  Let's say I have 10 disks in a diskgroup '+ DATA' and I did 'HIGH' level redundancy, means 3 way redundancy. Here I know 3-way the redundancy, it writes data on 3 discs at a time. But what of the other 7 discs. In fact, I need to know the mechanism of writing?

  -Each disc is identical to the other drive?

  -For HIGH redundancy, how many disk failure can be tolerated for any loss of data?

  Waiting for your kind reply......

  "on my PRODUCTION'---> you mean"on my FIRST.

  Yes, the data dictionary is updated when you run dbms_stats.gather% and updates data dictionary are through recovery that applies to the WAITING for more.

  NOLOGGING surgery would not be applied to the expectation (the index would be marked corrupted to the standby) unless you have set on FORCELOGGING.

  Hemant K Collette