ASM disk monitor, IO etc

It sounds like most of the third party tools will not support ASM usage, io stat etc., How well grid control be used and what is the best practice?

Any help on setting up the thresold alerts in asm?
1. I can query v$asm_diskgroup and find out how much % being used. How do I check the sql result value and send an email alert in Linux cron?
2. What is the best practice to monitor disk usage in asm/linux?
Thanks!

Similar Messages

How to resize ASM disks

Hi! I have Oracle RAC on Centos with one active node and share storage HP MSA1500 12x500 Gb FC. Also, i have two servers which i want install new rac database.
[oracle@server ~]$ crsctl query css votedisk
0. 0 /u04/sync/oracrs/CSSFile
located 1 votedisk(s).
[oracle@server ~]$ ocrcheck
Status of Oracle Cluster Registry is as follows :
Version : 2
Total space (kbytes) : 262120
Used space (kbytes) : 1672
Available space (kbytes) : 260448
ID : 1521772939
Device/File Name : /u04/sync/oracrs/CRSFile
Device/File integrity check succeeded
Device/File not configured
Cluster registry integrity check succeeded
[oracle@server ~]$
CRS & CSS install on ocfs.
Затем, через oracleasm
[oracle@server ~]$ /etc/init.d/oracleasm listdisks
VOL8
VOL9
[oracle@server ~]$
[root@server ~]# /etc/init.d/oracleasm querydisk /dev/sda1
Disk "/dev/sda1" is not marked an ASM disk
[root@server ~]# /etc/init.d/oracleasm querydisk /dev/sdb1
Disk "/dev/sdb1" is marked an ASM disk with the label ""
[root@server ~]# /etc/init.d/oracleasm querydisk /dev/sdc1
Disk "/dev/sdc1" is marked an ASM disk with the label ""
[root@server ~]# /etc/init.d/oracleasm querydisk /dev/sdd1
Disk "/dev/sdd1" is marked an ASM disk with the label "VOL8"
[root@server ~]# /etc/init.d/oracleasm querydisk /dev/sdd2
Disk "/dev/sdd2" is marked an ASM disk with the label "VOL9"
[root@server ~]# /etc/init.d/oracleasm querydisk /dev/sdd3
Disk "/dev/sdd3" is not marked an ASM disk
[root@server ~]#
[root@server ~]# fdisk -l
Disk /dev/cciss/c0d0: 72.8 GB, 72833679360 bytes
255 heads, 32 sectors/track, 17433 cylinders
Units = cylinders of 8160 * 512 = 4177920 bytes
Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 50 203984 83 Linux
/dev/cciss/c0d0p2 51 1305 5120400 82 Linux swap
/dev/cciss/c0d0p3 1306 17433 65802240 83 Linux
Disk /dev/sda: 1048 MB, 1048657920 bytes
33 heads, 61 sectors/track, 1017 cylinders
Units = cylinders of 2013 * 512 = 1030656 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 1017 1023580 83 Linux
Disk /dev/sdb: 500.0 GB, 500071791104 bytes
255 heads, 63 sectors/track, 60796 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 60796 488343838+ 83 Linux
Disk /dev/sdc: 499.0 GB, 499025092608 bytes
255 heads, 63 sectors/track, 60669 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 1 60669 487323711 83 Linux
Disk /dev/sdd: 500.0 GB, 500073750528 bytes
255 heads, 63 sectors/track, 60797 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdd1 1 1000 8032468+ 83 Linux
/dev/sdd2 1001 2000 8032500 83 Linux
/dev/sdd3 2001 3000 8032500 83 Linux
[root@server ~]#
Than in sqlplusi see, what disks use ASM:
SQL> select name, total_mb, free_mb,path from v$asm_disk;
NAME TOTAL_MB FREE_MB PATH
VOL1 476898 431798 /dev/raw/raw1
VOL2 475902 475379 /dev/raw/raw2
SQL> select name, total_mb, free_mb from v$asm_diskgroup;
NAME TOTAL_MB FREE_MB
DATA 476898 431798
RECOVERY_AREA 475902 475379
SQL> select name, type from V$asm_diskgroup;
NAME TYPE
DATA EXTERN
RECOVERY_AREA EXTERN
Also i see what disks use diskgroups DATA and RECOVERY:
[root@server ~]# cat /etc/sysconfig/rawdevices
# This file and interface are deprecated.
# Applications needing raw device access should open regular
# block devices with O_DIRECT.
# raw device bindings
# format: <rawdev> <major> <minor>
# <rawdev> <blockdev>
# example: /dev/raw/raw1 /dev/sda1
# /dev/raw/raw2 8 5
/dev/raw/raw1 /dev/sdb1
/dev/raw/raw2 /dev/sdc1
/dev/raw/raw8 /dev/sdd1
/dev/raw/raw9 /dev/sdd2
[root@server ~]#
[root@server ~]# mount
/dev/cciss/c0d0p3 on / type ext3 (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/cciss/c0d0p1 on /boot type ext3 (rw)
none on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
configfs on /config type configfs (rw)
ocfs2_dlmfs on /dlm type ocfs2_dlmfs (rw)
/dev/sda1 on /u04/sync type ocfs2 (rw,_netdev,datavolume,nointr,heartbeat=local)
oracleasmfs on /dev/oracleasm type oracleasmfs (rw)
[root@server ~]#
[root@server ~]# ls -l /dev/oracleasm/disks/
total 0
brw-rw---- 1 oracle dba 8, 49 Aug 8 19:34 VOL8
brw-rw---- 1 oracle dba 8, 50 Aug 8 19:34 VOL9
[root@server ~]#
How i could resize asm disk from 450 G for example to 100 Gb for my new rac installation?
Sorry for my english:(

Hi mmusette, hi all,
please, allow a little clarification. ASM allows resizing disks:
From: http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/storeman.htm#sthref1727
Resizing Disks in Disk Groups+
The RESIZE clause of ALTER DISKGROUP enables you to perform the following operations:
Resize all disks in the disk group
Resize specific disks
Resize all of the disks in a specified failure group
If you do not specify a new size in the SIZE clause then ASM uses the size of the disk as returned by the operating system. This could be a means of recovering disk space when you had previously restricted the size of the disk by specifying a size smaller than disk capacity.
The new size is written to the ASM disk header record and if the size of the disk is increasing, then the new space is immediately available for allocation. If the size is decreasing, rebalancing must relocate file extents beyond the new size limit to available space below the limit. If the rebalance operation can successfully relocate all extents, then the new size is made permanent, otherwise the rebalance fails.
However, if you have setup the ASM disk on a physical disk partition, you probably will not be able to resize the partition without destroying the data on the disk. If you, however, used a volume manager to create volumes and you based your ASM disks on those volumes (through RAW devices or directly) AND your volume manager allows resizing the volumes, you should be able to make use of the command mentioned above.
Thanks,
Markus

How can we monitor ASM disk usage on Standby Database.

I am looking for an option to automate deleting the archivelog which is on ASM diskgroup. I could do it if they were not in the ASM disk group with writing a script but with ASM I can't. Is there anything that I can monitor and get notified periodically reg. disk utilization on ASM and then write a script to delete some of the files especially archivelogs if needed.

Hi
what is your Oracle version and your OS?

Asm disk removed taking too much time to boot

hi
a local machine is configured with ASM by oracleasm with a total disk.As it was a training purpose so i have removed the disk eg /dev/sdb bluntly ie. just removing it from box.now i tried fsck -c -c -f /dev/ in rescue mode its didnot worked even not mounting the /mnt/sysimage.It claims for ext2fs error and mounting the fs etc.
Then after lots of days has gone.i fed up with this issues and reinstalled OS.
but my question is what exactly to do?obviously re-installation is not the exact way to do.
regards

If the +/dev/sdb+ was an ASM disk, then it should not impact the o/s when it is removed. ASM instance itself will fail with an error saying something like it was not able to mount the disk group.
If your system failed to boot correctly after this disk was removed, then +/dev/sdb+ contained more than just ASM data.
We dynamically add and remove ASM (multipath'ed) disks via kpartx - while o/s is running. No reboot. No problems.
I fail to see how a ASM disk could cause the type of problems you describe - unless it was more than just a disk used by ASM alone.

Please Help - When I try to add ASM Disk to ASM Diskgroup it crashes Server

We are using a Pillar SAN and have LUNS Created and are using the following multipath device: (I'm a DBA more then anything else... but I am rather familiar with linux .... SAN Hardware not so much)
Device Size Mount Point
/dev/dpda1 11G /u01
The Above device is working fine... Below are the ASM Disks being Created
Device Size Oracle ASM Disk Name
/dev/dpdb1 198G ORCL1
/dev/dpdc1 21G SIRE1
/dev/dpdd1 21G CART1
/dev/dpde1 21G SRTS1
/dev/dpdf1 21G CRTT1
I try to create to the first ASM Disk
/etc/init.d/oracleasm createdisk ORCL1 /dev/dpdb1
Marking disk "ORCL1" as an ASM disk: [FAILED]
So I check the oracleasm log:
#cat /var/log/oracleasm
Device "/dev/dpdb1" is not a partition
I did some research and found that this is a common problem with multipath devices and to work around it you have to use asmtool
# /usr/sbin/asmtool -C -l /dev/oracleasm -n ORCL1 -s /dev/dpdb1 -a force=yes
asmtool: Device "/dev/dpdb1" is not a partition
asmtool: Continuing anyway
now I scan and list the disks
# /etc/init.d/oracleasm scandisks
Scanning the system for Oracle ASMLib disks: [ OK ]
# /etc/init.d/oracleasm listdisks
ORCL1
Here is whats going on in /var/log/messages when I run the oracleasm scandisks command
# date
Fri Aug 14 13:51:58 MST 2009
# /etc/init.d/oracleasm scandisks
Scanning the system for Oracle ASMLib disks: [ OK ]
cat /var/log/messages | grep "Aug 14 13:5"
Aug 14 13:52:06 seer kernel: dpdb: dpdb1
Aug 14 13:52:06 seer kernel: dpdc: dpdc1
Aug 14 13:52:06 seer kernel: dpdd: dpdd1
Aug 14 13:52:06 seer kernel: dpde: dpde1
Aug 14 13:52:06 seer kernel: dpdf: dpdf1
Aug 14 13:52:06 seer kernel: dpdg: dpdg1
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: printk: 30 messages suppressed.
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: sda : READ CAPACITY failed.
Aug 14 13:52:06 seer kernel: sda : status=1, message=00, host=0, driver=08
Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sda: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sda: asking for cache data failed
Aug 14 13:52:06 seer kernel: sda: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sda:end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: Dev sda: unable to read RDB block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sda, logical block 0
Aug 14 13:52:06 seer kernel: unable to read partition table
Aug 14 13:52:06 seer kernel: SCSI device sdb: 21502464 512-byte hdwr sectors (11009 MB)
Aug 14 13:52:06 seer kernel: sdb: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdb: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdb: sdb1
Aug 14 13:52:06 seer kernel: SCSI device sdc: 421476864 512-byte hdwr sectors (215796 MB)
Aug 14 13:52:06 seer kernel: sdc: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdc: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdc: sdc1
Aug 14 13:52:06 seer kernel: SCSI device sdd: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdd: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdd: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdd: sdd1
Aug 14 13:52:06 seer kernel: SCSI device sde: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sde: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sde: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sde: sde1
Aug 14 13:52:06 seer kernel: SCSI device sdf: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdf: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdf: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdf: sdf1
Aug 14 13:52:06 seer kernel: SCSI device sdg: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdg: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdg: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdg: sdg1
Aug 14 13:52:06 seer kernel: SCSI device sdh: 2107390464 512-byte hdwr sectors (1078984 MB)
Aug 14 13:52:06 seer kernel: sdh: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdh: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdh: sdh1
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer kernel: Buffer I/O error on device sdi, logical block 0
Aug 14 13:52:06 seer kernel: sdi : READ CAPACITY failed.
Aug 14 13:52:06 seer kernel: sdi : status=1, message=00, host=0, driver=08
Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sdi: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sdi: asking for cache data failed
Aug 14 13:52:06 seer kernel: sdi: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sdi:end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer last message repeated 4 times
Aug 14 13:52:06 seer kernel: Dev sdi: unable to read RDB block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:06 seer kernel: unable to read partition table
Aug 14 13:52:06 seer kernel: SCSI device sdj: 21502464 512-byte hdwr sectors (11009 MB)
Aug 14 13:52:06 seer kernel: sdj: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdj: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdj: sdj1
Aug 14 13:52:06 seer kernel: SCSI device sdk: 421476864 512-byte hdwr sectors (215796 MB)
Aug 14 13:52:06 seer kernel: sdk: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdk: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdk: sdk1
Aug 14 13:52:06 seer kernel: SCSI device sdl: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdl: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdl: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdl: sdl1
Aug 14 13:52:06 seer kernel: SCSI device sdm: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdm: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdm: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdm: sdm1
Aug 14 13:52:06 seer kernel: SCSI device sdn: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdn: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdn: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdn: sdn1
Aug 14 13:52:06 seer kernel: SCSI device sdo: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdo: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdo: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdo: sdo1
Aug 14 13:52:06 seer kernel: SCSI device sdp: 2107390464 512-byte hdwr sectors (1078984 MB)
Aug 14 13:52:06 seer kernel: sdp: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdp: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdp: sdp1
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer kernel: sdq : READ CAPACITY failed.
Aug 14 13:52:06 seer kernel: sdq : status=1, message=00, host=0, driver=08
Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sdq: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sdq: asking for cache data failed
Aug 14 13:52:06 seer kernel: sdq: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sdq:end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer last message repeated 5 times
Aug 14 13:52:06 seer kernel: Dev sdq: unable to read RDB block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:06 seer kernel: unable to read partition table
Aug 14 13:52:06 seer kernel: SCSI device sdr: 21502464 512-byte hdwr sectors (11009 MB)
Aug 14 13:52:06 seer kernel: sdr: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdr: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdr: sdr1
Aug 14 13:52:06 seer kernel: SCSI device sds: 421476864 512-byte hdwr sectors (215796 MB)
Aug 14 13:52:06 seer kernel: sds: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sds: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sds: sds1
Aug 14 13:52:06 seer kernel: SCSI device sdt: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdt: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdt: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdt: sdt1
Aug 14 13:52:06 seer kernel: SCSI device sdu: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdu: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdu: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdu: sdu1
Aug 14 13:52:06 seer kernel: SCSI device sdv: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdv: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdv: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdv: sdv1
Aug 14 13:52:06 seer kernel: SCSI device sdw: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdw: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdw: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdw: sdw1
Aug 14 13:52:06 seer kernel: SCSI device sdx: 2107390464 512-byte hdwr sectors (1078984 MB)
Aug 14 13:52:06 seer kernel: sdx: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdx: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdx: sdx1
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer kernel: sdy : READ CAPACITY failed.
Aug 14 13:52:06 seer kernel: sdy : status=1, message=00, host=0, driver=08
Aug 14 13:52:06 seer kernel: sd: Current: sense key: Illegal Request
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sdy: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sdy: asking for cache data failed
Aug 14 13:52:06 seer kernel: sdy: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sdy:end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer last message repeated 5 times
Aug 14 13:52:06 seer kernel: Dev sdy: unable to read RDB block 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer kernel: end_request: I/O error, dev sdy, sector 0
Aug 14 13:52:06 seer kernel: unable to read partition table
Aug 14 13:52:06 seer kernel: SCSI device sdz: 21502464 512-byte hdwr sectors (11009 MB)
Aug 14 13:52:06 seer kernel: sdz: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdz: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdz: sdz1
Aug 14 13:52:06 seer kernel: SCSI device sdaa: 421476864 512-byte hdwr sectors (215796 MB)
Aug 14 13:52:06 seer kernel: sdaa: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdaa: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdaa: sdaa1
Aug 14 13:52:06 seer kernel: SCSI device sdab: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdab: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdab: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdab: sdab1
Aug 14 13:52:06 seer kernel: SCSI device sdac: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdac: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdac: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdac: sdac1
Aug 14 13:52:06 seer kernel: SCSI device sdad: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdad: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdad: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdad: sdad1
Aug 14 13:52:06 seer kernel: SCSI device sdae: 43006464 512-byte hdwr sectors (22019 MB)
Aug 14 13:52:06 seer kernel: sdae: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdae: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdae: sdae1
Aug 14 13:52:06 seer kernel: SCSI device sdaf: 2107390464 512-byte hdwr sectors (1078984 MB)
Aug 14 13:52:06 seer kernel: sdaf: Write Protect is off
Aug 14 13:52:06 seer kernel: SCSI device sdaf: drive cache: write through w/ FUA
Aug 14 13:52:06 seer kernel: sdaf: sdaf1
Aug 14 13:52:06 seer kernel: scsi_wr_disk: unknown partition table
Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sda, sector 0
Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sdi, sector 0
Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sdq, sector 0
Aug 14 13:52:07 seer kernel: end_request: I/O error, dev sdy, sector 0
Here's some extra info:
# /sbin/blkid | grep asm
/dev/sdc1: LABEL="ORCL1" TYPE="oracleasm"
/dev/sdk1: LABEL="ORCL1" TYPE="oracleasm"
/dev/sds1: LABEL="ORCL1" TYPE="oracleasm"
/dev/sdaa1: LABEL="ORCL1" TYPE="oracleasm"
/dev/dpdb1: LABEL="ORCL1" TYPE="oracleasm"
I have learned that by excluding devices in the oracleasm configuration file I eliminate those I/O errors in /var/log/messages
# cat /etc/sysconfig/oracleasm
# This is a configuration file for automatic loading of the Oracle
# Automatic Storage Management library kernel driver. It is generated
# By running /etc/init.d/oracleasm configure. Please use that method
# to modify this file
# ORACLEASM_ENABELED: 'true' means to load the driver on boot.
ORACLEASM_ENABLED=true
# ORACLEASM_UID: Default user owning the /dev/oracleasm mount point.
ORACLEASM_UID=oracle
# ORACLEASM_GID: Default group owning the /dev/oracleasm mount point.
ORACLEASM_GID=oinstall
# ORACLEASM_SCANBOOT: 'true' means scan for ASM disks on boot.
ORACLEASM_SCANBOOT=true
# ORACLEASM_SCANORDER: Matching patterns to order disk scanning
ORACLEASM_SCANORDER="dp sd"
# ORACLEASM_SCANEXCLUDE: Matching patterns to exclude disks from scan
ORACLEASM_SCANEXCLUDE="sdc sdk sds sdaa sda"
# ls -la /dev/oracleasm/disks/
total 0
drwxr-xr-x 1 root root 0 Aug 14 10:47 .
drwxr-xr-x 4 root root 0 Aug 13 15:32 ..
brw-rw---- 1 oracle oinstall 251, 33 Aug 14 13:46 ORCL1
Now I can go into dbca to create the ASM instance, which starts up fine... create a new diskgroup, I see ORCL1 as a provision ASM disk I select it ... Click OK
CRASH!!! Box hangs have to reboot it....
I have gotten myself to exactly the same point right before clicking OK and here is what is in the ASM alertlog so far
Fri Aug 14 14:42:02 2009
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as /u01/app/oracle/product/11.1.0/db_1/dbs/arch
Autotune of undo retention is turned on.
IMODE=BR
ILAT =0
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.6.0.
Using parameter settings in server-side spfile /u01/app/oracle/product/11.1.0/db_1/dbs/spfile+ASM.ora
System parameters with non-default values:
large_pool_size = 12M
instance_type = "asm"
diagnostic_dest = "/u01/app/oracle"
Fri Aug 14 14:42:04 2009
PMON started with pid=2, OS id=3300
Fri Aug 14 14:42:04 2009
VKTM started with pid=3, OS id=3302 at elevated priority
VKTM running at (20)ms precision
Fri Aug 14 14:42:04 2009
DIAG started with pid=4, OS id=3306
Fri Aug 14 14:42:04 2009
PSP0 started with pid=5, OS id=3308
Fri Aug 14 14:42:04 2009
DSKM started with pid=6, OS id=3310
Fri Aug 14 14:42:04 2009
DIA0 started with pid=7, OS id=3312
Fri Aug 14 14:42:04 2009
MMAN started with pid=8, OS id=3314
Fri Aug 14 14:42:04 2009
DBW0 started with pid=9, OS id=3316
Fri Aug 14 14:42:04 2009
LGWR started with pid=6, OS id=3318
Fri Aug 14 14:42:04 2009
CKPT started with pid=10, OS id=3320
Fri Aug 14 14:42:04 2009
SMON started with pid=11, OS id=3322
Fri Aug 14 14:42:04 2009
RBAL started with pid=12, OS id=3324
Fri Aug 14 14:42:04 2009
GMON started with pid=13, OS id=3326
ORACLE_BASE from environment = /u01/app/oracle
Fri Aug 14 14:42:04 2009
SQL> ALTER DISKGROUP ALL MOUNT
Fri Aug 14 14:42:41 2009
At this point I don't want to click the OK until I am sure someone is in the office to reboot the machine manually if I do hang it again.... I hung it twice yesterday, however I did not have the devices excluded in the oracleasm configuration file as i do now
Edited by: user10193377 on Aug 14, 2009 3:23 PM
Well Clicking OK hun it again and I am waiting to get back into it, to see what new information might be gleened
Does anyone have any ideas on what to check or where to look????? Will update more once I can log back in

Hi Mark,
It looks like something is not correct with your raw device partition based on the error messages:
Aug 14 13:52:06 seer kernel: Add. Sense: Logical unit not supported
Aug 14 13:52:06 seer kernel:
Aug 14 13:52:06 seer kernel: sda: test WP failed, assume Write Enabled
Aug 14 13:52:06 seer kernel: sda: asking for cache data failed
Aug 14 13:52:06 seer kernel: sda: assuming drive cache: write through
Aug 14 13:52:06 seer kernel: sda:end_request: I/O error, dev sda, sector 0
It could be a number of things. I would check with your vendor and Oracle support to see if the multipath software drive is supported and if there is a potential workaround for ASM. Sorry this is not quite the solution, but its what jumps to mind based on issues with multipath software and storage vendors for ASM with Linux and Oracle. Have you checked the validation matrix available on Metalink?
Cheers,
Ben

ASM Disk preparation for Datafiles and FRA in Oracle 10g RAC Inst

Dear Friends,
Please clarify wheteher the below method is correct to confiure ASM disks for Datafiles and FRA
Partitions provided by IT team for OCR and Voting Disk
/dev/sda1 - 150 GB (For +DATA)
/dev/sda2 - 100 GB (For +FRA)
OS : RHEL 5.6 (64 Bit)
kernel version = 2.6.18-238.el5
Steps:(Node1)
1) Install the RPM's for ASM
rpm -Uvh oracleasm-support-2.1.7-1.el5.x86_64.rpm
rpm -Uvh oracleasm-2.6.18-238.el5-2.0.5-1.el5.x86_64.rpm
rpm -Uvh oracleasmlib-2.0.4-1.el5.x86_64.rpm
2) Configure ASM
/etc/init.d/oracleasm configure
Default user to own the driver interface []: oracle
Default group to own the driver interface []: dba
Start Oracle ASM library driver on boot (y/n) [n]: y
Scan for Oracle ASM disks on boot (y/n) [y]:
Writing Oracle ASM library driver configuration: done
Initializing the Oracle ASMLib driver: [ OK ]
Scanning the system for Oracle ASMLib disks: [ OK ]
3) Cretae ASM Disk
/etc/init.d/oracleasm createdisk DISK1 /dev/sda1
/etc/init.d/oracleasm createdisk DISK2 /dev/sda2
4)/etc/init.d/oracleasm status
5)/etc/init.d/oracleasm scandisks
6)/etc/init.d/oracleasm listdisks
7) Nothing to perform on Node2
8) In dbca choose ASM and map the DISK1 for datafiles and DISK2 for FRA
Please confirm the above steps are right?if not please clarify
If DBCA ->ASM doesn't discover my disk then what should be the Discovery path i have to give?
Please refer any document / Metalink ID for the above complete process
Can i have ASM and oracle DB binary in the same home
Regards,
DB

user564706 wrote:
If DBCA ->ASM doesn't discover my disk then what should be the Discovery path i have to give?for asm disk created with oracleasm discovery path variable is ORCL:*
Please refer any document / Metalink ID for the above complete processhttp://docs.oracle.com/cd/B19306_01/install.102/b14203/storage.htm#BABIFHAB
Can i have ASM and oracle DB binary in the same homeyes. unless you want job role seperation or plan to run multiple versions of oracle homes
>
Regards,
DB

Difference between ASM Disk Group, ADVM Volume and ACFS File system

Q1. What is the difference between an ASM Disk Group and an ADVM Volume ?
To my mind, an ASM Disk Group is effectively a logical volume for Database files ( including FRA files ).
11gR2 seems to have introduced the concepts of ADVM volumes and ACFS File Systems.
An 11gR2 ASM Disk Group can contain :
ASM Disks
ADVM volumes
ACFS file systems
Q2. ADVM volumes appear to be dynamic volumes.
However is this therefore not effectively layering a logical volume ( the ADVM volume ) beneath an ASM Disk Group ( conceptually a logical volume as well ) ?
Worse still if you have left ASM Disk Group Redundancy to the hardware RAID / SAN level ( as Oracle recommend ), you could effectively have 3 layers of logical disk ? ( ASM on top of ADVM on top of RAID/SAN ) ?
Q3. if it is 2 layers of logical disk ( i.e. ASM on top of ADVM ), what makes this better than 2 layers using a 3rd party volume manager ( eg ASM on top of 3rd party LVM ) - something Oracle encourages against ?
Q4. ACFS File systems, seem to be clustered file systems for non database files including ORACLE_HOMEs, application exe's etc ( but NOT GRID_HOME, OS root, OCR's or Voting disks )
Can you create / modify ACFS file systems using ASM.
The oracle toplogy diagram for ASM in the 11gR2 ASM Admin guide, shows ACFS as part of ASM. I am not sure from this if ACFS is part of ASM or ASM sits on top of ACFS ?
Q5. Connected to Q4. there seems to be a number of different ways, ACFS file systems can be created ? Which of the below are valid methods ?
through ASM ?
through native OS file system creation ?
through OEM ?
through acfsutil ?
my head is exploding
Any help and clarification greatly appreciated
Jim

Q1 - ADVM volume is a type of special file created in the ASM DG. Once created, it creates a block device on the OS itself that can be used just like any other block device. http://docs.oracle.com/cd/E16655_01/server.121/e17612/asmfilesystem.htm#OSTMG30000
Q2 - the asm disk group is a disk group, not really a logical volume. It combines attributes of both when used for database purposes, as the database and certain other applications know how to talk "ASM" protocol. However, you won't find any general purpose applications that can do so. In addition, some customers prefer to deal directly with file systems and volume devices, which ADVM is made to do. In your way of thinking, you could have 3 layers of logical disk, but each of them provides different attributes and characteristics. This is not a bad thing though, as each has a slightly different focus - os file system\device, database specific, and storage centric.
Q3 - ADVM is specifically developed to extend the characteristics of ASM for use by general OS applications. It understands the database performance characteristics and is tuned to work well in that situation. Because it is developed in house, it takes advantage of the ASM design model. Additionally, rather than having to contact multiple vendors for support, your support is limited to calling Oracle, a one-stop shop.
Q4 - You can create and modify ACFS file systems using command line tools and ASMCA. Creating and modifying logical volumes happens through SQL(ASM), asmcmd, and ASMCA. EM can also be used for both items. ACFS sits on top of ADVM, which is a file in an ASM disk group. ACFS is aware of the characteristics of ASM\ADVM volumes, and tunes it's IO to make best use of those characteristics.
Q5 - several ways:
1) Connect to ASM with SQL, use 'alter diskgroup add volume' as Mihael points out. This creates an ADVM volume. Then, format the volume using 'mkfs' (*nix) or acfsformat (windows).
2) Use ASMCA - A gui to create a volume and format a file system. Probably the easiest if your head is exploding.
3) Use 'asmcmd' to create a volume, and 'mkfs' to format the ACFS file system.
Here is information on ASMCA, with examples:
http://docs.oracle.com/cd/E16655_01/server.121/e17612/asmca_acfs.htm#OSTMG94348
Information on command line tools, with examples:
Basic Steps to Manage Oracle ACFS Systems

Problem with create asm disk group

Hi all
I am about configuring ASM, so I have downloaded the Grid infrastructure 11g (32 bit), I have configured and created parameters and directories.
I runned the installer but get stack at the 3 step where I have to change the discovery path. I have taped as path /dev where I have created 3 partitions sdb1, sdc1 and sdd1.
Is there any thing should I perform on partitions may be or parameters to set before I go through the installation?
Thanks for help

You can use the below link to install ASMLIB:
http://gssdba.wordpress.com/category/asm/
REFERANCE : Doc ID 580153.1
There are two different methods to configure ASM on Linux:
ASM with ASMLib I/O: This method creates all Oracle database files on raw block devices managed by ASM using ASMLib calls. RAW devices are not required with this method as ASMLib works with block devices.
ASM with Standard Linux I/O: This method creates all Oracle database files on raw character devices managed by ASM using standard Linux I/O system calls. You will be required to create RAW devices for all disk partitions used by ASM.
You can download the ASMLIB rpm’s from below URL:
http://www.oracle.com/technetwork/server-storage/linux/downloads/rhel5-084877.html
STEP 01: LOG IN AS ROOT USER AND INSTALL THE RPMS
[root@node1 ASMLIB]# rpm -Uvh oracleasm-2.6.18-164.el5-2.0.5-1.el5.i686.rpm \
> oracleasmlib-2.0.4-1.el5.i386.rpm \
> oracleasm-support-2.1.8-1.el5.i386.rpm
warning: oracleasm-2.6.18-164.el5-2.0.5-1.el5.i686.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing… ########################################### [100%]
1:oracleasm-support ########################################### [ 33%]
2:oracleasm-2.6.18-164.el########################################### [ 67%]
3:oracleasmlib ########################################### [100%]
STEP 02: CONFIGURE ASMLIB
[root@node1 ASMLIB]# /etc/init.d/oracleasm configure
Configuring the Oracle ASM library driver.
This will configure the on-boot properties of the Oracle ASM library
driver. The following questions will determine whether the driver is
loaded on boot and what permissions it will have. The current values
will be shown in brackets (‘[]‘). Hitting <ENTER> without typing an
answer will keep that current value. Ctrl-C will abort.
Default user to own the driver interface []: oracle
Default group to own the driver interface []: dba
Start Oracle ASM library driver on boot (y/n) [n]: y
Scan for Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration: done
Initializing the Oracle ASMLib driver: [ OK ]
Scanning the system for Oracle ASMLib disks: [ OK ]
STEP 03 :CREATE ASM DISK
[root@node1 ASMLIB]# /etc/init.d/oracleasm listdisks
[root@node1 ASMLIB]#
[root@node1 ~]# /etc/init.d/oracleasm createdisk VOL1 /dev/sdb1
Marking disk “VOL1″ as an ASM disk: [ OK ]
[root@node1 ~]# /etc/init.d/oracleasm createdisk VOL2 /dev/sdc1
Marking disk “VOL2″ as an ASM disk: [ OK ]
[root@node1 ~]# /etc/init.d/oracleasm createdisk VOL3 /dev/sdd1
Marking disk “VOL3″ as an ASM disk: [ OK ]
[root@node1 ~]# /etc/init.d/oracleasm createdisk VOL4 /dev/sde1
Marking disk “VOL4″ as an ASM disk: [ OK ]
[root@node1 ~]# /etc/init.d/oracleasm createdisk VOL5 /dev/sdf1
Marking disk “VOL5″ as an ASM disk: [ OK ]
[root@node1 ~]# /etc/init.d/oracleasm listdisks
VOL1
VOL2
VOL3
VOL4
VOL5
[root@node1 ~]#

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 & Regards

Hi,
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

ASM Disk Sizes in a Disk Group

I have a Diskgroup that contains one ASMDisk that is 500gb. It needs to grow and my question is - Does the next disk added to the group need to be of the same size?
For example -
ASM_Disk1 = 500gb and is in ASM_Diskgrp1
ASM_Disk2 - 250gb >> can it be added to ASM_Diskgrp1
There is concern about balancing, etc. done by ASM
Wondering what experiences anyone has had with this?
Thanks!

Hi,
It's not mandatory, You can use disks with diferent sizes, but is extremally recomended that You put disks with the same size in a disk group.
you'd better use disks with the same storage capacity and performance.
The main reason is that ASM balances the I/O from all disks in a disk group due to this, put disks with the same same storage capacity and performance helps to improve the I/O and storage efficiently within the ASM disk group.
Regards,
Cerreia

Standby database with ASM disks?

Has anyone successfully created a standby database when the primary database and the standby database are using ASM disks? If the answer is yes, how did you copy the files(database backup, control files, etc.) from the asm on primary to asm on standby?
Note: I am using 10gR2 on HP-UX but the copy part should be platform independent so however you did it should help me.

Hi d_carmichael2001,
I had done database migration from Non-asm to ASM for single instance by RMAN.
and i think mostly steps are same for create standby database on ASM.
Have a Look.......
1.create a ASM instance manually on new server.
2.Take a backup of Prod database and controlfile.
**backup of controlfile for Standby should be taken as
BACKUP CURRENT CONTROLFILE FOR STANDBY;
Backup database cmd will be same as Backup database plus archivelog;
3. create standby database by using following cmd and set necessary parameter before execute it
Diskgroup for standby should be define in standby spfile's.
**Standby database should be in nomount stange
**connect as % rman TARGET / AUXILIARY SYS/sys_pwd@sbdb1
Use
DUPLICATE TARGET DATABASE FOR STANDBY ;
This command will copy the datafiles, archived redo log files and standby control file in the backup set to the standby database's storage area.
Thanks
Kuljeet Pal Singh

INS-30508 Invalid ASM disks on 11.2.0.3 OL 6.2 grid standalone install

New set of Dell servers R710s running OL 6.2 redhat compatible kernel
$ uname -a
Linux seoltpo-02 2.6.32-220.el6.x86_64
Connected to EMC VNX5500 and using powerpath 5.6.0. Not a rac environment ... doing 11.2.0.3 base install of grid infrastructure for a standalone server.
Not using ASMLIB.
Disk permissions are correct as grid install begins ...
brw-rw---- 1 grid oinstall 120, 704 Jul 26 21:18 emcpoweras
brw-rw---- 1 grid oinstall 120, 720 Jul 26 21:18 emcpowerat
brw-rw---- 1 grid oinstall 120, 736 Jul 26 21:18 emcpowerau
brw-rw---- 1 grid oinstall 120, 752 Jul 26 21:18 emcpowerav
brw-rw---- 1 grid oinstall 120, 768 Jul 26 21:18 emcpoweraw
brw-rw---- 1 grid oinstall 120, 784 Jul 26 21:18 emcpowerax
brw-rw---- 1 grid oinstall 120, 800 Jul 26 21:18 emcpoweray
brw-rw---- 1 grid oinstall 120, 816 Jul 26 21:18 emcpoweraz
GUI installer sees the powerpath LUNs after changing the Disk Discovery path ... for example ....
INFO: ... discoveryString = /dev/emcpower*
INFO: Executing [tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod, nohdr=true, verbose=true, disks=all, status=true, op=disks, asm_diskstring='/dev/emcpower*']
with environment variables {XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt, LANG=en_US.UTF-8, DISPLAY=191.4.0.79:0, PWD=/u01/software_install/11_2_base/grid, _=/u01/software_install/11_2_base/grid/install/.oui, NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat, USER=grid, QTINC=/usr/lib64/qt-3.3/include, CLASSPATH=, G_BROKEN_FILENAMES=1, HOME=/home/grid, HOSTNAME=waoltpo-02, MODULESHOME=/usr/share/Modules, LESSOPEN=|/usr/bin/lesspipe.sh %s, LD_LIBRARY_PATH=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/../lib, ORACLE_HOME=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin, LOGNAME=grid, SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass, SHELL=/bin/bash, CVS_RSH=ssh, SHLVL=2, HISTCONTROL=ignoredups, KDE_IS_PRELINKED=1, MAIL=/var/spool/mail/grid, QTDIR=/usr/lib64/qt-3.3, JAVA_HOME=, QTLIB=/usr/lib64/qt-3.3/lib, MODULEPATH=/usr/share/Modules/modulefiles:/etc/modulefiles, LS_COLORS=, LC_ALL=, KDEDIRS=/usr, HISTSIZE=1000, module=() { eval `/usr/bin/modulecmd bash $*`
}, LOADEDMODULES=, TERM=vt220, PATH=/usr/bin:/usr/ccs/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/dell/srvadmin/bin:/etc/opt/emcpower/bin:/home/grid/bin:/u01/software_install/11_2_base/grid/install}
INFO: Starting Output Reader Threads for process /tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod
INFO: Parsing 40960 CANDIDATE /dev/emcpoweras grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpowerat grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpowerau grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpowerav grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpoweraw grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpowerax grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpoweray grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpoweraz grid oinstall
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweru
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweru"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
*** Of course there are other LUNs not going to be part of ASM disk groups so it cannot read all of them initially.
Somehow after first looking at the disks and seeing them the first time the permissions are changed back on the disks over to root:root as soon as the GUI sees the disks.
You select the disks that you want in the GUI ( but the permissions have been changed already ) so click Next and wham INS 30508 ...
The Install log shows that kfod is apparently scanning the disks a bunch of time ... but before the error appears install log sees that permissions have changed.
Somehow actions caused from running the GUI are changing the permissions? Something is wrong somewhere ... powerpath ? 11.2.0.3 on this kernel version ? Seems very bizarre ...
NFO: Executing [tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod, nohdr=true, verbose=true, disks=all, status=true, op=disks, asm_diskstring='/dev/emcpoweras','/dev/emcpowerat','/dev/emcpowerau','/dev/emcpowerav','/dev/emcpoweraw','/dev/emcpowerax','/dev/emcpoweray','/dev/emcpoweraz']
with environment variables {XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt, LANG=en_US.UTF-8, DISPLAY=191.4.0.79:0, PWD=/u01/software_install/11_2_base/grid, _=/u01/software_install/11_2_base/grid/install/.oui, NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat, USER=grid, QTINC=/usr/lib64/qt-3.3/include, CLASSPATH=, G_BROKEN_FILENAMES=1, HOME=/home/grid, HOSTNAME=waoltpo-02, MODULESHOME=/usr/share/Modules, LESSOPEN=|/usr/bin/lesspipe.sh %s, LD_LIBRARY_PATH=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/../lib, ORACLE_HOME=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin, LOGNAME=grid, SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass, SHELL=/bin/bash, CVS_RSH=ssh, SHLVL=2, HISTCONTROL=ignoredups, KDE_IS_PRELINKED=1, MAIL=/var/spool/mail/grid, QTDIR=/usr/lib64/qt-3.3, JAVA_HOME=, QTLIB=/usr/lib64/qt-3.3/lib, MODULEPATH=/usr/share/Modules/modulefiles:/etc/modulefiles, LS_COLORS=, LC_ALL=, KDEDIRS=/usr, HISTSIZE=1000, module=() { eval `/usr/bin/modulecmd bash $*`
}, LOADEDMODULES=, TERM=vt220, PATH=/usr/bin:/usr/ccs/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/dell/srvadmin/bin:/etc/opt/emcpower/bin:/home/grid/bin:/u01/software_install/11_2_base/grid/install}
INFO: Starting Output Reader Threads for process /tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweraz
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweraz"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: The process /tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod exited with code 0
INFO: Waiting for output processor threads to exit.
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweray
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweray"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerax
INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerax"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweraw
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweraw"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerav
INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerav"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerau
INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerau"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerat
INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerat"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweras
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweras"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Output processor threads exited.
SEVERE: [FATAL] [INS-30508] Invalid ASM disks.
CAUSE: The disks [dev/emcpoweras, /dev/emcpowerat, /dev/emcpowerau, /dev/emcpowerav, /dev/emcpoweraw, /dev/emcpowerax, /dev/emcpoweray, /dev/emcpoweraz] were not valid.
ACTION: Please choose or enter valid ASM disks.
INFO: Advice is ABORT
INFO: Adding ExitStatus INVALID_USER_INPUT to the exit status set
INFO: Completed validating state <CreateASMDiskGroup>
INFO: Terminating all background operations
INFO: Terminated all background operations
INFO: Transition aborted
INFO: Rolled back to state <CreateASMDiskGroup>
Is there some kind of configuration steps I am missing somewhere?
Yeah I know probably going to have to open an SR here but some of you guys around here are pretty sharp. Can I attach the whole install log here somehow?

Well I am not exactly opposed to udev rules for the powerpath devices ... not that I know what that is exactly ... if this can fix my problem.
I found an example or two from google ...
It looks like on my OL 6.2 system there is a difference in the files ( rules I guess ) under /etc/udev/rules.d
# *** OL 5.7 system below
$ ls -ltr
total 232
-rw-r--r-- 1 root root 1088 Jun 6 2007 60-pcmcia.rules
-rw-r--r-- 1 root root 58016 Jun 6 2007 60-libsane.rules
-rw-r--r-- 1 root root 2319 Jul 14 2008 bluetooth.rules
-rw-r--r-- 1 root root 114 Nov 5 2008 90-alsa.rules
-rw-r--r-- 1 root root 1823 Nov 5 2008 85-pcscd_ccid.rules
-rw-r--r-- 1 root root 316 Dec 8 2010 60-raw.rules
-rw-r--r-- 1 root root 82 Jan 13 2011 90-hal.rules
-rw-r--r-- 1 root root 77 Mar 25 2011 05-udev-pp.rules
-rw-r--r-- 1 root root 292 May 11 2011 98-kexec.rules
-rw-r--r-- 1 root root 143 Jun 7 2011 60-net.rules
-rw-r--r-- 1 root root 331 Jun 9 2011 90-ib.rules
-rw-r--r-- 1 root root 992 Jul 8 2011 40-multipath.rules
-rw-r--r-- 1 root root 9366 Jul 22 2011 60-wacom.rules
-rw-r--r-- 1 root root 107 Jul 22 2011 95-pam-console.rules
-rw-r--r-- 1 root root 61 Jul 22 2011 90-dm.rules
-rw-r--r-- 1 root root 471 Jul 22 2011 51-hotplug.rules
-rw-r--r-- 1 root root 16732 Jul 22 2011 50-udev.rules
-rw-r--r-- 1 root root 515 Jul 22 2011 05-udev-early.rules
-rw-r--r-- 1 root root 175 Jul 22 2011 88-clock.rules
# *** OL 6.2 system below
$ ls -ltr
total 64
# *** OL 6.2 system below
$ ls -ltr
total 64
-rw-r--r--. 1 root root 1914 Apr 27 2010 85-pcscd_ccid.rules
-rw-r--r--. 1 root root 320 Jul 2 2010 90-alsa.rules
-rw-r--r--. 1 root root 1060 Jul 24 2010 60-pcmcia.rules
-rw-r--r--. 1 root root 1652 Nov 20 2010 60-fprint-autosuspend.rules
-rw-r--r--. 1 root root 2486 Dec 23 2010 97-bluetooth-serial.rules
-rw-r--r-- 1 root root 935 Mar 7 2011 95-dataeng-udev.rules
-rw-r--r-- 1 root root 77 Mar 25 2011 05-udev-pp.rules
-rw-r--r--. 1 root root 706 Mar 29 2011 56-hpmud_support.rules
-rw-r--r--. 1 root root 6858 Mar 29 2011 40-hplip.rules
-rw-r--r--. 1 root root 83 May 20 2011 90-hal.rules
-rw-r--r--. 1 root root 316 Oct 13 2011 60-raw.rules
-rw-r--r--. 1 root root 54 Dec 7 2011 99-fuse.rules
-rw-r--r--. 1 root root 292 Dec 7 2011 98-kexec.rules
-rw-r--r--. 1 root root 53 Dec 7 2011 91-drm-modeset.rules
-rw-r--r--. 1 root root 789 Jul 19 07:28 70-persistent-cd.rules
??? So no file 50-udev.rules ... in the 6.2 system ??? But tons of stuff in the 5.7 system ...

Change ASM DISK NAME in 11.2 version

Hi,
Is it possible to change ASM DISK NAME for example in diskgroup DATA01. I added disk without NAME, and system-choosen NAME is allocated. Can I set it to e.g., ORCL:DATA09 . Currently its DATA09_009.
Please suggest your views.
Thanks a lot.
Best Regards

You can change the label of disk using oracleasm renamedisk; oracle discourages it
I will changing the label of disk from CLONE1 to CLONE1a and CLONE2 to CLONE2a of diskgroup CLONE
SQL> col disk_number for 99
SQL> col name for a15
SQL> col label for a15
SQL> col path for a30
SQL> select disk_number,name,label,path from v$asm_disk;
0 DATA CLONE1 ORCL:CLONE1
1 LOGS CLONE2 ORCL:CLONE2
ASMCMD> lsdsk -G CLONE
Path
ORCL:CLONE1
ORCL:CLONE2
ASMCMD> umount CLONE
[root@otest]# /etc/init.d/oracleasm force-renamedisk CLONE1 CLONE1a
Renaming disk "CLONE1" to "CLONE1a": [ OK ]
[root@otest]# /etc/init.d/oracleasm force-renamedisk CLONE2 CLONE2a
Renaming disk "CLONE2" to "CLONE2a": [ OK ]
ASMCMD> mount CLONE
ASMCMD> lsdsk -G CLONE
Path
ORCL:CLONE1A
ORCL:CLONE2A
select disk_number,name,label,path from v$asm_disk;SQL> SQL> SQL> SQL>
0 DATA CLONE1A ORCL:CLONE1A
1 LOGS CLONE2A ORCL:CLONE2A
Edited by: vlethakula on Jan 18, 2013 11:48 AM
Edited by: vlethakula on Jan 18, 2013 11:56 AM

Custom Logical Disk monitor incorrectly flapping between healthy and unhealthy

One of the clients Ops Mgr 2012 SP1 UR8 environments I am supporting has had some custom logical disk monitoring setup; there are 5 groups dynamically populated by logical drives depending on their size (1st group has small drives up to the last group with
very large drives). There is a 'Warning' and 'Critical' Monitor setup per server OS version, the Monitors are not Enabled. There are Overrides applied to each group to enable the Monitor and apply a threshold - different threshold for each group.
During some BAU tuning I could see that some of the above Monitors were appearing as Top-Talking alerts. Further investigation showed that alerts were being triggered by drives that momentarily dropped below the applied threshold. I re-created the Monitors
from 'Simple Threshold' to 'Consecutive Samples' and set the 'Number of Samples' to 6 @ 3 minute intervals.
What I am seeing is that alerts from the above Monitors are still appearing as Top Talkers. When I check the Health Explorer of repeating alerts I can see the disk space is staying the same, below the applied threshold but the health is turning healthy then
back to unhealthy. I have confirmed each noisy Object has the expected threshold as per its dynamic group allocation and have also confirmed the drives are not fluctuating above and below the threshold. One thing I have noticed is that some drives Performance
View is patchy - lots of dotted lines between the coloured lines.
Its almost like the Monitor moves a Logical Disk Object into unhealthy state in the correct (and expected) manner, then it somehow picks up an incorrect threshold which is below the current usage level. This moves it into a healthy state only for the
whole process to repeat. For example: Drive X: on a server is very large, the Group that it sits in has a threshold of 102400MB, its current usage is ~stable at 45500MB. Looking in Health Explorer I can see 3:01pm green state/ 45573 last sampled value/ # of
samples 1 | 3:16pm yellow state/ 45573/ 6 samples | 3:34pm green state/ 45572/ 1 samples | 3:49pm yellow state/ 45571/ 6 samples | 4:01pm green state/ 45425/ 1 sample etc etc.
I'm scratching my head on this one and would appreciate any suggestions or assistance.
Thanks
BT

Thanks for the reply. It is not just one server / drive this is happening on. I am seeing it on everything; once they go into an unhealthy state they periodically go healthy and back again with no change in disk free space. Just to elaborate on how it is
setup; a Monitor has been created for each OS version (2003, 2008 and 2012) and a separate Monitor for Warning and Critical so 6 Monitors in total. Looking at the Warning Monitors; they are created with a threshold of 5120MB for 6 samples and set to disabled.
The following groups have been created and the following thresholds added:
Group 1 (less than 60GB size): override added to enable. This group will then pick up the 5120MB threshold.
Group 2 (60 – 250GB size): override added to enable and override added for 10240MB threshold
Group 3 (250 – 500GB size): override added to enable and override added for 20480MB threshold
Group 4 (500 – 1TB size): override added to enable and override added for 51200MB threshold
Group 5 (>1TB size): override added to enable and override added for 102400MB threshold
One drive I was looking at was in Group 2 (threshold of 10240MB), it was staying at approx. 8500MB but periodically going into healthy state then after 10mins (6 polls @ 2min intervals) back to unhealthy. This process repeats once or twice per day.
I am wondering if the Object is somehow picking up the threshold of the Monitor (5120MB) then going back to its correct overridden threshold. I have setup some test groups and monitors in a lab and will review the results over the coming days.
When the monitors were setup as 'Simple Threshold' this worked fine but were noisy due to drives spiking downwards. It was only when I re-wrote them as 'Consecutive Samples over Threshold' Monitors that this issue has started occurring.
Thanks

Oracleasm cannot find asm disks on boot

Hello!
RAC 11.2.0.2 on SLES10.
I have configured asmlib on a RAC system (multipath configured) and everything worked as a charm before booting node 2 in the cluster. Problem is that after reboot of node 2 i cannot see my asm disks anymore on that node. This only happens on node 2. I dont have this issue after rebooting node 1. However, if i do a manually "scandisks" on node 2 it sees the disks again and the cluster starts successfully..
I cannot see any difference between the two nodes.. the asmlib rpm's matches the kernel version.
oracle@prod2:~> uname -a
Linux prod2 2.6.16.60-0.54.5-smp #1 SMP Fri Sep 4 01:28:03 UTC 2009 x86_64 x86_64 x86_64 GNU/Linux
oracle@prod2:~> rpm -qa |grep oracleasm
oracleasm-support-2.1.4-1.SLE10
oracleasm-2.6.16.60-0.54.5-smp-2.0.5-1.SLE10
oracleasmlib-2.0.4-1.SLE10/etc/sysconfig/oracleasm looks like this:
# This is a configuration file for automatic loading of the Oracle
# Automatic Storage Management library kernel driver. It is generated
# By running /etc/init.d/oracleasm configure. Please use that method
# to modify this file
# ORACLEASM_ENABELED: 'true' means to load the driver on boot.
ORACLEASM_ENABLED=true
# ORACLEASM_UID: Default user owning the /dev/oracleasm mount point.
ORACLEASM_UID=oracle
# ORACLEASM_GID: Default group owning the /dev/oracleasm mount point.
ORACLEASM_GID=dba
# ORACLEASM_SCANBOOT: 'true' means scan for ASM disks on boot.
ORACLEASM_SCANBOOT=true
# ORACLEASM_SCANORDER: Matching patterns to order disk scanning
ORACLEASM_SCANORDER="dm"
# ORACLEASM_SCANEXCLUDE: Matching patterns to exclude disks from scan
ORACLEASM_SCANEXCLUDE="sd"I would be grateful if anyone out there can shed some light on this issue..
Thanks a bunch!

Hi,
I think you need to upgrade your powerpath version. If you are using clariion for your storage.

ASM disk monitor, IO etc

Similar Messages

Maybe you are looking for