Error messages

66 Topics

Maxuproc not get updated even after reboot
Hi, Got a update to change the "maxuproc for wt82369 by 1.5 times" , While verifying we make necessary modification on the Global (wt81958). Normally there is a relation between max_nprocs value and maxuproc value. FYI.. maxuprc = max_nprocs – reserved_procs (default is 5) In this case we modified the max_nprocs value from 30000 to 50000 FYI.. [root@wt81958 GLOBAL] /etc # cat /etc/system | grep max_nprocs set max_nprocs=50000 After the global zone reboot the value is not updated while we hit sysdef [root@wt81958 GLOBAL] /root # sysdef | grep processes 30000 maximum number of processes (v.v_proc) 29995 maximum processes per user id (v.v_maxup) Can anyone please assist us if any thing we missed in this to make the necessary changes to replicate. Awaiting for your valuable suggestions. Thanks, senthilsam
Solved
senthilsam
5 years ago Place Storage Foundation
3.2KViews
0likes
3Comments
vxlicrep ERROR V-21-3-1015 Failed to prepare report for key
Dear all, we got a INFOSCALE FOUNDATION LNX 1 CORE ONPREMISE STANDARD PERPETUAL LICENSE CORPORATE. I have installed key using the vxlicinst -k <key> command. But when I want to check it using vxlicrep I'm getting this error for the given key: vxlicrep ERROR V-21-3-1015 Failed to prepare report for key = <key> We have Veritas Volume Manager 5.1 (VRTSvxvm-5.1.100.000-SP1_RHEL5 and VRTSvlic-3.02.51.010-0) running on RHEL 5.7 on 64 bits. I've read that the next step is to run vxkeyless set NONE, but I'm afraid to run this until I cannot see the license reported correctly by vxlicrep. What can I do to fix it? Thank you in advance. Kind regards, Laszlo
Laszlo_Budai
7 years ago Place Storage Foundation
4.2KViews
0likes
7Comments
Query about cache volume and cache object
Hi I am creating a cache, but it is failing can you please suggest what's wrong with this?? # vxassist -g versant_vg make versant_CACHE 19.8 VxVM vxassist INFO V-5-1-13572 Volume length rounded-up to 32 so that#012#011it is a multiple of the disk group alignment. # vxmake -g versant_vg cache versant_CACHE_OBJECT cachevolname=versant_CACHE autogrow=on highwatermark=90 autogrowby=1g maxautogrow=4g VxVM vxmake ERROR V-5-1-10127 associating volume versant_CACHE with versant_CACHE_OBJECT:#012#011Cache volume for cache object is too small Thanks
Solved
arun660
9 years ago Place Storage Foundation
1.4KViews
0likes
3Comments
how to change a DISKID?
I have one broken DG: localhost.vtb24.ru# vxprint -hqt Disk group: somedg dg somedg default default 11000 1364281050.8.localhost dm disk1 disk1 auto 65536 2147417808 - dm disk2 - - - - NODEVICE v vol01 - DISABLED ACTIVE 4294834176 SELECT - fsgen pl vol01-01 vol01 DISABLED NODEVICE 4294834176 STRIPE 2/128 RW sd disk1-01 vol01-01 disk1 0 2147417088 0/0 disk1 ENA sd disk2-01 vol01-01 disk2 0 2147417088 1/0 - NDEV localhost.vtb24.ru# vxprint -g somedg -dF'%last_da_name %name %diskid' disk1 disk1 1431951508.19.localhost disk2 disk2 1431951509.21.localhost localhost.vtb24.ru# vxdisk -x DISKID -x DGID -p list DEVICE DISKID DGID ibm_vscsi0_0 - - ibm_vscsi0_1 - - disk1 1431951508.19.localhost 1364281050.8.localhost disk2 1431951508.19.localhost 1364281050.8.localhost Both discs have the same diskid. How can i fix this?
Solved
ikomyagin
10 years ago Place Storage Foundation
1.2KViews
0likes
1Comment
Unable to import disk Group - udid mismatch - label missing
Unable to import DG , Below is vxdisk list O/P : DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR disk_0 auto:none - - online invalid c0t5000CCA0251DB3C8d0s2 - disk_1 auto:none - - online invalid c0t5000CCA0251DCAE0d0s2 - disk_2 auto:none - - online invalid c0t5000CCA0251E4B84d0s2 - disk_3 auto:ZFS - - ZFS c0t5000CCA0251E5D78d0s2 - emcpower0s2 auto - - error udid_mismatch emcpower0c - emcpower1s2 auto:cdsdisk - (fdeappfmdev_dg) online thinrclm emcpower1c - emcpower2s2 auto - - error udid_mismatch emcpower2c - emcpower3s2 auto:cdsdisk - (fdeappfmdev_dg) online thinrclm emcpower3c - emcpower4s2 auto:cdsdisk - (fdeappfmdev_dg) online thinrclm emcpower4c - emcpower5s2 auto:cdsdisk - (fdeappfmdev_dg) online thinrclm emcpower5c - emcpower6s2 auto - - error udid_mismatch emcpower6c - emcpower7s2 auto:cdsdisk - (minotaurdbdev_dg) online thinrclm emcpower7c - emcpower8s2 auto:cdsdisk - (minotaurdbdev_dg) online thinrclm emcpower8c - emcpower9s2 auto:cdsdisk - (minotaurdbdev_dg) online thinrclm emcpower9c - emcpower10s2 auto:cdsdisk - (minotaurdbdev_dg) online thinrclm emcpower10c - emcpower11s2 auto - - error udid_mismatch emcpower11c - emcpower12s2 auto:cdsdisk - (minotaurdbdev_dg) online emcpower12c - * vxdisk list for emcpower0 for instance : Device: emcpower0s2 devicetag: emcpower0 type: auto flags: error private autoconfig udid_mismatch pubpaths: block=/dev/vx/dmp/emcpower0s2 char=/dev/vx/rdmp/emcpower0s2 guid: - udid: EMC%5FSYMMETRIX%5F000292601936%5F36033FF000 site: - Multipathing information: numpaths: 1 emcpower0c state=enabled update the udid didn't work , These disks emcpower0 , emcpower2 , emcpower6 , emcpower11 are reporting the below errors in messages file : Jun 9 15:15:03 vienna scsi: [ID 107833 kern.warning] WARNING: /pci@400/pci@2/pci@0/pci@c/SUNW,emlxs@0/fp@0,0/ssd@w50000974081e41ac,8 (ssd13): Jun 9 15:15:03 vienna Corrupt label - bad geometry Jun 9 15:15:03 vienna scsi: [ID 107833 kern.notice] Label says 585921440 blocks; Drive says 536878080 blocks SUN Explorer shows no label for theses LUNS , unlike other good LUNS "ex:emcpower12" ... LUNs are healthy from O.S. and storage side , No changes was done from storage side .. What Could be the reason , any suggesstion to solve this issue ?
hytham_fekry
10 years ago Place Storage Foundation
866Views
0likes
2Comments
Unable to boot solaris after un-encapsulating root disk
we have a Solaris 10 X86 "147441-12 " with vxvm version 5.1 installed on a X6270 M2 sun server , The customer have HW raid "RAID 1" configured .. 4 disks configured giving 2 disks to the O.S. these 2 disks are encapsulated using vxvm for rootdisk and root mirror ! After shutting down the server to replace one of the failed disks "HDD2/part of root mirror" , server boot process reported "unexpected free inode. please invoke fsck" .. I booted in failsafe mode , reverted vfstab to vfstab.prevm ... removed rootdev and vxvi lines in /etc/system , created install-db , removed root-done , replaced /a/boot/solaris/bootenv.rc with /a/boot/solaris/bootenv.rc.pre_vxvm .. updated boot archive , reboot into failsafe , did fsck for root disk .. the system hangs while booting with "WARNING: cannot find /etc/svc/volatile" .. if i revert all changes back to vmvm encapsulation it gives the same error .. booting from root mirror gives same error + fsck errors . Please advise ,
hytham_fekry
10 years ago Place Storage Foundation
1.4KViews
0likes
1Comment
Replacing/Restoring Failed Drive
Yestarday, I had two drives in my storage san fail. The san monitor reports that all the physical drives are fine. bash-2.03# vxdisk list | grep AMS AMS_WMS0_0 auto:cdsdisk remote996006 remote9960 online AMS_WMS0_1 auto:cdsdisk remote996004 remote9960 online AMS_WMS0_2 auto:cdsdisk remote996013 remote9960 online AMS_WMS01_0 auto - - error AMS_WMS01_1 auto - - error AMS_WMS01_2 auto:cdsdisk remote996012 remote9960 online AMS_WMS012_0 auto:cdsdisk remote996008 remote9960 online AMS_WMS012_1 auto:cdsdisk remote996002 remote9960 online AMS_WMS012_2 auto:cdsdisk remote996011 remote9960 online AMS_WMS0123_0 auto:cdsdisk remote996007 remote9960 online AMS_WMS0123_1 auto:cdsdisk remote996001 remote9960 online AMS_WMS0123_2 auto:cdsdisk remote996010 remote9960 online - - remote996003 remote9960 failed was:AMS_WMS01_1 - - remote996005 remote9960 failed was:AMS_WMS01_0 The devices on lines 5/6 are new. A result of me attempting to repair the two failed drives at the bottom. So far i've unmounted the volumes associated with the drives, but there are 11 more mounts attached to the Disk Group. Being new, I'm not sure what processes and systems are using those volumes and am reluctant to unmount them at the moment. I followed several guides trying to determine the cause of the problem and/or to restore the two disks. Here's some of the results of my effort so far. > vxprint -htg remote9960 DG NAME NCONFIG NLOG MINORS GROUP-ID ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK CO NAME CACHEVOL KSTATE STATE VT NAME NVOLUME KSTATE STATE V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE DC NAME PARENTVOL LOGVOL SP NAME SNAPVOL DCO dg remote9960 default default 126000 1032204684.1590.aeneas dm remote996001 AMS_WMS0123_1 auto 2048 1677616896 - dm remote996002 AMS_WMS012_1 auto 2048 1677616896 - dm remote996003 - - - - NODEVICE dm remote996004 AMS_WMS0_1 auto 2048 1677616896 - dm remote996005 - - - - NODEVICE dm remote996006 AMS_WMS0_0 auto 2048 1677616896 - dm remote996007 AMS_WMS0123_0 auto 2048 1258212096 - dm remote996008 AMS_WMS012_0 auto 2048 1258212096 - dm remote996010 AMS_WMS0123_2 auto 2048 2094367888 - dm remote996011 AMS_WMS012_2 auto 2048 2094367888 - dm remote996012 AMS_WMS01_2 auto 2048 2094367888 - dm remote996013 AMS_WMS0_2 auto 2048 2094367888 - v rem-01 - DISABLED ACTIVE 1921724416 SELECT - fsgen pl rem-01-02 rem-01 DISABLED NODEVICE 1921843200 STRIPE 4/64 RW sd remote996004-01 rem-01-02 remote996004 36096 480460800 0/0 AMS_WMS0_1 ENA sd remote996003-01 rem-01-02 remote996003 36096 480460800 1/0 - NDEV sd remote996002-01 rem-01-02 remote996002 36096 480460800 2/0 AMS_WMS012_1 ENA sd remote996001-01 rem-01-02 remote996001 36096 480460800 3/0 AMS_WMS0123_1 ENA v rem-02 - DISABLED ACTIVE 1921724416 SELECT - fsgen pl rem-02-02 rem-02 DISABLED NODEVICE 1921843200 STRIPE 4/64 RW sd remote996004-02 rem-02-02 remote996004 480496896 480460800 0/0 AMS_WMS0_1 ENA sd remote996003-02 rem-02-02 remote996003 480496896 480460800 1/0 - NDEV sd remote996002-02 rem-02-02 remote996002 480496896 480460800 2/0 AMS_WMS012_1 ENA sd remote996001-02 rem-02-02 remote996001 480496896 480460800 3/0 AMS_WMS0123_1 ENA v rem-03 - DISABLED ACTIVE 1000341504 SELECT - fsgen pl rem-03-01 rem-03 DISABLED NODEVICE 1000396800 STRIPE 2/64 RW sd remote996006-02 rem-03-01 remote996006 106826496 419443200 0/0 AMS_WMS0_0 ENA sd remote996008-03 rem-03-01 remote996008 1176381696 80755200 0/419443200 AMS_WMS012_0 ENA sd remote996005-02 rem-03-01 remote996005 106826496 419443200 1/0 - NDEV sd remote996007-03 rem-03-01 remote996007 1176381696 80755200 1/419443200 AMS_WMS0123_0 ENA v rem-04 - DISABLED ACTIVE 1921724416 SELECT - fsgen pl rem-04-02 rem-04 DISABLED NODEVICE 1921843200 STRIPE 4/64 RW sd remote996004-03 rem-04-02 remote996004 960957696 480460800 0/0 AMS_WMS0_1 ENA sd remote996003-03 rem-04-02 remote996003 960957696 480460800 1/0 - NDEV sd remote996002-03 rem-04-02 remote996002 960957696 480460800 2/0 AMS_WMS012_1 ENA sd remote996001-03 rem-04-02 remote996001 960957696 480460800 3/0 AMS_WMS0123_1 ENA v rem-08 - ENABLED ACTIVE 2097152000 SELECT rem-08-01 fsgen pl rem-08-01 rem-08 ENABLED ACTIVE 2097177600 STRIPE 2/64 RW sd remote996008-01 rem-08-01 remote996008 36096 1048588800 0/0 AMS_WMS012_0 ENA sd remote996007-01 rem-08-01 remote996007 36096 1048588800 1/0 AMS_WMS0123_0 ENA v rem-30 - DISABLED ACTIVE 1887436800 SELECT - fsgen pl rem-30-01 rem-30 DISABLED NODEVICE 1887436800 STRIPE 2/64 RW sd remote996006-03 rem-30-01 remote996006 526269696 943718400 0/0 AMS_WMS0_0 ENA sd remote996005-03 rem-30-01 remote996005 526269696 943718400 1/0 - NDEV v rem-40 - ENABLED ACTIVE 2097152000 SELECT rem-40-01 fsgen pl rem-40-01 rem-40 ENABLED ACTIVE 2097254400 STRIPE 4/64 RW sd remote996013-01 rem-40-01 remote996013 36096 524313600 0/0 AMS_WMS0_2 ENA sd remote996012-01 rem-40-01 remote996012 36096 524313600 1/0 AMS_WMS01_2 ENA sd remote996011-01 rem-40-01 remote996011 36096 524313600 2/0 AMS_WMS012_2 ENA sd remote996010-01 rem-40-01 remote996010 36096 524313600 3/0 AMS_WMS0123_2 ENA v rem-41 - ENABLED ACTIVE 2097152000 SELECT rem-41-01 fsgen pl rem-41-01 rem-41 ENABLED ACTIVE 2097254400 STRIPE 4/64 RW sd remote996013-02 rem-41-01 remote996013 524349696 524313600 0/0 AMS_WMS0_2 ENA sd remote996012-02 rem-41-01 remote996012 524349696 524313600 1/0 AMS_WMS01_2 ENA sd remote996011-02 rem-41-01 remote996011 524349696 524313600 2/0 AMS_WMS012_2 ENA sd remote996010-02 rem-41-01 remote996010 524349696 524313600 3/0 AMS_WMS0123_2 ENA v rem-42 - ENABLED ACTIVE 2097152000 SELECT rem-42-01 fsgen pl rem-42-01 rem-42 ENABLED ACTIVE 2097254400 STRIPE 4/64 RW sd remote996013-03 rem-42-01 remote996013 1048663296 524313600 0/0 AMS_WMS0_2 ENA sd remote996012-03 rem-42-01 remote996012 1048663296 524313600 1/0 AMS_WMS01_2 ENA sd remote996011-03 rem-42-01 remote996011 1048663296 524313600 2/0 AMS_WMS012_2 ENA sd remote996010-03 rem-42-01 remote996010 1048663296 524313600 3/0 AMS_WMS0123_2 ENA v rem-43 - ENABLED ACTIVE 2085427200 SELECT rem-43-01 fsgen pl rem-43-01 rem-43 ENABLED ACTIVE 2085427200 STRIPE 4/64 RW sd remote996013-04 rem-43-01 remote996013 1572976896 521356800 0/0 AMS_WMS0_2 ENA sd remote996012-04 rem-43-01 remote996012 1572976896 521356800 1/0 AMS_WMS01_2 ENA sd remote996011-04 rem-43-01 remote996011 1572976896 521356800 2/0 AMS_WMS012_2 ENA sd remote996010-04 rem-43-01 remote996010 1572976896 521356800 3/0 AMS_WMS0123_2 ENA v rimg02 - DISABLED ACTIVE 944793600 SELECT - fsgen pl rimg02-01 rimg02 DISABLED NODEVICE 944793600 STRIPE 4/64 RW sd remote996004-04 rimg02-01 remote996004 1441418496 236198400 0/0 AMS_WMS0_1 ENA sd remote996003-04 rimg02-01 remote996003 1441418496 236198400 1/0 - NDEV sd remote996002-04 rimg02-01 remote996002 1441418496 236198400 2/0 AMS_WMS012_1 ENA sd remote996001-04 rimg02-01 remote996001 1441418496 236198400 3/0 AMS_WMS0123_1 ENA > dxadm Select an operation to perform: 5 Select a removed or failed disk [<disk>,list,q,?] remote996003 VxVM ERROR V-5-2-1985 No devices are available as replacements for remote996003. Select a removed or failed disk [<disk>,list,q,?] remote996005 VxVM ERROR V-5-2-1985 No devices are available as replacements for remote996005. I attemped to reattached the failed disk: bash-2.03# /etc/vx/bin/vxreattach -c remote996003 VxVM vxdisk ERROR V-5-1-537 Device remote996003: Not in the configuration VxVM vxdisk ERROR V-5-1-558 Disk remote996003: Disk not in the configuration bash-2.03# /etc/vx/bin/vxreattach -c remote996005 VxVM vxdisk ERROR V-5-1-537 Device remote996005: Not in the configuration VxVM vxdisk ERROR V-5-1-558 Disk remote996005: Disk not in the configuration bash-2.03# vxdisk clearimport AMS_WMS01_1 VxVM vxdisk ERROR V-5-1-531 Device AMS_WMS01_1: clearimport failed: Disk device is offline I think this part is where I created the two duplicate devices. From this point, I'm going to have to step back and seek out guidance before I cause further problems.
Solved
Neobane
10 years ago Place Storage Foundation
2.8KViews
0likes
6Comments
Veritas Storage Foundation - Volume Disabled After 'rmdisk'
Dear All, I added a LUN to a specific volume and realised that I added it to the wrong volume. To remove the LUN the following command was run : "vxdg -g dg rmdisk vsp-xx-xx" I was then prompted to run the " -k" option to remove the disk. However after re-running the command with the " -k" option : "vxdg -g dg -k rmdisk vsp-xx-xx" ... the volume went into a disabled state. Fortunately no data was lost once the "vxmend" was completed on the volume. I would just like to know if this was to be expected when running the above with the " -k" option ? Regards
Solved
Shaun_Glass
10 years ago Place Storage Foundation
2KViews
0likes
4Comments
Trouble converting FileSystem metadata with fscdsconv in Linux
Hello everyone, I'm in the process of migrating a Solaris 5.10 server to Linux Red Hat 6.4 At this point, I'm trying to convert the byte order of some volumesthat come from Solaris in my Linux server using the following command: /opt/VRTS/bin/fscdsconv -y -e -f /tmp/vxConv/dbtemp01.tmp -t os_name=Linux,arch=x86 /dev/vx/rdsk/dgtemp/dbtemp01 Note: Because of the text formating, the above command could span two lines, but it I'mexecuting itin just one And I get the following errors: UX:vxfs fscdsconv: ERROR: V-3-20012: not a valid vxfs file system UX:vxfs fscdsconv: ERROR: V-3-24426: fscdsconv: Failed to migrate. Searching for a solution of these errors in the forums, I've found this post, where the user mikeboundsgives some steps to migrate Solaris to Linux. I've found that I've replicated these steps but I get stuck on the fscdsconv because the beforementioned errors. Does anyone know what could be happening here or have any sugestion to share? Software Versions: RHEL 6.4 x86_64 Veritas Storage Foundation Enterprise 6.2.0.100 on Linux Solaris 5.10 Veritas 5.0 on Solaris Disk layout v7 vxfs filesystem format Thank you very much in advance for any help/ideas to solve this Best regards Raul
Solved
RaulGomez
10 years ago Place Storage Foundation
2.2KViews
1like
7Comments
Issue while Extending file system in vxvm
Hi, I have a case as below, Please extend below file systems from 30G to 50G on server island. /dev/vx/dsk/VRP_PRD_ora_data_dg/sapdata2 30G 15G 14G 52% /oracle/VRP/sapdata2 /dev/vx/dsk/VRP_PRD_ora_data_dg/sapdata4 30G 15G 14G 51% /oracle/VRP/sapdata4 /dev/vx/dsk/VRP_PRD_ora_data_dg/sapdata1 30G 14G 15G 49% /oracle/VRP/sapdata1 /dev/vx/dsk/VRP_PRD_ora_data_dg/sapdata3 30G 27G 2.7G 91% /oracle/VRP/sapdata3 root@myers# vxdisk -o alldgs -e list DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR emcpower22s2 auto VRP_PRD_sapcent_dg01 VRP_PRD_sapcent_dg online emcpower22c - emcpower23s2 auto emcpower23s2 VRP_PRD_ora_data_dg online emcpower23c - emcpower24s2 auto emcpower24s2 VRP_PRD_ora_data_dg online emcpower24c - emcpower25s2 auto emcpower25s2 VRP_PRD_ora_data_dg online emcpower25c - emcpower26s2 auto emcpower26s2 VRP_PRD_ora_data_dg online emcpower26c - emcpower27s2 auto emcpower27s2 VRP_PRD_ora_bin_dg online emcpower27c - emcpower28s2 auto VRP_PRD_ora_arch_dg01 VRP_PRD_ora_arch_dg online emcpower28c - ====================================================================================== These are the 4 new luns of 30 GB assigned by Storage. 57. emcpower29e <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@29 58. emcpower30a <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@30 59. emcpower33a <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@33 60. emcpower34b <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@34 ==================================================================== When I tried to label them they are giving errors as, 57. emcpower29e <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@29 58. emcpower30a <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@30 59. emcpower33a <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@33 60. emcpower34b <EMC-SYMMETRIX-5874 cyl 29158 alt 2 hd 15 sec 128> /pseudo/emcp@34 Specify disk (enter its number): 57 selecting emcpower29e [disk formatted] Disk not labeled. Label it now? y Warning: error writing VTOC. Warning: no backup labels Write label failed FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk repair - repair a defective sector label - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> - execute <cmd>, then return =========================================================================== There are 4 lunsemcpower29e,emcpower30a,emcpower33a,emcpower34b which is require to initilize it and add them to theVRP_PRD_ora_data_dg diskgroup to increase filesystem to 20 GB more. Shall I have to proceed with the disk initilization in vxvm without labeling it or Please help me to proceed step by step activities required for this. Thanks,
Solved
allaboutunix
10 years ago Place Storage Foundation
3.7KViews
2likes
24Comments