Ignite System Requirements
Client Browser
- Internet Explorer 6.0 or higher
- Firefox 3 or higher
Server running Ignite Software
- The Ignite software can be installed on almost any Windows, Unix or Linux server. It only needs an operating system that can support JDK 1.5 or higher. Repository hardware and configuration must meet minimum requirements as shown below.
# Number of
monitored databases |
Minimum # of CPU |
RAM |
| <20 |
1 |
1 GB |
| 20-50 |
2 |
2 GB |
| 51-200 |
4 |
4 GB |
Ignite Performance Data Warehouse Repository:
- An Oracle or Microsoft SQL Server instance is utilized by Ignite to collect and process data from monitored servers. The data collection server is defined as the Ignite Repository server, and the requirements are listed below.
- Ignite Repository requires either:
- Oracle 8i, 9i, 10g or 11g. (8.1.7 or higher)
- Microsoft SQL Server 2000, 2005 or 2008
- "Express" editions of both Oracle and SQL Server can hold a repository but will likely run out of space due to the 4GB limitations.
- Do not put the repository into an instance that will be monitored. Doing so will affect the performance of that instance.
- Installation requires access to a DBA (Oracle) or Sysadmin (MSSQL) user for the install which will hold the repository.
- Repository hardware and configuration must meet minimum requirements as shown below.
# Number of
monitored databases |
Repository
Minimum # of CPU |
RAM |
| 1 |
1 |
512 MB |
| up to 5 |
2 |
1 GB |
| 5-200 |
4 |
4 GB |
Free Disk Space in Repository Instance: varies with number of monitored database instances and level of activity on each:
| Monitored Database Activity |
Repository Disk Space per Monitored DB |
| Light |
1 GB to 3 GB |
| Medium |
3 GB to 5 GB |
| Heavy |
5 GB to 10 GB |
| Minimum Oracle Parameters |
db_block_buffers (or db_cache_size)
Note that this is a critical parameter. |
>100 Mb per monitored database |
| shared_pool_size |
>50 MB |
| sort_area_size |
>4 MB |
| log_buffer |
>1 MB |
| session_cached_cursors |
>10 |
| Redo Log Size (select min(bytes) from v$log) |
>10 MB |
| Minimum SQL Server Configuration Parameters |
Minimum Server Memory
If monitoring more than 10 instances, increase by 20 MB per additional monitored instance |
1 GB |
Monitored Databases
Oracle Monitored Databases:
- Ignite for Oracle supports monitoring of Oracle 8i, 9i, 10g or 11g (8.1.7 or higher)
SYS user privileges are required for initial setup.
- The server holding the Ignite software must be able to connect to the monitored Oracle server.
SQL Server Monitored Databases:
- Ignite for SQL Server supports monitoring of SQL Server 2000 (SP3 and higher), 2005, and 2008.
- SYSADMIN privileges are required to setup Ignite
- The server holding the Ignite software must be able to connect to the monitored MSSQL server.
Sybase ASE Monitored Databases:
- Ignite for Sybase supports monitoring of ASE 12.5.0.3 and higher.
- SA_ROLE privileges are required to setup Ignite
- The server holding the Ignite software must be able to connect to the monitored Sybase server.
DB2-LUW Monitored Databases:
- Ignite for IBM DB2 UDB supports monitoring of DB2 UDB versions 8.2.2 or higher (or 8.1 FixPack 13).
- SYSADM privileges are required to setup Ignite
- The server holding the Ignite software must be able to connect to the monitored DB2 server.
VMware Monitoring
- Ignite8 Version 8.1 or higher
- VMware ESX 4.X or higher
- VMware vCenter 4.0 or higher (vCenter is optional but recommended)
- Ignite VM installs on any Windows, Linux or UNIX server with Java 1.5 or greater
- One time entry of a Read-only VMware password will be required. Password is not visible to IgniteVM users.
|
