The ASM diskgroup in exadata space question

Similar Questions

• 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

• How to identify the ASM DiskGroup attached to which disks?

  Hi guys,.
  
  In RAC 11 GR 2, how to identify which ASM Diskgroup is attached to which disks... (OS is RHEL 5.4).
  
  We could list ASM starts by,
  *#oracleasm listdisks * but this command does not display the disks assigned to ASM DiskGroup.
  
  Even for check location of OCR and voting disks only show Diskgroup name and not the actual discs.
  $ocrcheck
  $crsctl query css votedisk
  
  
  (as in gr 10, 2 RAC, we entered /etc/rules.d/udev/60-raw-rules raw file mapping of the OCR, voting disk and other ASM Diskgroup)
  
  
  Please help me, as long as the customer place, I could see LUN as assigned to the server and get is not an exact idea whose records have been used for OCR and voting disk DATA Diskgroup.
  
  
  Thank you
  Manish

  And for this, you can use oracleasm querydisk. Using that you can identify which device marked for asm or not. for example you can see below the example.

  [oracle@localhost init.d]$ sqlplus "/as sysdba"
  
  SQL*Plus: Release 10.2.0.4.0 - Production on Thu Jun 3 11:52:12 2010
  
  Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.
  
  Connected to:
  Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
  With the Partitioning, OLAP, Data Mining and Real Application Testing options
  
  SQL> select path from v$asm_disk;
  
  PATH
  --------------------------------------------------------------------------------
  /dev/oracleasm/disks/VOL2
  /dev/oracleasm/disks/VOL1
  
  SQL> exit;
  
  [oracle@localhost init.d]$ su
  Password:
  [root@localhost init.d]# /sbin/fdisk -l
  
  Disk /dev/sda: 80.0 GB, 80000000000 bytes
  255 heads, 63 sectors/track, 9726 cylinders
  Units = cylinders of 16065 * 512 = 8225280 bytes
  
     Device Boot      Start         End      Blocks   Id  System
  /dev/sda1   *           1        1305    10482381   83  Linux
  /dev/sda2            1306        9401    65031120   83  Linux
  /dev/sda3            9402        9662     2096482+  82  Linux swap / Solaris
  /dev/sda4            9663        9726      514080    5  Extended
  /dev/sda5            9663        9726      514048+  83  Linux
  
  Disk /dev/sdb: 80.0 GB, 80026361856 bytes
  255 heads, 63 sectors/track, 9729 cylinders
  Units = cylinders of 16065 * 512 = 8225280 bytes
  
     Device Boot      Start         End      Blocks   Id  System
  /dev/sdb1               1        4859    39029886   83  Linux
  /dev/sdb2            4860        9729    39118275   83  Linux
  [root@localhost init.d]# ./oracleasm querydisk /dev/sdb1
  Device "/dev/sdb1" is marked an ASM disk with the label "VOL1"
  [root@localhost init.d]# ./oracleasm querydisk /dev/sdb2
  Device "/dev/sdb2" is marked an ASM disk with the label "VOL2"
  [root@localhost init.d]# ./oracleasm querydisk /dev/sda1
  Device "/dev/sda1" is not marked as an ASM disk
  [root@localhost init.d]#
  

  Also in windows:

  C:\Documents and Settings\comp>asmtool -list
  NTFS                             \Device\Harddisk0\Partition1           140655M
  ORCLDISKDATA1                    \Device\Harddisk0\Partition2             4102M
  ORCLDISKDATA2                    \Device\Harddisk0\Partition3             4102M
  NTFS                             \Device\Harddisk0\Partition4           152617M
  
  C:\Documents and Settings\comp>
  

  answered by Alex.
  Reference:-How to identify what disc rawdevice is named as VOL1 in ASM OS level

  Happy new year.
  Kind regards

• ASM diskgroup space do not free themselves after RMAN archivelog delete

  Version Infra grid: 11.2.0.4

  DB version: 11.2.0.4

  OS: Oracle Linux 6.4

  Storage: Enterprise-class storage (EMC VMAX)

  We are in the Bank we have a database of CARS of Production 2 nodes very critical.

  Newspaper archives are stored in ARCH_DG diskgroup. Because of the unexpectedly heavy workload, our diskgroup ARCH_DG became full and we got the usual error

  ORA-00257: archiver error. Connect internal only, until this just released.

  To wear the DB back to business quickly, I tried to delete the old archive logs more than 1 day of the diskgroup first using the following command

  RMAN > delete noprompt archivelog until ' SYSDATE-1';

  So, I started to see the following message

  
  

  RECID = STAMP 19807 = 849396325 name=+ARCH_DG/bsoaprd/archivelog/2014_06_04/thread_2_seq_10066.331.849396309 archived log file

  Delete archived log

  RECID = STAMP 19809 = 849396940 name=+ARCH_DG/bsoaprd/archivelog/2014_06_04/thread_2_seq_10067.274.849396925 archived log file

  Delete archived log

  name=+ARCH_DG/bsoaprd/archivelog/2014_06_04/thread_2_seq_10068.341.849397529 RECID archived log file = 19810 STAMP = 849397543

  Delete archived log

  name=+ARCH_DG/bsoaprd/archivelog/2014_06_04/thread_2_seq_10069.298.849398167 RECID archived log file = 19812 STAMP = 849398182

  Delete archived log

  RECID = STAMP 19813 = 849398806 name=+ARCH_DG/bsoaprd/archivelog/2014_06_05/thread_2_seq_10070.317.849398783 archived log file

  Delete archived log

  name=+ARCH_DG/bsoaprd/archivelog/2014_06_05/thread_2_seq_10071.342.849399327 RECID archived log file = 19814 STAMP = 849399337

  Although I could see messages "deleted archived newspaper" as stated above there are 2 inconsistencies (odd behavior)

  1 inconsistency. Not a single byte released upwards of archive diskgroup. Each log archiving is 4 GB in size. I got "journal archived deleted" message at least 25 archived log files. For example, 100 GB should have been released.

  The diskgroup to archive has remained at 99.9% as shown below and the DB was inaccessible.

  SQL > select name,.

  Round(total_mb/1024,2) Total_GB.

  Round(free_mb/1024,2) Free_GB.

  free_mb/total_mb * 100 "% free"

  ABS ((free_mb/total_mb*100)-100) '% complete '.

  v $ asm_diskgroup;  2 3 4 5 6

  NAME TOTAL_GB FREE_GB % free full
  ------------------------------ ---------- ---------- ---------- ------------
  ARCH_DG 1000.78 99.9223633.077636719
  DATA_DG 10000.02 1188.19 11.8818616 88.1181384
  OCR_VOTE_DG 12 11.09 92.4623525 7.53764754
  < snipped >

  
  

  Inconsistency2. The number of available archived newspapers remained unchanged. He was always showing 301

  SQL > select count (*) from v$ archived_log where status = 'A ';

  COUNT (*)

  ----------

  301

  RMAN later > remove obsolete; command removed 17 archived newspapers.

  This means that 17 x 4 = 68 GB should have been released.

  But Diskgroup of free space and the County of v$ archived_log.status = 'A' is unchanged, as mentioned above.

  , Of ASMCMD, I deleted manually a full archive directory connects using rm-rf command.

  Even after running rm - rf on a whole directory full of archived newspaper space was not released and we always receive ""ORA-00257: archiver error '. "

  So, we had to shoot down the cluster using "stop crsctl crs. After the cluster has been raised using 'crsctl start crs' on both nodes,

  space has been freed up, and the DB became accessible.

  I wonder why the ASM diskgroup space was not release despite the removal of the archive logs. Are the 1 & 2 above mentioned inconsistencies caused by something handle to open the file ?

  Hello

  Please run command you at the level of the ASM, below

  SQL > alter diskgroup check all the repair;

  -At the end of the same thing, run below command and enable it to perform

  SQL > alter diskgroup rebalance power 4.

  -To validate the space

  $ asmcmd Pei lsdg

  Kind regards
  Loriette

• Display spfile ASM diskgroup while the database cannot be started?

  Hi all
  
  We are 10.2.0.3 and window 2003 server. And the init.ora file has a line in ' SPFILE='+DG_DATA/MITCH/spfileMITCH.ora'.
  
  Once I cannot start the database and got the below error. I googled and he said if I can reduce large_pool_size or sga_target, I should be able to start. But I need to know what in the spfile to create the new file init. So my question is how to view the contents of a SPFILE recorded in the ASM diskgroup. I have leans on the log of alerts to found the parameter values. But I don't know if there is a way better and safer to enter the SPFILE. Thanks in advance for your help,
  
  Shirley
  
  ORA-27102: out of memory
  OSD-00026: additional error information
  S/O-error: (OS 1455) the pagefile is too small for this operation ends

  Shirley,

  Not even in normal file system you "cannot read spfile. Its always better to create pfile from spfile

   sqlplus '/as sysdba'
   sqlplus >create pfile='/location/init.ora' from spfile;
  
   or you can start an instance with pfile
   sqlplus> startup nomount pfile='/location..../init.ora';
   If successfully processed all the parameters
   sqlplus>alter database mount;
   sqlplus>alter database open;
  
   If successful shutdown it down and create spfile from pfile='/location/init.ora';
  
   sqlplus>create spfile from pfile='/location/init.ora';
   sqlplus>startup;
  

  Concerning

• DBFS ASM diskgroup

  Re: our new X 3 machines (in the data center, not yet installed).

  I know that some of these was kind of covered in the previous thread on DBFS. However, I have a little different issues...

  I understand that the DBFS ASM diskgroup is mandatory and that, due to the nature of how calculated its size, the ACS consultants set to its minimum size. However, is it possible (preferably at configuration time) increase the ASM diskgroup? Or is it meant to be a size defined, anything?

  Oracle, told me that I could put newspapers Flashback in DBFS ASM diskgroup (as long as I don't configure DBFS to use, of course). I don't know that I've read that Flashback Logs MUST be put in the db_recovery_file_dest (fast recovery or RECO diskgroup area). Anyone used DBFS (ASM diskgroup) for such storage? I know that this is not IDEAL given the fact, that it won't spread across all storage cells, but I'm trying to find a way to separate newspapers archive logs Flashback as we monitor the location of the log archiving for the use of space (we get an alert if it becomes too full and automatically kick off an archivelog backup/purge at a certain level of use).

  Mark

  Spinning two first records on each cell contains a partition of 29 GB in size with the operating system. The other 10 contain rather a GridDisk 29 GB size where the diskgroup DBFS_DG is built. In other words: DBFS_DG The diskgroup is spreading through all the cells, but only on 10 discs (not 12 as DATA and RECO) on each cell.

  In this way, the GridDisks that make up DATA and RECO can be the same size on all readers of spinning. And the diskgroup DBFS_DG consume about 300 GB on each cell for this reason, which can not be changed reasonably, I guess.

  You can set DB_RECOVERY_FILE_DEST = '+ DBFS_DG' and turn on Flashback Database, so that Flashback Logs are generated, even if you set LOG_ARCHIVE_DEST_1 in the diskgroup RECO, so that Archivelogs get stored there. And with RMAN backups, you specify the FORMAT '+ RECCE' to get the backups in the recovery area (DBFS_DG in this example).

  Kind regards

  Uwe Hesse

• How to stop the ASM

  How to stop the ASM 11 g, I have question smiler mentioned in the thread, I just want to know if this question or 11g feature.
  
  
  
  
  Unable to stop ASM 11 g R2

  Here, if your use of OCR in diskgroup in ASM, then no way to cpl using srvctl, you have to stop, the Group of cpl, This is reading, I got from oracle.

• ASM Diskgroup

  Hello

  SQL > select NAME from v$ asm_diskgroup;

  NAME

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

  DATA

  FRA

  SQL > show disk parameter;

  VALUE OF TYPE NAME

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

  asm_diskgroups string FRA

  asm_diskstring string/dev/oracleasm/disks

  I wonder why these two commands produce two different values for asm_diskgroups?  Could someone please give me a hint?

  Hello

  The ASM Diskgroup can be started in multiple ways.

  11.2 docs

  On attachment to the boot disk groups

  At startup, the Oracle ASM instance try to mount the following disk groups:

  • Drive of the specified groups in the ASM_DISKGROUPS initialization parameter
  • Group of disks used by the Cluster Synchronization Services (CSS) for the vote of the files
  • Groups of disks used by Oracle Clusterware for Oracle Cluster Registry (OCR)
  • Group of disks used by the Oracle ASM instance to store the settings of the server ASM (SPFILE) file

  If no disk group are in the previous list, then the instance Oracle ASM do not mount at startup disk groups.

  What I see is happening... .i, please post below

  When you start the ASM, oracle will try read header of all the disk/LUN using asm_diskstring parameter in OCR/RSC (srvctl config asm) or spfile. If find ASM no matter what set of ASM DISKS it will try to mount automatically, because only when the DSO starting, he will deliver ALTER DISKGROUP MOUNT ALL.

  ASM find / know what are diskgroup can be mounted due head ASM DISK that contains this info on diskgroup.

  Other cases

  ASM is set on not (AUTO_START = never) automatically starts and is not not running, but the database is configured to start automatically (AUTO_START = always) and database dependency with diskgroup resource (for example, ora. DATA.dg), so during the startup of the crsd resource lance database dependency CSSD > ASM > DISGROUP > DATABASE

  11 GR 1 material and beyond... A lot of things (asm diskgroup, databases, etc.) became the resource managed by CRSD. Thus, by default, these resources are managed by CRSD not only by itself. I mean crsd knows and manage what resource needs to be started or a stop in the correct order.

  On your case a database resource can be begin your ASM diskgroup

  START_DEPENDENCIES = hard (ora. DATA.dg, ora. FRA.dg)

  This means that this resource will start only if these diskgroup and all its dependencies set first.

  Post edited by: Levi-Pereira

• Adding to the capacity of the disks to existing ASM DiskGroup

  Hi, I have a Production (11.2.0.3) sitting on a RAC LIB 6.3 cluster database platform with storage of ASM and everything works normally, but I'm running out of space in one of disk groups.

  I drive new capabilities to add to this group of disks, but when I run the following command to root OS no entries are returned:

  /etc/init.d/oracleasm listdisks

  If I go into ASMCMD and run lsdsk, I get the following returned:

  / dev/map/oradata

  / dev/map/oraflash

  Also, if I connect to the instance of the ASM of network user name and perform the following steps, I get the following text:

  SQL > select name from V$ ASM_DISKGROUP;

  NAME

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

  DATA

  FLASH

  My question is why /etc/init.d/oracleasm listdisks command returns no results?  Note that I've done the scandisks /etc/init.d/oracleasm on both nodes.

  The disc, I want to add is called/dev/map/oradata2

  When I go to the /etc/init.d/oracleasm/dev/map/oradata2 DATA2 createdisk to create the disc, and run the scandisks on both nodes, I guess the listdisks still not will be able to list the discs of data, Flash and Data2

  My big concern is that when I add create disc on Node1, Node2 might not be able to see the newly created disk when I run the command Scandisks.

  Here, any help would be appreciated.

  Oracleasm will be only the list disks that have been added and marked by using the command "oracleasm createdisk. You can also pay attention to the ORACLEASM_SCANEXCLUDE variable, which can hold devices names oracleasm must ignore. To see the devices in a cluster, your devices must be shared, which is the underlying storage topology.

• 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

• Question of the ASM

  Hello
  
  I'll put up a 11.2.0.3 new install and I have a problem in my hands a little bit.
  
  While doing the installation, I created the asm on a partition disk in:

  oracleasm createdisk DATA /dev/sdb2

  Now, after rebooting, it may be the case when my score is not identified as/dev/sdb2 more instance cannot find the disc, so I need to tag it with something like

  e2label <partition> <labelname>

  to ensure consistent names after a reboot and my instance ASM will not fail
  
  My question is, can I I "remap" the ASM/dev/sdb2 < labelname > disc without having to recreate all over again? If so, how?
  
  Thank you
  NACEUR

  N wrote:
  ASM autonomous, that is right.

  oracleasm createdisk is executed before installing the GRID.

  just now, I am from sracth, comes to complete installation of oel6 and create the partitions with fdisk on my raid1 + 0
  one that I have already formatted with ext3 and im moving the installers to the server to start

  Any guide you know I can't go through?

  Have not yet installed oracleasm.

  The next steps so far are:
  -Once all the installation on the server programs I'm good to go with oracleasm
  --> Create disc on an unformatted partition/dev/sdb2
  --> install grid
  --> create diskgroup
  --> install 11 GR 2
  --> instance to create

  DO NOT use oracleasm - as I have said, it is expected to be close to retirement. If you don't want to be related to it.

  Make sure that the device has the appropriate permissions before you start.
  In the installation program, select ASM for OCR. in the lower right corner to select CHANGE DISKSTRING and configured to point to/dev/sd * and he sees only one with the correct permissions. It will ask you the name of diskgroup, and you select the sdb2 with REDUNDANCY EXTERNAL device. It will automatically load the initial configuration. Watch the udev.config to find out how to set permissions on startup

  I don't usually promote other websites, but this looks like a good start on how to correctly configure udev...
  http://www.Oracle-base.com/articles/Linux/udev-SCSI-rules-configuration-in-Oracle-Linux-5-and-6.php#create_udev_rules_file

  >

  If you could point me to a guide on how can I do this without using asmlib I would be grateful.

  Do not!

• Best approach to replace the storage of an ASM diskgroup nondisruptive?

  Hi Experts,

  Please advise what the best approach is to replace the storage of ASM diskgroup without downtime, or minimal service interruption?

  Thanks in advance.

  RAJ_KUMAR wrote:

  Hi Experts,

  Please advise what the best approach is to replace the storage of ASM diskgroup without downtime, or minimal service interruption?

  Thanks in advance.

  New drive for fixation to the BONE

  Add the new disk to the selected disk group

  Wait for rebalancing complete

  remove old disk of selected disk group.

  Wait for rebalancing complete

  I just finished the migration to an all new SAN with zero downtime.

• 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

• resize the disk/diskgroup LUN and asm

  Happy new year to all.
  
  I have a little problem of resizing an ASM diskgroup and maybe someone here can help me.
  
  I had a lun with size 50G and added on a disk called LUN1D1 asm.
  Then I created a DISKGROUP called data1 Witch (external) contain some LUN1D1.
  Data1 is then conducted asm volume. So I have a volume of asm with size 50G and I need 100 g.
  
  Now, I have increased the size of the lun with 50 G (100G in total). I rescaned the LUN and os see the new size.
  
  The problem is that I can't resize DISKGROUP data1 or disk LUN1D1.
  
  Database of oral 11.2.0.3.0 x 64

  KFOD read the values of the BONE, so something is wrong on the BONE and does not recognize these new values.

  Did you follow the following steps?
  http://www.Novell.com/support/kb/doc.php?id=7009660

• How to find the drive assigned to ASM diskgroup

  Hi all
  I created some ASM disks and do not know if I attributed to a diskgroup. Please may I know how to find the disc by ASM diskgroup or free on the disk that can be used.
  
  
  Thank you.

  Hello

  You must make reference to:
  http://download.Oracle.com/docs/CD/B28359_01/server.111/b31107/asmdiskgrps.htm#CHDIBGGH
  If you scroll down a bit you'll find: "groups example 4-3 look at a disk with associated disks.

  You can also check more specifically:
  http://www.Stanford.edu/dept/ITSS/docs/Oracle/10G/server.101/b10755/dynviews_1019.htm

  HTH,
  Thierry