Red Hat supports Satellite installations on a Stand-Alone Database using Oracle Database 10g Release 2 Standard and Enterprise Edition or Oracle 11g. Ensure the Stand-Alone Database runs on a different server to the Red Hat Network Satellite.
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) assess your sizing requirements. Use the following formula to determine the required size of your database:
250 KiB per client system
500 KiB per channel, plus 230 KiB per package in the channel (so a channel with 5000 packages would require 1.1 Gib)
For instance, an Red Hat Network 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 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 Red Hat Network Satellite to install properly.
The Oracle database should have a user assigned to Red Hat Network 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:
Additional database requirements include:
Two additional suggested recommendation for user's default tablespace include:
Ensure that the NLS/charset setting is set to "UTF8"' when using an external database, not 'AL32UTF8' or other charsets. Using other charsets may lead to problems later.
The disk layout on the database machine is independent of Satellite and entirely up to the customer.