Using Monitoring Tools

Oracle strongly recommends using monitoring tools to collect performance data as part of the diagnostic process. Monitoring the Oracle Hyperion Financial Management application server, web servers, database server(s) and network layers provide useful performance data.

On a Linux environment, tools such as OS Watcher Black Box can be used to monitor the operating system and the Financial Management processes.

On a Windows environment, a tool such as Microsoft Performance Monitoring can be used to monitor the Financial Management application process performance. Steps for configuring Performance Monitor to gather the counters specific for Financial Management applications can be found here:

Configuring Performance Monitor

Performance counters to monitor include:

Subsystem	Counter	Guidance
Memory	Memory: Free System Page Table Entries	Warning when Free System Page Table Entries is less than 8,000. Critical when Free System Page Table Entries is less than 5,000.
Memory	Memory: Available Mbytes	Should be no lower than 20% to 25% of installed physical memory. In these cases, carefully monitor Paging activity.
Memory	Memory: Page Reads/sec	This counter should be below 1,000 at all times.
Processor	Processor: % Processor Time: _Total	Total processor utilization should be lower than about 70% to 80%.
Processor	Processor: % Processor Time: (N)	Each processor instance should be lower than about 70% to 80% utilization.
Disk	Physical Disk: Avg. Disk sec/Transfer	Must be lower than about 25 ms. General rule: When Avg. Disk Seconds/Transfer (the disk latency counter) is significantly greater than 25 ms, the disk subsystem is unhealthy and is a bottleneck. Please note that this counter does not tell you how to fix the problem; it only indicates there is a problem.
Disk	PhysicalDisk: Average Disk Queue Length	The average should be less than the number of spindles of the disk. If a SAN is being used, ignore this counter and concentrate on the latency counters: PhysicalDisk\Average Disk sec/Read and PhysicalDisk\Average Disk sec/Write.
Disk	PhysicalDisk: Average Disk sec/Read	The average value should be below 20 ms. Spikes (maximum values) should not be higher than 50 ms.
Disk	PhysicalDisk: Average Disk sec/Write	The average value should be below 20 ms. Spikes (maximum values) should not be higher than 50 ms.
Network	Network Interface: Bytes Total/sec	For a 100-Mbps network interface card (NIC), it should be below 6–7 MB/sec. For a 1000-Mbps NIC, it should be below 60–70 MB/sec.
Network	Network Interface: Packets Outbound Errors	It should be zero (0) at all times.

Process	Counters / Guidance
Oracle Hyperion Financial Management: Instance: 1 JHsxServer 2. XFMDataSource	Process: % Processor Time – Process processor utilization should be lower than 90%. Process: Private Bytes - reports bytes allocated exclusively for a specific process; its value tends to rise for a leaking process. Process: Working Set - reports the shared and private bytes allocated to a process; its value tends to rise for a leaking process. Process: Page Faults /sec - reports the total number of faults (hard and soft faults) caused by a process; its value tends to rise for a leaking process. Process: Page File Bytes - reports the size of the paging file; its value tends to rise during a memory leak. Process: Handle Count - reports the number of handles that an application opened for objects creates. Handles are used by programs to identify resources that they must access. The value of this counter tends to rise during a memory leak. Process: Virtual Bytes - The current size, in bytes, of the virtual address space the process is using. The virtual byte of the perfmon process grows at a quick rate and never releases any memory indicating memory leak in application. Process: Virtual Bytes Peak - The maximum size, in bytes, of virtual address space the process has used at any one time. The virtual byte of the perfmon process grows at a quick rate and never releases any memory indicating memory leak in application. Process: Pool Nonpaged Bytes - The size, in bytes, of the Nonpaged pool, an area of system memory (physical memory).

Process

Counters / Guidance

Oracle Hyperion Financial Management:

Instance:

1 JHsxServer

2. XFMDataSource

Process: % Processor Time – Process processor utilization should be lower than 90%.

Process: Private Bytes - reports bytes allocated exclusively for a specific process; its value tends to rise for a leaking process.

Process: Working Set - reports the shared and private bytes allocated to a process; its value tends to rise for a leaking process.

Process: Page Faults /sec - reports the total number of faults (hard and soft faults) caused by a process; its value tends to rise for a leaking process.

Process: Page File Bytes - reports the size of the paging file; its value tends to rise during a memory leak.

Process: Handle Count - reports the number of handles that an application opened for objects creates. Handles are used by programs to identify resources that they must access. The value of this counter tends to rise during a memory leak.

Process: Virtual Bytes - The current size, in bytes, of the virtual address space the process is using. The virtual byte of the perfmon process grows at a quick rate and never releases any memory indicating memory leak in application.

Process: Virtual Bytes Peak - The maximum size, in bytes, of virtual address space the process has used at any one time. The virtual byte of the perfmon process grows at a quick rate and never releases any memory indicating memory leak in application.

Process: Pool Nonpaged Bytes - The size, in bytes, of the Nonpaged pool, an area of system memory (physical memory).