ASM Disks on Solaris 10
All,
I have presented RAID storage LUNs to a 2 node cluster with multipathing enabled via standard solaris MPxIO. Have also created special files using mknod instead of using standard SCSI names. Wondering if this is sufficient to retain device names across server reboots on both nodes?
Thanks
Stalin
using mknod , that is a good way to help , when major + minor of device differ each of node.
and that's enough.
http://dbaforums.org/oracle/lofiversion/index.php?t9102.html
Similar Messages
-
Need to format the old ASM disks on solaris.10.
Hello Gurus,
we uninstalled the ASM on solaris, but while installing the ASM again it says that mount point already used by another instance, but there is no db and ASM running (this is the new server) so we need to use dd command or need to reformat the raw devices which already exists and used by the old ASM instance,here is the confusion...
there are 6 Luns presented to the this host for ASM,its not used by anyone...
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> solaris
/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0
1. c0t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> solaris
/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0
2. c2t60050768018E82BE98000000000007B2d0 <IBM-2145-0000-150.00GB>
/scsi_vhci/ssd@g60050768018e82be98000000000007b2
3. c2t60050768018E82BE98000000000007B3d0 <IBM-2145-0000 cyl 44798 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g60050768018e82be98000000000007b3
4. c2t60050768018E82BE98000000000007B4d0 <IBM-2145-0000 cyl 19198 alt 2 hd 64 sec 256>
/scsi_vhci/ssd@g60050768018e82be98000000000007b4
5. c2t60050768018E82BE98000000000007B5d0 <IBM-2145-0000 cyl 5118 alt 2 hd 32 sec 64>
/scsi_vhci/ssd@g60050768018e82be98000000000007b5
6. c2t60050768018E82BE98000000000007B6d0 <IBM-2145-0000 cyl 5118 alt 2 hd 32 sec 64>
/scsi_vhci/ssd@g60050768018e82be98000000000007b6
7. c2t60050768018E82BE98000000000007B7d0 <IBM-2145-0000 cyl 5118 alt 2 hd 32 sec 64>
/scsi_vhci/ssd@g60050768018e82be98000000000007b7
but the thing is when we try to list the raw devices by ls -ltr on /etc/rdsk location all disk owned by root and other not in oracle:dba & oinstall.
root@b2dslbmom3dbb3301 [dev/rdsk]
# ls -ltr
total 144
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t0d0s0 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0:a,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t0d0s1 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0:b,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t0d0s2 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0:c,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t0d0s3 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0:d,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t0d0s4 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0:e,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t0d0s5 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0:f,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t0d0s6 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0:g,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t0d0s7 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0:h,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t1d0s0 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0:a,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t1d0s1 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0:b,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t1d0s2 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0:c,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t1d0s3 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0:d,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t1d0s4 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0:e,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t1d0s5 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0:f,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t1d0s6 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0:g,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t1d0s7 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0:h,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t3d0s0 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@3,0:a,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t3d0s1 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@3,0:b,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t3d0s2 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@3,0:c,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t3d0s3 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@3,0:d,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t3d0s4 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@3,0:e,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t3d0s5 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@3,0:f,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t3d0s6 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@3,0:g,raw
lrwxrwxrwx 1 root root 64 Jun 10 13:24 c0t3d0s7 -> ../../devices/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@3,0:h,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B7d0s0 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b7:a,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B7d0s1 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b7:b,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B7d0s2 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b7:c,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B7d0s3 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b7:d,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B7d0s4 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b7:e,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B7d0s5 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b7:f,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B7d0s6 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b7:g,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B6d0s0 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b6:a,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B6d0s1 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b6:b,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B6d0s2 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b6:c,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B6d0s3 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b6:d,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B6d0s4 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b6:e,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B6d0s5 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b6:f,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B6d0s6 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b6:g,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B5d0s0 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b5:a,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B5d0s1 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b5:b,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B5d0s2 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b5:c,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B5d0s3 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b5:d,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B5d0s4 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b5:e,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B5d0s5 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b5:f,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B5d0s6 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b5:g,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B4d0s0 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b4:a,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B4d0s1 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b4:b,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B4d0s2 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b4:c,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B4d0s3 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b4:d,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B4d0s4 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b4:e,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B4d0s5 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b4:f,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B4d0s6 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b4:g,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B3d0s0 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b3:a,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B3d0s1 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b3:b,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B3d0s2 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b3:c,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B3d0s3 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b3:d,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B3d0s4 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b3:e,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B3d0s5 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b3:f,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B3d0s6 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b3:g,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B2d0s0 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b2:a,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B2d0s1 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b2:b,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B2d0s2 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b2:c,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B2d0s3 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b2:d,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B2d0s4 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b2:e,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B2d0s5 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b2:f,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:13 c2t60050768018E82BE98000000000007B2d0s6 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b2:g,raw
lrwxrwxrwx 1 root root 68 Jun 13 15:34 c2t60050768018E82BE98000000000007B2d0 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b2:wd,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:47 c2t60050768018E82BE98000000000007B3d0s7 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b3:h,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:48 c2t60050768018E82BE98000000000007B4d0s7 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b4:h,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:49 c2t60050768018E82BE98000000000007B5d0s7 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b5:h,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:51 c2t60050768018E82BE98000000000007B6d0s7 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b6:h,raw
lrwxrwxrwx 1 root root 67 Jun 13 15:53 c2t60050768018E82BE98000000000007B7d0s7 -> ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b7:h,raw
so we need to know where the raw devices located for oracle to do the dd command to remove the old asm header on the raw device inorder to start the fresh installation
but when we use the command which already given by the unix person who is no longer works here now, we are able to see the following information
root@b2dslbmom3dbb3301 [dev/rdsk] # ls -l c2t600*d0s0|awk '{print $11}' |xargs ls -l
crwxr-x--- 1 oracle oinstall 118, 232 Jun 14 13:29 ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b2:a,raw
crwxr-x--- 1 oracle oinstall 118, 224 Jun 14 13:31 ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b3:a,raw
crwxr-x--- 1 oracle oinstall 118, 216 Jun 14 13:32 ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b4:a,raw
crw-r----- 1 root sys 118, 208 Jul 18 13:19 ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b5:a,raw
crw-r----- 1 root sys 118, 200 Jul 18 13:19 ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b6:a,raw
crw-r----- 1 root sys 118, 192 Jul 18 13:19 ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b7:a,raw
also we are having the information of the mkode, with minor and major number we used for making the softlinks for raw device with ASM.
Cd dev/oraasm/
/usr/sbin/mknod asm_disk_03 c 118 232
/usr/sbin/mknod asm_disk_02 c 118 224
/usr/sbin/mknod asm_disk_01 c 118 216
/usr/sbin/mknod asm_ocrvote_03 c 118 208
/usr/sbin/mknod asm_ocrvote_02 c 118 200
/usr/sbin/mknod asm_ocrvote_01 c 118 192
But the final thing is we need find out where the above configuration located on the host, i think this raw device present method is different than the normal method on solaris??
please help me to proceed my installtion .... thanks in advance....
i am really confused with the following command from where we are getting the oracle disk raw devices information,since there is no info there in /etc/rdsk location (Os is solaris 10)
root@b2dslbmom3dbb3301 [dev/rdsk] # ls -l c2t600*d0s0|awk '{print $11}' |xargs ls -l
crwxr-x--- 1 oracle oinstall 118, 232 Jun 14 13:29 ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b2:a,raw
crwxr-x--- 1 oracle oinstall 118, 224 Jun 14 13:31 ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b3:a,raw
crwxr-x--- 1 oracle oinstall 118, 216 Jun 14 13:32 ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b4:a,raw
crw-r----- 1 root sys 118, 208 Jul 18 13:19 ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b5:a,raw
crw-r----- 1 root sys 118, 200 Jul 18 13:19 ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b6:a,raw
crw-r----- 1 root sys 118, 192 Jul 18 13:19 ../../devices/scsi_vhci/ssd@g60050768018e82be98000000000007b7:a,raw
please help....Hi Winner;
For your issue i suggest close your thread here as changing thread status to answered and move it to Forum Home » Grid Computing » Automatic Storage Management which you can get more quick response
Regard
Helios -
Hi experts
amm trying to install and configure Grid Infra install on Solaris 10
SunOS trosuncluster1 5.10 Generic_147440-01 sun4u sparc SUNW,Sun-Fire-V245
when i come to select disk group characteristic, it does not show candidate disks??? where I need to install GI
what am i missing
thanks# cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c0 scsi-bus connected configured unknown
c0::dsk/c0t0d0 CD-ROM connected configured unknown
c1 scsi-sata connected configured unknown
c1::dsk/c1t0d0 disk connected configured unknown
c1::dsk/c1t1d0 disk connected configured unknown
c1::dsk/c1t2d0 disk connected configured unknown
c1::dsk/c1t3d0 disk connected configured unknown
c2 fc-fabric connected configured unknown
c2::500601653ea01a52 disk connected configured unknown
c2::5006016c3ea01a52 disk connected configured unknown
usb0/1 unknown empty unconfigured ok
usb0/2 unknown empty unconfigured ok
usb0/3 unknown empty unconfigured ok
usb1/1.1 unknown empty unconfigured ok
usb1/1.2 unknown empty unconfigured ok
usb1/1.3 unknown empty unconfigured ok
usb1/1.4 unknown empty unconfigured ok
usb1/2 unknown empty unconfigured ok
usb1/3 unknown empty unconfigured ok
usb2/1 unknown empty unconfigured ok
usb2/2 unknown empty unconfigured ok
usb2/3 unknown empty unconfigured ok
usb2/4 unknown empty unconfigured ok
usb2/5 unknown empty unconfigured ok
usb2/6 unknown empty unconfigured ok
usb2/7 unknown empty unconfigured ok
usb2/8 unknown empty unconfigured ok
we have 4 disks
# df -k
Filesystem kbytes used avail capacity Mounted on
rpool/ROOT/s10s_u10wos_17b
70189056 4834399 47404882 10% /
/devices 0 0 0 0% /devices
ctfs 0 0 0 0% /system/contract
proc 0 0 0 0% /proc
mnttab 0 0 0 0% /etc/mnttab
swap 29938944 376 29938568 1% /etc/svc/volatile
objfs 0 0 0 0% /system/object
sharefs 0 0 0 0% /etc/dfs/sharetab
/platform/sun4u-us3/lib/libc_psr/libc_psr_hwcap1.so.1
52239282 4834399 47404882 10% /platform/sun4u-us3/lib/libc_psr.so.1
/platform/sun4u-us3/lib/sparcv9/libc_psr/libc_psr_hwcap1.so.1
52239282 4834399 47404882 10% /platform/sun4u-us3/lib/sparcv9/libc_psr.so.1
fd 0 0 0 0% /dev/fd
swap 29941312 2744 29938568 1% /tmp
swap 29938608 40 29938568 1% /var/run
rpool/export 70189056 32 47404882 1% /export
rpool/export/home 70189056 31 47404882 1% /export/home
orcl01 70189056 31 70188963 1% /orcl01
rpool 70189056 106 47404882 1% /rpool
Edited by: 912919 on 15-May-2012 07:56 -
Soft I/O error in ASM disk volume when using iostat commmand
Dear All,
We are having 2 node 11g rac/sun solaris 10/ASM storage, when we using iostat in node 2 getting soft I/O error keep on increasing.
s/w h/w trn tot device
*82 0 0 82 c4t600A0B80006766CD000003DF4B20A7FCd0*
s/w h/w trn tot device
0 0 0 0 md/d10
0 0 0 0 md/d11
0 0 0 0 md/d12
0 0 0 0 md/d20
0 0 0 0 md/d21
0 0 0 0 md/d22
0 0 0 0 md/d30
0 0 0 0 md/d31
0 0 0 0 md/d32
0 0 0 0 md/d40
0 0 0 0 md/d41
0 0 0 0 md/d42
0 0 0 0 md/d50
4 0 2 6 c0t0d0
0 0 0 0 c1t2d0
0 0 0 0 c1t0d0
0 0 0 0 c1t4d0
0 0 0 0 c1t1d0
2 0 0 2 c3t203200A0B86766CDd31
0 0 0 0 c4t600A0B80006766CD000003E14B20C891d0
40 0 0 40 c4t600A0B80006766CD000003DF4B20A7FCd0
0 0 0 0 c4t600A0B80006766CD000003DD4B20A57Fd0
0 0 0 0 c4t600A0B80006766CD000003C34B0D2D31d0
2 0 0 2 c4t600C0FF0000000000859635DB0097B00d0
2 0 0 2 c4t600C0FF000000000085963724A889B00d0
2 0 0 2 c4t600C0FF0000000000859635AFC5A7F02d0
2 0 0 2 c4t600C0FF0000000000859635AFC5A7F01d0
2 0 0 2 c4t600C0FF0000000000859635AFC5A7F00d0
2 0 0 2 c2t202200A0B86766CDd31
0 0 0 0 c4t600A0B80006766CD000052274FD0B057d0
1 0 0 1 c4t600C0FF0000000000859635DB0097B02d0
2 0 0 2 c4t600C0FF000000000085963565767D300d0
2 0 0 2 c4t600C0FF00000000008596326C5F42901d0
1 0 0 1 c4t600C0FF00000000008596326C5F42900d0
1 0 0 1 c2t203300A0B86766CDd31
0 0 0 0 proddb2.zakathouse.org:vold(pid672)
please advice me how to troubshoot and fix this error
Thanks & RegardsHi,
I suggest to have a look at following script which is provided by oracle to monitor IO.
ASMIOSTAT Script to collect iostats for ASM disks [ID 437996.1]
Further this i have questions
1) Are you logged in asm sysasm? Make sure that you have proper rights
2) Did you check the liveness of asm instance? Make sure its up and functional also check the asm alert.log for awareness.
Hope this helps -
Cannot see EMC PowerPath devices from ASM instance on Solaris 10 x86
Hello,
I'm trying to use EMC PowerPath devices as ASM disks, but cannot see any usable disk
from the ASM instance.
My configuration:
Hardware: Sun X4600M2
Solaris 10 8/07 x86_64
EMC PowerPath 5.0.2_b030
Oracle 10.2.0.1.0
The PP devices are /dev/rdsk/emcpower* which are softlinks to the correpsonding /devices/pseudo/emcp*.
Since I know that these devices must have suitable permissions, I've set ownership and
permission of e.g. /devices/pseudo/emcp@1:a,raw to oracle:dba and 660. The ASM instance's
init.ora file has *.asm_diskstring='/dev/rdsk/emcpower*', so I assume it will scan all
/dev/rdsk/emcpower* softlinks and fetch the ones with sufficient permissions. But nonetheless
a 'select count(*) from v$asm_disk' gives me 0, i.e. nothing.
I've just read some recommendations of using slice 6 of the disk with partition type 'usr', but
this seems to me quite superficial. I would like to use simply slice (=partition) 0 starting from
cylinder 1.
I would be very glad for any solution.
Best regards
UdoProblem solved.
After some tests with plain files instead of devices via undocumented parameter
asmallow_only_raw_disks=false in order to check ASM functionality,
I've finally created new node devices only for oracle (and set_asm_allow... back to true).
original EMC PowerPath pseudo devices (e.g.):
-bash-3.00$ ls -l /devices/pseudo/emcp@13:a,raw
crw------- 1 root sys 215, 832 Dec 10 15:29 /devices/pseudo/emcp@13:a,raw
corresponding new character device with proper ownership and permissions:
-bash-3.00$ ls -l /u01/app/ora-dev/raw/emcp13a
crw-rw---- 1 oracle dba 215, 832 Dec 10 14:56 /u01/app/ora-dev/raw/emcp13a
With *.asm_diskstring='/u01/app/ora-dev/raw/emcp*' in ASM-instance's init.ora,
I was able to see the devices via select * from v$asm_disk and could create the
ASM diskgroups.
Regards
Udo -
Create ASM disks on Solarix X64 fails with ORA-15031
I am trying to create a ASM disk group on SOLARIS x64 using a NETAPP LUN. Below are the disks which are configured
SQL> show parameter asm;
NAME TYPE VALUE
asm_diskgroups string DATA
asm_diskstring string /dev/rdsk/c2t9*
asm_power_limit integer 1
asm_preferred_read_failure_groups string
bash-3.00# ls -ltr /dev/rdsk/c2t9d0s7
lrwxrwxrwx 1 root root 80 May 22 16:27 /dev/rdsk/c2t9d0s7 -> ../../devices/iscsi/[email protected]%3Asn.157399130103EC,99:h,raw
bash-3.00# ls -ltr ../../devices/iscsi/[email protected]%3Asn.157399130103EC,99:h,raw
crw-r----- 1 oracle dba 32, 583 May 22 16:56 ../../devices/iscsi/[email protected]%3Asn.157399130103EC,99:h,raw
I get these errors when I try to create a disk group
SQL> create diskgroup DATA external redundancy disk '/dev/rdsk/c2t9d0s7';
create diskgroup DATA external redundancy disk '/dev/rdsk/c2t9d0s7'
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-15031: disk specification '/dev/rdsk/c2t9d0s7' matches no disks
ORA-15025: could not open disk '/dev/rdsk/c2t9d0s7'
ORA-15056: additional error message
Solaris-AMD64 Error: 13: Permission denied
Additional information: 42
Additional information: 198045856
Additional information: 198045848
Please help.My guess is that you did not run fdisk and partition off the first 1M and ASM overwrote the VTOC rendering the device useless.
fdisk
create new partition
primary partition 1
start 2 end <last cylinder>
Then point your disk string to these partitions (<diskname>p1?)
Once this is done, I ALWAYS test to make sure the oracle AND grid user can read and write to this device from ALL nodes. I use the dd command to do this.
DO NOT DO THIS ON AN ALREADY CONFIGURED AND FUNCTIONING ASM DEVICE. Doing so will erase the device.
make a file in $HOME that contains one line:
cat <<EOF >> $HOME/x.x
this is a test
EOF
node1
dd if=$HOME/x.x of=<disk???p1> bs=20 count=1
node2
dd if=<disk???p1> of=$HOME/y.y bs=20 count=1 ##y.y should be the contents of node1:x.x
node1
dd if=/dev/zero of=<disk???p1> bs=8192 count=1000 ## erase the device for ASM usage.
Fix any read/write issues before proceeding. -
Add LUN into asm in rac (Solaris)
I have a 2 node oracle rac with asm . I have to add new LUN to asm to increase space in asm disk group I have done the following on node1
Ran format
Created the partition on slice4 on the new device file corresponding to the LUN
Created the block and character device file like RAC_ORACLE_data_05 under /dev/dsk/oracle and /dev/rdsk/oracle (where the other device files used by ASM also reside) using the major and minor number of the new LUN
Changed the permissions to oracle:dba
The new LUN is now visible through the ASM on node 1 as RAC_ORACLE_data_05
My question is what steps I need to carry out on node 2 of the cluster
The disk is visible on node 2 as well
The disk is already showing up with the partitions as created through node 1
Do I have to create the device file under /dev/dsk/oracle with the major minor numbers as shown on node 2 for the LUN
TIA
RavinderAlmost never use Solaris (last Oracle db I managed on Solaris was 10 years ago). And as this is not a Solaris o/s forum space, you should not expect quick answers to your Solaris o/s questions (which has little to do with ASM).
A comment though on what needs to be done at o/s level to satisfy RAC/ASM requirements.
ASM does not care for device names. Device names do not need to be persistent before and after reboots. Device names do not need to be persistent across RAC nodes in a cluster.
ASM simply needs to
a) be able to discover the device
b) be able to open the device
This means that the device name needs to match the ASM disk discovery string (or vice versa) across all RAC nodes/ASM instances. And that the device permissions need to allow access read/write access to ASM.
ASM enumerates devices it can I/O using its discovery string. For each device, ASM opens the device. It then reads the ASM disk label of the disk. If there is a valid label, ASM knows the disk name, status, and failgroup and diskgroup this disk belongs to. If no label, ASM treats it as a candidate disk.
So from an o/s perspective - a cluster LUN/disk needs to be visible on all nodes, in order to use that disk for RAC/grid storage. Actual device name is not important.
So whatever you did on node 1 to make that new LUN available to ASM, you need to do on node 2 and others.
I have 2 bash scripts I feel are essential to managing a RAC. The 1st script enables me to execute a command on all RAC nodes. The 2nd script enables me to copy/distribute a local file to all other RAC nodes.
So using these scripts and dealing with Linux as o/s, I would determine whether the new disk/LUN is seen by all RAC nodes, and whether the permissions are correct for ASM usage.
If not, I will use the 2nd script to distribute the config file(s) needed to configure the other RAC nodes with the same changes (on Linux this typically would be /etc/multipath.conf). And then use the 1st script to enable those changes on all RAC nodes (e.g. by restarting multipathd). -
Can't have ASM mark a NFS file as an ASM disk : -is not a block device
Hello,
I’m trying to experiment with ASM for learning purpose. Because I don’t have access to a SAN, I am trying to use NFS files but I can’t manage to have ASM mark those files as ASM disks.
[root@localhost /]# /etc/init.d/oracleasm createdisk ASM_DISK_1 /mnt/asm_dsks/dg1/disk1
Marking disk "ASM_DISK_1" as an ASM disk: [FAILED]
The oracleasm log says: File "/mnt/asm_dsks/dg1/disk1" is not a block device
OK, more context now:
I am trying to install ASM on a RHEL5 virtual machine (on vmware).
[root@localhost /]# uname -rm
2.6.18-8.el5 x86_64
I followed this document:
http://www.oracle.com/technology/pub/articles/smiley-11gr1-install.html until I got stuck at the following command:
/etc/init.d/oracleasm createdisk ...
Now, the NFS filesystem comes from a Solaris 10 system (the only one that's available) running on a physical sun box (this one is not a virtual system).
I have tried many combinations. I tried creating the files on the linux VM, using dd. As root, as oracle. I tried creating them on the Solaris side, using mkfile... no matter what I try, I always get the same issue.
I tried to follow this document: Creating Files on a NAS Device for Use with ASM (http://download.oracle.com/docs/html/B10811_05/app_nas.htm#BCFHCIEC)
But nothing seems to work.
Any idea, recommendations?
Thanks,
Laurent.Hi buddy,
I guess the metalink note 731775.1 should help You.
In fact the procedure is:
- Create the disk devices on your NFS directory (using dd)
- Adjuste the permissions over those files (in this case, oracle:dba)
- Adjust the ASM_DISKSTRING at the ASM instance and setting the NFS directory in the discovery path
- Verify if they are available at v$asm_disk view
- Create the diskgroup using the the NFS disks that You have created.
Hope it helps,
Cerreia -
Hi,
I want to configure ASM on Solaris Oracle sparc-64 bit server with Netapp storage.
I am bit confused, when to create diskgroup using asmca. Because there is no asmlib package available. I cannot start grid installation because during installation it asking for disk (which i want to use from shared storage diskgroup).
YuvrajYou should read the installation REQUIREMENTS for the platform you are using. You do NOT need to follow some other document to "mark" the devices for ASM. It is not necessary. I have NEVER done this, nor have I EVER used asmlib on Linux. IT IS NOT NECESSARY!!!!!!! Read the Oracle docs.
have sys admin configure devices to be visible for all nodes (stand-alone or cluster)
Make sure you use fdisk and use a partition that excludes the first 2 cylinders (0-1). Your partitions should start at cylinder 2. If you do not, ASM will overwrite the Solaris VTOC for the device rendering it unusable until you correctly partition the devices. The device should only have 2 partitions. Partition 1 is cylinder 0-1, and Partition 2 is cylinders 2-<last>. All ASM disks in a given DISKGROUP need to be EXACTLY the same size. You can have multiple diskgroups with different size devices, but that just makes managing your devices more complicated. A word of warning, in 11gR2, if you use a diskgroup with EXTERNAL REDUNDANCY, you will only get 1 voting file. The recommendation for a CRS diskgroup is to be made up of 3 x 2G devices for OCR/VOTING with NORMAL redundancy. This will create 3 voting files.
set correct ownership of grid:oinstall (or whatever:whatevergroup) for only partition 2 of these devices
Next make sure the grid user and the oracle rdbms user can both READ and WRITE to these partitions (rdbms user must be a member of the oinstall/whatever group).
during the install, make sure you change the ASM_DISKSTRING to point to these devices:
eg: /dev/whatever*p2. The installer will then mark the devices properly and create the diskgroup(s)
I don't know why so many people make this so hard. It is NOT that hard!!!!!
[Frame of reference: I have installed > 75 10g-11gR2 clusters.]
Edited by: onedbguru on Dec 9, 2012 1:12 PM -
Hi I am using Oracle 10gR2 on Solaris 10. I have some 12 ASM disks in a Disk Group. I want to remove 3 ASM Disks. Can I do this operation online? Will my data be affected? How should I proceed about it? When I will remove the ASM Disks, can I safely detach those disks physically? please help.
regardsahsen.javaid wrote:
Hi I am using Oracle 10gR2 on Solaris 10. I have some 12 ASM disks in a Disk Group. I want to remove 3 ASM Disks. Can I do this operation online? As already commented, yes. I would like to give you a practical example of how utterly neat ASM is in this regard and why it is IMO a major mistake not to use ASM.
We had to swap storage systems. This means that we have to migrate an entire Oracle database (over 1TB in size) from one set of LUNs to a completely different set of LUNs (on a different storage system).
The new LUNs are added to the existing diskgroup. The old LUNs are dropped (the drop is of course not immediate). A rebalance is issued. The next morning the entire database has been moved and restriped on the new set of LUNs and the old LUNs can now be removed from the system. This while the database was up and running and normal processing continued uninterrupted (this is a 24x7 database).
Then I get comments from some customers (like from a major local financial institution recently) that "+No, we do not want to use ASM as we rather use Veritas+". People like that are missing the point of what ASM is. Totally. -
[FATAL] [INS-30508] Invalid ASM disks.
Dear Gurus
please help for troubleshoot the Invalid asm disk error on solaris
Oracle Grid 11.2.0.3.0
Solaris10 with EMC Powerpath Partition
-bash-3.2$ ./runInstaller -silent -responseFile /aaa/Oracle11g_SunSPARC_64bit/grid/response/grid_install.rsp
Starting Oracle Universal Installer...
Checking Temp space: must be greater than 180 MB. Actual 90571 MB Passed
Checking swap space: must be greater than 150 MB. Actual 90667 MB Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2013-09-15_12-17-47PM. Please wait ...-bash-3.2$ [FATAL] [INS-30508] Invalid ASM disks.
CAUSE: The disks [/dev/rdsk/emcpower2a, /dev/rdsk/emcpower6a, /dev/rdsk/emcpower8a] were not valid.
ACTION: Please choose or enter valid ASM disks.
A log of this session is currently saved as: /tmp/OraInstall2013-09-15_12-17-47PM/installActions2013-09-15_12-17-47PM.log. Oracle recommends that if you want to keep this log, you should move it from the temporary location to a more permanent location.I'm grateful for your response and your time
We had resolve the issue our self
[/dev/rdsk/emcpower2a, /dev/rdsk/emcpower6a, /dev/rdsk/emcpower8a]
above partition by default take the slice 0
we had refer below link
ASM Create Partitions in Solaris and add them as disks in AS
In Sparc architecture, the solaris disk is subdivided into 8 slices.
Below is the common configuration of these eight slices:
slice 0: Holds files and directories that make up the operating
system.*
slice 1: Swap, Provides virtual memory, or swap space.
slice 2: Refers to the entire disk, by convention. The size of this
slice should not be changed.**
slice 3: /export, Holds alternative versions of the operating system.
slice 4: /export/swap. Provides virtual memory space for client
systems. ***
slice 5: /opt. Holds application software added to a system.
slice 6: /usr. Holds operating system commands--also known as
executables-- designed to be run by users.
slice 7: /home. Holds files created by users.
* Cannot be used as ASM disk. Using this slice causes disk corruption
and may render the disk as unusable.
** Should not be used as ASM Disk, as slice refers to the entire disk
(Including partition tables).
*** Is the recommended slice to be used for ASM disk.
as per asm recommendation we had used slice 4 the same
so we had detail diagnose and came to know that we have to use
[/dev/rdsk/emcpower2e, /dev/rdsk/emcpower6e, /dev/rdsk/emcpower8e]
here e refer the slice 4
we had use below changes in silent file and it's working fine
oracle.install.asm.diskGroup.disks=/dev/rdsk/emcpower2e,/dev/rdsk/emcpower6e,/dev/rdsk/emcpower8e
sample logs
INFO: Starting Output Reader Threads for process /tmp/OraInstall2013-09-17_05-03-21PM/ext/bin/kfod
INFO: Parsing 2560 CANDIDATE /dev/rdsk/emcpower2e oracle oinstall
INFO: The process /tmp/OraInstall2013-09-17_05-03-21PM/ext/bin/kfod exited with code 0
INFO: Waiting for output processor threads to exit.
INFO: Parsing 2560 CANDIDATE /dev/rdsk/emcpower6e oracle oinstall
INFO: Parsing 2560 CANDIDATE /dev/rdsk/emcpower8e oracle oinstall -
ORA-15020: discovered duplicate ASM disk
Hello.
I am installing Oracle GI and Rdbms 11.2.0.3+, and when the installer is creating the diskgroup fail with the error ORA-15020: discovered duplicate ASM disk.
INFO: Read: Configuring ASM failed with the following message:
INFO: Read: One or more disk group(s) creation failed as below:
INFO: Read: Disk Group DATA1 creation failed with the following message:
INFO: Read: ORA-15018: diskgroup cannot be created
INFO: Read: ORA-15020: discovered duplicate ASM disk "DATA1_0004"
INFO: Read:
INFO: Read:
INFO: Completed Plugin named: Automatic Storage Management Configuration Assistant
I have permission with all the disk:
crw-rw---- 1 oracle dba 118, 30 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d10s6
crw-rw---- 1 oracle dba 118, 22 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d11s6
crw-rw---- 1 oracle dba 118, 14 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d12s6
crw-rw---- 1 oracle dba 118, 6 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d13s6
crw-rw---- 1 oracle dba 118, 38 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d14s6
crw-rw---- 1 oracle dba 118, 110 Mar 6 10:49 /dev/rdsk/c1t50001FE1500B89E8d1s6
crw-rw---- 1 oracle dba 118, 102 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d2s6
crw-rw---- 1 oracle dba 118, 94 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d3s6
crw-rw---- 1 oracle dba 118, 86 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d4s6
crw-rw---- 1 oracle dba 118, 78 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d5s6
crw-rw---- 1 oracle dba 118, 70 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d6s6
crw-rw---- 1 oracle dba 118, 62 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d7s6
crw-rw---- 1 oracle dba 118, 54 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d8s6
crw-rw---- 1 oracle dba 118, 46 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89E8d9s6
crw-rw---- 1 oracle dba 118, 150 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd10s6
crw-rw---- 1 oracle dba 118, 142 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd11s6
crw-rw---- 1 oracle dba 118, 134 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd12s6
crw-rw---- 1 oracle dba 118, 126 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd13s6
crw-rw---- 1 oracle dba 118, 118 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd14s6
crw-rw---- 1 oracle dba 118, 222 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd1s6
crw-rw---- 1 oracle dba 118, 214 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd2s6
crw-rw---- 1 oracle dba 118, 206 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd3s6
crw-rw---- 1 oracle dba 118, 198 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd4s6
crw-rw---- 1 oracle dba 118, 190 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd5s6
crw-rw---- 1 oracle dba 118, 182 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd6s6
crw-rw---- 1 oracle dba 118, 174 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd7s6
crw-rw---- 1 oracle dba 118, 166 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd8s6
crw-rw---- 1 oracle dba 118, 158 Mar 4 17:17 /dev/rdsk/c1t50001FE1500B89EDd9s6
All the partition start with the cylinder 1.
Do you know the workaround?
I have a open sr severity 2, but they are working too slow.
Regards,
MiltonHello Levi.
I set the variables:
ORACLE_HOME=/oracluster/product/11.2/clusterware
ORACLE_SID=+ASM1
PATH=/usr/bin:/usr/ccs/bin:/usr/ccs/bin:/sbin:/usr/sbin:/oracluster/product/11.2/clusterware/bin:/oracluster/product/11.2/clusterware/OPatch:/oracluster/product/11.2/clusterware/opmn/bin:/opt/xpdf-3.02pl1-solaris:/usr/ucb:
NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
ORACLE_BASE=/orasoft/product
SSH_AUTH_SOCK=/tmp/ssh-PThz1424/agent.1424
EDITOR=vi
LOGNAME=oracle
MAIL=/var/mail//oracle
PS1=sc-prodbd0-1>(oracle):$PWD>
LDR_CNTRL=NOKRTL
USER=oracle
ORACLE_HOSTNAME=sc-prodBD0-1
SHELL=/bin/ksh
ORACLE_TERM=vt220
HOME=/orasoft
LD_LIBRARY_PATH=/oracluster/product/11.2/clusterware/lib:/usr/local/lib:
TERM=vt220 -
Recovery of data after ASM Disk fails
OS : Sun Solaris
DB: 10.2.0.3 RAC (2 Nodes)
Are there any steps to be followed for recovery of data after ASM Disk fails?
We are using a 2 Node RAC with ASM normal redundancy. Say if one disk of a diskgroup fails, then what steps we need to follow to make sure that Database is aware of the new disk ?you said you are using NOrmal Redundancy, which is 2 way mirroring. So with that said, your data should be fine as one only disk has failed and got mirrored. So once you replace to disk, oracle should pick that up and move to data back into it....BUT NOT QUIET SURE, just an opinion.
-
How to find LUN against San disk on solaris 9 using EVA5000 stoarge
Hi,
I have persented may many disk of same size form EVA5000 using sun Emlux card ( single path ). I want to identify "World Wide LUN Name" against eache disk in format.Your help i requied in this case.
In format i have output like this
14. c4t50001FE15003769Dd1 <COMPAQ-HSV110(C)COMPAQ-3020 cyl 51198 alt 2 hd 128 sec 128>
/ssm@0,0/pci@18,700000/SUNW,emlxs@2/fp@0,0/ssd@w50001fe15003769d,1
15. c4t50001FE15003769Dd2 <COMPAQ-HSV110(C)COMPAQ-3020 cyl 51198 alt 2 hd 128 sec 128>
/ssm@0,0/pci@18,700000/SUNW,emlxs@2/fp@0,0/ssd@w50001fe15003769d,2
16. c4t50001FE15003769Dd3 <COMPAQ-HSV110(C)COMPAQ-3020 cyl 63998 alt 2 hd 128 sec 128>
/ssm@0,0/pci@18,700000/SUNW,emlxs@2/fp@0,0/ssd@w50001fe15003769d,3
17. c4t50001FE15003769Dd4 <COMPAQ-HSV110(C)COMPAQ-3020 cyl 63998 alt 2 hd 128 sec 128>
/ssm@0,0/pci@18,700000/SUNW,emlxs@2/fp@0,0/ssd@w50001fe15003769d,4
luxadm -v display /dev/rdsk/c2t50001FE15003769Cd1s0
Displaying information for: /dev/rdsk/c2t50001FE15003769Cd1s0
DEVICE PROPERTIES for disk: /dev/rdsk/c2t50001FE15003769Cd1s0
Vendor: COMPAQ
Product ID: HSV110 (C)COMPAQ
Revision: 3110
Serial Num: Unavailable
Unformatted capacity: 8192.000 MBytes
Read Cache: Enabled
Minimum prefetch: 0x0
Maximum prefetch: 0x0
Device Type: Disk device
Path(s):
/dev/rdsk/c2t50001FE15003769Cd1s2
/devices/pci@8,600000/SUNW,emlxs@1/fp@0,0/ssd@w50001fe15003769c,1:c,raw
LUN path port WWN: 50001fe15003769c
Host controller port WWN: 10000000c95598e6
Path status: O.K.
/dev/rdsk/c2t50001FE150037699d1s2
/devices/pci@8,600000/SUNW,emlxs@1/fp@0,0/ssd@w50001fe150037699,1:c,raw
LUN path port WWN: 50001fe150037699
Host controller port WWN: 10000000c95598e6
Path status: O.K.
bash-2.05# luxadm -e dump_map /devices/pci@8,600000/SUNW,emlxs@1/fp@0,0/ssd@w50001fe15003769c,1:c,raw
Pos Port_ID Hard_Addr Port WWN Node WWN Type
0 20000 0 50001fe150029129 50001fe150029120 0xc (Array controller device)
1 20001 0 50001fe15002912c 50001fe150029120 0xc (Array controller device)
2 40001 0 50001fe15003769c 50001fe150037690 0xc (Array controller device)
3 40002 0 50001fe150037699 50001fe150037690 0xc (Array controller device)
4 4000a 0 10000000c95598e6 20000000c95598e6 0x1f (Unknown Type,Host Bus Adapter)
bash-2.05#
But on EVA5000 i have following identy.
World Wide LUN Name:
6005-08b4-0001-0525-0002-8000-05a5-0000
UUID:
6005-08b4-0001-0525-0002-8000-05a5-0000
Is there any way i can identify LUN name on sun solaris 9 against stoarge disk.
Thanks,
Mazharhi onedbaguru,
thanks for the reply.
my questions are still there.
As per my plans: i shall use 200GB as ASM DG1 with external redudency, 80GB as ASM DG2 with external redudency and ASM 100GB and each 2GB for voting and OCR with external redudency.
1. My Question is: how to do it command by command? what i need is, what do from current state and how to do so that my Disks are ready for OCR,VD and ASM assuming if i have no support for system/storage admin?
2. Do i need to leave first MB for all disks including OCR, VD and ASM Disks as well?
3. If this thread needs to be moved to some other group then please suggest how to do it?
Point#3 is not important at all, i would love to see some expert DBA replying me here.
Waiting for Expert guide.
Regards,
Adnan -
Hi ,
I have created a virtual machine of around 50gb and on that i have added 4 harddisk of around 3gb after that i have mount those disk and created folders accordingly i have installed OLE 5.5 and oracle 10g relaease 2 above things i have done for ASM for asm configuration . now the above are copy and paste from virtual machine
I have added 4 machines mount them created folders on them naming asm1,asm2,asm3,asm4 and created raw devices in them with the help of dd command of 3 gb files each .....after that i relate them losteup devices and raw devices and later on as chage the owner and permissions related to oracle .......... at the time the owner changed to oracle so i created my asm instance with one diskgroup and normal redundancy ......but when i reboot my machine started the following asm instance I got the following error .........
ASM Cache 25165824 bytes
ORA-15032: not all alterations performed
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "DATA"
later on i came to know that it is not able to getthe disk which i created and the cause is the owner has become root so that 's the major cause i was not able to get my diskgroup so i changed the owner and permssions granted to oracle and at that time it has changed but when reboot of machine makes it root user so iam not able to configure it becasue when surfing these are the commands
chown oracle:dba /dev/raw/raw1
# chown oracle:dba /dev/raw/raw2
# chown oracle:dba /dev/raw/raw3
# chown oracle:dba /dev/raw/raw4
# chmod 660 /dev/raw/raw1
# chmod 660 /dev/raw/raw2
# chmod 660 /dev/raw/raw3
# chmod 660 /dev/raw/raw4
but after reboot owner becomes root and coz of this iam not able to access my diskgroup iam pasting output of certain things
fdisk -l
Disk /dev/sda: 53.6 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 4614 36957532+ 83 Linux
/dev/sda3 4615 5889 10241437+ 83 Linux
/dev/sda4 5890 6527 5124735 5 Extended
/dev/sda5 5890 6271 3068383+ 82 Linux swap / Solaris
/dev/sda6 6272 6526 2048256 83 Linux
Disk /dev/sdb: 3221 MB, 3221225472 bytes
255 heads, 63 sectors/track, 391 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 391 3140676 83 Linux
Disk /dev/sdc: 3221 MB, 3221225472 bytes
255 heads, 63 sectors/track, 391 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 1 391 3140676 83 Linux
Disk /dev/sdd: 3221 MB, 3221225472 bytes
255 heads, 63 sectors/track, 391 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdd1 1 391 3140676 83 Linux
Disk /dev/sde: 3221 MB, 3221225472 bytes
255 heads, 63 sectors/track, 391 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sde1 1 391 3140676 83 Linux
[root@oracle10 ~]#
df -h
[root@oracle10 ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 9.5G 8.5G 546M 95% /
/dev/sda6 1.9G 46M 1.8G 3% /tmp
/dev/sda2 35G 2.6G 30G 8% /u01
/dev/sda1 99M 30M 65M 32% /boot
tmpfs 252M 0 252M 0% /dev/shm
/dev/sdb1 3.0G 2.6G 235M 92% /asm1
/dev/sdc1 3.0G 2.6G 235M 92% /asm2
/dev/sdd1 3.0G 2.6G 235M 92% /asm3
/dev/sde1 3.0G 2.6G 235M 92% /asm4
/dev/hdc 639M 639M 0 100% /media/My Disc
the content of /etc/rc.local
#!/bin/sh
# This script will be executed after all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.
touch /var/lock/subsys/local
/sbin/losetup /dev/loop1 /asm1/disk1
/sbin/losetup /dev/loop2 /asm2/disk2
/sbin/losetup /dev/loop3 /asm3/disk3
/sbin/losetup /dev/loop4 /asm4/disk4
raw /dev/raw/raw1 /dev/loop1
raw /dev/raw/raw2 /dev/loop2
raw /dev/raw/raw3 /dev/loop3
raw /dev/raw/raw4 /dev/loop4
the content of /etc/fstab
LABEL=/ / ext3 defaults 1 1
LABEL=/tmp /tmp ext3 defaults 1 2
LABEL=/u01 /u01 ext3 defaults 1 2
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
LABEL=SWAP-sda5 swap swap defaults 0 0
/dev/sdb1 /asm1 ext3 defaults 0 2
/dev/sdc1 /asm2 ext3 defaults 0 2
/dev/sdd1 /asm3 ext3 defaults 0 2
/dev/sde1 /asm4 ext3 defaults 0 2
Iam struggling with these for 3 days pls help was trying to paste the contents of alert file but that exceed the max length
Thanks in Advance
Regards
KavitaUsing raw and block devices in 11g is not supported
http://download.oracle.com/docs/cd/E11882_01/install.112/e17212/whatsnew.htm#BGGEJJHE
So if this Prod /dev/test of business database dont use it
you can install the asmlib and use oracleasm utility to create asm disks
oracleasm createdisk DISK1 /dev/sdb1
then create diskgroup to use DISK1
Edited by: KG on Apr 15, 2011 4:41 AM
Maybe you are looking for
-
ACR 4.1 Color space(s)
Windows XP Bridge CS3 ACR 3.7 and previous used to give the option to convert to various colour spaces (profiles I always get confused here). I've noticed that my Canon raw files show up in bridge as "colour mode RGB" If I edit in ACR4.1 and save; th
-
Using dbms_xmlsave.insertXML
Hi all, I am reading an XML data which has similar structure to: <dept> <name> department name </name> <loc> department location </loc> <emp> <fisrt> first name for first employee </first> <last> last name for first employee </last> </emp> <emp> <fir
-
SDK 1.4 compilation problems
I get the following error when I try to compile a java program in the 1.4 envt. There are no errors in 1.3 envt. home/skreddy/jsdk14/jre/lib/sparc/client/libjvm.so, because ld.so.1: xjavac: fatal: relocation error: file /home/skreddy/jsdk14/jre/lib/s
-
Calling BIP from Forms: Having Java version problem
<h5> Hi, I tried to call a BIP report through Oracle Forms. I followed this PDF. http://www.oracle.com/technology/products/xml-publisher/docs/Forms_BIP_v22.pdf Problem is, when I run the form, I get this error (copied from the Java Console) </h5> <h6
-
Identifying auto-increment columns
Hi, I am developing a database management package for mysql. I want to be able to provide a sql dump facility, which will produce the sql code for creating a table and populating it. I do not seem to be able to find a function for identifying if a fi