• 192 KB per client system
• 64 MB per channel
For instance, an RHN Satellite Server 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 Server to install properly.
The Oracle database should have a user assigned to RHN Satellite Server 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
• CREATE SYNONYM
• CREATE TABLE
• CREATE VIEW
• CREATE PROCEDURE
• CREATE TRIGGER
• CREATE TYPE
• CREATE SESSION
Chapter 2. Requirements
12
Summary of Contents for NETWORK SATELLITE 5.0.0 -
Page 1: ...Red Hat Network Satellite 5 0 0 Installation Guide 5 0 0 ISBN N A Publication date ...
Page 2: ...Red Hat Network Satellite ...
Page 4: ...Red Hat Network Satellite ...
Page 14: ...8 ...
Page 24: ...18 ...
Page 28: ...22 ...
Page 58: ...52 ...
Page 78: ...72 ...
Page 84: ...78 ...