Installation guide
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 proces s.
If you are installing RHN Satellite with Embedded Database, skip to Section 2.4, “Additional
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 installations in conjunction with Oracle Database 10 g Release 2 Standard and Enterprise
Edition or Oracle 11g. The Stand-Alone Database must not run on the same server as the RHN Satellite.
Note
Migration from an embedded to an external database is not currently supported.
A single 12 GB tablespace is recommended for most installations, although many customers will find it
possible to function with a smaller tablespace. Have an experienced Oracle database administrator
(DBA) as sess your sizing requirements. Use the following formula to determine the required size of your
database:
250 KiB per client s ystem
500 KiB per channel, plus 230 KiB per package in the channel (so a channel with 500 0 packages
would require 1.1 Gib)
For instance, an RHN Satellite containing four channels and serving 10 ,000 systems would require 2.5
GiB for its clients and 11 GiB 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 that 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 s hould be generous in your database sizing estimates, you must consider that size affects
the time to conduct backups and adds load to other system res ources. If the database is s hared, 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 ins tallation.
The precise access levels required by the Oracle user are as follows:
ALT ER 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
UTF-8 character set
Two additional suggested recommendation for user's default tables pace include:
Uniform Extent Size
Auto Segment Space Management
Note
Ensure that the NLS/charset setting is set to "UTF8"' when using an external database, not
'AL32UTF8' or other chars ets. Using other charsets may lead to problems later.
The disk layout on the database machine is independent of the RHN Satellite and entirely up to the
customer.
2.4. Additional Requirements
The following additional requirements must be met before the RHN Satellite ins tallation:
Full Access
Client s ystems need full network access to the RHN Satellite solution's services and ports .
Firewall Rules
RHN strongly recommends firewalling the RHN Satellite solution from the Internet. However, various
TCP ports must be opened on the Satellite, depending on your implementation of RHN Satellite.
Some UDP ports will also be required for DHCP and T FTP services to function correctly.
Red Hat Network Satellite 5.4 Installation Guide
10