Assigning a PVID To An ASM Disk Corrupts the ASM Disk Header

[ID 353761.1]

    
修改时间:2011-11-18类型:ALERT状态:PUBLISHED优先级:1   
    单击此项可添加到收藏夹    为此文档评级    通过电子邮件发送此文档的链接    在新窗口中打开文档    可打印页        没有任何注释注释 (0)    转到底部转到底部

In this Document
  Description
  Likelihood of Occurrence
  Possible Symptoms
  Workaround or Resolution
  References

Applies to:
Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 11.2.0.3 - Release: 10.1 to 11.2
IBM AIX on POWER Systems (64-bit)
***Checked for relevance on 30-Apr-2010***

AIX5L Based Systems (64-bit)
Description
Assigning a Physical Volume ID (PVID) to an existing ASM disk will destroy the ASM disk header rendering the
ASM disk unusable.

Various documents including the 10gR1 and 10gR2 installation instructions for AIX platforms suggest to assign
a PVID to disks to be used for ASM using the following command:
 

  # /usr/sbin/chdev -l hdiskn -a pv=yes


These documents furthermore suggest that this command is to be run on ALL nodes of a RAC cluster. This
does not present a problem as long as the disks have not yet been used by ASM. If however the disk are
already in use and above command is issued against an ASM disk the file header will be destroyed.
This is likely to happen if a new node is added to an existing RAC cluster as the documentation seems
to imply this has to be done on all nodes.

To check if a device has an associated PVID , use lspv:
EXAMPLE:


# lspv

hdisk0 0003286f04bc73ee rootvg active
hdisk1 0003286f867d77e1 rootvg active
hdisk2 0003286fb3470dae vg01 active
hdisk3 0003286fb3474190 vg01 active
hdisk4 0003286fb34747d1 vg01 active
hdisk5 0003286fb3474dff vg01 active
hdisk6 0003286fb3475428 vg01 active
hdisk7 0003286fb347607d vg01 active
hdisk8 0003286fb34766f3 vg01 active
hdisk9 0003286fb3476d70 vg01 active
hdisk10 0003286fb34773d5 vg01 active
hdisk11 0003286fb34780b8 vg01 active
hdisk12 0003286fb347872f vg01 active
hdisk13 0003286fb347940c vg01 active
hdisk14 0003286fb3479a7b vg01 active

The second column is the PVID.
Likelihood of Occurrence
This is more likely to happen in a RAC environment, specifically if a new node is added to an existing
cluster.
Possible Symptoms
If the 'chdev' command is run while ASM instances have the disk mounted nothing will be noticed immediately
as the disk header is only read when the disk is mounted. If however the diskgroup is unmounted and re-mounted
(e.g. ASM instance restart) the disk is no longer recognized as an ASM disk and the diskgroup mount will fail
with
ORA-15063 "diskgroup \"%s\" lacks quorum of %s PST disks; %s found"
or
ORA-15063: ASM discovered an insufficient number of disks for diskgroup s%
ORA-15040: diskgroup is incomplete
ORA-15042: ASM disk "%" is missing
Workaround or Resolution
Do not assign a PVID to ASM disks, contrary to the documentation PVIDs are not required for ASM disks
as ASM uses the ASM disk header to discover it's disks.
This has been addressed in (Documentation)  Bug 3636335 which states:

       "This is a doc. bug and we are going to clearly document not to put PVIDs on
        disks given to ASM. The idea here is that ASM is the one which manages the
        disk and not any OS / vendor volume managers etc., PVIDs are needed for volume
        groups to work. For ASM to work, PVIDs are not needed. ASM has its own headers
        to identify the disk which is what is getting written here. "

As long as there is still an ASM instance which has the disk(group) mounted the
contents may be backed up via RMAN as soon as possible.

Also the action plan from the Document 750016.1 can be applied. Also recommend to raise an SR with Oracle Support.
References
BUG:3636335 - PVID IN DISK HEADER IS OVERWRITTEN AFTER ADDING A NEW DISK TO ASM DISKGROUP
Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide 10g Release 2 (10.2) for AIX
    
       
相关内容
       
     
    
   
产品
       
     

    Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition > STORAGE > ASM Administration, Errors

    
   
关键字
       
     
AIX;ASM
    
   
错误
       
     
ORA-15040;ORA-15042;ORA-15063
返回页首返回页首

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/38267/viewspace-717109/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/38267/viewspace-717109/