Adding a device to ASM disk using asmtool

Hello

I create ASM disks.

Background: Oracle enterprise linux 6. I'd partition the shared disks (SCSi) during the installation of Linux (don't know what to do, I just did).

Now if I run oracleasm createdisk, it is said that the devices are busy. No, I removed the mounts of the devices in/etc/fstab. Now createdisk said that "the device is not a partition. Now I use asmtool command instead:

/ usr/sbin/asmtool - c-l/dev/oracleasm n OCRVOTE s/dev/sdc - a force = yes

That works fine, but I need to add more then one device to drive OCRVOTE. If I do

/ usr/sbin/asmtool - c-l/dev/oracleasm n OCRVOTE s/dev/sdd - force = yes

It is said: asmtool: unable to create 'OCRVOTE' ASM disk: file exists

Hello

You're basically labelling records at the level of the BONE.

This name must be unique.

You must give the label name different labelling while.

/ usr/sbin/asmtool - c-l/dev/oracleasm - n OCRVOTE1 s/dev/SDS - a force = yes

Then use ASM diskgroup in the future.

Kind regards

Loriette

Tags: Database

Similar Questions

  • recommendation of the number of ASM disks on 11 GR 2

    Hi all

    I'm deployment RAC Oracle 11 g 2 + ASM AIX6.1 and an EMC SAN.

    I am planing to create three groups of disks DATA, FRA, and OCR, I use external redundancy.
    I have the questions:

    How many records you create for each group of records? is there any number of disks recommended for the DATA and FRA?
    FRA: This is for the flash recovery area disk group so all the backups will be stored here. should have the size of the DATA multiplied by 2?
    OCR: Will contain OCR and voting disks, is it enough not to have only a single drive since I'm on external redundancy? What is the recommendation?

    Kind regards

    Hello

    What is the right way to create my ASM disks? If I follow these steps, I should find the/dev / disks in my ASM_DISKS list? and then, of these discs, I can create my groups of disks?

    Yes... It is simpler than Linux (when you use MPIO or ASMLIB)... On AIX you just set the permission on/dev/rhdisk and asm_diskstring/dev/rhdis *, you need to create partition (LV) on these physical disks.

    These permissions are constantly, only returning to the default root: System in case of device to remove/add.

    You must use rhdisk hdisk.

    The special file rhdisk provides first IO functions to access and control to physical disk for the physical disk device drivers. Access IO gross is provided through the/dev/rhdisk0, / dev/rhdisk1,..., character special files.

    Direct access to physical disks through block special files should be avoided. This access may affect the performance and also cause problems of consistency of the data between the data and the data in the buffer cache pages system block I/O. Special files/dev/hdisk block are reserved for the system in the management of logical volumes, paging devices and file systems.

    Important: the physics of the disks MUST NOT have PVID. {: identifier of the thread = 2312281}

    # Added: edited by: Levi Pereira January 12, 2012 16:07
    Also, I recommend:
    DOC said: Oracle recommends that the allocation unit (to THE) size for a group of disks attached to 4 megabytes (MB).
    Definition of SIZE is a difference when you don't need broadband to e/s. IE: used for Diskgroup that will store the data files

    See the example:

    # lspv
DISK            PVID                                VG_NAME
============================================================
hdisk12         none                                None
hdisk13         none                                None
hdisk14         none                                None

## Change permission of /dev/rhdisk*  to GRID OS owner and ASMADMIN OS group and "chmod 660"
## If you are not using  job role separation installation the default is "oracle: dba"
#  ls -ltr /dev/rh*
crw-rw----    1 oracle   asmadmin     17, 10 Jan  5 17:01 /dev/rhdisk12
crw-rw----    1 oracle   asmadmin     17, 11 Jan 12 15:00 /dev/rhdisk13
crw-rw----    1 oracle   asmadmin     17, 12 Jan 12 15:16 /dev/rhdisk14

Disks to discover [disks=raw,asm,all]
raw = disks not used by ASM
asm = disks used by ASM
all = All disks

$ /u01/app/grid/grid_has/kfod disks=raw asm_diskstring='/dev/rhdisk*'
--------------------------------------------------------------------------------
 Disk          Size Path                                     User     Group
================================================================================
   1:     204800 Mb /dev/rhdisk12                             oracle   asmadmin
   2:     204800 Mb /dev/rhdisk13                             oracle   asmadmin
   3:     204800 Mb /dev/rhdisk14                             oracle   asmadmin
--------------------------------------------------------------------------------
ORACLE_SID ORACLE_HOME
================================================================================
      +ASM /u01/app/grid/grid_has

SQL>
set linesize 100
col path for a30
col header_status for a20
select path,header_status from v$asm_disk
where header_status <> 'MEMBER';
PATH                           HEADER_STATUS
------------------------------ --------------------
/dev/rhdisk12                   FORMER
/dev/rhdisk13                   FORMER
/dev/rhdisk14                   FORMER

$ sqlplus / as sysasm

SQL>
 CREATE DISKGROUP DATA NORMAL REDUNDANCY
    FAILGROUP STG1_CTL1 DISK '/dev/rhdisk12'
    FAILGROUP STG2_CTL1 DISK '/dev/rhdisk13'
    FAILGROUP STG1_CTL2 DISK '/dev/rhdisk14'
 ATTRIBUTE 'compatible.asm' = '11.2.0.0.0';

Diskgroup created.

$ asmcmd lsdg DATA

Inst_ID  State    Type    Rebal  Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
      1  MOUNTED  NORMAL  N         512   4096  1048576    614400   614238           204800          204719              0             N  DATA/

$  asmcmd  lsdsk -p -G DATA
Group_Num  Disk_Num     Incarn  Mount_Stat  Header_Stat  Mode_Stat  State   Path
        5         0  782499361  CACHED      MEMBER       ONLINE     NORMAL  /dev/rhdisk12
        5         1  782499362  CACHED      MEMBER       ONLINE     NORMAL  /dev/rhdisk13
        5         2  782499363  CACHED      MEMBER       ONLINE     NORMAL  /dev/rhdisk14

$  asmcmd lsdsk -k -G DATA
Total_MB  Free_MB   OS_MB  Name       Failgroup  Failgroup_Type  Library  Label  UDID  Product  Redund   Path
  204800   204746  204800  DATA_0000  STG1_CTL1  REGULAR         System                         UNKNOWN  /dev/rhdisk12
  204800   204746  204800  DATA_0001  STG2_CTL1  REGULAR         System                         UNKNOWN  /dev/rhdisk13
  204800   204746  204800  DATA_0002  STG1_CTL2  REGULAR         System                         UNKNOWN  /dev/rhdisk14

    Kind regards
    Levi Pereira

    Published by: Levi Pereira January 12, 2012 15:50

  • Label of the ASM to name of LUN mapping; Are not even necessary device names when you use ASMLib?

    = Environment details start =.

    OS: Oracle Linux 6.4

    Version Infra grid: 11.2.0.4

    Storage: EMC VMAX

    ASM Lib version:

    # rpm - qa | grep oracleasm

    oracleasm-support - 2.1.8 - 1.el6.x86_64

    oracleasmlib - 2.0.4 - 1.el6.x86_64

    oracleasm version came not in rpm-qa output may be because it is part of the Oracle Linux kernel. But the 2 components above are not

    = Environment details end =.

    We have a 2 node RAC cluster.

    We wanted to add 2 LUNS to our data Diskgroup and asked team storage available to both nodes of the cluster.

    After that they provided, the Linux Admin scanned the LUN and powerpath device names were generated. The powerpath device names like SCSI logic unit number names are incremented sequentially. Because, two additional powerpath LUN used to Node1 to a local file system, the names of powerpath were incrementing differently in the two nodes.

    Thus, for the same LUNS emcpowerpath names differed in Node2. Linux Admin did not notice this difference. And he told us the names of newly added from Node1 LUNS powerpath that have been

    / dev/emcpowerv

    / dev/emcpowerw

    But in Node2, the same LUN were appointed

    / dev/emcpowert

    / dev/emcpoweru

    The DBA guess powerpath name these 2 LUNS will be same on Node2, label the discs to help

    oracleasm createdisk DATA17/dev/emcpowerv1

    oracleasm createdisk DATA18/dev/emcpowerw1

    After marking in node 1, the DBA ran scandisks in Node2. But while the oracleasm scandisks in Node2 is running, it does not seem to/dev/emcpowerv and/dev/emcpowerw in Node2. Instead, ASMLib is smart enough to read the LUN ID in Node1 and search devices powerpath with the same LUN ID and labels as Node1. What's it like in Node2, / dev/emcpowert is labeled DATA17 and/dev/emcpoweru is labeled DATA18 correctly, as shown below.

    Node1

    Node2

    LUN ID

    Label of the ASM

    / dev/emcpowerv

    / dev/emcpowert

    873F

    DATA17

    / dev/emcpowerw

    / dev/emcpoweru

    629:

    DATA18

    Confirmed using the oracleasm querydisk Pei/dev/emcpower < x > .

    During labelling using the oracleasm createdisk , since we use the LUN name I always thought that asmlib dealt only with the names of devices (Powerpath name in this case). I didn't know that ASMLib treats ID LUN. If ASMLIB faces in LUN ID internally, then you don't need to have the same name for a particular LUN for disks shared in different RAC nodes? Right?

    ASMLIB contains 3 packs. Oracleasmlib, which is distributed under a license of Oracle user space and is not part of the standard GPL software distribution. Oracleasm-support, which is in the standard repository and kernel driver of Oracleasm, which is included in the core Oracle UEK only or distributed by Red Hat to RHCK kernel. The subsequent RHCK driver requires a Red Hat subscription. You need all 3 installed packages.

    ASMLib doesn't care to the SCSI ID or device names. When you configure a device to ASMLIB, he writes a header special disk in the device, the command scandisk read and identify a device. ASMLIB devices are populated under the tree of device/dev/oracleasm and found by ASM using the default ORCL: device chain.

    Don't forget that ASMLIB does not work with multiple devices and if you use DB-Multipath or EMC Powerpath, you need to blacklist the physical devices so ASMLIB will use powerpath or multipath device instead. Otherwise there will be no failover devices like ASMLIB will simply use the first device found and ignore the other. Check the following:

    http://www.Oracle.com/technetwork/topics/Linux/multipath-097959.html

  • 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

  • If you use network storage, configure ASM disks with external redundancy groups

    Hi Experts,

    If you use network storage, configure ASM disks with external redundancy groups. Don't use groups of Oracle ASM failure. Oracle failure groups consume cycles additional CPU and can run in unpredictable ways after suffering from a disk failure. When you use external redundancy, disk failure are transparent to the database and do consume no additional database CPU cycle, because it is discharged on storage processors.

    This does not mean

    • RAID 1 + 0 for diskgroup + REDO1
    • RAID 1 + 0 for diskgroup + REDO2
    • RAID 5 for diskgroup + DATA
    • RAID 5 for diskgroup + FRA

    Is this one suggested, the recommended best practices for oracle on VMWARE?


    Thank you and best regards,

    IVW


    Hello

    You can check the storage analysis as well...

    http://www.Dell.com/downloads/global/solutions/tradeoffs_RAID5_RAID10.PDF

    discussion of the Oracle

    https://asktom.Oracle.com/pls/asktom/f?p=100:11:P11_QUESTION_ID:359617936136

  • Unlike used MB of available space in the ASM disk between primary and standby database group

    Hi all

    We are seeing a difference in ASM disk group DATA1 USED_MB between elementary school a Standby.Its an AAM.4 node RAC

    Primary

    -------

    NAME                              TOTAL USED GB FREE GB REQUIRED FREE GB USABLE % USABLE free of CHARGE (GB)

    ------------------------------ ------------ ------------ ------------ ---------------- ---------------- --------------

    Data1 141 534 66 082 75 452 15 726 42.0 59 726

    DATA_XDP501 17 766 11 635 6 131 2 538 3 593 20.0

    Standby

    NAME                              TOTAL USED GB FREE GB REQUIRED FREE GB USABLE % USABLE FREE (GB)

    ------------------------------ ------------ ------------ ------------ ---------------- ---------------- --------------

    Data1 141 534 57 059 84 475 15 726 68 749 49.0

    DATA_XDP801 17 766 11 781 5 985 2 538 3 447 19.0

    Mode standby is runnig like

    OPEN_MODE

    --------------------

    READ ONLY TO APPLY

    Some body give an overview on what could be the purpose or specific controls will help

    Thank you

    Soundar.M

    Hello

    You can run sql in below document ASM sqlplus.

    Then, you will come to know which files are files of redundent on ASM diskgroup.

    HOW to map ASM FILES WITH FILES of DATABASE ONLINE (Doc ID 552082.1)

    Delete these additional level of the DSO files, then validate.

    Kind regards
    Loriette

  • 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.

  • Prepare disks using ASMlib and oracleasm ASM

    Normally ASMlib/oracleasm is used to prepare the ASM disks. I wonder, in addition to this tool, is there another tool GUI based to use to prepare the ASM disks?



    Thank you

    Scott

    There is no graphical interface for asmlib. to create diskgroup, you can use asmca.

  • 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

  • ASM disks - expand a based San LUN

    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...

    Thanks for any help.

    Have you tried:

    SQL > alter diskgroup DATA42 resize all the 4 powers of rebalancing.

  • 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.

  • Difference between ADVM Volume and filesystem ACFS ASM disk group

    Q1. What is the difference between an ASM disk group and a Volume of ADVM?

    In my opinion, an ASM disk group is actually a logical volume to the database (including the FRA files) files.

    11 GR 2 appears to have introduced the notions of volumes ADVM and filesystems ACFS.

    11 GR 2 ASM disk group can contain:

    • ASM disks
    • Volumes ADVM
    • Filesystems ACFS

    Q2. ADVM volumes appear to be dynamic volumes.

    However is it therefore not effectively overlaying a logical volume (the volume ADVM) under ASM disk group (conceptually a logical volume as well)?

    Even worse, if you left the ASM disk group redundancy in hardware RAID / SAN level (as recommended Oracle), you actually have 3 layers of logical disk? (ASM on top of ADVM on top of RAID/SAN)?

    Q3. If it is 2 layers of logical disk (i.e. on top of ADVM ASM), what makes this better than 2 layers using a 3rd party volume manager (for example the DSO at the top of the 3rd party LVM) - something Oracle encourages against?

    Q4. ACFS file systems, seem to be file systems clustered for not including ORACLE_HOMEs database files, application exe etc (but NOT GRID_HOME, OS root, OCR or voting records)

    Can you create / modify filesystems ACFS using ASM.

    The diagram of topology of oracle for ASM in ASM 11 GR 2 administration guide, says ACF in ASM. I'm not sure about that if ACFS belongs to ASM or ASM is located at the top of the ACF?

    Q5. Connected to the 4th quarter. There seems to be a number of different ways, ACFS file systems can be created? Which of this is the valid methods?

    • Thanks to ASM?
    • through native OS file system creation?
    • through OEM?
    • through acfsutil?

    my head explodes

    Any help and clarification appreciated

    Jim


    Q1 - volume ADVM is a type of special file created at the DG of the DSO.  Once created, it creates a block device on the BONE itself which can be used as any other block device.  http://docs.Oracle.com/CD/E16655_01/server.121/e17612/asmfilesystem.htm#OSTMG30000

    Q2 - the asm disk group is a group of disks, not really a logical volume.  It combines the attributes of both when it is used for purposes of database as the database and some other applications know how to talk about Protocol 'ASM '.  However, you won't find all the versatile applications that can do.  In addition, some clients prefer to deal directly with files and devices of volume systems which ADVM is forced to make.  In your thinking, you have 3 layers of logical disk, but each of them provides features and different attributes.  This is not a bad thing, though, as each has a slightly different purpose - os file system\device, specific database and storage-centric.

    Q3 - ADVM is specifically developed to extend the features of the DSO for use by General applications of BONE.  It includes the performance of database features and is tuned to work well in this situation.  Because it is developed in-house, it benefits from the design of ASM model.  In addition, rather than having to communicate with several vendors for support, your support is limited to calling Oracle, a single window.

    Q4 - you can create and modify filesystems ACFS by using command line tools and the ASMCA.  Creation and modification of logical volumes coming through SQL (ASM), asmcmd and ASMCA.  EM can also be used for the two elements.  ACFS is located at the top of the ADVM, which is a file in an ASM disk group.  ACFS is aware of the characteristics of the ASM\ADVM volumes and tunes it's IO make best use of these features.

    Q5 - several ways:

    1) connect to ASM with SQL, use 'alter diskgroup add volume' as Mihael points out.  This creates an ADVM volume.  Then, put in shape volume using the "mkfs" (* nix) or acfsformat (windows).

    (2) use ASMCA - a GUI to create volume and a file system.  Probably the easiest if your head is explosion.

    (3) use "asmcmd" to create a volume and 'mkfs' to put in shape file ACFS system.

    Here is information on the ASMCA, with examples:

    http://docs.Oracle.com/CD/E16655_01/server.121/e17612/asmca_acfs.htm#OSTMG94348

    Information about the command line tools, with examples:

    Basic steps to manage systems Oracle ACFS

  • [FATAL] [INS-30508] Invalid ASM disks.

    Dear gurus

    Please help to solve the no disk error invalid asm on solaris

    Oracle Grid 11.2.0.3.0

    Solaris10 with EMC Powerpath Partition

    -bash - $3.2. / runInstaller-silent - responsefile /aaa/Oracle11g_SunSPARC_64bit/grid/response/grid_install.rsp

    From Oracle Universal Installer...

    Check the Temp space: must be greater than 180 MB.   Real 90571 MB passed

    Check the swap space: must be greater than 150 MB.   Real 90667 MB passed

    Preparations for the launch of Oracle Universal Installer from/tmp/OraInstall2013-09-15_12-17-47 PM. Please wait...-bash - $3.2 [FATAL] [INS-30508] ASM invalid records.

    CAUSE: The disk [/ dev/rdsk/emcpower2a, / dev/rdsk/emcpower6a, / dev/rdsk/emcpower8a] were not valid.

    ACTION: Choose or enter valid ASM disks.

    A log of this session is currently registered as: / tmp/OraInstall2013-09-15_12-17-47PM/installActions2013-09-15_12-17-47PM.log. Oracle recommends that if you want to keep this log, you must move it from the temporary location to a more permanent location.

    Thank you for your reply and your time

    We had the problem of our self

    [/ dev/rdsk/emcpower2a, / dev/rdsk/emcpower6a, / dev/rdsk/emcpower8a]

    above default partition take slice 0

    We see link below

    Create the ASM Partitions in Solaris and add them as records of ACEs

    In architecture, Sparc, solaris disk is subdivided into 8 slices.

    This is the current configuration of these eight slices:

    slice 0: contains the files and directories that make up the operation

    System *.

    Unit 1: Swap, provides virtual memory or swap space.

    Unit 2: refers to the disk set, by convention. The size of this

    slice cannot be changed.* *.

    Unit 3: / export, holds different versions of the operating system.

    Unit 4: / export/swap. Provides virtual memory space for the customer

    systems. ***

    slice 5: large chocks software added to a system.

    Unit 6: / usr. Contains commands for operating system - also known under the name

    executables - designed to be run by the users.

    Group 7: / home. Contains files created by users.

    * Cannot be used as ASM disk. The use of this installment involves alteration of the disc

    and can make the disc unusable.

    * Should not be used as ASM virtual disk, slice refers to the entire disk

    (Including the partition tables).

    Is the range recommended to use for ASM disk.

    in accordance with the recommendation of the DSO we had used unit 4 the same

    so we had to diagnose details and came to know that must be used

    [/ dev/rdsk/emcpower2e, / dev/rdsk/emcpower6e, / dev/rdsk/emcpower8e]

    e make the unit 4

    We had use below evolution silent file and it works fine

    oracle.install.asm.diskGroup.disks=/dev/rdsk/emcpower2e,/dev/rdsk/emcpower6e,/dev/rdsk/emcpower8e

    newspapers of the sample

    INFO: From Threads drive output for process/tmp/OraInstall2013-09-17_05-03-21 PM/ext/bin/kfod

    INFO: Parsing 2560 CANDIDATE/dev/rdsk/emcpower2e oracle oinstall

    INFO: Process/tmp/OraInstall2013-09-17_05-03-21 PM/ext/bin/kfod came out with code 0

    INFO: Waiting for threads processor out to leave.

    INFO: Parsing 2560 CANDIDATE/dev/rdsk/emcpower6e oracle oinstall

    INFO: Parsing 2560 CANDIDATE/dev/rdsk/emcpower8e oracle oinstall

  • Disgroup unable to mount ASM (disk error exist not at all)

    one of our RAC system have ill of ASM.

    ASM guest 3,4,5 disc error is missing, while we, that there is only the configured disk 1,2,3 for FLIGHT 1,2,3
    on the two nodes of the RAC

    1. How can we be sure where Disc 3,4,5 is?
    2. how to get rid of this non - exist disks?

    Thank you all for the replies and advice

    BR/ricky

    alter diskgroup asm_sai mount

    *

    ERROR on line 1:

    ORA-15032: not all changes made

    ORA-15040: diskgroup is incomplete

    ORA-15042: ASM '5' disc is missing

    ORA-15042: ASM disk '4' is missing

    ORA-15042: ASM disk '3' is missing


    /etc/init.d/oracleasm listdisks

    VOL1

    VOL2

    VOL3


    Device "/ dev/emcpowere1 ' is marked an ASM disk with the label"VOL1 '.

    Device "/ dev/emcpowerf" is not marked as a disc of the ASM

    Device "/ dev/emcpowerf1 ' is marked with an ASM disk with the label"VOL2 ".

    Device "/ dev/emcpowerg" is not marked as a disc of the ASM

    Device "/ dev/emcpowerg1 ' is marked with an ASM disk with the label «VOL3»


    Select GROUP_NUMBER, NAME, STATE, TYPE of v$ asm_diskgroup;

    GROUP_NUMBER STATE TYPE NAME

    ------------ ------------------------------ ----------- ------

    0 REMOVED ASM_SAI

    Select GROUP_NUMBER, DISK_NUMBER, MOUNT_STATUS, State, NAME, path of v$ asm_disk;

    GROUP_NUMBER DISK_NUMBER MOUNT_S STATE NAME

    ------------ ----------- ------- -------- ------------------------------

    PATH

    --------------------------------------------------------------------------------

    0 NORMAL 0 CLOSED

    ORCL:VOL1

    0 2 CLOSED NORMAL

    ORCL:VOL3

    0 1 CLOSED NORMAL

    ORCL:VOL2

    What version of Oracle and what operating system are you using?

  • Remove/add question ASM Disk

    Hi all

    I have a small question-

    We have an ASM Diskgroup that had 8 drives in it. I removed 2 Diskss and the Diskgroup has been rebalanced. I did not do anything with the disks removed.

    They both appear in the target of the DSO as qualified to add in the Diskgroup.

    Do I need to re-format/partition/create disc on them before adding them back in? Existing data on the Diskl would cause a problem in the Diskgroup?

    This is the first time I'll add back discs that were previously in the Diskgroup.

    Thanks in advance for the advice.

    Michele

    Hello

    Disks can be assigned to a diskgroup must have the status of 'CANDIDATE' or 'OLD' or 'CONFIGURED '.

    · CANDIDATE - disk is not part of a disk group and may be added to a disk with the ALTER DISKGROUP statement group

    · Provisioned - disk is not part of a disk group and may be added to a disk with the ALTER DISKGROUP statement group. The status of CONFIGURED header is different from the
    Header in the CONFIGURED one CANDIDATE country status means that an additional platform-specific action was taken by an administrator to allow the ASM disk.

    · FORMER - disk was once part of a disk group, but has been removed itself from the group. It can be added to a new group of disks with the ALTER DISKGROUP statement.

    The ALTER DISKGROUP... REMOVE the DRIVE without option statement WAITING returns before the fall and rebalancing are completed. Do not re-use, remove or disconnect drive fell to the HEADER_STATUS column for this disc in the view V$ ASM_DISK changes to the FORMER.

    You can't change anything at the OS level. Oracle will reuse without needs asmdisk perform all administrative tasks at the level of the BONE.

    Kind regards
    Levi Pereira

Maybe you are looking for