The running of the "vxddladm assign names" command causes the user-group ownership and permissions for ASM disks to be lost.
book
Article ID: 100033829
calendar_today
Updated On:
Description
Error Message
# /usr/lib/vxvm/bin/vxdmpraw enable oracle dba 755 emc_clariion0_252
VxVM vxdmpraw ERROR V-5-2-6158
Device ownership for the device 'emc_clariion0_252' is already set.
Please use vxdmpraw disable to remove ownership for
this device and then execute vxdmpraw enable with new
ownership details.
Cause
This is due to a bug in the VxVM code and the fix has been identified.
Resolution
The /etc/vx/.vxdmprawdev file keeps track of the user/group ownership and permissions set for the ASM disks and since this file still exists, the following two workarounds will restore these values on the ASM disks.
Workaround #1:
# rm -rf /dev/vx/rdmp/
*
# rm -rf dev/vx/dmp/*
# vxdctl enable
so for the emc_clariion0_252 ASM disk this workaround would have involved running:
# rm -rf /dev/vx/rdmp/emc_clariion0_252*
# rm -rf /dev/vx/dmp/emc_clariion0_252*
# vxdctl enable
Workaround #2:
# /usr/lib/vxvm/bin/vxdmpraw disable
# /usr/lib/vxvm/bin/vxdmpraw enable
so for the emc_clariion0_252 ASM disk, the following commands would have been needed:
# /usr/lib/vxvm/bin/vxdmpraw disable oracle dba 755 emc_clariion0_252
# /usr/lib/vxvm/bin/vxdmpraw enable oracle dba 755 emc_clariion0_252
Additionally two hotfixes have been created for this - one for VxVM 6.1.1 on Solaris 10 sparc and one for VxVM 6.2.1 on Solaris 10 sparc.
If either of these hotfixes are required, please contact Veritas Support.
These fixes will be included in the next GA patches for the 6.1.1 and 6.2.1 on Solaris 10 sparc, but these GA patches have yet to be planned.
Issue/Introduction
On a SFHA 6.1 and 6.2 cluster both running on Solaris 10 sparc, the Oracle databases were configured to run on ASM disks. However when running the 'vxddladm assign names' command as part of the device tree refresh activity when doing lun removal/addition activities, the user/group ownership and permissions for the ASM disks were being lost which resulted in a service interruption on the Oracle databases.
For example in the case of the emc_clariion0_252 ASM disk:
# /usr/lib/vxvm/bin/vxdmpraw enable oracle dba 755 emc_clariion0_252
VxVM vxdmpraw INFO V-5-2-6157
Device enabled : emc_clariion0_252
VxVM vxdmpraw INFO V-5-2-6155
Please set ASM_DISKSTRING to '/dev/vx/rdmp/*' or '/dev/vx/dmp/*'
for Oracle ASM to work on DMP devices.
# ls -l /dev/vx/rdmp | grep emc_clariion0_252
crwxr-xr-x 1 oracle dba 311, 18 Mar 13 09:42 emc_clariion0_252
crwxr-xr-x 1 oracle dba 311, 16 Mar 13 09:42 emc_clariion0_252s0
crwxr-xr-x 1 oracle dba 311, 17 Mar 13 09:42 emc_clariion0_252s1
crwxr-xr-x 1 oracle dba 311, 18 Mar 13 09:42 emc_clariion0_252s2
crwxr-xr-x 1 oracle dba 311, 19 Mar 13 09:42 emc_clariion0_252s3
crwxr-xr-x 1 oracle dba 311, 20 Mar 13 09:42 emc_clariion0_252s4
crwxr-xr-x 1 oracle dba 311, 21 Mar 13 09:42 emc_clariion0_252s5
crwxr-xr-x 1 oracle dba 311, 22 Mar 13 09:42 emc_clariion0_252s6
crwxr-xr-x 1 oracle dba 311, 23 Mar 13 09:42 emc_clariion0_252s7
# ls -l /dev/vx/dmp | grep emc_clariion0_252
brwxr-xr-x 1 oracle dba 311, 18 Mar 13 09:42 emc_clariion0_252
brwxr-xr-x 1 oracle dba 311, 16 Mar 13 09:42 emc_clariion0_252s0
brwxr-xr-x 1 oracle dba 311, 17 Mar 13 09:42 emc_clariion0_252s1
brwxr-xr-x 1 oracle dba 311, 18 Mar 13 09:42 emc_clariion0_252s2
brwxr-xr-x 1 oracle dba 311, 19 Mar 13 09:42 emc_clariion0_252s3
brwxr-xr-x 1 oracle dba 311, 20 Mar 13 09:42 emc_clariion0_252s4
brwxr-xr-x 1 oracle dba 311, 21 Mar 13 09:42 emc_clariion0_252s5
brwxr-xr-x 1 oracle dba 311, 22 Mar 13 09:42 emc_clariion0_252s6
brwxr-xr-x 1 oracle dba 311, 23 Mar 13 09:42 emc_clariion0_252s7
However after running the 'vxddladm assign names' command, the settings for the emc_clariion0_252 ASM disk were lost.
# ls -l /dev/vx/rdmp | grep emc_clariion0_252
brw------- 1 root root 289, 58 Feb 10 13:10 emc_clariion0_252
brw------- 1 root root 289, 56 Feb 10 13:10 emc_clariion0_252s0
brw------- 1 root root 289, 57 Feb 10 13:10 emc_clariion0_252s1
brw------- 1 root root 289, 58 Feb 10 13:10 emc_clariion0_252s2
brw------- 1 root root 289, 59 Feb 10 13:10 emc_clariion0_252s3
brw------- 1 root root 289, 60 Feb 10 13:10 emc_clariion0_252s4
brw------- 1 root root 289, 61 Feb 10 13:10 emc_clariion0_252s5
brw------- 1 root root 289, 62 Feb 10 13:10 emc_clariion0_252s6
brw------- 1 root root 289, 63 Feb 10 13:10 emc_clariion0_252s7
# ls -l /dev/vx/dmp | grep emc_clariion0_252
brw------- 1 root root 289, 58 Feb 10 13:10 emc_clariion0_252
brw------- 1 root root 289, 56 Feb 10 13:10 emc_clariion0_252s0
brw------- 1 root root 289, 57 Feb 10 13:10 emc_clariion0_252s1
brw------- 1 root root 289, 58 Feb 10 13:10 emc_clariion0_252s2
brw------- 1 root root 289, 59 Feb 10 13:10 emc_clariion0_252s3
brw------- 1 root root 289, 60 Feb 10 13:10 emc_clariion0_252s4
brw------- 1 root root 289, 61 Feb 10 13:10 emc_clariion0_252s5
brw------- 1 root root 289, 62 Feb 10 13:10 emc_clariion0_252s6
brw------- 1 root root 289, 63 Feb 10 13:10 emc_clariion0_252s7
When trying to re-enable the user/group ownership and permissions, the following error was reported:
# /usr/lib/vxvm/bin/vxdmpraw enable oracle dba 755 emc_clariion0_252
VxVM vxdmpraw ERROR V-5-2-6158
Device ownership for the device 'emc_clariion0_252' is already set.
Please use vxdmpraw disable to remove ownership for
this device and then execute vxdmpraw enable with new
ownership details.
Was this article helpful?
thumb_up
Yes
thumb_down
No