Defining a "default RPMs" installation of the SLES OS
(Doc ID 386391.1)
Last updated on JANUARY 30, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.4 to 11.2.0.2 [Release 9.2 to 11.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
UnitedLinux (32-bit)
Linux x86
IBM: Linux on System z
IBM S/390 Based Linux (31-bit)
SUSE \ UnitedLinux x86-64
Linux x86-64
z*OBSOLETE: IBM Linux on POWER Systems - alternate
UnitedLinux Itanium
Linux Itanium
Goal
This document will explain the RDBMS installation symptoms that might be observed when SLES OS RPMs that are expected to be present from the initial OS installation are in-fact absent.
After defining a "default RPMs" installation of the SLES OS, the document begins with several example RDBMS installation symptoms that have been observed, each of which indicate that a "default installation" of SLES 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 SLES in this document are from a 64-bit SLES 9 SP2 installation, the principles of this note apply to all certified Linux distributions. The equivalent NOTE for the RHEL OS is <NOTE 376183.1>, "Defining a "default RPMs" installation of the RHEL OS". The equivalent NOTE for the Oracle Enterprise Linux (OEL) is <NOTE 401167.1>, "Defining a "default RPMs" installation of the OEL OS".
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 |