Foglight for Oracle (Cartridge) 5.9.3.20

In addition to these general UNIX® system requirements, each agent user account requires additional privileges depending on the operating system, as specified in the following table.


	NOTE: When monitoring DB2, SYSMON role and privileges for OS user is not required but is recommended to allow the installation to provide more information when discovering DB2 databases.

Linux/UNIX permissions

Table 18. Linux/UNIX Permissions
Permission	Linux®	Solaris®	AIX®	HP-UX
Execute	awk df free getconf head hostname iostat lsnrctl netstat ps sed tail sysstat uname uptime vmstat /proc/	awk db2ptree df head hostname iostat lsnrctl mpstat uptime netstat pagesize ps psrinfo tail uname vmstat /usr/sbin/prtconf	awk df head hostname iostat lsattr lsdev lsnrctl netstat oslevel pagesize ps tail uname uptime vmstat	awk bdf bindprocessor getconf head hostname ioscan iostat lsattr lsdev lsnrctl netstat oslevel pagesize ps sar tail uname uptime vmstat /usr/sbin/
Read	cpuinfo free* getconf sysstat package* /proc /proc/cpuinfo* /proc/net/dev /proc/stat /proc/vmstat on Linux >= 2.6			/var/adm/syslog/syslog.log

VMware permissions

To monitor VMware®, users must have read only access to the virtual center.

Windows permissions

Foglight support monitoring Windows® operating system in one of two ways: WinRM and WMI. The preferred method is WinRM when no WinRM connection WMI connection is used.

WinRM (default) - Based on Kerberos authentication or Basic authentication uses standard HTTP headers. For more information, see http://support.quest.com/technical-documents/foglight-agent-manager/5.9.3/foglight-agent-manager-guide/advanced-system-configuration-and-troubleshooting/configuring-windows-remote-management-winrm.

WMI (fallback) — Permission to access both DCOM and WMI. For more information, see

http://support.quest.com/technical-documents/foglight-agent-manager/5.9.3/foglight-agent-manager-guide/advanced-system-configuration-and-troubleshooting/configuring-windows-management-instrumentation-wmi.