How to Configure a Local YUM Repository from DVD in Oracle Linux, RHEL, and CentOS (Complete Offline Package Management Guide)

📅 Last Updated: August 2026

This guide has been completely updated for Oracle Linux 6/7/8/9, Red Hat Enterprise Linux (RHEL) 6/7/8/9, and CentOS 7/Stream. It explains how to configure an offline YUM repository using a DVD or ISO image, verify repository configuration, install software packages, troubleshoot common issues, and implement enterprise Linux administration best practices.

Software package management is one of the most important responsibilities of a Linux system administrator. Whether installing security updates, database software, development libraries, or system utilities, Linux relies on package repositories to provide software in a secure and organized manner.

In enterprise environments, servers are often isolated from the Internet for security reasons. Oracle Database servers, production Oracle E-Business Suite environments, financial systems, and government infrastructures commonly operate in secure networks without direct Internet access. In such cases, configuring a local DVD or ISO repository provides a reliable method for installing packages while maintaining strict security controls.

Oracle Linux, Red Hat Enterprise Linux (RHEL), and CentOS use the Yellowdog Updater Modified (YUM) package management system (or DNF in newer releases) to download, install, update, and remove RPM packages. By creating a local repository from installation media, administrators can continue installing software even when no external repository is available.

This guide explains the complete process of configuring a DVD-based YUM repository, understanding repository architecture, testing package installation, troubleshooting repository issues, and following production-ready Linux administration practices.

Quick Solution

Mount the Oracle Linux, RHEL, or CentOS installation DVD (or ISO), create a repository definition file under /etc/yum.repos.d/, configure the baseurl to point to the mounted media, clean the YUM cache, rebuild repository metadata, and verify the repository using yum repolist before installing packages.

What Is YUM?

YUM (Yellowdog Updater Modified) is a package management utility used on RPM-based Linux distributions. It automatically resolves software dependencies, downloads packages from configured repositories, verifies package integrity, and installs or updates software.

Primary YUM functions include:

Installing software packages.
Updating installed software.
Removing packages.
Resolving dependencies automatically.
Managing multiple software repositories.
Verifying package availability.

What Is a YUM Repository?

A YUM repository is a structured location that stores RPM packages and metadata required by the package manager. Repositories may reside on:

Oracle Linux public repositories.
Red Hat Subscription repositories.
CentOS mirrors.
Local HTTP servers.
FTP servers.
NFS shares.
DVD or ISO media.
Local filesystem directories.

Each repository contains package metadata that enables YUM to identify available packages, dependency relationships, versions, and updates.

Online vs Offline Repositories

Feature	Online Repository	DVD Repository
Internet Required	Yes	No
Suitable for Secure Networks	No	Yes
Automatic Updates	Yes	Limited to DVD Content
Installation Speed	Network Dependent	Local Media Speed
Production Oracle Servers	Sometimes Restricted	Commonly Used

Why Configure a DVD Repository?

A DVD repository is commonly used when systems operate in environments where Internet access is unavailable or intentionally restricted.

Typical use cases include:

Oracle Database production servers.
Oracle E-Business Suite environments.
Government networks.
Military environments.
Banking infrastructure.
Highly secured enterprise data centers.
Disaster recovery environments.
Virtual machines without Internet connectivity.

How YUM Repository Architecture Works

Linux Server

      │

      ▼

YUM / DNF

      │

      ▼

Repository Configuration

/etc/yum.repos.d/

      │

      ▼

Mounted DVD or ISO

      │

      ▼

RPM Packages

      │

      ▼

Package Installation

When a package installation request is issued, YUM reads the repository definition, accesses the repository metadata, resolves dependencies, and installs the requested RPM packages from the configured source.

Business Impact

Proper repository configuration directly affects software deployment, patch management, and system maintenance. Incorrect repository settings can delay production deployments, prevent package installation, and increase administrative effort.

A correctly configured offline repository provides:

Reliable package installation.
Controlled software versions.
Improved security.
Reduced Internet dependency.
Consistent server builds.
Faster software deployment.
Simplified disaster recovery.

Prerequisites

Oracle Linux, RHEL, or CentOS installation DVD or ISO.
Root or sudo privileges.
Available DVD drive or mounted ISO image.
Access to the /etc/yum.repos.d directory.
Basic Linux command-line knowledge.

Understanding Repository Files

Repository definitions are stored as text files with the .repo extension inside the following directory:

/etc/yum.repos.d/

Each repository definition typically contains:

Parameter	Description
name	Repository display name.
baseurl	Location of the repository.
enabled	Enables or disables the repository.
gpgcheck	Controls package signature verification.
gpgkey	Location of the GPG public key (if used).

Linux Administrator Recommendation

Whenever possible, create a dedicated local repository instead of repeatedly mounting installation media. For production Oracle Database and Oracle E-Business Suite environments, maintaining a centralized offline repository simplifies package management, improves consistency across servers, and reduces administrative overhead.

Step 1 – Insert and Mount the Installation DVD

Insert the Oracle Linux, RHEL, or CentOS installation DVD into the server. If you are using a virtual machine, attach the installation ISO image to the virtual DVD drive.

Create a mount point if one does not already exist.

mkdir -p /mnt/cdrom

Mount the DVD or ISO.

mount /dev/cdrom /mnt/cdrom

If using an ISO image stored locally, mount it with the loop option.

mount -o loop OracleLinux.iso /mnt/cdrom

Step 2 – Verify the Mount

Confirm that the installation media is mounted successfully.

df -h

You can also verify the mount location.

mount | grep cdrom

List the DVD contents to confirm that package directories such as Packages or BaseOS are available.

ls -l /mnt/cdrom

Step 3 – Create the Repository Configuration File

Create a new repository definition file inside the repository configuration directory.

vi /etc/yum.repos.d/localdvd.repo

Example repository configuration:

[LocalDVD]

name=Oracle Linux DVD Repository

baseurl=file:///mnt/cdrom

enabled=1

gpgcheck=0

Repository Parameters Explained

Parameter	Purpose
LocalDVD	Unique repository identifier.
name	Friendly repository name displayed by YUM.
baseurl	Location of the mounted DVD repository.
enabled=1	Enables the repository.
gpgcheck=0	Disables GPG signature verification for the local media.

Step 4 – Disable Unused Online Repositories (Optional)

If the server has no Internet access, disable repositories that are no longer required to avoid timeout delays.

yum-config-manager --disable '*'

Then enable only the local DVD repository if necessary.

Step 5 – Clear the YUM Cache

Remove previously cached repository metadata.

yum clean all

This forces YUM to reload metadata from the DVD repository.

Step 6 – Rebuild Repository Metadata

Generate fresh cache information.

yum makecache

Successful execution confirms that repository metadata has been read correctly.

Step 7 – Verify the Repository

Display the configured repositories.

yum repolist

Example output:

repo id          repo name

LocalDVD         Oracle Linux DVD Repository

Step 8 – Install a Test Package

Install a package from the DVD repository to verify that package management is functioning correctly.

yum install tree

If the package installs successfully, the repository has been configured correctly.

Common Repository Errors

Error	Possible Cause	Resolution
Cannot find a valid baseurl	Incorrect mount path	Verify the baseurl and mount point.
No repositories available	Repository disabled	Enable the repository and rebuild the cache.
Package not found	Package absent from DVD	Verify the package exists on the installation media.
Metadata download failure	Repository path incorrect	Verify the mounted directory contains repository metadata.

Troubleshooting Checklist

Verify that the DVD or ISO is mounted.
Confirm the baseurl points to the correct directory.
Ensure the repository file is saved under /etc/yum.repos.d/.
Run yum clean all before testing.
Rebuild the repository cache using yum makecache.
Confirm that repository metadata is present.
Verify file permissions on the mounted media.
Test package installation using a small utility package.

Production Case Study

A production Oracle Database server located inside a secure financial network required additional operating system packages before an Oracle patch could be applied. Since Internet access was prohibited, the administrator mounted the Oracle Linux installation ISO, configured a local DVD repository, rebuilt the repository cache, and successfully installed the required RPM packages without modifying the organization's security policy or requiring temporary network access.

Oracle Linux, RHEL, and CentOS Repository Differences

Although Oracle Linux, Red Hat Enterprise Linux (RHEL), and CentOS all use the RPM package format, their repository management differs depending on the distribution and subscription model.

Distribution	Repository Source	Internet Access
Oracle Linux	Oracle Public Yum Server / Local Repository	Optional
Red Hat Enterprise Linux (RHEL)	Red Hat Subscription Manager	Usually Required
CentOS	CentOS Mirror Repositories	Usually Required
Offline Environment	DVD / ISO Repository	No

YUM vs DNF

Beginning with Oracle Linux 8 and RHEL 8, DNF (Dandified YUM) became the default package manager. The familiar yum command is generally retained as a compatibility wrapper, so most existing YUM commands continue to work without modification.

Feature	YUM	DNF
Package Format	RPM	RPM
Dependency Resolution	Good	Improved
Performance	Good	Better
Oracle Linux 8/9 Support	Compatibility Command	Default
Repository Files	.repo	.repo

Useful Linux Commands

Display Configured Repositories

yum repolist

Display Repository Details

yum repoinfo

List Available Packages

yum list available

Search for a Package

yum search package_name

Display Package Information

yum info package_name

Install a Package

yum install package_name

Update Installed Packages

yum update

Remove a Package

yum remove package_name

Linux Administrator Best Practices

Create a local repository for production environments without Internet access.
Keep installation media synchronized with the operating system version.
Back up custom .repo configuration files before system upgrades.
Use meaningful repository names to simplify administration.
Verify package integrity before installation.
Run yum clean all after modifying repository configurations.
Rebuild metadata using yum makecache whenever repository contents change.
Document repository configuration as part of server build procedures.
Maintain a centralized offline repository for multiple production servers where possible.
Review repository configuration after operating system patching or migration.

Common Administrator Mistakes

Using an incorrect baseurl path.
Forgetting to mount the DVD or ISO before testing the repository.
Leaving obsolete online repositories enabled in offline environments.
Ignoring repository metadata errors.
Not clearing the YUM cache after changing repository settings.
Mixing repositories from different operating system versions.
Removing installation media before package installation completes.
Not verifying available disk space before installing packages.

Frequently Asked Questions (FAQ)

Can I use an ISO image instead of a physical DVD?

Yes. Mounting an ISO image with the loop option is a common and recommended approach, especially in virtualized environments.

Does this procedure work on Oracle Linux 8 and 9?

Yes. The repository configuration remains the same. Although DNF is the default package manager, the yum command is retained as a compatibility wrapper in most installations.

Why does `yum repolist` show no repositories?

This usually indicates that the repository file is incorrect, the installation media is not mounted, or the repository metadata cannot be found at the specified baseurl.

Should I disable Internet repositories?

In isolated production environments, disabling unused online repositories avoids unnecessary connection timeouts and ensures packages are installed only from approved local sources.

Can I use one local repository for multiple servers?

Yes. Many organizations maintain a centralized HTTP, NFS, or FTP repository that multiple servers access, eliminating the need to mount installation media on each system.

About the Author

Rana Abdul Wahid is an Oracle Database and Oracle E-Business Suite Consultant with more than 15 years of experience in Oracle Database Administration, Oracle E-Business Suite Application DBA, Oracle Cloud Infrastructure (OCI), Oracle RAC, Oracle Data Guard, RMAN Backup & Recovery, Linux/Unix Administration, MySQL, Microsoft SQL Server, PostgreSQL, and enterprise infrastructure management.

His expertise includes Oracle Database Security, Performance Tuning, Backup & Recovery, Oracle E-Business Suite administration, AutoConfig, Oracle Forms, Oracle WebLogic Server, Linux system administration, and enterprise production support.

Learn more about the author →

Conclusion

Configuring a local YUM repository from a DVD or ISO image is a practical and reliable solution for Linux servers operating in offline or highly secure environments. By properly mounting the installation media, creating a repository definition, rebuilding the package metadata, and verifying repository functionality, administrators can install and maintain software without relying on Internet connectivity.

Following the best practices outlined in this guide helps ensure consistent package management, simplifies server provisioning, supports enterprise security policies, and provides a dependable software installation method for Oracle Linux, Red Hat Enterprise Linux, and CentOS systems.

Final Linux Administrator Recommendation

For enterprise environments, maintain a centralized and well-documented offline repository, regularly validate repository metadata, archive installation media for disaster recovery, and standardize repository configurations across all production servers. This approach improves reliability, strengthens security, and simplifies long-term Linux system administration.

Found this guide helpful? Explore more Oracle Database, Oracle E-Business Suite, Linux administration, RMAN, Oracle Forms, and production troubleshooting articles in the Oracle Error Codes Guide.

Oracle Database Error Solutions & DBA Knowledge Base