WITH REDUNDANCY ASM DISKGROUP

Similar Questions

• Cannot create a with RAC ASM diskgroup

  I have,
  
  I have 2 W2003 SP2 with Oracle 10 g with RAC and ASM 2.
  I certainly have a few errors to create the diskgroup:
  Stamp the disc on node1
  I create the Group on node1
  Stamp the disc on Node2
  I create the Group on Node2
  I have remove the diskgroup, remove the stamp, but now I can not re - create my group I ORA-15018 and ORA-00600 code kfcMount54.
  
  Is this a how to completely clean the disc and diskgroup and how to properly add a diskgroup RAC?
  
  Thanks for your help.

  1) access at metalink.oracle.com

  You must have a support contract with oracle to access to metalink (and you really need one if you want to run cars on a production environment)

  (2) bounce = redΘmarrer

• ASM diskgroup with different disc size

  Hello
  
  DB: 10.2.0.4
  Operating system: AIX 5.3 64-bit L
  
  I have installation on 10g RAC ASM with node 2. It has the only Eve on ASM.
  
  Total DB size is 250 GB.
  Total size of FRA is 700 GB.
  
  My FRA diskgroup to archivelog (also holds multiplex controlfile) each size of 50 GB drive. Even if I set the retention period for 1 day, backup to disk, rman getting failed, due to space issues. So I manually delete obsolete data report and rerun backup.
  
  I want to add the workspace to FRA diskgroup regarding adding disks to FRA diskgroup. But, I have 100 GB drives available , it's not the same waist size of current existing FRA disc (50 GB).
  
  Here's my question
  
  (1) that I can Add the size different to the same diskgroup disc ?. If I add, are there performance problems?
  My all data files are out of FRA diskgroup and there are someother diskgroup.
  
  (2) if FRA diskgroup 50 GB and 100 GB of disks, and then how the archivelog and backup data will be erased?
  Will the data stored up to 50 GB in all disks in FRA, even * 100 GB * disc is?.
  
  (3) while doing recovery with different size of disk at diskgroup, what kind of problems can I face in performance wise?
  
  (4) can I remove any diskgroup 50 GB disks and add the 100 GB drive, so that I can increase the size of the disk in the same diskgroup?. I'll remove it and add at the same time.
  
  (5) add disks redundant external diskgroup , I'm ok with the following query?
  
  ALTER DISKGROUP FRA add DRIVE ' </dev/rhdsk1 >', </dev/rhdsk2 > ', </dev/rhdsk3 > ';
  
  
  Please help me on my doubts above.
  
  Thank you and best regards,
  Therese

  Hi Sunand,

  (1) can I add different diskgroup disc even size?. If I add, are there performance problems?
  My all data files are out of FRA diskgroup and there are someother diskgroup.

  A minimum of four (Oracle ASM disks) LUNS of equal size and performance is recommended for each disk group

  (2) if FRA diskgroup 50 GB and 100 GB of disks, and then how the archivelog and backup data will be erased?
  Data are saved up to 50 GB in all disks of FRA, same 100 GB drive is it?

  Oracle ASM data distribution policy is based on the ability. Ensure that the Oracle ASM disks in a disk group have the same ability to maintain balance.

  (3) while doing recovery with different size of disk at diskgroup, what kind of problems can I face in performance wise?

  Ensure that all Oracle ASM disks in a disk group have similar performance characteristics and the availability of storage. In configurations of storage with dimmers of mixed speed, for example, 10 K and 15 K rpm, i/o performance is limited by the slow speed control.

  (4) can I remove any diskgroup 50 GB disks and add the 100 GB drive, so that I can increase the size of the disk in the same diskgroup?. I'll remove it and add at the same time.

  Yes. First, you add the 100 GB drive and then remove the drives from 50 GB.

  (5) to add disks to external redundancy diskgroup, I'm ok with the following query?
  ALTER DISKGROUP FRA ADD DRIVE ",", ";

  Redundancy is controlled by the diskgroup. Then simply add the disks.

  e.g ALTER DISKGROUP FRA ADD DISK '/dev/rhdsk1', '/dev/rhdsk2', '/dev/rhdsk3';
  

  See doc below... Here are all your anwser.

  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14231/storeman.htm#i1014729

  Kind regards
  Levi Pereira
  http://levipereira.WordPress.com

• 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

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

• 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

• Disaster recovery with different ASM starts

  Hi@all,

  in fact, I'm testing a scenario of recovery after a disaster. To an Oracle Linux 6 Server with installed grid below 12 c and Ora Database 11.2.0.4 (there is also a 12.1.0.2 instance of database) I'm doing a recovery after a disaster. But I'm unleashed by the restoration and recovery of the database. The problem here is that ASM diskgroup name has changed. As you read I also changed the physical server, but I think that should not be a problem.

  To the old server, I have two ASM starts '+ DATA' and '+ FRA_1', to the new, they are called '+ DATA_SRVNAME' and '+ FRA_SRVNAME '. I already changed the startup in spfile parameter, but now after restoring the controlfile RMAN has directions to the old diksgroup:

  RMAN> report schema;
  
  
  using target database control file instead of recovery catalog
  RMAN-06139: WARNING: control file is not current for REPORT SCHEMA
  Report of database schema for database with db_unique_name SID
  
  
  List of Permanent Datafiles
  ===========================
  File Size(MB) Tablespace           RB segs Datafile Name
  ---- -------- -------------------- ------- ------------------------
  1    0        SYSTEM               ***     +DATA/SID/datafile/system.438.816606399
  

  So I tried three ways. First was rename data file name:

  ALTER DATABASE RENAME FILE '+DATA/SID/datafile/system.438.816606399' TO '+DATA_SRVNAME/SID/datafile/system.438.816606399';
  

  Then had to set the newname in RMAN:

  set newname for datafile 16 to '+DATA_SRVNAME/SID/datafile/mms_basic_tab.455.816617697/';
  

  And the second was to recreate the controlfile with

  CREATE CONTROLFILE REUSE DATABASE "SID" RESETLOGS ARCHIVELOG
      MAXLOGFILES 16
      MAXLOGMEMBERS 3
      MAXDATAFILES 254
      MAXINSTANCES 1
      MAXLOGHISTORY 1815
  LOGFILE
    GROUP 1 ('+DATA__SRVNAME', '+FRA_SRVNAME')  SIZE 1024M,
  DATAFILE
    '+DATASRVNAME/SID/datafile/system.438.816606399',
  CHARACTER SET AL32UTF8;
  

  But the three methods gave me the error that the file data to the new location is not available (for example):

  ORA-15012: ASM file '+DATA_QUM169/cogn11/datafile/system.438.816606399' does not exist
  

  So now my question: how am I able to say the controlfile or the database to use the another diskgroup in ASM?

  I know, the simplest way would be to create a diskgroup + DATA and do the restore / recovery, but on the new server, I have no more storage to assign to a new diskgroup, and because there are running other forums I would'nt change ASM starts.

  Do you have anny solution?

  A big thank you and best regards,

  Dave

  Please try this

  RMAN > run

  {

  the value of newname for datafile 1 to "+ DATA_SRVNAME";

  restore data file 1;

  switch datafile 1;

  recover datafile 1;

  }

  Did you create + diskgroup DATA_SRVNAME?

  and

• 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

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

• 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

• 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

• 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