1 Database Installation Pre-Installation Tasks

The installation of the Configuration Change Console and its components must be executed in the order documented below:

Oracle database installation and configuration
Configuration Change Console Server installation and configuration
Configuration Change Console Agent installation

Before installing the database, read through the following preparatory tasks.

Determining Database Size

This section provides a guideline for database sizing. It does not necessarily reflect every environment.

The size of the database correlates with the number of expected changes, rather than to the number of devices in the infrastructure. The first graph shows some change counts that might exist in some environments based on the expected change rates. A low change rate would mean that not very many changes happen on the rules sets that are configured. These can be used as a guideline when estimating how many changes you might expect to collect over a month.

Description of the illustration graph1.jpg

The next graph shows the estimated tablespace size versus the number of changes in the environment. The number of changes shown in the graph reflects the number of changes the application can retain in its repository. If you have your data purging set to three months, then you would find the number of changes you expect in a three month period. The previous graph showed some example total change counts for one month.

If you were storing events for three months, you would need to multiply the estimated change counts in the previous graph by three.

Description of the illustration graph2.jpg

Note that if the tablespace is not sufficient in size, there may be data loss should the database become full. Once the database reaches its capacity you will receive an error message in your server log. You will be able to see this under the Administration > Server Reports > Server and Database Logs screen. Any new data will not be saved and users will not be able to log in to the product. To prevent data loss and user lockout, it is best to over-estimate the space needed for your database or leave a small buffer of disk space for auto-extension of the tablespace.

This graph does not include other tablespaces such as TEMP and UNDO. You must allocate an appropriate amount of disk space for these tablespaces based on your own best practices.

System Requirements

The specific operating system requirements for the database server are contingent on the required database size. All operating systems on which an Oracle database can operate are supported.

The following table lists some suggestions for various sizes of environments. These can change depending on many factors in a specific customer environment, but can be used as a rough guideline to follow.

Table 1-1 Recommended Size for Environments

Deployment Size Disk Space	Host	CPU/Host	Physical Memory	Minimums Recommended
25 Agents (typical rate change)	1	1 (3Ghz)	2 GB	65 GB
250 Agents (typical rate change)	1	2 (3Ghz)	4 GB	150 GB
1000 Agents (typical rate change)	1	4 (3Ghz)	4 GB	550 GB
10,000 Agents (typical rate change)	1	8 (3Ghz)	8 GB	2.3 TB

Deployment sizes are based on the sizing section in the documentation above. Total Recommended Disk Space includes the three Configuration Change Console tablespaces as well as Database software, Temp, and Undo tablespace size. Minimum recommended disk space is based on saving raw events for only 3 months and utilizing the majority of Configuration Change Console features.