Before you add the disk(s) to your production diskgroup, you can use the next steps to validate whether the candidate disk(s) is/are in good shape and can be accessed from each node (without harm the existing production diskgroups), as follow:
1) As Oracle OS user, run the next commands on each node (if ASMLIB API is used):
$>id
$>/etc/init.d/oracleasmscandisks
$>/etc/init.d/oracleasmlistdisks
$>/etc/init.d/oracleasmquerydisk<eachdiskfrompreviousoutput>
Note: All the disks must be visible from each node.
2) Confirm the disks are visible (I/O) at OS level (as Oracle OS user) from each node:
$>id
$>ls-l<diskname>
$>ddif=<raw/partitionfileinquestion>of=/dev/nullcount=100bs=8192
Example:
$>ddif=/dev/raw/raw1of=/dev/nullcount=100bs=8192#rawdevice
$>ddif=/dev/oracleasm/disks/PRODA07of=/dev/nullcount=100bs=8192#ASMLIBdevice
3) Create a new temporary diskgroup:
SQL>CREATEDISKGROUPTESTEXTERNALREDUNDANCYDISK'<YOURCANDIDATEDISK>';
4) Check if the diskgroup is created and mounted:
SQL>SELECTSTATE,NAMEFROMV$ASM_DISKGROUP;
5) If so, then manually mount it on the other ASM instance(s):
SQL>ALTERDISKGROUPTESTMOUNT;
SQL>SELECTSTATE,NAMEFROMV$ASM_DISKGROUP;
6 If the previous steps had success and the TEST diskgroup can be successfully mounted (on each ASM instance), then drop the TEST diskgroup as follow:
SQL>alterdiskgrouptestdismount;--(fromalltheASMinstances,exceptfromone).
SQL>DROPDISKGROUPTEST;--(fromtheASMinstance,whichthediskgroupisstillmounted).
7) Then the candidate disk is ready to be added to the desired diskgroup:
SQL>ALTERDISKGROUP<myproductiondiskgroup>ADDDISK'<yourcandidatedisk>';
NOTE:288002.1 - OERR: ORA-15075 disk(s) are not visible cluster-wide
From Oracle
-------------------------------------------------------------------------------------------------------
Blog: http://blog.csdn.net/tianlesoftware
Email: [email protected]
DBA1 群:62697716(满); DBA2 群:62697977(满) DBA3 群:62697850(满)
DBA 超级群:63306533(满); DBA4 群: 83829929 DBA5群: 142216823
聊天 群:40132017 聊天2群:69087192
--加群需要在备注说明Oracle表空间和数据文件的关系,否则拒绝申请