Perform a shown command on the VG device files.
Perform a syncvg to validate VG integrity.
Perform a redfinevg to correct the VGDA state.
Perform a synchlvodm to correct the LV ownership.
第1题:
The 'lsvg -o' command is run with an output of only rootvg, but the server has another volume group named datavg, which is notdisplayed. What is the likely cause?()
第2题:
While attempting to expand a file system, an administrator receives an error message indicating that the filesystem is not recognized. Running the 'lsfs' command fails to display any output, but the 'df' command is working and displays normal filesystems. What is the likely cause of the problem?()
第3题:
Which presents the heirarchical relationship between LVM entities?()
第4题:
A system administrator would like to rename volume group oldvg to newvg. This volume group resides on hdisk1. What is the appropriate procedure to perform this?()
第5题:
You are using an Automatic Storage Management (ASM) instance to manage the files of your production database. You have two disk groups, DG1 and DG2, with one device each. In the parameter file of the production database, the following parameters have been specified: DB_CREATE_ONLINE_LOG_DEST_1 = ’+dg1’ DB_CREATE_ONLINE_LOG_DEST_2 = ’+dg2’ What would be the impact of this setting?()
第6题:
Using varyonvg appvg.
Using varyonvg -f appvg.
Under the control of resource group management.
Automatically at boot time using chvg -ay appvg.
第7题:
There is not an available disk to allocate to the snapshot volume group
One of the physical volumes associated with rootvg has a status of missing
Rootvg is running in enhanced concurrent mode
A snapshot volume group cannot be created for the rootvg
第8题:
PowerHA only manages VxVM volume groups by using customized pre- and post-event scripts
PowerHA is tightly coupled with AIX LVM. All volumes groups must be converted to AIX LVM
PowerHA supports VxVM as an OEM volume group type. PowerHA manages the volume group with a limited suite of management tasks
PowerHA supports VxVM as an OEM volume group type. All cluster operations applicable with AIX LVM are also applicable with VxVM
第9题:
The /etc/filesystems file is missing.
The /dev/hd8 logical volume is corrupt.
The hosting volume group is not varied on.
The /var and /tmp filesystems may be full.
第10题:
datavg is in an offline state.
‘lsvg -o’ only displays the root volume group.
‘lsvg -o’ only displays the fist volume group.
datavg has no filesystems and therefore, is inactive.
第11题:
Remove the physical volume from the system.
Remove the physical volume from the volume group.
Remove the physical partitions from the volume group.
Remove the logical volume copies from the failing drive.
第12题:
Change the quorum required to false.
Change the Volume Group auto vary on to yes, and then vary off the Volume Group.
Change the auto vary on value of the Volume Group to no, and then vary off the volume group.
Set the Volume Group major number to the same value that the Volume Group had on the system on which it was created.
第13题:
After an HACMP migration, which included a large number of shared disks,cluster testing is performed. During testing, it becomes apparent that Fast Disk Takeover is not working properly. Which of the following is the most likely cause of the problem?()
第14题:
Using splitvg to create a snapshot volume group of rootvg results in an error. What is the most likely cause of the error()
第15题:
Following a successful migration,it is highly recommended that concurrent Volume Groups be Converted to enhanced concurrent capable Volume Groups. In order to follow this recommendation,what step must be completed first?()
第16题:
A Volume Group appvg has been converted to enhanced concurrent volume mode using C- SPOC. How should the Volume Group be brought online?()
第17题:
lspv datavg
lslv -a datavg
lsfs -v datavg
lsvg -l datavg
第18题:
The shared logical volumes and filesystems did not have database permissions.
There was a test instance running on the standby system that must be shutdown.
The tablespaces had an indicator indicating that the database had not shutdown properly.
The startup script for the highly available instance did not first perform cleanup operations.
第19题:
The shared volume groups have not been converted to Big VGs.
The ’t factor needs to be set on the volume group using chvg -t 2 vgname.
The shared volume groups have not been converted to enhanced concurrent mode.
The shared volume groups need to be varied on using the passive varyon option on all nodes.
第20题:
reboot the server in maintenance mode;migratevg -y newvg oldvg;reboot the server in normal mode
unmount all filesystems in the volume group;varyoffvg oldvg;migratepv -y oldvg -n newvg varyonvg newvg
unmount all filesystems in the volume group;varyoffvg oldvg;exportvg oldvg;importvg -y newvg hdisk1;mount all
unmount all filesystems in the volume group;varyoffvg oldvg;for each logical volume in the volume group do cplv -v oldvg -y newvg;varyonvg newvg;mount all
第21题:
When a new log group is added, it would have one member in each disk group.
When a new log group is added, it would have two members in each disk group.
When a new tablespace is added, it would have one data file in each disk group.
When a new log file is added, it would have one member spread across the disk groups.
第22题:
The Volume Groups must be changed with chvg -E vgname.
The Volume Groups must be a member of a resource group and must be varied on al nodes of the cluster.
The Volume Groups must be a member of a resource group and must be varied off all nodes of the cluster.
The Volume Grups cannot be changed to enhanced concurrent capable because they must be recreated with mkvg -C vgname.
第23题:
Volume Group > Physical Volume > Logical Volume > Filesystem
Physical Volume > Volume Group > Logical Volume > Filesystem
Volume Group > Physical Volume > Filesystem > Logical Volume
Physical Volume > Volume Group > Filesystem > Logical Volume