Red Hat NETWORK SATELLITE SERVER 3.6, Installation Manual

Page: 14 / 62

10 Chapter 2. Requirements
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 need to consider that size
does affect the time to conduct backups and adds load to other system resources. If the database is
being shared, its hardware and spacing is entirely dependent on what else is using it.
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 will need 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
Additional database requirements include:
•
Security Identifier (SID)
•
Listener Port
•
Username
•
Uniform Extent Size
•
Auto Segment Space Management
•
UTF-8 character set
The disk layout on the database machine is independent of the RHN Satellite Server and entirely up
to the customer.
2.4. Additional Requirements
The following additional requirements must be met before the RHN Satellite Server installation:
•
Full Access
Client systems need full network access to the RHN Satellite Server solution’s services and ports.
•
Firewall Rules