D
dbeavon
Guest
The poor memory allocation by OEE was addressed in an 11.7 service pack. It shouldn't blow up anymore when usertabelstat or userindexstat or the other two are set to high values. ... and if that doesn't work, we can now use the new OE 11.7 parameters to disable "per-user" usage stats without losing them altogether for the system as a whole. As soon as I saw those "per-user" usage stat parameters, it felt like a load was lifted. (I'm not sure why the integer counters - tracked by table and active user - were so challenging to maintain and resource-intensive to query.) It would be nice to be able to find these OEE issues in the KB. I get the feeling that this OEE/OEM stuff is not widely used, or at least not on HP-UX. Maybe it was built for Windows/Linux the software QA was only done on that side of things. The HP-UX guys seem to like their CHUI tools - like promon or protop or whatever - and maybe they don't even attempt to use new-fangled graphical management tools like OEE/OEM. ;-) The usage stats are the primary reason that OEE U/I becomes sluggish. Its worse than a simple usability issue because the gathering of the stats will actually swamp admin server (java) on the back-end at 200% for over ten minutes, causing a bunch of pain for the system as a whole. Here is a suggestion... Why not put the usage statistics in a subsequent link that you would click if you wanted it? Then the information could be pulled in on-demand, and not whenever we need to see basic details about a database connection (ie. login time, i.p. address, active transactions, and so on).
Continue reading...
Continue reading...