ASM Disk Mount Error

Hi,
I am consistently getting the following error since yesterday while mounting the ASM disk.
1. I created the ASM disks successfully and created the appropriate ASM DiskGroups using asmca utility.
2. I was able to see the diskgroups as mounted from asmcmd tool.
3. All of a sudden, all the diskgroups were dismounted yesterday and I see the following error in the alert logs for all the
diskgroups.
4. This is using ASM11g
As I exhausted all my avenues to fix, I have turned to you for further assistance. Please do the needful.
SQL> /* ASMCMD */ALTER DISKGROUP DataVSPSI MOUNT
NOTE: cache registered group DATAVSPSI number=3 incarn=0x7934bf5d
NOTE: cache began mount (first) of group DATAVSPSI number=3 incarn=0x7934bf5d
NOTE: Assigning number (3,0) to disk (ORCL:D01_VSP_SI)
Thu Dec 27 17:38:29 2012
NOTE: start heartbeating (grp 3)
kfdp_query(DATAVSPSI): 11
kfdp_queryBg(): 11
NOTE: cache opening disk 0 of grp 3: D01_VSP_SI label:D01_VSP_SI
NOTE: F1X0 found on disk 0 au 2 fcn 0.0
NOTE: cache mounting (first) external redundancy group 3/0x7934BF5D (DATAVSPSI)
NOTE: starting recovery of thread=1 ckpt=2.1 group=3 (DATAVSPSI)
WARNING: IO Failed. group:3 disk(number.incarnation):0.0xeae44fae disk_path:ORCL:D01_VSP_SI
AU:4 disk_offset(bytes):4333568 io_size:122880 operation:Read type:asynchronous
result:I/O error process_id:32162
WARNING: IO Failed. group:3 disk(number.incarnation):0.0xeae44fae disk_path:ORCL:D01_VSP_SI
AU:4 disk_offset(bytes):4202496 io_size:131072 operation:Read type:asynchronous
result:I/O error process_id:32162
ORA-15080: synchronous I/O operation to a disk failed
ERROR: ASM recovery failed to read ACD
NOTE: cache initiating offline of disk 0 group DATAVSPSI
NOTE: process 32162 initiating offline of disk 0.3940831150 (D01_VSP_SI) with mask 0x7e in group 3
WARNING: Disk D01_VSP_SI in mode 0x7f is now being taken offline
NOTE: initiating PST update: grp = 3, dsk = 0/0xeae44fae, mode = 0x15
kfdp_updateDsk(): 12
kfdp_updateDskBg(): 12
ERROR: too many offline disks in PST (grp 3)
WARNING: Disk D01_VSP_SI in mode 0x7f offline aborted
Thu Dec 27 17:38:29 2012
NOTE: halting all I/Os to diskgroup DATAVSPSI
NOTE: crash recovery signalled OER-15130
ERROR: ORA-15130 signalled during mount of diskgroup DATAVSPSI
NOTE: cache dismounting (clean) group 3/0x7934BF5D (DATAVSPSI)
NOTE: lgwr not being msg'd to dismount
NOTE: cache dismounted group 3/0x7934BF5D (DATAVSPSI)
Also, I think the lower level disk is fine as I am able to write to the disk as follows :
[oracle@rmanqa01 trace]$ dd of=/dev/sdp1
Test Test
0+1 records in
0+1 records out
10 bytes (10 B) copied, 4.97435 seconds, 0.0 kB/s
[oracle@rmanqa01 trace]$ id
uid=500(oracle) gid=500(oinstall) groups=6(disk),500(oinstall),501(dba),502(oper),503(asmadmin),504(asmdba),505(asmoper),506(horcm)
[oracle@rmanqa01 trace]$ ls -l /dev/sdp1
brw-rw---- 1 root disk 8, 241 Dec 28 11:59 /dev/sdp1
[oracle@rmanqa01 trace]$
The oracleasm also lists the disk D01_VSP_SI as follows :
[root@rmanqa01 log]# /etc/init.d/oracleasm listdisks
A01_VSP_SI
ADSK01
ARCH_AMS_SI
D01_VSP_SI
DATA_AMS_SI
DDSK01
DEMO_ARCH
DEMO_DATA
L01_VSP_SI
RDSK01
REDO_AMS_SI
You have new mail in /var/spool/mail/root
[root@rmanqa01 log]# /etc/init.d/oracleasm querydisk D01_VSP_SI
Disk "D01_VSP_SI" is a valid ASM disk
[root@rmanqa01 log]#
kfed tool was giving proper data till yesterday.
Today, I am getting the following :
./kfed read /dev/oracleasm/disks/D01_VSP_SI
kfbh.endian: 84 ; 0x000: 0x54
kfbh.hard: 101 ; 0x001: 0x65
kfbh.type: 115 ; 0x002: *** Unknown Enum ***
kfbh.datfmt: 116 ; 0x003: 0x74
kfbh.block.blk: 1936020512 ; 0x004: T=0 NUMB=0x73655420
kfbh.block.obj: 2147486324 ; 0x008: TYPE=0x8 NUMB=0xa74
kfbh.check: 2886846267 ; 0x00c: 0xac11c73b
kfbh.fcn.base: 0 ; 0x010: 0x00000000
kfbh.fcn.wrap: 0 ; 0x014: 0x00000000
kfbh.spare1: 0 ; 0x018: 0x00000000
kfbh.spare2: 0 ; 0x01c: 0x00000000
ERROR!!!, failed to get the oracore error message
[oracle@rmanqa01 bin]$
Please help.
Thanks
V V
Edited by: user13479556 on Dec 28, 2012 12:00 PM

Thanks Berx for pointing that out.
I deleted the ASM disks and the diskgroups and re-created a fresh and was able to start the ASM instance and mount the DGs.
Now the mount is persistent, but the dbca fails with the following error in the alert log. Under what situations can this error be seen ?
NOTE: Loaded library: System
SUCCESS: diskgroup DATAAMSSI was mounted
SUCCESS: diskgroup ARCHAMSSI was mounted
ERROR: failed to establish dependency between database R3AMSSI and diskgroup resource ora.DATAAMSSI.dg*ERROR: failed to establish dependency between database R3AMSSI and diskgroup resource ora.ARCHAMSSI.dg*Mon Dec 31 20:25:25 2012
SUCCESS: diskgroup LOGAMSSI was mounted
Mon Dec 31 20:25:25 2012
ERROR: failed to establish dependency between database R3AMSSI and diskgroup resource ora.LOGAMSSI.dg
Mon Dec 31 20:25:25 2012
Successful mount of redo thread 1, with mount id 784925673
Completed: Create controlfile reuse set database "R3AMSSI"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
Datafile
'+DATAAMSSI/R3AMSSI/system01.dbf',
'+DATAAMSSI/R3AMSSI/sysaux01.dbf',
'+DATAAMSSI/R3AMSSI/undotbs01.dbf',
'+DATAAMSSI/R3AMSSI/users01.dbf'
LOGFILE GROUP 1 ('+LOGAMSSI/R3AMSSI/redo01.log') SIZE 51200K,
GROUP 2 ('+LOGAMSSI/R3AMSSI/redo02.log') SIZE 51200K,
GROUP 3 ('+LOGAMSSI/R3AMSSI/redo03.log') SIZE 51200K RESETLOGS
Stopping background process MMNL
Stopping background process MMON
Starting background process MMON
Starting background process MMNL
Mon Dec 31 20:25:28 2012
MMON started with pid=17, OS id=10452
ALTER SYSTEM enable restricted session;
Mon Dec 31 20:25:28 2012
MMNL started with pid=18, OS id=10454
alter database "R3AMSSI" open resetlogs
RESETLOGS after incomplete recovery UNTIL CHANGE 945183
Errors in file /u01/app/oracle/diag/rdbms/r3amssi/R3AMSSI/trace/R3AMSSI_ora_10434.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '+LOGAMSSI/r3amssi/redo01.log'
ORA-17503: ksfdopn:2 Failed to open file +LOGAMSSI/r3amssi/redo01.log
ORA-15173: entry 'redo01.log' does not exist in directory 'r3amssi'
Errors in file /u01/app/oracle/diag/rdbms/r3amssi/R3AMSSI/trace/R3AMSSI_ora_10434.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '+LOGAMSSI/r3amssi/redo01.log'
ORA-17503: ksfdopn:2 Failed to open file +LOGAMSSI/r3amssi/redo01.log
ORA-15173: entry 'redo01.log' does not exist in directory 'r3amssi'
Mon Dec 31 20:25:29 2012
Checker run found 5 new persistent data failures
Mon Dec 31 20:27:07 2012
I can verify from asmcmd that the redologs mentioned above as missing is very much present in '+LOGAMSSI/R3AMSSI'
Thanks
V V

Similar Messages

  • Disk Mounting error

    Trying to download a program and get the "disk mounting failed" message.
    Using an EMac with OS 10.3.9, downloading a .dmg file about 5.6MB using Safari 1.3.1(v312.3.3). I've gotten all the updates and Java fixes I can think of. I am able to download other files w/o problem. The file I'm trying to download is Limewire. I've been on their discussion board but no results.
    Any sugesstions?
    Oh, the Safari downloads about 180kb of the file and then gives me the error and I'm using a cable modem connection.
    EMac   Mac OS X (10.3.9)  

    I just had the very same problem (with a CD instead of DVD, but same error) and found your unanswered post. I checked out another site, and it suggested that the I/O problem has something to do with data corruption....
    And then I remembered that when watching DVD's - if they are dirty, they won't play...
    And I ejected the CD, and found some gummy jam like substance on the data side.
    Cleaned it off, and now it works fine....hope this helps you or others!

  • ASM disk mount and dismount !

    Hello ,
    I found this listing continues in my alert.log.I found when oracle archives it mounts the disk and the unmounts it.Is it Usual?
    Thread 1 cannot allocate new log, sequence 161
    Checkpoint not complete
    Current log# 1 seq# 160 mem# 0: +ORCL_ONLINE_OPS1/dwh/redo01.log
    Thread 1 advanced to log sequence 161
    Current log# 2 seq# 161 mem# 0: +ORCL_ONLINE_OPS1/dwh/redo02.log
    Wed Jan 9 17:22:13 2008
    SUCCESS: diskgroup ORCL_ARCH was mounted
    SUCCESS: diskgroup ORCL_ARCH was dismounted
    SUCCESS: diskgroup ORCL_ARCH was mounted
    SUCCESS: diskgroup ORCL_ARCH was dismounted
    SUCCESS: diskgroup ORCL_ARCH was mounted
    SUCCESS: diskgroup ORCL_ARCH was dismounted
    Wed Jan 9 17:27:50 2008
    Shutting down archive processes
    Wed Jan 9 17:27:55 2008
    Thansk,
    Pam

    please check metalink note
    Note.361173.1 Asm Diskgroup success Mount And Umount messages in alert.log during Rman Backup
    Thanks,
    Anil

  • ASM disk mount in alter log

    Hello
    I am running Oracle 10g with ASM and I am seeing 1 of my 3 disk groups being mounted and unmounted in the alter log of on database instance.
    SUCCESS: diskgroup FLASH was mounted
    SUCCESS: diskgroup FLASH was dismounted
    On this disk group I have only my archive logs. Is this normal ?

    Danny,
    Are you on RAC? Check this mealink note 361173.1 which talks about the same thing.
    Update:
    Ignore the messages. They are just informal ones and will be removed from future(!)versions. Basically ASM close (or dismount) those groups when it closes the file descriptors on that DG and mounts when it opens first file on that DG.
    Look at this thread over Orafaq where Gopal mentioned for this message this note,
    http://www.orafaq.com/maillist/oracle-l/2007/02/18/1244.htm
    Aman....
    Edited by: Aman.... on Sep 19, 2008 8:52 AM

  • Error while creating asm disk group

    i am trying to convert my database SRAVAN as an ASM instance.
    so do i need to set ORACLE_SID=+ASM???? r else it wil be SRAVAN??
    I WAS ENDED UP WITH FOLLOWING ERRORS WHILE CREATING DISK GROUP.
    guyz please do help me
    SQL> CREATE DISKGROUP dgroup1
    2 NORMAL REDUNDANCY
    3 FAILGROUP ctlr1
    4 DISK '/u04/app/oracle/product/asmdisks/disk1'
    5 FAILGROUP ctlr2
    6 DISK '/u04/app/oracle/product/asmdisks/disk2';
    CREATE DISKGROUP dgroup1
    ERROR at line 1:
    ORA-15018: diskgroup cannot be created
    ORA-15031: disk specification '/u04/app/oracle/product/asmdisks/disk2' matches
    no disks
    ORA-15025: could not open disk '/u04/app/oracle/product/asmdisks/disk2'
    ORA-15059: invalid device type for ASM disk
    Linux Error: 32768: Unknown system error
    Additional information: 42
    Additional information: -1073785968
    ORA-15031: disk specification '/u04/app/oracle/product/asmdisks/disk1' matches
    no disks
    ORA-15025: could not open disk '/u04/app/oracle/product/asmdisks/disk1'
    ORA-15059: invalid device type for ASM disk
    Linux Error: 32768: Unknown system error
    Additional information: 42
    Additional information: -1073785968
    [oracle@sierra200 dbs]$ cd /u04/app/oracle/product/asmdisks
    [oracle@sierra200 asmdisks]$ ls -ltr
    total 205008
    -rwxrwxrwx 1 oracle oinstall 104857600 Jul 27 11:42 disk1
    -rwxrwxrwx 1 oracle oinstall 104857600 Jul 27 11:47 disk2
    Thanks & Regards
    Sravan Dalavai

    Looks like you are asking ASM to use plain files. Have you used the Device Loopback (losetup) a d made the emulate raw devices?
    http://www.idevelopment.info/data/Oracle/DBA_tips/Automatic_Storage_Management/ASM_20.shtml

  • 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

  • I downloaded my CSDesignWebPremium and when I tried to mount the disk--an error message said "DesignWebPremium,_CS6_LS16.dmg" not recognized

    I downloaded my CSDesignWebPremium and when I tried to mount the disk--an error message said "DesignWebPremium,_CS6_LS16.dmg" not recognized
    (I am using a MAC 2.6 GHz Intel Core i7 (16GB 1600 MHz DDR3) OSX 10.7.5)

    Squasha9 it would appear that the DMG you downloaded is corrupted.  Where did you download the installation files from?  You can download a copy of the installation files from Download CS6 products.

  • Disk image could not be mounted - error

    Ok, I've been using TC (Time Capsule) for a week now, and it was working great. Then in the middle of the week I decided to change the password for TC. Now when I reboot my iMac, TM (Time Machine) will not back up and it gives me a failed - "the backup disk image could not be mounted" error. Then if I go to the AirPort Utility and reboot TC, all of the sudden TM works. Couple of days go by and when I reboot the iMac again, I have to do the whole process again of rebooting TC to get TM to work. Has anyone encountered this issue? I think I explained it well...

    This happened to me too.
    I called Apple (they'll talk to you for 90 days after you buy your Time Capsule and solve all your problems.)
    The solution was to rename the Time Capsule. Here's how:
    Open Time Capsule in System Preferences, click on Change Disk, and choose None from the list.
    Open Airport Utility (choose Go from the Finder Menu, choose Utilities from the list, then Airport Utility), highlight your Time Capsule when its picture appears in the left side bar. Click Manual Setup in the main window, then the Disk icon on the top. Highlight the lower of the two names Time-Capsule Disk and change it to something short and one word, like Disk. Click Update, then close Airport Utility after your Time Capsule restarts.
    Go back to Time Capsule Preferences and click on the Choose Disk button in the center of the main part of the window, then choose your newly-named Time Capsule (If you see more than one Time Capsule name there, restart your computer first).
    This solved it for me. The guy on the phone said that in the tech help people's experience the Time Machine program doesn't like long names or ones with "higher" ascii characters in them.
    Good luck.
    jmb

  • Can't mount disk image error message for TC

    After a couple of frustrating days trying to get a back-up to my TC to work (time wasted waiting for the process to fail each time - Can't mount disk image error type messages etc) I finally got onto this forum and find quite a few people sharing my problem! I wont wait as long next time I have a problem to enter the discussions, tho I must admit I don't get many problems with my Apple gear.
    There doesn't appear to be a solution in the threads, but at least I am not alone!
    How long before and will Apple fix this?

    DiskImageMounter.app is in /System/Library/CoreServices/.

  • 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

  • ORA-15042: ASM disk "2" is missing from group number "1"

    Hi,
    I'm working on an Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production With the Automatic Storage Management option.
    Into the ASM I had 3 diskgroups:
    - ARCHIVELOG (4 disks)
    - ONLINELOG (1 disks)
    - DATA (10 disks)
    When I try to startup the ASM instance I got:
    A-15042: ASM disk "2" is missing from group number "1"The diskgroup won't be mounted.
    I would like to remove that disk and later add a new one.
    I can I do that?
    I'm not able to mount the ARCHIVELOG diskgroup.
    I tried the command
    SQL> alter diskgroup archivelog drop disk ARCH3 force;
    alter diskgroup archivelog drop disk ARCH3 force
    ERROR at line 1:
    ORA-15032: not all alterations performed
    ORA-15001: diskgroup "ARCHIVELOG" does not exist or is not mountedThanks in advance,
    Samuel
    Edited by: Samuel Rabini on Jan 10, 2012 4:11 PM

    As that database is on AWS, I tried this:
    - drop diskgroup archivelog
    - detach of those 4 disks
    - create new 4 disks
    - attach new disks
    - assign those disks to ASM with oracleasm utilty
    - create diskgroup archivelog
    It worked.
    But because I was on AWS and more because it was the ARCHIVELOG diskgroup.
    What would I had to do if it was the DATA diskgroup?
    Thanks

  • Shrinking ASM disk

    I just tried to resize an ASM disk and although the feedback was 'successful', there doesn't appear to have been any change.
    I was attempting to shrink disk DATA_0001 from 200G to 100G. Am I missing something obvious?
    SQL> select group_number, name, path, os_mb, total_mb, free_mb from v$asm_disk;
    GROUP_NUMBER NAME                 PATH                                OS_MB   TOTAL_MB    FREE_MB
              0                      /dev/iscsi/rman11                   20489          0          0
              0                      /dev/iscsi/rmanB11                 102398          0          0
              0                      /dev/iscsi/rman1                    20490          0          0
              0                      /dev/iscsi/vote3                      300          0          0
              0                      /dev/iscsi/vote1                      300          0          0
              0                      /dev/iscsi/rmanP11                 204805          0          0
              0                      /dev/iscsi/vote2                      300          0          0
              0                      /dev/iscsi/rmanP1                  204810          0          0
              0                      /dev/iscsi/rmanB1                  102405          0          0
              1 DATA_0000            /dev/iscsi/db1                      10245      10245      10109
              2 FRA_0000             /dev/iscsi/flshbk1                  20490      20490      20465
    GROUP_NUMBER NAME                 PATH                                OS_MB   TOTAL_MB    FREE_MB
              2 FRA_0001             /dev/iscsi/flshbkR1                409605     409605     409262
              1 DATA_0001            /dev/iscsi/dbR1                    204810     204810     202297
    13 rows selected.
    SQL> alter diskgroup data resize disk 'data_0001' size 100g;
    Diskgroup altered.
    SQL> select group_number, name, path, os_mb, total_mb, free_mb from v$asm_disk;
    GROUP_NUMBER NAME                 PATH                                OS_MB   TOTAL_MB    FREE_MB
              0                      /dev/iscsi/rman11                   20489          0          0
              0                      /dev/iscsi/rmanB11                 102398          0          0
              0                      /dev/iscsi/rman1                    20490          0          0
              0                      /dev/iscsi/vote3                      300          0          0
              0                      /dev/iscsi/vote1                      300          0          0
              0                      /dev/iscsi/rmanP11                 204805          0          0
              0                      /dev/iscsi/vote2                      300          0          0
              0                      /dev/iscsi/rmanP1                  204810          0          0
              0                      /dev/iscsi/rmanB1                  102405          0          0
              1 DATA_0000            /dev/iscsi/db1                      10245      10245      10004
              2 FRA_0000             /dev/iscsi/flshbk1                  20490      20490      20465
    GROUP_NUMBER NAME                 PATH                                OS_MB   TOTAL_MB    FREE_MB
              2 FRA_0001             /dev/iscsi/flshbkR1                409605     409605     409262
              1 DATA_0001            /dev/iscsi/dbR1                    204810     204810     202402
    13 rows selected.The free_mb seems to have increased, but otherwise I can't see the effect of my change. Maybe I'm looking in the wrong place??
    I tried restarting the ASM instance but it made no difference.
    After resizing the disk in ASM I shrunk the disk volume in our storage array. ASM was of course down at the time.
    When I attempted to restart ASM I saw this ...
    SQL> startup
    ASM instance started
    Total System Global Area  283930624 bytes
    Fixed Size                  2158992 bytes
    Variable Size             256605808 bytes
    ASM Cache                  25165824 bytes
    ORA-15032: not all alterations performed
    ORA-15036: disk '/dev/iscsi/dbR1' is truncatedNone of my diskgroups are mounted ...
    SQL> select group_number, name, state from v$asm_diskgroup;
    GROUP_NUMBER NAME            STATE
              0 DATA            DISMOUNTED
              0 FRA             DISMOUNTEDHere's the messages from the ASM instance alert log ...
    SQL> ALTER DISKGROUP ALL MOUNT
    NOTE: cache registered group DATA number=1 incarn=0x5f5e3343
    NOTE: cache began mount (not first) of group DATA number=1 incarn=0x5f5e3343
    NOTE: cache registered group FRA number=2 incarn=0x5f5e3344
    NOTE: cache began mount (not first) of group FRA number=2 incarn=0x5f5e3344
    WARNING::ASMLIB library not found. See trace file for details.
    NOTE: Assigning number (1,0) to disk (/dev/iscsi/db1)
    NOTE: cache dismounting group 1/0x5F5E3343 (DATA)
    NOTE: dbwr not being msg'd to dismount
    NOTE: lgwr not being msg'd to dismount
    NOTE: cache dismounted group 1/0x5F5E3343 (DATA)
    NOTE: cache ending mount (fail) of group DATA number=1 incarn=0x5f5e3343
    kfdp_dismount(): 1
    kfdp_dismountBg(): 1
    NOTE: De-assigning number (1,0) from disk (/dev/iscsi/db1)
    ERROR: diskgroup DATA was not mounted
    NOTE: Assigning number (2,1) to disk (/dev/iscsi/flshbkR1)
    NOTE: Assigning number (2,0) to disk (/dev/iscsi/flshbk1)
    NOTE: cache dismounting group 2/0x5F5E3344 (FRA)
    NOTE: dbwr not being msg'd to dismount
    NOTE: lgwr not being msg'd to dismount
    NOTE: cache dismounted group 2/0x5F5E3344 (FRA)
    NOTE: cache ending mount (fail) of group FRA number=2
    incarn=0x5f5e3344
    kfdp_dismount(): 2
    kfdp_dismountBg(): 2
    NOTE: De-assigning number (2,0) from disk (/dev/iscsi/flshbk1)
    NOTE: De-assigning number (2,1) from disk (/dev/iscsi/flshbkR1)
    ERROR: diskgroup FRA was not mounted
    ORA-15032: not all alterations performed
    ORA-15036: disk '/dev/iscsi/dbR1' is truncated
    ERROR: ALTER DISKGROUP ALL MOUNTAny clues?
    Thanks,
    Steve

    Thanks Markus. I changed the size of the volume back to the original and was able to restart the ASM instances on both nodes. I confirmed it saw the size as the original 200G.
    I then shut down ASM on the second node and issued the alter on the first node. Here's what happened ...
    SQL> select group_number, name, path, os_mb, total_mb, free_mb from v$asm_disk order by name;
    GROUP_NUMBER NAME       PATH                                OS_MB   TOTAL_MB    FREE_MB
               1 DATA_0000  /dev/iscsi/db1                      10245      10245      10004
               1 DATA_0001  /dev/iscsi/dbR1                    204810     204810     202402
               2 FRA_0000   /dev/iscsi/flshbk1                  20490      20490      20465
               2 FRA_0001   /dev/iscsi/flshbkR1                409605     409605     409262
               0            /dev/iscsi/rman1                    20490          0          0
               0            /dev/iscsi/rmanP1                  204810          0          0
               0            /dev/iscsi/rmanB1                  102405          0          0
               0            /dev/iscsi/rmanP11                 204805          0          0
               0            /dev/iscsi/rmanB11                 102398          0          0
               0            /dev/iscsi/rman11                   20489          0          0
    10 rows selected.
    SQL> alter diskgroup data resize disk 'data_0001' size 100g;
    alter diskgroup data resize disk 'data_0001' size 100g
    ERROR at line 1:
    ORA-15032: not all alterations performed
    ORA-15130: diskgroup "DATA" is being dismounted
    ORA-15066: offlining disk "DATA_0001" may result in a data lossHere's the details from the alert log ...
    SQL> alter diskgroup data resize disk 'data_0001' size 100g
    NOTE: requesting all-instance membership refresh for group=1
    WARNING: cache read a corrupted block gn=1 dsk=1 blk=257 from disk 1
    NOTE: a corrupted block was dumped to /var/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_ora_5295.trc
    ERROR: cache failed to read gn=1 dsk=1  blk=257 from disk(s): 1
    ORA-15196: invalid ASM block header [kfc.c:9133] [endian_kfbh] [2147483649] [257] [0 != 1]
    System State dumped to trace file /var/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_ora_5295.trc
    NOTE: cache initiating offline of disk 1  group 1
    WARNING: initiating offline of disk 1.3688884620 (DATA_0001) with mask 0x7e
    NOTE: initiating PST update: grp = 1, dsk = 1, mode = 0x15
    kfdp_updateDsk(): 14
    Thu May 07 15:45:38 2009
    kfdp_updateDskBg(): 14
    ERROR: too many offline disks in PST (grp 1)
    Thu May 07 15:45:38 2009
    NOTE: halting all I/Os to diskgroup DATA
    Thu May 07 15:45:38 2009
    SQL> alter diskgroup DATA dismount force
    NOTE: active pin found: 0x0x6ddf6060
    NOTE: active pin found: 0x0x6ddf6168
    ERROR: ORA-15130 signalled during resize of diskgroup DATA
    Thu May 07 15:45:38 2009
    NOTE: membership refresh pending for group 1/0xdc0f1999 (DATA)
    kfdp_query(): 15
    kfdp_queryBg(): 15
    SUCCESS: refreshed membership for 1/0xdc0f1999 (DATA)
    ERROR: ORA-15130 thrown in RBAL for group number 1
    Errors in file /var/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_rbal_5202.trc:
    ORA-15130: diskgroup "DATA" is being dismounted
    Errors in file /var/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_rbal_5202.trc:
    ORA-15130: diskgroup "DATA" is being dismounted
    ORA-15032: not all alterations performed
    ORA-15130: diskgroup "DATA" is being dismounted
    ORA-15066: offlining disk "DATA_0001" may result in a data loss
    ERROR: alter diskgroup data resize disk 'data_0001' size 100g
    NOTE: cache dismounting group 1/0xDC0F1999 (DATA)
    NOTE: dbwr not being msg'd to dismount
    Thu May 07 15:45:41 2009
    Dirty detach reconfiguration started (old inc 6, new inc 6)
    List of nodes:
    0
    Global Resource Directory partially frozen for dirty detach
    * dirty detach - domain 1 invalid = TRUE
    10 GCS resources traversed, 0 cancelled
    Dirty Detach Reconfiguration complete
    Thu May 07 15:45:41 2009
    freeing rdom 1
    Thu May 07 15:45:41 2009
    WARNING: dirty detached from domain 1
    NOTE: cache dismounted group 1/0xDC0F1999 (DATA)
    kfdp_dismount(): 16
    kfdp_dismountBg(): 16
    NOTE: De-assigning number (1,0) from disk (/dev/iscsi/db1)
    NOTE: De-assigning number (1,1) from disk (/dev/iscsi/dbR1)
    SUCCESS: diskgroup DATA was dismounted
    SUCCESS: alter diskgroup DATA dismount force
    ERROR: PST-initiated MANDATORY DISMOUNT of group DATA
    Thu May 07 15:46:06 2009
    SQL> alter diskgroup data resize disk 'data_0001' size 100g
    ORA-15032: not all alterations performed
    ORA-15001: diskgroup "DATA" does not exist or is not mounted
    ERROR: alter diskgroup data resize disk 'data_0001' size 100gLooks like my earlier attempt has indeed screwed up something so even though the instances start OK and mount the diskgroup, I think there's a fair chance something would go splat sooner rather than later.
    As this is a test database, I think I'll cut my losses and rebuild the diskgroup then restore it from backup. I'm assuming the effort involved in correcting the corruption will be greater than rebuilding and restoring.
    Do you agree with this?
    Then I'll try again and hopefully get it right.
    Thanks for your help!!!
    Steve

  • Using udev devices for ASM disk on Linux

    Hello all,
    I need details related to using udev devices as ASM disk on Linux.
    What I want to know is, once i get the list of ASM Disks that are used to create the DiskGroups, based on the path of the Disk (whether /dev/sdj or /dev/dm-3 or /dev/asm_udev_device, /dev/vx/<vxvm-volume>, /dev/<lvm-volume>) how do i get to know if the device type is a udev device?
    I want to know an automated process, so that i can script it out to separate out each device easily.
    Please let me know if anyone has expertise on using udev devices with Oracle ASM.
    I have referred the link but no much details available http://www.oracle.com/technology/products/database/asm/pdf/device-mapper-udev-crs-asm%20rh4.pdf
    Further, the behavior of udevinfo command is very different across version of Linux. From Suse 10 onwards, udevadm has to be used instead.
    Its confusing to me.
    Please help.
    ~Sumeet.

    My installation, ASM On SI
    S.O HP-UIx
    Disk internal, not SAN
    Internal disk configuration for Oracle.
    PV Name /dev/dsk/c11t0d0
    PV Name /dev/dsk/c11t1d0
    PV Name /dev/dsk/c11t2d0
    PV Name /dev/dsk/c11t3d0
    PV Name /dev/dsk/c11t4d0
    PV Name /dev/dsk/c11t6d0
    Vg:
    /dev/vgora
    Lv
    /dev/vgora/lvu01 <-- Oracle Bin mounted /u00
    /dev/vgora/lvu02 <-- External Archive /u02
    In /dev/vgora
    brw-r----- 1 root sys 64 0x010001 Mar 8 14:42 lvu01
    brw-r----- 1 root sys 64 0x010002 Mar 8 16:15 lvu02
    brwxrwxr-x 1 root sys 64 0x010003 Mar 19 14:19 lvasm01
    brwxrwxr-x 1 root sys 64 0x010004 Mar 19 14:20 lvasm02
    brwxrwxr-x 1 root sys 64 0x010005 Mar 19 14:20 lvasm03
    brwxrwxr-x 1 root sys 64 0x010006 Mar 19 14:20 lvasm04
    brwxrwxr-x 1 root sys 64 0x010007 Mar 19 14:20 lvasm05
    brwxrwxr-x 1 root sys 64 0x010008 Mar 19 14:20 lvasm06
    brwxrwxr-x 1 root sys 64 0x010009 Mar 19 14:20 lvasm07
    brwxrwxr-x 1 root sys 64 0x01000a Mar 19 14:20 lvasm08
    brwxrwxr-x 1 root sys 64 0x01000b Mar 19 14:20 lvasm09
    brwxrwxr-x 1 root sys 64 0x01000c Mar 19 14:21 lvasm10
    crw-r----- 1 root sys 64 0x010001 Mar 8 14:42 rlvu01
    crw-r----- 1 root sys 64 0x010002 Mar 8 16:15 rlvu02
    crw-r--r-- 1 root sys 64 0x010000 Mar 8 14:19 group
    FOR ASM
    crw-rw---- 1 oracle dba 64 0x010003 Mar 19 14:19 rlvasm01
    crw-rw---- 1 oracle dba 64 0x010004 Mar 19 14:20 rlvasm02
    crw-rw---- 1 oracle dba 64 0x010005 Mar 19 14:20 rlvasm03
    crw-rw---- 1 oracle dba 64 0x010006 Mar 19 14:20 rlvasm04
    crw-rw---- 1 oracle dba 64 0x010007 Mar 19 14:20 rlvasm05
    crw-rw---- 1 oracle dba 64 0x010008 Mar 19 14:20 rlvasm06
    crw-rw---- 1 oracle dba 64 0x010009 Mar 19 14:20 rlvasm07
    crw-rw---- 1 oracle dba 64 0x01000a Mar 19 14:20 rlvasm08
    crw-rw---- 1 oracle dba 64 0x01000b Mar 19 14:20 rlvasm09
    crw-rw---- 1 oracle dba 64 0x01000c Mar 19 14:21 rlvasm10
    And the problem is:
    When i run dbca for create diskgroup, that not recognize the disk.
    I will set asm_diskstring with the correctly path.
    I try to create a diskgroup from command line, but i see this error.
    SQL> create diskgroup DG_DATA_01 external redundancy DISK '/dev/vgora/rlvasm01' ;
    create diskgroup DG_DATA_01 external redundancy DISK '/dev/vgora/rlvasm01'
    ERROR at line 1:
    ORA-15018: diskgroup cannot be created
    ORA-15031: disk specification '/dev/vgora/rlvasm01' matches no disks
    ORA-15025: could not open disk '/dev/vgora/rlvasm01'
    ORA-15059: invalid device type for ASM disk
    Additional information: 255

  • How to add ASM Disk to Disk Group that is shown as MEMBER?

    HI,
    We have a Production Oracle RAC on HP-UX. We have Two Disk Groups one for Arcive (ARC_DISK) and other for Database(DATA_DISK).
    Today I wanted to add another 200 GB of Disk Space to the DATA_DISK Group.
    I opened DBCA and could not find the new disk in the 'Show Candidates' option. But after the Unix admin changed the ownership and permission of the Disk, it was shown in 'Show Candidates' option. I selected this Disk and continued but got an error later as we didnt change the ownership and permission from the 2nd Unix server. After doing this, , when I open DBCA to add disk, nothing is shown in 'Show Candidates' option but when we click on 'Show All', the new disk is listed as MEMBER (header status) but not allocated to any Disk Group.
    I would like to know how to allocate this Disk (which is already shown as MEMBER) to the DATA_DISK - ASM diskgroup. This is a production database system.
    Rgds,
    Thiru

    user1983888 wrote:
    Hi,
    Due to huge difference in Disk Size which I am trying to add to the existing Disk Group which has 1024 GB of Disk, would it be a better idea to create a new Disk Group with 200g GB Disk? Will this command work as the header_status is already MEMBER?
    SQL>CREATE DISKGROUP DATA_DISK1
    EXTERNAL REDUNDANCY
    DISK 'disk path';
    Thanks.Yes, you can create new diskgroup (DATA_DISK1). Just make sure all datafile in DATA_DISK autoextend off, then create all your new datafile to the new diskgroup DATA_DISK1. The command will not work as the header_status is MEMBER. You'll receive ORA-15018 & ORA-15033 error. As I mentioned before, you need to use FORCE option or format the disk using dd* command before perform above command.
    1st Option : (Format the raw disk using dd command creating new diskgroup. Header_status MEMBER -> CANDIDATE). E.g.
    1. dd if=/dev/zero of=/dev/rdsk/c2t1d0 bs=8192 count=1000 //any rac nodes
    2. # chown oracle:oinstall /dev/rdsk/c2t1d0 //perform on both node. This apply if using LVM or direct access to raw
    3. SQL> create diskgroup data_disk1 external redundancy disk '/dev/rdsk/c2t1d0'; //any RAC node in ASM instance
    4. SQL> alter diskgroup data_disk1 mount; //try to mount on the other node
    2nd Option : (Using FORCE option when creating the new diskgroup. Header_Status = MEMBER)
    1. # chown oracle:oinstall /dev/rdsk/c2t1d0 //perform on both node. This apply if using LVM or direct access to raw
    2. SQL> create diskgroup data_disk1 external redundancy disk '/dev/rdsk/c2t1d0' force; //any RAC node in ASM instance
    3. SQL> alter diskgroup data_disk1 mount; //try to mount on the other node
    Just be careful when using FORCE option or DD command. If you perform this operation on existing ASM disk groups disk, it may destroy existing disk groups.

Maybe you are looking for

  • All master data values not shown in query selections

    Hi I have created a query on a BasisCube containing the InfoObject 0FUNC_AREA. I loaded data to 0FUNC_AREA and the cube. I then created a query on the cube, in which I want to filter on 0FUNC_AREA. However, when I get the list of available values for

  • My iphone was stolen- pick pocket in china

    my iphone was stolen in china, dongguan city guangding province, china yongning zhangmutou town on the 1st street.  can i locate the exact location of my  iphone? how.? my qq is still in operation which i can see in my friend qq when switch on. can i

  • Invalid Directory in mail account configuration

    In Mac Mail, I have 4 accounts configured.  One each from Yahoo, MSN, Comcast and Mobile Me.  In the advanced tab of accounts, there is the box that you can uncheck to leave a copy of incoming mail on the server.  But when I try to do that with the C

  • Computer Running Slow... what should I do? is it the version or something else?

    I have a Mac Book, Mac OS X , Version 10.5.8 that is running very slow. I am assuming I need to save my files to an external hard drive, clean it up and then purchase and buy a new version.  Leopard? or something? Can anyone give me advice? I don't k

  • No Power to Audigy 2 ZS Platinum Pro I/O

    Hi, I've just installed an Audigy 2 ZS Platinum Pro in my computer. I have the sound card and software functioning fine from what I can tell, but there is no power to the I/O Hub. I have connected the I/O Hub to the sound card using the AD_Link cable