[xploit]

# lsvg oradata
0516-010 : Volume group must be varied on; use varyonvg command.

i am running on a VIO server, connected to a SAN storage.

# lsvg
rootvg
oradata
# lsvg oradata
0516-010 : Volume group must be varied on; use varyonvg command.
# lsvg rootvg
VOLUME GROUP:       rootvg                   VG IDENTIFIER:  00c036f400004c0000000126f11348f9
VG STATE:           active                   PP SIZE:        128 megabyte(s)
VG PERMISSION:      read/write               TOTAL PPs:      511 (65408 megabytes)
MAX LVs:            256                      FREE PPs:       416 (53248 megabytes)
LVs:                13                       USED PPs:       95 (12160 megabytes)
OPEN LVs:           11                       QUORUM:         2 (Enabled)
TOTAL PVs:          1                        VG DESCRIPTORS: 2
STALE PVs:          0                        STALE PPs:      0
ACTIVE PVs:         1                        AUTO ON:        yes
MAX PPs per VG:     32512
MAX PPs per PV:     1016                     MAX PVs:        32
LTG size (Dynamic): 256 kilobyte(s)          AUTO SYNC:      no
HOT SPARE:          no                       BB POLICY:      relocatable
# lspv
hdisk0          00c036f4f11339af                    rootvg          active

[aejara]

It's quite clear that this oradata VG is in the ODM, but the disks that once were part of this VG are not accessible right now (it's not usual to see oradata VGs in a VIOS, so I guess that in the past those disks were shown to the partition, the VG was imported or created in the AIX, the disks were removed and the VG was never exported).
Check lsdev -Cc disk to see if you have any other Defined disk in the system, and if you HAVE TO see disks, rescan (using cfgmgr); and if it doesn't work, you will need to redo the zonning to assign these disks... but my best guess is that you DON'T need to see these VG in the VIOS (but maybe just the disks to assign them to a VIOC LPAR).

[xploit]

sorry, the above output is from a client LPAR , that should hold the oracle database.

so any ideas?
can i add physical volume to the already created volume group oradata?

# lsdev -Cc disk
hdisk0 Available Virtual SCSI Disk Drive
hdisk1 Defined Virtual SCSI Disk Drive
hdisk2 Defined Virtual SCSI Disk Drive
hdisk3 Defined Virtual SCSI Disk Drive
hdisk4 Defined Virtual SCSI Disk Drive
hdisk5 Defined Virtual SCSI Disk Drive
hdisk6 Defined Virtual SCSI Disk Drive
hdisk7 Defined Virtual SCSI Disk Drive
hdisk8 Defined Virtual SCSI Disk Drive

[j.gann]

how about finding out what happened to the oravg first? disks deleted by accident or on purpose? just forgotten to export the vg prior to deletion?

this info cannot be found in this forum but from your colleagues.

one of the golden rules of server management: have a changelog

good luck

[aejara]

Easy, you have to work on VIOS side... it seems that those disks are not mapped anymore...
As padmin run:
lsmap -all , and check the mapping to your LPAR.
As root run:
lsdev -Cc disks
errpt
and any usual command to check for your "lost" disks.