Defining a "default RPMs" installation of the RHEL OS
(Doc ID 376183.1)
Last updated on JANUARY 30, 2022
Applies to:
Oracle Database Exadata Express Cloud Service - Version N/A and laterGen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Linux x86-64
Red Hat Enterprise Linux Workstation
Linux x86
Linux on IBM Z
Red Hat Advanced Server
Red Hat Enterprise Linux Advanced Server Itanium
Red Hat Enterprise Linux Advanced Server x86-64 (AMD Opteron Architecture)
Linux Itanium
Goal
This document will explain the RDBMS installation symptoms that might be observed when Linux OS RPMs that are expected to be present from the initial OS installation are in-fact absent.
After installing default RPM' s the document begins with several example RDBMS installation symptoms that have been observed, each of which indicate that a "default installation" of RHEL is missing. This document then continues with a strategy to verify the exact RPM groupings and the individual RPMs that were selected at OS install time. Finally, the document concludes with example RPM command outputs for a "default RPMs" installation.
Although the details that are used to explain the concept of a "default-RPMs" installation of RHEL AS/ES in this document are from a 64-bit RHEL 4 U1 installation, the principles of this note apply to all certified Linux distributions. The equivalent NOTE for the SLES OS is:
The equivalent NOTE for the Oracle Enterprise Linux (OEL) is:
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |