Setup udev rules with Red Hat 5/6 on VMware

May 16, 2013 by Leave a Comment

To work on VMware Fusion, set the following on the .vmx file; without this entry, the scsi_id command does not return any values by default.
disk.EnableUUID = “TRUE” 
 
Retrieve and generate a unique SCSI identifier with the scsi_id command:

[root@rhel59dra ~]# /sbin/scsi_id -g -u -s /block/sdc

36000c29b80c12910ca4e6a95a1949d8b
[root@rhel59dra ~]# /sbin/scsi_id -g -u -s /block/sdd
36000c29344da4eab5b78409de3706424
[root@rhel59dra ~]# /sbin/scsi_id -g -u -s /block/sde
36000c291cd542d388fdee223fa90ca69
[root@rhel59dra ~]# /sbin/scsi_id -g -u -s /block/sdf
36000c296666187fd5223c0a34ca52f71
 
Add entries to a custom udev rules file
[root@rhel59dra ~]# cat /etc/udev/rules.d/99-oracle-asmdevices.rules
KERNEL==”sd?1″, BUS==”scsi”, PROGRAM==”/sbin/scsi_id -g -u -s /block/$parent”, RESULT==”36000c29b80c12910ca4e6a95a1949d8b”, NAME=”ASMOCR01″, OWNER=”oracle”, GROUP=”dba”, MODE=”0660″
KERNEL==”sd?1″, BUS==”scsi”, PROGRAM==”/sbin/scsi_id -g -u -s /block/$parent”, RESULT==”36000c29344da4eab5b78409de3706424″, NAME=”ASMOCR02″, OWNER=”oracle”, GROUP=”dba”, MODE=”0660″
KERNEL==”sd?1″, BUS==”scsi”, PROGRAM==”/sbin/scsi_id -g -u -s /block/$parent”, RESULT==”36000c291cd542d388fdee223fa90ca69″, NAME=”ASMOCR03″, OWNER=”oracle”, GROUP=”dba”, MODE=”0660″
KERNEL==”sdf[0-9]“, BUS==”scsi”, PROGRAM==”/usr/bin/udevinfo -q name -p %p”, RESULT==”%k”, PROGRAM==”scsi_id -g -u -d /dev/$parent”, RESULT==”36000c296666187fd5223c0a34ca52f71″, NAME=”ASMDATA0%n”, OWNER=”oracle”, GROUP=”dba”, MODE=”0660″
 
Note:
For disks with multiple partitions, the syntax in the udev rules are different.
KERNEL==”sd[c-z]1″, BUS==”scsi”, PROGRAM=”/sbin/scsi_id -g -u -s /block/%P”, RESULT==”3*”, NAME=”ASM%c”, OWNER=”oracle”, GROUP=”dba”, MODE=”0660″
 
 
To make sure that udev rules work:
[root@rhel59dra ~]# udevtest /block/sdc/sdc1
[root@rhel59dra ~]# udevtest /block/sdd/sdd1
[root@rhel59dra ~]# udevtest /block/sde/sde1
[root@rhel59dra ~]# udevtest /block/sdf/sdf1    
[root@rhel59dra ~]# udevtest /block/sdf/sdf2    
[root@rhel59dra ~]# udevtest /block/sdf/sdf3    
[root@rhel59dra ~]# udevtest /block/sdf/sdf4    
 
Restart udev rules:
RHEL 5: /sbin/udevcontrol reload_rules
RHEL 6: /sbin/udevadm control –reload-rules 
/sbin/start_udev  
 
Verify that proper devices are created

[root@rhel59dra ~]# ls -l /dev/ASM*

brw-rw—- 1 oracle dba 8, 81 May 15 23:45 /dev/ASMDATA01
brw-rw—- 1 oracle dba 8, 82 May 15 23:45 /dev/ASMDATA02
brw-rw—- 1 oracle dba 8, 83 May 15 23:45 /dev/ASMDATA03
brw-rw—- 1 oracle dba 8, 84 May 15 23:45 /dev/ASMDATA04
brw-rw—- 1 oracle dba 8, 33 May 15 23:45 /dev/ASMOCR01
brw-rw—- 1 oracle dba 8, 49 May 15 23:45 /dev/ASMOCR02
brw-rw—- 1 oracle dba 8, 65 May 15 23:45 /dev/ASMOCR03 

Filed under ASM, Exadata, Linux, RAC Tagged with , ,

ASM Recommended Init.ora parameters

May 10, 2013 by Leave a Comment

Prior to 11.2, the following set of init.ora parameters were recommended:

*.db_cache_size=64m  

*.large_pool_size=12M

*.shared_pool_size=128M

*.processes=300

 

Going forward with 11.2 and higher, oracle recommends setting memory_target to approximately 1.5 GB.  Also, you will notice that we are leveraging memory_target versus sga_target which insinuates that we are not using huge pages for ASM memory structures:

alter system set memory_target=1536m scope=spfile;

 

The equation for the process parameters is:

Processes=25 + (10 + max number of concurrent database file creations, and file extend operations possible) * n.

Where n is the number of databases connecting to ASM.

 

Posted by Charles Kim, Oracle ACE Director

Filed under ASM

ASM Pocket Reference Guide

March 12, 2013 by Leave a Comment

Download the latest ASM Pocket Reference Guide prepared by Charles Kim, Oracle ACE Director, and Nitin Vengurlekar

Filed under ASM, General DBA, RAC

Viscosity Has 10 presentations at IOUG Collaborate 2013

February 10, 2013 by Leave a Comment

We will post the 10th session shortly …

Session #

Title

Room Assignment and Time

604

Rolling your own Database Operations Center (DOC) using Oracle Technology you already own

Mile High Ballroom 2A => Mon, Apr 08, 2013 (09:45 AM – 10:45 AM)

344

Performance Tuning your DB Cloud in OEM 12c Cloud Control – 360 Degrees

Mile High Ballroom 4A  => Mon, Apr 08, 2013 (09:45 AM – 10:45 AM)

614

Automate Data Guard Best Practices

Mile High Ballroom 2B => Mon, Apr 08, 2013 (05:00 PM – 06:00 PM)

 

 

 

477

Why Every Database Needs to be Virtualized

Mile High Ballroom 4A => Tue, Apr 09, 2013 (12:00 PM – 12:30 PM)

343

Oracle VM, OEM 12c and Cloud Computing:  Panel of Experts

C#13 vSIG Meeting => Tue, Apr 09, 2013 (4:15 PM – 5:15 PM)

 

 

 

441

ASM New Features – The New ASM Frontier

Mile High Ballroom 2C => Wed, Apr 10, 2013 (08:15 AM – 09:15 AM)

414

Engineered Systems Curriculum: The Perfect Marriage: ZFS Storage Appliance with Exadata

Mile High Ballroom 1C => Wed, Apr 10, 2013 (11:00 AM – 12:00 PM)

783

Virtualized Oracle Stretched RAC Cluster using VMware vSphere and EMC VPLEX

Mile High Ballroom 2A => Wed, Apr 10, 2013 (04:15 PM – 05:15 PM)

 

 

 

757

From Big Data to Exadata: The Best of Both Worlds for Business Analytics

Mile High Ballroom 1B => Thu, Apr 11, 2013 (09:45 AM – 10:45 AM)

 

 

 

Filed under ASM, Data Guard, Exadata, Linux, RAC, ZFSSA

Viscosity North America

December 8, 2012 by Leave a Comment

VNA Core Competencies

Viscosity’s Core Competency centers arounds Oracle Real Application Clusters (RAC).   Because we are the top Oracle RAC Experts, we intimately know storage architecture, network infrastructure, operating systems, and most importantly, Oracle RAC database interactions within the ecosystem.  

Viscosity was formed by former Oracle Employees each of which worked in various capacities within Oracle Corporation. These capacities include Oracle Database, RAC Development, Oracle Consulting and Oracle Technical Architects, Design and Performance Tuning experts.

I am a co-founder and President of Viscosity North America, an Oracle ACE Director, an Oracle Certified DBA, Certified RAC Expert and a VMware Certified Professional. I specialize in Exadata, RAC, and Virtualization (VMware and Oracle VM) and authored three books: Oracle Database 11g New Features for DBA and Developers, Linux Recipes for Oracle DBAs and Oracle Data Guard 11g Handbook. I hold certifications in Oracle, VMware, Red Hat Linux, and Microsoft and has over 20 years of Oracle experience. I’ve sat on the panel of experts at VM World and Oracle OpenWorld for virtualization and Linux. I was one of the founding members of the IOUG virtualization SIG that launched in 2011 at Oracle OpenWorld.

If you look at the core of our competencies, we focus on what we are best at …  RAC.  RAC experts are expected to have in-depth knowledge in networks, clustering, storage, and operating systems.  Several of the managing directors have served as system administrators in past lives and hold specialized certifications in flavors of Unix.  

Because we know RAC, we know infrastructure.  Because we know infrastructure, we’ve adjusted our focus to the world of Database Cloud.  Not only do we adopt Oracle’s consolidation theme with Oracle RAC, we are heavily invested in VMware and Oracle VM.  Several of the managing directors at Viscosity hold certifications on VMware.  

Another area of mastery that we have taken is in the world of Exadata and Oracle engineered systems.  Not only are we the experts in Exadata implementation and performance tuning, we are also experts inother engineered systems such as the ZFS Storage Appliance and Oracle Database Appliance.

Viscosity’s Oracle Center of Expertise has developed best practices and tight partner relationships to implement world-class solutions. Our vast experience and intellectual property give customers insight into what is driving IT complexity. We can deliver a set of practical executable plans for simplifying IT infrastructure, helping reduce operating costs while freeing up resources for new business initiatives.

 

Filed under ASM, Data Guard, Exadata, Linux, RAC, RMAN

ASM IO Statistics (asmiostat.sh)

September 15, 2012 by Leave a Comment

ASM IO Statistics (asmiostat.sh)

Please refer to the following Metalink:

ASMIOSTAT Script to collect iostats for ASM disks [ID 437996.1]

 
This script is applicable for 10.2 and 11.1 ASM instances.
 
  
The following command will gather ASM IO Stats 10 times every two seconds.
 
$ +ASM – oracle: ./asmiostat.sh -s +ASM -h /opt/app/oracle/product/11.1.0/asm 2 10

Filed under ASM

Script to re-create the ASM disk group on Exadata

July 5, 2012 by Leave a Comment

Often, the Exadata arrives at the customer site with High redundancy disk groups when the customer wants to exploit as much of the disk space available on the Normal redundancy.   Here’s a simple script to convert the high redundancy disk group to a normal redundancy disk group:
 
cat gen_dg.sql
define DG=’&1′
set pages 0
set lines 200 trims on feed off  echo off echo off ver off
spool cr_&DG..sql
prompt CREATE DISKGROUP &DG NORMAL REDUNDANCY
 
 
set serveroutput on size unlimited
 
 
declare
v_failgroup v$asm_disk.failgroup%TYPE;
 
 
cursor c1 is
select chr(39)||path||chr(39) path, name
from v$asm_disk
where group_number = (select group_number from v$asm_diskgroup
                      where name=upper(‘&DG’))
and failgroup=v_failgroup
order by path;
 
 
cursor c2 is
select distinct failgroup
from v$asm_disk
order by failgroup;
 
 
cursor c3 is
select allocation_unit_size, compatibility, database_compatibility
from v$asm_diskgroup;
r3 c3%ROWTYPE;
 
 
begin
for r2 in c2 loop
v_failgroup := r2.failgroup;
dbms_output.put_line(‘FAILGROUP ‘||r2.failgroup||’ DISK’);
 
 
for r1 in c1 loop
if c1%rowcount = 1 then
   dbms_output.put_line(r1.path);
else
   dbms_output.put_line(‘,’||r1.path);
end if;
 
 
end loop;
 
 
end loop;
 
 
open c3; fetch c3 into r3;
dbms_output.put_line(‘ATTRIBUTE’);
dbms_output.put_line(chr(39)||’compatible.asm’||chr(39)||’='||chr(39)||r3.compatibility||chr(39)||’,');
dbms_output.put_line(chr(39)||’compatible.rdbms’||chr(39)||’='||chr(39)||r3.database_compatibility||chr(39)||’,');
dbms_output.put_line(chr(39)||’au_size’||chr(39)||’='||chr(39)||r3.allocation_unit_size||chr(39)||’,');
dbms_output.put_line(chr(39)||’cell.smart_scan_capable’||chr(39)||’='||chr(39)||’TRUE’||chr(39)||’;');
close c3;
 
 
end;
/

spool off

Filed under ASM, Exadata, RAC

Attach Home to rebuild the oraInventory

June 28, 2012 by Leave a Comment

cd /apps
mv oraInventory oraInventory.OLD
mkdir oraInventory
 

$ /apps/oracle/product/11.2.0/grid/oui/bin

+ASM – oracle: ./attachHome.sh
Starting Oracle Universal Installer…
 
Checking swap space: must be greater than 500 MB.   Actual 32767 MB    Passed
The inventory pointer is located at /etc/oraInst.loc
The inventory is located at /apps/oraInventory
‘AttachHome’ was successful.
 
 
$ /apps/oracle/product/11.2.0/DB/oui/bin

DBATOOLS – oracle: ./attachHome.sh
Starting Oracle Universal Installer…
 
Checking swap space: must be greater than 500 MB.   Actual 32767 MB    Passed
The inventory pointer is located at /etc/oraInst.loc
The inventory is located at /apps/oraInventory
‘AttachHome’ was successful.
 
 
DBATOOLS – oracle: cd /apps/oraInventory
$ /apps/oraInventory
DBATOOLS – oracle: cd ContentsXML/
 
$ /apps/oraInventory/ContentsXML
DBATOOLS – oracle: cat inventory.xml
<?xml version=”1.0″ standalone=”yes” ?>
<!– Copyright (c) 1999, 2010, Oracle. All rights reserved. –>
<!– Do not modify the contents of this file by hand. –>
<INVENTORY>
<VERSION_INFO>
   <SAVED_WITH>11.2.0.2.0</SAVED_WITH>
   <MINIMUM_VER>2.1.0.6.0</MINIMUM_VER>
</VERSION_INFO>
<HOME_LIST>
<HOME NAME=”Ora11g_gridinfrahome1″ LOC=”/apps/oracle/product/11.2.0/grid” TYPE=”O” IDX=”1″ CRS=”true”/>
<HOME NAME=”OraDb11g_home1″ LOC=”/apps/oracle/product/11.2.0/DB” TYPE=”O” IDX=”2″/>
</HOME_LIST>
</INVENTORY>
 
+ASM – oracle: ./opatch lsinv |grep ^Patch
Patch history file: /apps/oracle/product/11.2.0/grid/cfgtoollogs/opatch/opatch_history.txt
Patch  12431716     : applied on Thu Jun 09 16:49:01 CDT 2011
Patch  11724916     : applied on Thu Jun 09 16:29:52 CDT 2011
Patch  12311357     : applied on Thu Jun 09 16:29:24 CDT 2011
 
+ASM – oracle: db DBATOOLS
The Oracle base remains unchanged with value /apps/oracle
 
$ /apps/oracle/product/11.2.0/grid/OPatch
DBATOOLS – oracle: cd $ORACLE_HOME/OPatch
$ /apps/oracle/product/11.2.0/DB/OPatch
DBATOOLS – oracle: ./opatch lsinv |grep ^Patch
Patch history file: /apps/oracle/product/11.2.0/DB/cfgtoollogs/opatch/opatch_history.txt
Patch  12431716     : applied on Thu Jun 09 16:53:03 CDT 2011
Patch  11724916     : applied on Thu Jun 09 16:38:21 CDT 2011
Patch  12311357     : applied on Thu Jun 09 16:37:54 CDT 2011 

Filed under ASM, General DBA, Oracle VM, RAC

Create ASMLIB disks for EMC disks

May 15, 2012 by Leave a Comment

Create ASMLIB disks with /etc/init.d/oracleasm command. 

You must be logged in as root:

- root: cat /proc/partitions  |grep emcpower

 120    32    1048576 emcpowerc
 120    33    1047383 emcpowerc1
 120    48    1048576 emcpowerd
 120    49    1047383 emcpowerd1
 120    64    1048576 emcpowere
 120    65    1047383 emcpowere1
 120    80    1048576 emcpowerf
 120    81    1047383 emcpowerf1
 120    96    1048576 emcpowerg
 120    97    1047383 emcpowerg1
 120   112  471859200 emcpowerh
 120   113  471849051 emcpowerh1
 120   128  471859200 emcpoweri
 120   129  471849051 emcpoweri1
 120   144  471859200 emcpowerj
 120   145  471849051 emcpowerj1
 120   160  471859200 emcpowerk
 120   161  471849051 emcpowerk1
 120   176  524288000 emcpowerl
 120   177  524277179 emcpowerl1
 120   192  524288000 emcpowerm
 120   193  524277179 emcpowerm1
 120   208  471859200 emcpowern
 120   209  471849051 emcpowern1
 120   224  471859200 emcpowero
 120   225  471849051 emcpowero1
 
 - root: cat cr_asmlib_disks.txt
/etc/init.d/oracleasm createdisk VISC_PV101_DISK1 /dev/emcpowerc1
/etc/init.d/oracleasm createdisk VISC_PV101_DISK2 /dev/emcpowerd1
/etc/init.d/oracleasm createdisk VISC_PV101_DISK3 /dev/emcpowere1
/etc/init.d/oracleasm createdisk VISC_PV101_DISK4 /dev/emcpowerf1
/etc/init.d/oracleasm createdisk VISC_PV101_DISK5 /dev/emcpowerg1
 
 - root: ksh cr_asmlib_disks.txt
Marking disk “VISC_PV101_DISK1″ as an ASM disk: [  OK  ]
Marking disk “VISC_PV101_DISK2″ as an ASM disk: [  OK  ]
Marking disk “VISC_PV101_DISK3″ as an ASM disk: [  OK  ]
Marking disk “VISC_PV101_DISK4″ as an ASM disk: [  OK  ]
Marking disk “VISC_PV101_DISK5″ as an ASM disk: [  OK  ]
 
Next, you need to scan the disks on the remaining RAC nodes:

- root: /etc/init.d/oracleasm scandisks
Scanning the system for Oracle ASMLib disks:

You can verify the the disks on the other RAC nodes with the listdisks option:

- root: /etc/init.d/oracleasm listdisks
TRAX_PV101_DISK1
TRAX_PV101_DISK2
TRAX_PV101_DISK3
TRAX_PV101_DISK4
TRAX_PV101_DISK5

Filed under ASM, Linux, RAC Tagged with , ,

ASM Disk Group Configuration

April 16, 2012 by Leave a Comment

ASM Disk Group Configuration

Everyone should be leveraging ASMLIB instead of using block devices to create our ASM disk groups    

Proper ASM configuration and standardization and following best practices is just as important in a virtualized environment as it is in a bare metal environment            
First, create ASMLIB disks with oracleasm

  • sudo to root
  • cd /etc/init.d 
  • ./oracleasm createdisk DATA101_DISK000 /dev/oracle/DATA101_disk000p1
    • Repeat for each disk
  • On other RAC nodes
    • ./oracleasm scandisks
    • ./oracleasm listdisks


List of available disks on April 29, 2012
cd /dev/oracle
lrwxrwxrwx 1 root root 8 Apr 28 16:22 DATA501_disk009p1 -> ../dm-85

lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA501_disk003p1 -> ../dm-105
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA101_disk003p1 -> ../dm-100
lrwxrwxrwx 1 root root 8 Apr 28 16:22 DATA101_disk001p1 -> ../dm-99
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA101_disk002p1 -> ../dm-102
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA501_disk005p1 -> ../dm-110
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA101_disk004p1 -> ../dm-101
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA101_disk000p1 -> ../dm-104
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA501_disk006p1 -> ../dm-111
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA501_disk008p1 -> ../dm-107
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA501_disk004p1 -> ../dm-112
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA501_disk000p1 -> ../dm-108
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA501_disk002p1 -> ../dm-109
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA501_disk001p1 -> ../dm-103
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA501_disk007p1 -> ../dm-106

Naming Convention Legend for Disk Groups

  • Diskgroup names will be DATA101 or PF101 for RAID 10 disk groups
  • Diskgruop names will DATA501 or PF501 for RAID 5 disk groups
Naming Convention Legend for Disks
  • pd = production data
  • pf = production fast recovery area(fra)
  • dd = would be development data
  • df = would be development fra
  • 101 = raid 10 first disk group
  • 501 = raid 05 first disk group
  • And _diskxxx can be disk000 to disk999


Modify /etc/sysconfig/oracleasm (on each node)

As root:  Make changes to the following lines:
# ORACLEASM_SCANORDER: Matching patterns to order disk scanning

ORACLEASM_SCANORDER=”dm-”

# ORACLEASM_SCANEXCLUDE: Matching patterns to exclude disks from scan
ORACLEASM_SCANEXCLUDE=”sd”
   Important Notes:

  • Only use the partitioned disk when creating ASMLIB disks
  • The partitioned disk will have p1, p2, etc. at the end of the device name
  • After you scan the disk, you should see an entry in /proc/partitions
  • Do NOT use /dev/oracle devices
  • Instead use /dev/mapper devices

RAID 10
——-
[root@dllprdorl01 tmp]# cat ora_asm.txt

/etc/init.d/oracleasm createdisk DATA101_DISK000 /dev/mapper/DATA101_disk000p1
/etc/init.d/oracleasm createdisk DATA101_DISK001 /dev/mapper/DATA101_disk001p1
/etc/init.d/oracleasm createdisk DATA101_DISK002 /dev/mapper/DATA101_disk002p1
/etc/init.d/oracleasm createdisk DATA101_DISK003 /dev/mapper/DATA101_disk003p1
/etc/init.d/oracleasm createdisk DATA101_DISK004 /dev/mapper/DATA101_disk004p1

RAID 5
——
/etc/init.d/oracleasm createdisk DATA501_DISK000 /dev/mapper/DATA501_disk000p1
/etc/init.d/oracleasm createdisk DATA501_DISK001 /dev/mapper/DATA501_disk001p1
/etc/init.d/oracleasm createdisk DATA501_DISK002 /dev/mapper/DATA501_disk002p1
/etc/init.d/oracleasm createdisk DATA501_DISK003 /dev/mapper/DATA501_disk003p1
/etc/init.d/oracleasm createdisk DATA501_DISK004 /dev/mapper/DATA501_disk004p1
/etc/init.d/oracleasm createdisk DATA501_DISK005 /dev/mapper/DATA501_disk005p1
/etc/init.d/oracleasm createdisk DATA501_DISK006 /dev/mapper/DATA501_disk006p1
/etc/init.d/oracleasm createdisk DATA501_DISK007 /dev/mapper/DATA501_disk007p1
/etc/init.d/oracleasm createdisk DATA501_DISK008 /dev/mapper/DATA501_disk008p1
/etc/init.d/oracleasm createdisk DATA501_DISK009 /dev/mapper/DATA501_disk009p1



ASM Disk Group Information

  • First, we will set our Allocation Unit (AU) to 4MB in size
  • Second, we will use ‘ORCL:*’ disks instead of block devices when creating our new disk groups
SQL> alter system set asm_diskstring=’/dev/oracle’,'ORCL:PD*’;

 
System altered.
 
Add the following to the init+ASM1.ora on each node
For automatic mount of diskgroups
asm_diskgroups=’DATA03′,’DATA60′,’FRA03′,’FRA60′,’DATA101′,’DATA501′ 


#asm_diskstring=’/dev/oracle’
asm_diskstring=’/dev/oracle’,'ORCL:PD*’
 
For the time being, manually mount the diskgroups on each node:
SQL> alter system set asm_diskstring=’/dev/oracle’,'ORCL:PD*’;

System altered.

SQL> alter diskgroup DATA101 mount;
Diskgroup altered.

SQL> alter diskgroup DATA501 mount;
Diskgroup altered.
 
 
Creating ASM Disk Groups

RAID 10 DATA Disk Group

+ASM1 > cat cr_DATA101.sql

create diskgroup DATA101 external redundancy disk ‘ORCL:DATA101_DISK000′,
‘ORCL:DATA101_DISK001′,
‘ORCL:DATA101_DISK002′,
‘ORCL:DATA101_DISK003′,
‘ORCL:DATA101_DISK004′
ATTRIBUTE ‘au_size’ = ’4M’,
‘compatible.rdbms’ = ’11.1′,
‘compatible.asm’ = ’11.1′;

RAID 5 DATA Disk Group
+ASM1 > cat cr_DATA501.sql

create diskgroup DATA501 external redundancy disk ‘ORCL:DATA501_DISK000′,
‘ORCL:DATA501_DISK001′,
‘ORCL:DATA501_DISK002′,
‘ORCL:DATA501_DISK003′,
‘ORCL:DATA501_DISK004′,
‘ORCL:DATA501_DISK005′,
‘ORCL:DATA501_DISK006′,
‘ORCL:DATA501_DISK007′,
‘ORCL:DATA501_DISK008′,
‘ORCL:DATA501_DISK009′
ATTRIBUTE ‘au_size’ = ’4M’,
‘compatible.rdbms’ = ’11.1′,
‘compatible.asm’ = ’11.1′;

Filed under ASM, Exadata, General DBA, Linux

← Older posts