Database Requirements - Red Hat NETWORK SATELLITE 5.3.0 Installation Manual

Hide thumbs Also See for NETWORK SATELLITE 5.3.0:
Table of Contents

Advertisement

Chapter 2. Requirements
• The package repository may be any large storage device easily and securely accessed by the
other components. The space requirements depend on the number of packages that will be stored.
Default Red Hat channels contain approximately 3 GB of packages each, and that size grows with
each synchronization; customers must also account for the space requirements of packages in their
own private channels. Whatever storage solution the customer chooses, its mount point may be
defined during the installation process.
If you are installing RHN Satellite with Embedded Database, skip to
Requirements".

2.3. Database Requirements

This section applies only to RHN Satellite with Stand-Alone Database as the requirements for the
Embedded Database are included in the Satellite machine's hardware requirements. Red Hat supports
RHN Satellite 5.2.0 installations in conjunction with Oracle Database 10g Release 2, Standard or
Enterprise Edition. The Stand-Alone Database must not run on the same server as the RHN Satellite.
A single 6 GB tablespace is recommended as more than sufficient for most installations. It is
possible for many customers to function with a smaller tablespace. An experienced Oracle database
administrator (DBA) will be necessary to assess sizing issues. The following formula should be used to
determine the required size of your database:
• 192 KB per client system
• 64 MB per channel
For instance, an RHN Satellite containing 10 channels serving 10,000 systems would require 1.92 GB
for its clients and 640 MB for its channels. If custom channels are to be established for testing and
staging of packages, they must be included in this formula.
Keep in mind, the database storage needs may grow rapidly, depending upon the variance of the
following factors:
• The number of public Red Hat packages imported (typical: 5000)
• The number of private packages to be managed (typical: 500)
• The number of systems to be managed (typical: 1000)
• The number of packages installed on the average system (typical: 500)
Although you should be generous in your database sizing estimates, you must consider that size
affects the time to conduct backups and adds load to other system resources. If the database is
shared, its hardware and spacing are entirely dependent on what else is using it.
Additionally, block sizes must be a minimum of 8 KB for RHN Satellite to install properly.
The Oracle database should have a user assigned to RHN Satellite with full DDL and DML access to
that user's default tablespace. The user needs standard connection information for the database at the
time of installation.
The precise access levels required by the Oracle user are as follows:
• ALTER SESSION
• CREATE SEQUENCE
10
Section 2.4, "Additional

Advertisement

Table of Contents
loading

Table of Contents