Originally posted by: nagger
This sounds like the running kernel and /unix mismatch.
This happens when you upgrade your AIX (i.e. changed /unix) and forget to reboot so you are running the previous version of /unix in memory.
Have you updated recently or could you take a reboot?
I suspect this because the command will look are the wrong bit of the kernel for numbers and then try a allocate many GB's of memory for the data structure instead of KB and generates the "not enough memory" errors.
I would also expect other performance tools to show weird results.
ta Nigel