ASM Diskgroup existing disks

Similar Questions

• Transfer data from local disk to Asm Diskgroup and vice versa

  Hi all

  I have two node rac installation and now I want to move the data from local disk to ASM DiskGroup.

  Is it possible, if yes, then please mention the way to him.

  Kind regards

  Ronak

  Hi all

  Thank you. Found that its possible using package 'DBMS_FILE_TRANSFER '.

  Kind regards

  Ronak

• 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 with 1 disk? Is this possible?

  setenv ORACLE_SID + ASM
  sqlplus "/ as sysdba".
  SQL > startup nomount
  SQL > create diskgroup data disk ' / dev/dsk/c0t5d1s4 ";
  SQL > shutdown immediate
  SQL > startup mount
  
  
  ^^
  I saw once on the google site a syntax as above. I was under the assumption that, for alteast disks 2 ASM are required (assuming normal redundancy); But here we can see one disc is defined.
  
  Sorry, I don't have an ASM Setup to test this, so would you need advice from people.

  By default, ASM tries to create a normal redundancy disk group. Therefore, he expected to have at least 2 groups of disks.
  But yes, even with one disk, you can create a disk group, but you must expressly state that it will be external redundancy.

  ++
  Connected to:
  Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
  With partitioning, OLAP, Data Mining and Real Application Testing options

  SQL > create diskgroup abc disk ' / dev/raw/raw6 ";
  create diskgroup abc disk ' / dev/raw/raw6.
  *
  ERROR on line 1:
  ORA-15018: diskgroup cannot be created.
  ORA-15072: command requires at least 2 groups of failure, discovered only 1
  +++

  +++
  Connected to:
  Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
  With partitioning, OLAP and Data Mining options

  SQL > create diskgroup abc disk ' / dev/raw/raw3 ';
  create diskgroup abc disk ' / dev/raw/raw3 '.
  *
  ERROR on line 1:
  ORA-15018: diskgroup cannot be created.
  ORA-15072: command requires at least 2 groups of failure, discovered only 1

  SQL > create diskgroup redundancy abc external disk ' / dev/raw/raw3 ';

  DiskGroup created.
  +++

• How to OCR and the drive to vote of raw devices for ASM diskgroup

  Hello
  
  I plan to upgrade my environment clusterware/ASM 11.1.0.6 to the grid
  infrastructure 11.2.0.1 on Solaris sparc 64-bit.
  I also plan on spending the OCR and discs of raw devices to ASM voting
  starts. But how to do? When should I do: upgrade
  process or after the upgrade? When should I start?
  
  Thank you

  create a disk group or use an existing disk group that matches your redundancy needs

  To ocr asm
  ===============
  1 ensure that the clusterware version 11.2.0
  # crsctl query crs activeversion
  Oracle Clusterware version active on the cluster is [11.2.0.1.0]

  2. replace the OCR file by the asm disk group
  #ocrconfig - replaced - replacement<+ASM diskgroup="">

  3 remove the old file ocr
  #ocrconfig - remove

  4. check the integrity of the ocr
  $cluvfy comp ocr n - verbose

  SE asm votedisk
  ======================
  1. Add the voting disk to the asm disk group
  #crsctl replace votedisk<+asm disk="" groupname="">

  Note: According to the disk group redundancy the required number of ocr and voting disk files will be created
  Normal: 2ocr, 3voting disc
  For the great: 3 ocr, voting 5 disc

  do not backup the ocr/votedisk dd in 11.2.0

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

• That means recommended recommended for an ASM diskgroup to maintain production database?

  Dear Experts,

  That means recommended recommended for an ASM diskgroup to maintain production database?

  + DATA

  to keep the redo log groups redo1a, redo2a, redo3a with 3 members = redo1b, redo2b, redo3b, redo1c, redo2c, redo3c

  to organize 3 controlfiles

  organize storage of data files

  to keep the index tablespaces

  How many disk (as a point of reference)

  + FRA

  Where to place archivelogs

  Thanks in advance,

  Kind regards

  IVW

  Salvation;

  A good practice is:

  + DATA holds:

  • Redo log files, Member 1.
  • Control file.
  • Data files.

  + FRA holds:

  • Redo log files, Member of the 2.
  • Control file
  • Backup of files: archived redo logs, control automatic file backups, spills auto backups, copies, backup sets, flashback logs.

  This is the distribution of files most used; but always distribution will depend on the size of your database and how do you set up your database. Remember that you need to know how your database works. As Aman said in another post, distribution of files depends on how many disk groups you can have, depending on the speed of the disc.

  Kind regards.

  Willy

• 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

• 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

• The ASM diskgroup in exadata space question

  All,
  
  I have an environment exadata 1 CCR node with 3 knots of strorage.
  
  My RECO ASM diskgroup is constantly showing the problems of space... Always higher than 80%.
  
  I just want to get a Board if I can remove mirroring and recover the space... Even though I know that the result of the deletion of the mirroring...
  
  Can I reduce the diskgroup RECO and create an another diskgroup?
  
  I want just a few ideas to do this without great risk involved...

  You may want to consider these MOS notes for more information on resizing the griddisks:
  Resize diskgroup without downtime to Exadata (Doc ID 1272569.1)
  How to resize the disk drive/grid ASM in environment Exadata (Doc ID 1245494.1)

  As others have mentioned, there is no way to change the level of redundancy in ASM, so you need to delete and re-create the diskgroup if you want to change to redundancy. We strongly discourage the use of EXTERNAL with Exadata redundancy.

• 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

• Reconfigure existing disk on MD3220i groups

  Hello

  I currently have a MD3220i with two disk RAID 10 groups. I would like to reconfigure them in a large RAID5. These are used by a Hyper-V Cluster Server 2012 running. What would be the proper way to remove the volumes of the beam, removing the existing disk groups, create the new disk group and adding the new volume as a shared Cluster Volume? I know it's more a question of Microsoft but no direction is much appreciated

  Thank you

  Mike.

  Hello Mike,.

  You will need to do is remove your connection host of virtual disks first.  Once this has been done, then you want to delete the virtual disks. Once the virtual disks have been removed, you can remove the disk group.  Once the disk group has been deleted then you can recreate the new disk group and create the virtual disks and then assign them to the cluster.

  Please let us know if you have any other questions.

• 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

• The existing disk stores can be renamed?

  Hi all

  We want to upgrade to spring given gemfire worm 1.2.2/gemfire 6.5.1 to make use of the key/value constraint, but it broke our config xml to store existing drive (store disk moved up level in the most recent version).

  We have existing disk files that share the same name as the region we want to be migrated, but with the new configuration of the disk stores will use a different id and so create differently named disc store files.

  Is it possible to change the name of store existing to the new drive so that existing persistent files can be migrated transparently.

  Thank you

  I'm not sure that SDG 1.2.2 officially support GFE 6.5.
  You can rename the files of record store if you use the same version of GemFire in both cases. If you go from 6.5 to 6.6, there is a way of migration for disc stores. See the documentation for more details.
  If your region (and the record store) called 'data' in SDG, you'll like in the files on disc in the store:

  BACKUP_data.if
  BACKUP_data_1.crf
  BACKUP_data_1.drf
  BACKUP_data_2.crf
  BACKUP_data_2.drf
  

  If you define a named record store item you see as:
  You will get files like (no leader '_') record store:

  BACKUPdata_new.if
  BACKUPdata_new_1.crf
  BACKUPdata_new_1.drf
  

  You should be able to rename the files BACKUP_data * to BACKUPdata_new *.
  Barry

• 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