vxconfigd behaves erratically if there are more than 40GB of physical memory on an AIX system
|Article:AL1063|||||Created: 2010-12-28|||||Updated: 2010-12-28|||||Article URL http://www.symantec.com/docs/AL1063|
The following are some of the reported erratic behaviors.
- Running "vxdctl enable" causes vxconfigd to lose the licenses
- Veritas Volume Manager (VxVM) commands fail because of "Memory allocation failure" error
- vxconfigd dies on the Veritas Volume Replicator (VVR) secondary during synchronization started by "vradmin syncrvg" command
Please note that there can other unpredictable errors reported by vxconfigd.
Please go to the article below for full detail.
Article URL http://www.symantec.com/docs/AL1063