If more than one Oracle instance is monitored on the same host, mutiple VMSTAT and IOSTAT commands are created causing a high CPU utilisation.
WORKAROUND #1
Disable the OS collections for all of the instances except for one.
WORKAROUND #2
Disable the "File System IO" collection to stop the IOSTAT command.
WORKAROUND #3
The VMSTAT command is run by a collection that combines OS and JDBC collection information so this is slightly more problematic to disable.
WORKAROUND #4
Revoke the permission for the OS user to execute the IOSTAT/VMSTAT commands.
Doing this would cause the Agent logs to get errors printed into them; however, it would also stop these commands from executing without disabling the entire OS collection.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center