Re: ASM disk discovery in AIX
- From: TESTAJ3@xxxxxxxxxxxxxx
- To: smishra_97@xxxxxxxxx
- Date: Fri, 15 May 2009 10:36:29 -0400
I've had success with clearing out the "discovery string path", if you
fire up dbca what does it show for ASM disks, on linux we deal with
/dev/oracleasm for the devices, can I assume you've run oracleasm
createdisk command?
joe
_______________________________________
Joe Testa, Oracle Certified Professional
(Work) 614-677-1668
(Cell) 614-312-6715
Interested in helping out your marriage?
Ask me about "Weekend to Remember"
Dec 11-13, 2009 here in Columbus.
From:
Sanjay Mishra <smishra_97@xxxxxxxxx>
To:
oracle-l@xxxxxxxxxxxxx
Date:
05/15/2009 10:09 AM
Subject:
ASM disk discovery in AIX
Sent by:
oracle-l-bounce@xxxxxxxxxxxxx
Hi
I am facing issue with discovery of disks on the AIX server. This is new
environment which is 4 -node RAC and when I am trying to configure ASM
disk group , I am not able to see the ASM disks. Here is what is available
so far
Db Version : 10.2.0.4
Platform : AIX
1. Permission on ASM disk are Oracle:oinstall
2. Also Mode setting is 660
3. More information on Major/Minor along with Alias. I tried to use
/dev/*, /dev/ora_asm* but no one is able to discover any disk.
racdb1 dev$ls -ltr |grep "36, 39"
crw-rw---- 1 root system 37, 39 Mar 31 13:32 rhdiskpower39
brw-rw---- 1 root system 37, 39 Mar 31 13:32 hdiskpower39
crw-rw---- 1 oracle oinstall 37, 39 Apr 30 15:07 ora_asm_disk34
4. Reserve_lock information
racdb1:/dev$lsattr -El hdiskpower39
cgname Consistency Group Name
True
clr_q yes Clear Queue (RS/6000) True
location Location True
lun_id 0x1b9000000000000 LUN ID False
lun_reset_spt yes FC Forced Open LUN True
max_coalesce 0x20000 Maximum coalesce size True
max_transfer 0x40000 Maximum transfer size True
pvid none Physical volume identifier
False
pvid_takeover yes Takeover PVIDs from hdisks True
q_err no Use QERR bit True
q_type simple Queue TYPE False
queue_depth 16 Queue DEPTH True
reassign_to 120 REASSIGN time out value True
reserve_lock no Reserve device on open True
rw_timeout 40 READ/WRITE time out True
scsi_id 0x632913 SCSI ID False
start_timeout 180 START unit time out True
ww_name 0x50060482d530b488 World Wide Name False
5. Tried to Truss the rbal process and ran the "Select * from v$asm_disk"
and here is the ouutput
540734: = 1
540734: thread_wait(3000) = 0
540734: statx(".", 0x0FFFFFFFFFFFB330, 176, 0) = 0
540734: open(".", O_RDONLY) = 14
540734: getdirent64(14, 0x0000000110647CF0, 4096) = 264
540734: klseek(14, 0, 0, 0x0FFFFFFFFFFFB230) = 0
540734: kfcntl(14, F_GETFD, 0x000000011025EF78) = 0
540734: kfcntl(14, F_SETFD, 0x0000000000000001) = 0
540734: close(14) = 0
540734: statx("/", 0x0FFFFFFFFFFFB550, 176, 020) = 0
540734: statx("./", 0x0FFFFFFFFFFFB550, 176, 020) = 0
540734: statx("./../", 0x0FFFFFFFFFFFB330, 176, 0) = 0
540734: open("./../", O_RDONLY) = 14
540734: getdirent64(14, 0x0000000110647CF0, 4096) = 2360
540734: klseek(14, 0, 0, 0x0FFFFFFFFFFFB230) = 0
540734: kfcntl(14, F_GETFD, 0x000000011025EF78) = 0
540734: kfcntl(14, F_SETFD, 0x0000000000000001) = 0
540734: fstatx(14, 0x0FFFFFFFFFFFB550, 176, 020) = 0
540734: getdirent64(14, 0x0000000110647CF0, 4096) = 2360
540734: close(14) = 0
540734: statx("./../../", 0x0FFFFFFFFFFFB330, 176, 0) Err#13 EACCES
540734: thread_post(1458215) = 0
540734: thread_post(1458215) = 0
540734: thread_post(1458215) = 0
540734: thread_wait(2270) (sleeping...)
540734: thread_wait(2270) = 1
540734: times(0x0FFFFFFFFFFFD760) = 32513143
540734: times(0x0FFFFFFFFFFFD6B0) = 32513143
540734: open("/proc/651314/psinfo", O_RDONLY) = 14
540734: kread(14, "\0 \0010204\001\0\0\001".., 448) = 448
540734: close(14) = 0
Any more checking that can help
TIA
Sanjay
Other related posts:
