LVM commands throwing device configuration database query failed for vg (varyonvg fails with error 0516-1888 / mkvg error libodm: cannot open the object class collection file)
For example,
# mkvg -y datavg hdisk17 hdisk18
0519-100 libodm: Cannot open the object class collection file. Check path name and permissions. 0516-307 mkvg: Unable to access Device Configuration Database.
#extendvg productsvg hdisk10
0516-306 extendvg: Unable to find volume group productsvg in the Device Configuration Database. extendvg: LVM system call returned with error code (-271). 0516-792 extendvg: Unable to extend volume group the same.
#varyonvg productsvg
0516-1888 varyonvg: Device Configuration Database query failed.
#importvg -y prodvg hdisk2
0516-1888 varyonvg: Device Configuration Database query failed.
0516-780 importvg: Unable to import volume group from hdisk2.
If there are no disk/adapter/path errors or disk reservation conflict errors and VGDA metadata is intact on all the disks of the VG (in case of extendvg / varyonvg / importvg) and still seeing any of the mentioned errors, then you can proceed further.
First, try "synclvodm -Pv vgname". If it doesn't help, proceed with the further steps.
The issue could happen if you have placed a system-wide LDR_CNTRL maxdata entry in your "/etc/environment". This is a bad practice as it would apply to all 32-bit applications on the system. Set it to only for the application that needs it, for example in its startup script.
If the memory allocated to a process is not sufficient for the ongoing process, then the programs on AIX can abort.
On AIX systems (only for 32-bit processes), 256 MB are allocated to each process by default. Memory limit can be increased to a maximum of 2 GB with the environment variable LDR_CNTRL.
It is advised with DSA value in export.
#export LDR_CNTRL=MAXDATA=0x80000000@DSA
Value 8 stands for 8x256MB (max. value) => 2 GB
Reattempt to varyonvg the VG or mkvg.
Note: This technote is intended only for 32-bit applications. It does not apply to 64-bit applications and using these commands in a 64-bit environment can limit memory rather than increase it.
| SUPPORT |
|
If you require more assistance, use the following step-by-step instructions to contact IBM to open a case for software with an active and valid support contract.
1. Document (or collect screen captures of) all symptoms, errors, and messages related to your issue.
2. Capture any logs or data relevant to the situation.
3. Contact IBM to open a case:
-For electronic support, see the IBM Support Community:
https://www.ibm.com/mysupport
-If you require telephone support, see the web page:
https://www.ibm.com/planetwide/
4. Provide a clear, concise description of the issue.
- For more information, see: Working with IBM AIX Support: Describing the problem.
5. If the system is accessible, collect a system snap, and upload all of the details and data for your case.
- For more information, see: Working with IBM AIX Support: Collecting snap data
|
[{"Type":"MASTER","Line of Business":{"code":"LOB08","label":"Cognitive Systems"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG10","label":"AIX"},"ARM Category":[{"code":"a8m0z000000cvyiAAA","label":"LVM"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"}],"Version":"All Versions"}]