Create the ASM disk groups instance is not found

Similar Questions

• Add more space to the ASM disk group

  Hi all

  I am new to the DBA role and also in a process of learning. I need your help in putting a space at the ASM disk group. My VMware admin will add disk space to the virtual machine, and then the Linux admin will add space on Linux servers. Finally, I think I need to rebalance the database disk group to view the extra space. I'm not sure of what all the steps involved in this process. I like to read the Oracle Documentation, but I'm blurry and hesitant. Please let me know the steps to follow to add the ASM disk group space.

  We use

  Oracle DB version 11.2.0.3.0

  Linux version: 2.6.18 - 238.12.1.el5

  Thanks for your help

  No....

  You don't need any instance restart. More when you add a disk to a diskgroup, all rac nodes can see.

  just...

  You should add a node and watch v$ asm_operation...

  Concerning

• How to increase space in the ASM disk groups?

  Hi all

  I'm a newbie DBA in my team and today morning received an alert of OEM which:

  Target name = + ASM_ZEUS.techiebros.com

  Message = disk group DATA requires rebalance because at least a disk space is low.

  Any solution?

  To fix this, you can run this command: Alter diskgroup ASMDB add drive "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>

• 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

• RunInstall does not show the ASM disks

  Hello

  I googled arleady for so long but I can't find the solution for my problem.

  I'm under runInstall of the Oracle Grid Infrastructure installation program. When it comes to "Create the ASM disk groups", the window does not show one of my starts created previously, even if I change the discovery trail to ' / oracleasm/dev/discs / * "Please help!

  [dev root@grid1] # / usr/sbin/oracleasm listdisks

  DATA01

  DATA02

  FRA01

  FRA02

  OCRVOTE01

  OCRVOTE02

  OCRVOTE03

  [dev root@grid1] # / usr/sbin/oracleasm-discover

  ASMLib /opt/oracle/extapi/64/asm/orcl/1/libasm.so using

  [Library ASM - Generic Linux, version 2.0.4 (KABI_V2)]

  Disk discovery: ORCL:DATA01 [31455232 blocks (16105078784 bytes), maxio 512]

  Disk discovery: ORCL:DATA02 [31455232 blocks (16105078784 bytes), maxio 512]

  Disk discovery: ORCL:FRA01 [20969472 blocks (10736369664 bytes), maxio 512]

  Disk discovery: ORCL:FRA02 [20969472 blocks (10736369664 bytes), maxio 512]

  Disk discovery: ORCL:OCRVOTE01 [10477194 blocks (5364323328 bytes), maxio 512]

  Disk discovery: ORCL:OCRVOTE02 [10483712 blocks (5367660544 bytes), maxio 512]

  Disk discovery: ORCL:OCRVOTE03 [10483712 blocks (5367660544 bytes), maxio 512]

  [dev root@grid1] # / usr/sbin/oracleasm querydisk DATA01

  Disk 'DATA01' is a valid ASM disk

  [records root@grid1] # pwd

  / dev/oracleasm/Disks

  [records root@grid1] # he's

  Total 0

  BRW - rw - 1 grid asmadmin 8, 65 4 Mar 11:18 DATA01

  BRW - rw - 1 grid asmadmin 8, 81-4 Mar 11:18 DATA02

  BRW - rw - 1 grid asmadmin 8, 97-4 Mar 11:18 FRA01

  BRW - rw - 1 grid asmadmin 8, 113 4 Mar 11:18 FRA02

  BRW - rw - 1 grid asmadmin 8, 17 4 Mar 11:16 OCRVOTE01

  BRW - rw - 1 grid asmadmin 8, 33-4 Mar 11:17 OCRVOTE02

  BRW - rw - 1 grid asmadmin 8, 49-4 Mar 11:17 OCRVOTE03

  [records root@grid1] # rpm - qa | grep oracle

  oracleasm-support - 2.1.8 - 1.el6.x86_64

  oracleasmlib - 2.0.4 - 1.el6.x86_64

  oraclelinux-release-6Server - 6.0.2.x86_64

  oraclelinux-release-notes-6Server - 14.x86_64

  kmod-oracleasm - 2.0.8 - 4.el6_6.x86_64

  Oracle-logos - 60.0.14 - 1.0.2.el6.noarch

  to clarify this, please login as user "grid" and run the command
       id

  This will show you if id is a member of the Group asmadmin.

  Martin

• 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

• How to move or migrate whole directories between ASM disk groups?

  Hi all!
  
  I'm playing with Oracle ASM and Oracle Database 11 g R1, I am a student. It's just for testing purposes.
  
  Features of the computer are:
  Processor: Intel Pentium 4 HT 3.00 Ghz.
  Memory RAM: 2 GB.
  Hard drive: 250 GB
  O.S.: Windows XP Professional Edition SP 2.
  
  I installed Oracle ASM, I have created an ASM disk group (+ FRA), I installed Oracle Database and I created a test database. The database works correctly on the ASM disk group. Days, I got help on the initialization parameters, DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_1, DB_CREATE_ONLINE_LOG_DEST_2 and DB_RECOVERY_FILE_DEST, according to their function, I created another 3 ASM (+ FILES, LOG1, LOG2) disk groups. There are four initialization settings pointing to its corresponding ASM disk group. As you can deduce, for the time of installation of the Oracle database, I used the ASM '+ FRA' disk group and inside the directories were created: CONTROLFILE, DATAFILE, ONLINELOG, fichier_parametres, TEMPFILE, and the SPFile.
  
  My point is that I want to move or migrate the DATAFILE, fichier_parametres, TEMPFILE directories and the SPFile to '+ FILES', ONLINELOG and CONTROLFILE to '+ LOG1' and '+ LOG2', in this way, the ASM '+ FRA' disk group will contain the Flash recovery area only. What is the procedure for that?
  
  Thanks in advance!

  user1987306 wrote:
  Hi all!

  My point is that I want to move or migrate the DATAFILE, fichier_parametres, TEMPFILE directories and the SPFile to '+ FILES', ONLINELOG and CONTROLFILE to '+ LOG1' and '+ LOG2', in this way, the ASM '+ FRA' disk group will contain the Flash recovery area only. What is the procedure for that?

  Thanks in advance!

  Hello

  There are two approaches that you can use, here are some
  -To move the data file, start the database in State of Mt.
  RMAN > copy datafile '+ FRA/xxx' to '+ FILES1 ";
  SQL > alter database file rename '+ FRA/xxx' '+ fichiers1/xxx. "

  -To move the temporary file
  SQL > alter tablespace TEMP add tempfile '+ FILES1' SIZE 10 M;
  SQL > alter database file temporary '+ FRA/xxx' drop;

  -To move onlinelog
  SQL > alter database add logfile Member '+ LOG1' group 1;
  SQL > alter database add logfile Member '+ LOG2' group 1;
  SQL > modify the members of database drop logfile "+ FRA/xxx."

  -To move controlfile
  SQL > restore controlfile on '+ FILES1' of '+ FRA/xxx. "
  the spfile update to reflect the new location of the controlfile

  See you soon

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

• 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

  

• 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

• 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

• Reinstallation of Oracle 11 g 2 RAC grid problem - ASM disk group

  People,
  
  Hello.
  
  I want to install Oracle 11 g RAC 2 with 2 Virtual Machines (rac1 and rac2 which BONES are Oracle Linux 5.6) in VMPlayer.
  
  I was installing Infrastructure of grid using runInstaller in the first rac1 VM from step 1 to step 9/10.
  
  On 9/10 in the wizard step, by chance, I touch the mouse, and the wizard disappeared.
  
  The grid in the 2 VMs installation directory is the same: / u01
  
  I have to make sure that everything is correct, delete the directory/U01 to 2 virtual machines and install again the grid in rac1.
  
  I realized that this is not the right way to remove/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 must correct one by one. I reinstall the grid and get the error message in step 5 of 9 as follows:
  
  [INS - 30516] Please specify unique disk groups.
  [INS-3050] ASM disk group empty.
  Cause - the installer has detected the name of Group of disk already exists on the system.
  Action - specify the different disk group.
  
  In the wizard, the old disk group name is 'DATA' and his candidate records (5 ASMDISKs) are gone. I try to use another name "DATA2", but no ASMDISKs are "candidate records. For "All discs", it is impossible to select all ASMDISKs.
  
  I want to use the same disk group ASM 'DATA' and do not want to create a new disk group.
  
  My question is:
  
  How to make previous ASM disks and his group of 'DATA' therefore "Candidate records" who can use again?
  
  
  Thank you.

  Hello
  If you use oracleasm, then rebuild again asm disks.

  oracleasm deletedisk

  http://sabdarsyed.blogspot.com/2007/07/installing-configuring-Oracle-ASM-on.HTML should help. (use only delete and create orders without having to reinstall again)

• 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

• 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

• Cannot create the ASM Diskgroup ORA 15020 and ORA-15018

  Hello team,

  Could not create the ASM diskgroup with the following error:

  SQL > create diskgroup redundancy data_asm1 external disk ' / dev/sdf *;

  create diskgroup redundancy data_asm1 external disk ' / dev/sdf. "

  *

  ERROR on line 1:

  ORA-15018: diskgroup cannot be created.

  ORA-15020: discovered in double disc ASM 'DATA_ASM1_0000 '.

  ASM Diskstring

  SQL > show parameter asm_diskstring

  VALUE OF TYPE NAME

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

  asm_diskstring string/dev/oracleasm/disks/DISK *, /dev / sd *

  Please let me know how to solve this problem

  Kind regards

  Hello

  check your disc diskgroup status grid +. display result

  1 res ora of $ crsctl State. GRID.dg or $ crsctl status res ora.grid.dg

  Note the distinction uppercase / lowercase of the crs resource

  2. run below as a user of the grid. (necessary to set SID = + ASM? If not already preset)

  ASMCMD > lsdg

  Tobi