Disk Group requires rebalance because at least one disk is low on space.

I am getting alert over OEM Grid as below.
Message=Disk Group DSKGRP_UAT_01 requires rebalance because at least one disk is low on space.
Metric=Disk Minimum Free (%) without Rebalance
I tried query with;
select GROUP_NUMBER, DISK_NUMBER ,TOTAL_MB,FREE_MB ,(FREE_MB/TOTAL_MB)*100 from v$asm_disk order by 5 desc;
to find the disk group breached the threshold.
Let me know how can i query and find each file size on ASM Disk.
Edited by: Sivaprasad S on Jun 3, 2011 3:25 AM

Try this one:
select a.group_number , a.name , b.bytes , count(*) over ( partition by a.group_number , a.file_number , a.file_incarnation) doublecount
from v$asm_alias a , v$asm_file b
where a.group_number=b.group_number and a.file_number=b.file_number and a.file_incarnation = b.incarnation Note that there is a column named doublecount - if the value in that column is larger than one then we have two (or more) asm synonyms pointing to the same file. This should be taken into consideration when computing disk space.

Similar Messages

  • EM Alert: Warning:+ASM Disk Group requires rebalance

    Environment:
    O.S Version : HP-UX B.11.31 U ia64
    Oracle DB Version : 11.2.0.3.0 , Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    Database files are on : ASM Disk Group
    It is about the ASM Diskgroup low disk space alert by Oracle Enterprise Manager.
    Message=Disk Group DG_FLASH_01 requires rebalance because at least one disk is low on space.
    Metric=Disk Minimum Free (%) without Rebalance
    Metric value=18.961548
    Disk Group Name=DG_FLASH_01
    Severity=Warning
    Target Name=+ASM_dbsrver.siva.com
    Target type=Automatic Storage Management
    There is only 1 LUN assigned to this diskgroup +DG_FLASH_01_.
    We have a Oracle Enterprise Manager Grid Control Job MN_DBSRVR_DEL_ARCHIVELOGS runs every 12 hours by 1 AM and again at 1PM daily. It cleans-up the archivelogs older than 3 days old. The FLASH diskgroup is continuously being written with new files for both archivelogs and flashback logs.
    If there was multiple disks and a vast difference between the files on the different LUNs then a rebalance would be good to run.
    How to address such recurring alert of " *Disk Group DG_FLASH_01 requires rebalance because at least one disk is low on space*. " with _only one LUN on the +ASM Diskgroup_?                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    As I stated earlier there is only one disk on this diskgroup
    DISK_NUMBER      OS_MB   TOTAL_MB    FREE_MB NAME                           PATH
              0      65536      65536      12995 DG_FLASH_01_0000        /devasm/gc/ora_asm_gc_b03_a14_d10_08_36
              0      65536      65536      43064 DG_DATA_01_0000         /devasm/gc/ora_asm_gc_b03_a13_d12_08_35So disk REBALANCE not required
    Edited by: Sivaprasad S on Feb 14, 2013 11:46 PM

  • Oracleasm listdisks is not listing all disk groups and returning "strange special characters" and disks groups are dismounting unexpected

    Hi everybody,
    I have a 3 node Oracle Cluster with verstion 11.2.0.3.0 installed using ASM/ACFS/ADVM.
    Red Hat 5.7 - Kernel 2.6.18-371.12.1.el5 64bits
    OracleASM version:
         oracleasm-support-2.1.8-1.el5
         oracleasm-2.6.18-371.12.1.el5-2.0.5-1.el5
         oracleasmlib-2.0.4-1.el5
    On may, 2014 we had a physical failure in our storage system and all our disk partitions were completely lost.
    The Oracle Grid Infrastructure and Oracle RDBMS haven't needed to be reinstalled because they were healthy.
    The Oracle Cluster Registry (OCR) was lost (it was composed by three ASM disk groups in a redundant structure) and after recreation of the OCR disk groups I recover the Oracle Registry information from backup.
    All cluster information were recovered (listener, SCAN, VIP, databases and services)
    Databases could not be started because all ASM disk groups have been lost and oracle ASM instance (asmcmd -p) was showing all disk groups, but they were all "empty" - the physical partition related with them were recreated.
    All the "old" disk groups were dropped, and the "new" disk groups were recreated and all the backups from the databases were restored.
    After all services were up, and the environment seems to be OK, I check the healthiness of it, by executing the oracle cluster post-installation tool and others verify tools (crsctl and srvctl), well all returning messages saying that the environment was completely OK and no errors were found or generated (including in many log files I have inspected)
    After 2 weeks from the completely recover of the environment, without any error/failure message been received from it, the disk groups started to dismount unexpectedly, from whatever node and not only one specific disk group stops, but any one of them, any time.
    I opened a SR in Metalink (Oracle Support) and they conduct me to upgrade RedHat kernel version and OracleASM version.
    Simultaneously I opened a Case Solution in RedHat to help me identify the better way to do the upgrade in advantage of the Oracle specifications.
    From:
    rpm -qa | grep kernel
    kernel-devel-2.6.18-274.el5
    kernel-headers-2.6.18-274.el5
    kernel-2.6.18-274.el5
    rpm -qa | grep oracleasm
    oracleasm-support-2.1.8-1.el5
    oracleasmlib-2.0.4-1.el5
    oracleasm-2.6.18-274.el5-2.0.5-1.el5
    To:
    rpm -qa | grep kernel
    kernel-devel-2.6.18-371.12.1.el5
    kernel-2.6.18-371.12.1.el5
    kernel-headers-2.6.18-371.12.1.el5
    rpm -qa | grep oracleasm
    oracleasm-support-2.1.8-1.el5
    oracleasm-2.6.18-371.12.1.el5-2.0.5-1.el5
    oracleasmlib-2.0.4-1.el5
    Well, after this upgrade less times the disk groups dismounted, but they continue dismounting from whatever node, any disk group, any time.
    So, I opened another SR in Metalink (3-10143566371 still open) and they are conducting me again to upgrade the RedHat kernel version and OracleASM version.
    Information about OracleASM:
    # oracleasm listdisks
    ACFS
    FRA
    OCR01
    OCR02
    OCR03
    $ asmcmd -p
    ASMCMD [+] > ls -l
    State    Type    Rebal  Name
    MOUNTED  EXTERN  N      ACFS/
    MOUNTED  EXTERN  N      ARCH/
    MOUNTED  EXTERN  N      DEV/
    MOUNTED  EXTERN  N      DIR_LOG/
    MOUNTED  EXTERN  N      JAVA_ARCHIVE/
    MOUNTED  EXTERN  N      MSAF/
    MOUNTED  NORMAL  N      OCR/
    MOUNTED  EXTERN  N      PRD_DATA/
    MOUNTED  EXTERN  N      PRD_REDO1/
    MOUNTED  EXTERN  N      PRD_REDO2/
    MOUNTED  EXTERN  N      PRD_REDO3/
    MOUNTED  EXTERN  N      PRD_REDO4/
    MOUNTED  EXTERN  N      RASTR/
    MOUNTED  EXTERN  N      STAGE/
    This is what happens when execute "oracleasm scandisks":
    # oracleasm scandisks
    Reloading disk partitions: done
    Cleaning any stale ASM disks...
    Scanning system for ASM disks...
    Instantiating disk "ùìÿÿÿÿÿÿÿÿÿÿÿìóæþÿ¥Ï¨®Ð¢"
    Unable to instantiate disk "ùìÿÿÿÿÿÿÿÿÿÿÿìóæþÿ¥Ï¨®Ð¢"
    Instantiating disk "ü´ñõ
                            ñõúìsö"
    Unable to instantiate disk "ü´ñõ
                                    ñõúìsö"
    ~±Ã1~u·}cÿ-Ûg disk "
    ¾s
    ~±Ã1~u·}cÿ-Ûinstantiate disk "
    ¾s
      Instantiating disk "à·Öªß³Ö½Þ®hìëÖßßÞÖÛÜØÖÕ"
    Unable to instantiate disk "à·Öªß³Ö½Þ®hìëÖßßÞÖÛÜØÖÕ"
    Instantiating disk "êËbkî,c
    ~,XZ±´b¹u²´biÅr"
    Unable to instantiate disk "êËbkî,c
    ~,XZ±´b¹u²´biÅr"
    Instantiating disk "
    PuTTYPuTTYUnable to instantiate disk "
    kÍ3|úùõ/øÊInstantiating disk "u
    i)ïìL"
    kÍ3|úùõ/øÊe to instantiate disk "u
    My question is: "This will really solve the problem?"
    Another: "Oracle really understood what is happening and they can help me to solve this problem?"
    Final: "Can anyone please help me this problem?"

    Hi,
    my two cent.
    Wait for the SR feedback.
    But for the future I advice you to do an ASM Metadata backup to be able to restore this data if you lost
    configurations or complete disks and so on.
    asmcmd md_backup -b <Pfad>/Filename
    and also an ocrconfig backup via crontab.
    ocrconfig -local -manualbackup
    regards

  • How to increase space in ASM disk groups?

    Hi All,
    I am a newbie DBA in my team and today morning got a OEM alert that:
    Target name=+ASM_ZEUS.techiebros.com
    Message=Disk Group DATA requires rebalance because at least one disk is low on space.
    Any solution?

    To solve it you can run this command: Alter diskgroup ASMDB Add Disk 'here the way of the new disk' Rebalance power 4 WAIT;
    After that, you can see through the v$asm_operation;
    Read : <http://jarneil.wordpress.com/2008/10/27/asm-rebalance-io-saturation/> or < http://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_1006.htm>

  • How many disk groups for +DATA?

    Hi All,
    Does oracle recommends having one big/shared asm disk group for all of the databases?
    In our case we going to have 11.2 and 10g rac running against 11.2 ask...
    Am I correct in saying that I have to set asm’s compatibility parameter to 10 in order to be able to use the same disk?
    Is this is a good idea? Or should i create another disk group for the 10g db’s?
    I’m assuming there are feature that will not be available when the compatibility is reduced to 10g...

    Oviwan wrote:
    what kind of storage system do you have? nas? what is your protocol between server and storage? tcp/ip (=>nfs)? fc?....
    if you have a storage with serveral disks then you create mostly more than one lun (raid 0, 1, 5 or whatever). if the requirement is, that you need a 1 TB diskgroup, then I would not create 1 1TB lun, I would create 5x200GB lun's for example, just for the case that you have to extend the diskgroup with a same lun size. if its 1 TB then you have to add another 1TB lun, if there are 5x200GB luns then you can simply add 200GB.
    I have nowhere found a document that says: if you have exactly 16 lun's for a diskgroup it's best. it depends on os, storage, etc...
    so if you create a 50gb diskgroup I would create just one 50gb lun for example.
    hthyes its NAS, connectd using Iscsi. it has 5 disks 1TB each and configued with RAID5. I found below requirments on asm ... it indicates 4luns as minimum per diskgroup, but it doesnt clearify whether its for external redundancy or as mredundancy types.
    •A minimum of four LUNs (Oracle ASM disks) of equal size and performance is recommended for each disk group.
    •Ensure that all Oracle ASM disks in a disk group have similar storage performance and availability characteristics. In storage configurations with mixed speed drives, such as 10K and 15K RPM, I/O performance is constrained by the slowest speed drive.
    •Oracle ASM data distribution policy is capacity-based. Ensure that Oracle ASM disks in a disk group have the same capacity to maintain balance.
    •Maximize the number of disks in a disk group for maximum data distribution and higher I/O bandwidth.
    •Create LUNs using the outside half of disk drives for higher performance. If possible, use small disks with the highest RPM.
    •Create large LUNs to reduce LUN management overhead.
    •Minimize I/O contention between ASM disks and other applications by dedicating disks to ASM disk groups for those disks that are not shared with other applications.
    •Choose a hardware RAID stripe size that is a power of 2 and less than or equal to the size of the ASM allocation unit.
    •Avoid using a Logical Volume Manager (LVM) because an LVM would be redundant. However, there are situations where certain multipathing or third party cluster solutions require an LVM. In these situations, use the LVM to represent a single LUN without striping or mirroring to minimize the performance impact.
    •For Linux, when possible, use the Oracle ASMLIB feature to address device naming and permission persistency.
    ASMLIB provides an alternative interface for the ASM-enabled kernel to discover and access block devices. ASMLIB provides storage and operating system vendors the opportunity to supply extended storage-related features. These features provide benefits such as improved performance and greater data integrity.
    one more question about fdisk partitioning. is it correct that we should only create one partition per luns (5x200Gb luns in my case) is it because this way i will have more consistent set of luns( in term of performance)?

  • Disk Group from normal to external in a RAC environment

    Hello,
    my environment is based on 11.2.0.3.7 RAC SE with two nodes.
    Currently I have 4 DG, all in NORMAL redundancy, to contain respectively:
    ARCH
    REDO
    DATA
    VOTING
    At the moment I focus only with non-VOTING DG.
    Each of them has 2 failure groups that physically maps to disks in 2 different server rooms.
    The storage arrays are EMC VNX (one in each server room).
    They will be substituted by a VPLEX system that will be configured as a single storage entity with DGs in external redundancy.
    I see from document id
    How To Move The Database To Different Diskgroup (Change Diskgroup Redundancy) (Doc ID 438580.1)
    that it is not possbile to do this online apparently.
    Can you confirm?
    I also read the thread in this forum:
    https://community.oracle.com/message/10173887#10173887
    that seems to confirm this too.
    I have some pressure to free the old storage arrays, but in short time I will not be able to stop the RAC RDBMSs I have in place.
    So the question is: can I proceed into two steps so that
    1) add a third failure group composed by the VPLEX disks
    2) wait for data sync of the third failure group
    3) drop one of the two old failure groups (ASM should be let me make this, correct?)
    3) brutally remove all disks of the remaining old storage failure group
    and proceed in reduced redundancy for some time until I can afford the maintenance window
    Inside the ASM administrator guide I see this:
    Normal redundancy disk group - It is best to have enough free space in your disk
    group to tolerate the loss of all disks in one failure group. The amount of free
    space should be equivalent to the size of the largest failure group.
    and also
    Normal redundancy
    Oracle ASM provides two-way mirroring by default, which means that all files are
    mirrored so that there are two copies of every extent. A loss of one Oracle ASM
    disk is tolerated. You can optionally choose three-way or unprotected mirroring.
    spare

    When you are creating external table you must specify location that external table will use to manipulate with external data.
    This is done with LOCATION and/or DEFAULT_DIRECTORY parameter.
    If you want that every instance in your cluster is able to use one specific external table, then you would need to have the location specified in the create external table command visible/accessible to all servers in your cluster, propably by some specific shared os disks/storage configuration; e.g. mounting remote disks, and this could very easy cause slower ext. table performance than it would be when the specified location is on the db server.
    This will be the one and only way because it is impossible to specify remote location, either when creating directory or in any specification parameters when creating external table.

  • "must choose at least one" validation in dataTable?

    Hello, group,
    How do you validate a set of checkboxes, one per table row, in which the user must select at least one?
    We have a page containing a dataTable, each row of which represents an object, one of whose attributes is "active". Our requirement is that at least one object must be selected as "active" by the user.
    How do we validate this?
    I'm considering the following:
    (1) Put a validator on each checkbox that simply increments a count in a request-scoped bean if the checkbox is checked (and always returns success).
    (2) Put a validator on a hidden field at the bottom of the form that requires the count be greater than zero.
    Is there a better way? (Will this even work at all? :) )
    Thanks.
    John.

    Looks interesting, thank you very much.
    I would actually need the multiple row selector, I think, since the requirement is at least one. I see there's no "validator" attribute, but I assume we could just hang a f:validator off of it (or write our attribute and submit a patch!).
    That jenia component set looks good for some other requirements we have.
    John.

  • Standby Database ASM Disk Groups

    Hi Guys
    I wonder if anyone can tell me - does a standby database have to have an identical configuration for its ASM Disk Groups?
    My production database has two disk groups, one for data and the other for temp.  Can I get away with a single diskgroup in my standby database or would I need two of the same name as the production database?
    Cheers
    Simon

    Hi Saml
    I have been busy googling at the same time as discussing this and it would appear that it will use the db_file_name_convert:
    http://asanga-pradeep.blogspot.com.au/2012/07/11gr2-standalone-data-guard-with-asm.html
    The link above shows the output of someones RMAN session where the OMF names are changed automatically.  Problem is that some people are recommending that the parameter not be used, so now I am really confused!
    I think I will try the parameter, if it doesnt work or the duplicate fails I will drop the temp table space in production and then do the duplicate, then recreate the temp tablespace.  I can do that because there will be no one on the system on Sunday when I do it.
    Thanks again for your help - I will let you know how it goes.
    Ragards
    Simon

  • Disk Label requirement

    Hi,
    Any one explain, why disk labeling required . If there is no disk label it will create problem, please clarify.
    Regards,
    Siva

    I'm not in the expert class, I'm simply another Solaris administrator but I can give you a simple answer. The disk label is required because it provides some very basic low level information needed by the system for disk access. If the disk is divided into partitions, the disk label would give an indication as to the location and size of each partition. If you wanted to mount a filesystem stored in the fifth partition on the disk, the system can use the data recorded in the disk label to find that partition. Of course, things have a way of getting complicated. There are different sorts of disk labels so you can have situations where you have the wrong kind label on a disk for a particular purpose. That's where understanding the requirements can get tricky.

  • Reinstalling Oracle 11gR2 RAC Grid Problem - ASM Disks Group

    Folks,
    Hello.
    I am installing Oracle 11gR2 RAC using 2 Virtual Machines (rac1 and rac2 whose OS are Oracle Linux 5.6) in VMPlayer.
    I have been installing Grid Infrastructure using runInstaller in the first VM rac1 from step 1 to step 9 of 10.
    On the step 9 of 10 in the Wizard, accidentally, I touch the Mouse, and the Wizard is gone.
    The directory for installing Grid in the 2 VMs is the same: /u01
    In order to make sure everything is correct, I delete entire directory /u01 in the 2 VMs and install Grid in rac1 again.
    I have understood it's not the right way to delete /u01. The right way is to follow the tutorial
    http://docs.oracle.com/cd/E11882_01/install.112/e22489/rem_orcl.htm#CBHEFHAC
    But I have deleted /u01 and need to fix one by one. I install Grid again and get the error message on step 5 of 9 as follows:
    [INS - 30516] Please specify unique disk groups.
    [INS-3050] Empty ASM disk group.
    Cause - Installer has detected the disk group name provided already exists on the system.
    Action - Specify different disk group.
    In Wizard, the previous Disk Group name is "DATA" and its Candidate disks (5 ASMDISKs) are gone. I try to use a different name "DATA2", but no ASMDISKs come up under "Candidate disks". For "ALL Disks", all ASMDISKs cannot be selected.
    I want to use the same ASM disk group "DATA" and don't want to create a new disk group.
    My question is:
    How to have the previous ASM disks and its group "DATA" come up under "Candidate Disks" so that can use it again ?
    Thanks.

    Hi, in case this helps anyone else. I got this INS-30516 error too was stumped for little while. I have 2 x 2-node RAC which are hitting same SAN. The first-built RAC has a DATA diskgroup. When went to build second RAC on new ASM disk new DIskgroup (but same diskgroup name DATA) got INS-30516 about diskgroup name already in use etc. Finally figured out all that was required was to restrict diskstring using button in installer to only retrieve the LUNS for this RAC (this was quick and dirty - all LUNS for both RAC being presented to both RAC). Once diskstring only searched for the LUNS required for this RAC only, e.g.
    ORCL:DATA_P* (for DATA_PD and FRA_PD)
    the error went away.
    I also have DATA_DR and FRA_DR presenting to both RAC. Apparently it scans the header and if it finds a diskgroup name that is already in use based on the diskstring scan it will not allow reuse of the diskgroup name since it has no way of knowing that the other ASM disks are for a different RAC.
    HTH

  • Is it better to use ASM if my DB uses only one disk ?

    Hello
    I am planning to install a NEW database 11g R1 on a new windows server.
    I am running a 9.2 DB and will export its data to the freshly installed 11gR1.
    I ma wondering if i have to use the ASM feature ?
    The dabatase files are small : 52 Gb, and it will keep on one disk.
    I have understood that the main benefit of using ASM in automatic multi disk storage.
    Does it worth to use it on my small DB ?
    Thank you for your kind answers.
    Christian

    If you want to learn ASM then using it with a single disk system and just creating the diskgroups to not use Oracle redundancy is an option. Also one of the things ASM is designed to provide is async IO, that is, easy managment of raw partitions. Depending on your platform ASM may be desirable from this point of view.
    Also does a one disk set-up today mean only a one disk set-up tomorrow? It is possible to migrate a database to a new disk server via ASM while the database is running. You create a mirror, allow it to populate, and then remove the original disk. The database data files are now on a new disk storage unit.
    But ASM is by no means required or necessary. You just want to consider all the options it provides and the headaches it brings to determine which set of values: use or not, is right for your situation.
    HTH -- Mark D Powell --

  • ASM - Service Guard/SGeRAC - Disk Groups - Sizing

    Hai.
    I'm new to ASM. We want to use ASM with HP-UX11.23 and MC Service Guard/SGeRAC A11.1.17. We decided to start with initial DB sizing of 25GB, I mean the Disk Group ( hence, Volume Group) size. So, I would like to know recomended no: of Disks in this Disk Group and Disks sizing? We want to go with only one Disk Group. Also, I have few questions:
    1) Do we need to have separate Disk Groups for ArchiveLogs & Database Files?
    2) Can we use ASM Disk Groups for Archive Logs or is a regular File System recomended or can we have both?
    regards,
    Dileep Tallam.

    Looking at the scalability and Data Growth data rate in you Org.., say in next 2 to 5 years ..... Estimate the size of Disk Group.
    Single Disk Group is a good idea, as multiple disk groups gives no performance agains.
    If planning for Flash too , Then give a separate Disk Group to Flash.
    Comming to
    1) Do we need to have separate Disk Groups for ArchiveLogs & Database Files?
    No need for a separate Disk group for Arch/, Ctrl, Data, Redo. You can put all in one Disk Group.
    2) Can we use ASM Disk Groups for Archive Logs or is a regular File System recomended or can we have both?
    Archive Logs are supported on ASM. Depending upon your Backup Stragey.
    If RMAN - ASM
    else
    file system.
    Regards
    Satish

  • Create ASM Disk Groups cannot see Disk Path to select during installation

    Hello Guys,
    I am setting up 2 node RAC on 11gR2 and Linux.
    I have configured all the pre-installation steps that are required to run Grid Setup as per my understanding.
    I have configure SAN partitions using multipath.
    I can see my SAN volume when i query multipath -l
    Then i configured the raw partitions by oracleasm. Configured and then created mount points:
    /dev/oracleasm/disks/
    CRSVOL1 DATAVOL1 FRAVOL1
    Later on I created the disks using oracle asm command:
    /usr/sbin/oracleasm createdisk CRSVOL1 /dev/mapper/racdbp1 and so on...
    I have run /usr/sbin/oracleasm scandisks
    Cleaning any stale ASM disks...
    Scanning system for ASM disks...
    And when i list disk with command /usr/sbin/oracleasm listdisks
    it shows the disk like this on both nodes:
    CRSVOL1
    DATAVOL1
    FRAVOL1
    BUT during the installation screen when it comes to create ASM Disk Groups It shows nothing in the add disk frame, I cant select the volumes I can list, like i did above.
    Any hint please?
    Thanks, Imran

    Thanks but my problem is very specific. I feel that i have performed all the necessary steps to get complete the step i discussed above. As per different commands all is set. But i am unable to see Disks and Disks Paths during the installation screen. This is another output to verify if the installe user have rights on the asm devices:
    [grid@racnode1 mapper]$ cd /dev/oracleasm/disks/
    DATAVOL1 ETSCRS1 ETSVOT1 ETSVOT3 FRAVOL1
    ETSASM1 ETSCRS2 ETSVOT2 EXTRADM
    [grid@racnode1 mapper]$ cd /dev/oracleasm/disks/
    [grid@racnode1 disks]$ ls -ltr
    total 0
    brw-rw---- 1 grid asmadmin 8, 1 Oct 2 16:47 ETSASM1
    brw-rw---- 1 grid asmadmin 8, 5 Oct 2 16:47 DATAVOL1
    brw-rw---- 1 grid asmadmin 8, 6 Oct 2 16:47 FRAVOL1
    brw-rw---- 1 grid asmadmin 8, 7 Oct 2 16:47 ETSVOT1
    brw-rw---- 1 grid asmadmin 8, 8 Oct 2 16:47 ETSVOT2
    brw-rw---- 1 grid asmadmin 8, 9 Oct 2 16:47 ETSVOT3
    brw-rw---- 1 grid asmadmin 8, 10 Oct 2 16:47 ETSCRS1
    brw-rw---- 1 grid asmadmin 8, 11 Oct 2 16:47 ETSCRS2
    brw-rw---- 1 grid asmadmin 8, 13 Oct 2 16:47 EXTRADM
    I will appreciate if you can help me to get through this step... Is there anything else needs to be verified?
    Regards, Imran

  • How to remove Disk Group after deinstall of Grid Infrastructure

    Hello,
    I deinstalled an Oracle Grid Infrastructure for a standalone server. I made the mistake of telling OUI not to drop the Disks/Disk Group. Now when I try to do a new install it shows the disks as members of a Disk Group already on the page 'Create Disk Groups'. How can I get those disks out of the disk group? I tried oracleasm but it does not see any Disk Groups.

    OS is CentOS 5.6
    I am using formatted (ext3) logical volumes. Let me explain a bit why I am doing this. This is a system I lease for my own personal use. I am leasing it so that I can learn Oracle High Availability. Unfortunately due to how each VM is provisioned only a single virtual disk (raw disk) is allocated per instance. I have not leased a dedicated server due to the cost and so do not have/cannot get multiple raw disks. The logical volumes aren’t setup with any RAID on my virtual machine as there are just additional LVM’s assign internally to my server. The underlying host server uses RAID-10.
    When I set up the Disk Group "DATA" for ASM I used the following:
    [root@remarkable:/dev/mapper]pwd
    /dev/mapper
    [root@remarkable:/dev/mapper]ls -l
    total 0
    crw-rw-rw- 1 root root 10, 63 Jul 2 12:55 control
    brw-rw-rw- 1 root disk 253, 0 Jul 2 12:55 VolGroup00-LogVol00
    brw-rw-rw- 1 root disk 253, 2 Aug 10 18:07 VolGroup00-LogVol001
    brw-rw-rw- 1 root disk 253, 3 Aug 10 18:07 VolGroup00-LogVol002
    brw-rw-rw- 1 root disk 253, 4 Aug 10 18:07 VolGroup00-LogVol003
    brw-rw-rw- 1 root disk 253, 1 Jul 2 12:55 VolGroup00-LogVol01
    That worked fine when I set it up initially. But then I realized the groups were not set correctly for the oracle user or the ASM home after I did the install. So I uninstalled the ASM and then set the groups correctly for the Oracle user. However, when I uninstalled the ASM I mistakenly chose not to blow away the disk group. So now when I try to install the Grid Infrastructure using OUI it shows the 3 disks I want to use as already being members of a Disk Group and I don't know how to change that. I tried the oracleasm deletedisk command but oracleasm does not think any disk groups exist.
    [root@remarkable:/dev/mapper]oracleasm listdisks
    [root@remarkable:/dev/mapper]oracleasm deletedisk Disk1
    Disk "DISK1" does not exist or is not instantiated
    So I am not sure where to go from here.

  • ASM Disk group - solaris

    Hi experts
    amm trying to install and configure Grid Infra install on Solaris 10
    SunOS trosuncluster1 5.10 Generic_147440-01 sun4u sparc SUNW,Sun-Fire-V245
    when i come to select disk group characteristic, it does not show candidate disks??? where I need to install GI
    what am i missing
    thanks

    # cfgadm -al
    Ap_Id Type Receptacle Occupant Condition
    c0 scsi-bus connected configured unknown
    c0::dsk/c0t0d0 CD-ROM connected configured unknown
    c1 scsi-sata connected configured unknown
    c1::dsk/c1t0d0 disk connected configured unknown
    c1::dsk/c1t1d0 disk connected configured unknown
    c1::dsk/c1t2d0 disk connected configured unknown
    c1::dsk/c1t3d0 disk connected configured unknown
    c2 fc-fabric connected configured unknown
    c2::500601653ea01a52 disk connected configured unknown
    c2::5006016c3ea01a52 disk connected configured unknown
    usb0/1 unknown empty unconfigured ok
    usb0/2 unknown empty unconfigured ok
    usb0/3 unknown empty unconfigured ok
    usb1/1.1 unknown empty unconfigured ok
    usb1/1.2 unknown empty unconfigured ok
    usb1/1.3 unknown empty unconfigured ok
    usb1/1.4 unknown empty unconfigured ok
    usb1/2 unknown empty unconfigured ok
    usb1/3 unknown empty unconfigured ok
    usb2/1 unknown empty unconfigured ok
    usb2/2 unknown empty unconfigured ok
    usb2/3 unknown empty unconfigured ok
    usb2/4 unknown empty unconfigured ok
    usb2/5 unknown empty unconfigured ok
    usb2/6 unknown empty unconfigured ok
    usb2/7 unknown empty unconfigured ok
    usb2/8 unknown empty unconfigured ok
    we have 4 disks
    # df -k
    Filesystem kbytes used avail capacity Mounted on
    rpool/ROOT/s10s_u10wos_17b
    70189056 4834399 47404882 10% /
    /devices 0 0 0 0% /devices
    ctfs 0 0 0 0% /system/contract
    proc 0 0 0 0% /proc
    mnttab 0 0 0 0% /etc/mnttab
    swap 29938944 376 29938568 1% /etc/svc/volatile
    objfs 0 0 0 0% /system/object
    sharefs 0 0 0 0% /etc/dfs/sharetab
    /platform/sun4u-us3/lib/libc_psr/libc_psr_hwcap1.so.1
    52239282 4834399 47404882 10% /platform/sun4u-us3/lib/libc_psr.so.1
    /platform/sun4u-us3/lib/sparcv9/libc_psr/libc_psr_hwcap1.so.1
    52239282 4834399 47404882 10% /platform/sun4u-us3/lib/sparcv9/libc_psr.so.1
    fd 0 0 0 0% /dev/fd
    swap 29941312 2744 29938568 1% /tmp
    swap 29938608 40 29938568 1% /var/run
    rpool/export 70189056 32 47404882 1% /export
    rpool/export/home 70189056 31 47404882 1% /export/home
    orcl01 70189056 31 70188963 1% /orcl01
    rpool 70189056 106 47404882 1% /rpool
    Edited by: 912919 on 15-May-2012 07:56

Maybe you are looking for