VGID on disk incorrect - can VGID be updated?

[sbrews]

I have a disk that has somehowe gotten itself into a "missing" status.

# lsvg -p datavg
datavg:
PV_NAME           PV STATE          TOTAL PPs   FREE PPs    FREE DISTRIBUTION
hdisk2            active            135         65          27..00..00..11..27
hdisk3            active            135         96          27..00..15..27..27
hdisk4            active            135         72          18..00..00..27..27
hdisk5            active            135         118         27..10..27..27..27
hdisk20           active            543         4           00..00..00..00..04
hdisk14           active            135         94          27..00..13..27..27
hdisk15           active            135         26          00..00..00..00..26
hdisk25           active            135         81          27..00..00..27..27
hdisk16           active            135         0           00..00..00..00..00
hdisk11           missing           543         12          00..00..00..00..12
hdisk19           active            543         542         108..109..108..108..109

I have tried to varyoff and varyon with no luck

# varyoffvg datavg
# varyonvg datavg
PV Status:      hdisk19 000c81bfa3f14e75        PVACTIVE
                hdisk3  000c81bf26d50998        PVACTIVE
                hdisk4  000c81bf26d50e3a        PVACTIVE
                hdisk5  000c81bf26d512ff        PVACTIVE
                hdisk20 000c81bfd9455f04        PVACTIVE
                hdisk14 000fa68fd114db65        PVACTIVE
                hdisk15 000fa68fd1143e7a        PVACTIVE
                hdisk2  000fa68f337c1a18        PVACTIVE
                hdisk25 000c81bf5abfb58a        PVACTIVE
                hdisk16 000fa68fd1131a13        PVACTIVE
                hdisk11 000fa68f3f597c75        LVMRECNMTCH
varyonvg: Volume group datavg is varied on.
root@lanaexpress2:/ # 0516-934 /usr/sbin/syncvg: Unable to synchronize logical volume loglv00.
0516-934 /usr/sbin/syncvg: Unable to synchronize logical volume rcatbinlv.
0516-932 /usr/sbin/syncvg: Unable to synchronize volume group datavg.

I have tried to export and import... and this identfies the issue - vgid is incorrect

# varyoffvg datavg
# exportvg datavg
# importvg -y datavg hdisk3
0516-1791 redefinevg: lvm_rec for PV hdisk11 has VGID 0000000000000000 (000c81bf26f77f6a expected)
PV Status:      hdisk2  000fa68f337c1a18        PVACTIVE
                hdisk3  000c81bf26d50998        PVACTIVE
                hdisk4  000c81bf26d50e3a        PVACTIVE
                hdisk5  000c81bf26d512ff        PVACTIVE
                hdisk20 000c81bfd9455f04        PVACTIVE
                hdisk14 000fa68fd114db65        PVACTIVE
                hdisk15 000fa68fd1143e7a        PVACTIVE
                hdisk25 000c81bf5abfb58a        PVACTIVE
                hdisk16 000fa68fd1131a13        PVACTIVE
                hdisk19 000c81bfa3f14e75        PVACTIVE
                        000fa68f3f597c75        NONAME
varyonvg: Volume group datavg is varied on.
0516-1281 synclvodm: Warning, lv control block of loglv00
        has been over written.
0516-622 synclvodm: Warning, cannot write lv control block data.
0516-622 synclvodm: Warning, cannot write lv control block data.
imfs: 0506-914cannot find log for volume group datavg.
datavg
PV Status:      hdisk2  000fa68f337c1a18        PVACTIVE
                hdisk3  000c81bf26d50998        PVACTIVE
                hdisk4  000c81bf26d50e3a        PVACTIVE
                hdisk5  000c81bf26d512ff        PVACTIVE
                hdisk20 000c81bfd9455f04        PVACTIVE
                hdisk14 000fa68fd114db65        PVACTIVE
                hdisk15 000fa68fd1143e7a        PVACTIVE
                hdisk25 000c81bf5abfb58a        PVACTIVE
                hdisk16 000fa68fd1131a13        PVACTIVE
                hdisk11 000fa68f3f597c75        LVMRECNMTCH
                hdisk19 000c81bfa3f14e75        PVACTIVE
varyonvg: Volume group datavg is varied on.

I can otherwise query the disk with lspv -l hdisk11 and see my logical volumes. Is there a way to update the vgid
so that it knows its part of the vg or should the data on this disk be considered lost and use other recovery
methods?

Server is AIX version 5300-12-05-1140

 

[sbrews]

Update - after trying recreatevg and redefinevg without luck it was decided to clean up the vg and recreate the affected file systems.

However, if anyone does know of a way to recover a corrupted vgid, I would like to know the process.