How To - Exadata - Configure YUM to connect to Oracle Public Repository

Asset ID:	1-71-2160289.1
Update Date:	2018-05-23
Keywords:

Solution Type Technical Instruction Sure

Solution 2160289.1 : How To - Exadata - Configure YUM to connect to Oracle Public Repository

Applies to:

Exadata Database Machine V2 - Version All Versions and later
Exadata Database Machine X2-2 Hardware - Version All Versions and later
Exadata X6-2 Hardware - Version All Versions and later
Exadata X3-8 Hardware - Version All Versions and later
Exadata X3-2 Hardware - Version All Versions and later
Linux x86-64
Linux x86

Goal

The goal of this document is to assist in configuring an Exadata system to connect to the Oracle Public YUM repositories. While this document is intended for Exadata systems, it can be useful for anyone using Oracle Linux.

NOTE: Your Exadata Engineered System must have a working connection to the internet for YUM to work correctly. If your system is isolated from the internet due to security policies, you will need to set up a local repository and populate it manually. Contact Oracle Support for information on information on doing this.

EEST Engineers should refer to Doc ID 2151708.1 - "How-To - Creating a Local Repository from a Compute Node Base Repository" ISO for information on setting up a local repository on an isolated Exadata system.

NOTE: While this document covers configuring access to the Oracle Public YUM Repository, DO NOT USE yum update with this repository to update an Exadata system. This can lead to severe problems with the system's operation. Only use this repository to install additional packages needed for your system (for example, installing packages to allow running of GUI applications on the server) or to update specific individual packages (for example, to resolve a security vulnerability).

Solution

To configure your Exadata system to use the Oracle Public YUM Repository, accomplish the following actions as root.

I. Checking YUM Configuration

1. Change to the /etc directory.

cd /etc

2. Ensure the contents of the yum.conf file look like the following. Make any changes necessary before proceeding to step 3.

     [main]
     cachedir=/var/cache/yum
     keepcache=0
     debuglevel=2
     logfile=/var/log/yum.log
     distroverpkg=redhat-release
     tolerant=1
     exactarch=1
     obsoletes=1
     gpgcheck=1
     plugins=1

# Note: yum-RHN-plugin doesn't honor this.
metadata_expire=1h

# Default.
# installonly_limit = 3

     # PUT YOUR REPOS HERE OR IN separate files named file.repo
     # in /etc/yum.repos.d
     # Never update kernel and kernel-uek
     installonlypkgs=kernel kernel-smp kernel-bigmem kernel-enterprise kernel-debug kernel-unsupported kernel-uek
     exclude=up2date

NOTE: If your system needs to use a proxy to access the internet, add the following line to the yum.conf file:

proxy=http://<url.to.proxy>:<port>

For example:

proxy=http://www.myproxy.com:80

You can also use an IP address in place of the URL.

3. Change to the /etc/yum.repos.d directory.

cd /etc/yum.repos.d

4. List the contents of the yum.repos.d directory.

Repository configuration files have a file extension of .repo.

If the only files in the directory are Exadata-computenode.repo.sample and/or ULN-Base.repo, go on to the "II. Creating a Repo File" section.

If there are more files than just Exadata-computenode.repo.sample and/or ULN-Base.repo, go on to the "III. Adding a Repository Configuration" section.

II. Creating a Repo File

1. In /etc/yum.repos.d, edit a new file called oracle-public-yum-ol6.repo .

2. In the new file, add the following lines:

     [public_ol6_latest]
     name=Oracle Linux $releasever Latest ($basearch)
     baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/$basearch/
     gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6
     gpgcheck=1
     enabled=1

3. Save the file.

4. Go to the "IV. Test the Repository" section.

III. Adding a Repository Configuration

1. Review each of the repo files in the /etc/yum.repos.d. Look for section that looks similar to this:

If you do not see this in any of the repo files, accomplish the steps in the "II. Creating a Repo File" section.

If you do see this in one of the repo files, go to step 2.

2. Ensure the enabled line is set to 1 (active):

enabled=1

If not set to 1, make the change and save the file.

If set to 1, you are already configured to access the Oracle Public YUM Repository.

3. Go to the "IV. Test the Repository" section.

IV. Test the Repository

Issue the following command:

yum repolist

You should see the list of repositories that you added using this document.

For any errors, first go back and retrace your steps to ensure all of the above steps were correctly accomplished. If the configuration is confirmed good, check the list of common errors below for a possible solution. If no solution is found, open a Service Request with Oracle Support.

Common Errors:

Errno -1 - Error importing repomd.xml for public_ol6_latest: Damaged repomd.xml file

Example error output:

http://public-yum.oracle/com/repo/OracleLinux/OL6/latest/x86_64/repodata/repomd.xml: [Errno -1] Error importing repomd.xml for public_ol6_latest: Damaged repomd.xml file

Cause:

Usually caused by an error in the configuration files. Go back through the steps above and ensure you did each step correctly. Additionally, check that any firewalls on your network are not interfering with YUM communications with the Oracle repository.

Errno 12 - Timeout on <web address of repository>

Example error output:

http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/x86_64/repodata/repomd.xml: (28, 'connect() timed out!')

Cause:

- Go back through the steps above and ensure you did each step correctly. Additionally, check that any firewalls on your network are not interfering with YUM communications with the Oracle repository.

- Apply the solution in Doc ID 1546671.1.

Errno 14 - PYCURL ERROR 6 - "Couldn't resolve host 'some.host.name'"

Example error output:

     Could not retrieve mirrorlist http://apt.sw.be/redhat/el6/en/mirrors-rpmforge error was
     14: PYCURL ERROR 6 - "Couldn't resolve host 'apt.sw.be'"
     http://apt.sw.be/redhat/el6/en/x86_64/rpmforge/repodata/repomd.xml: [Errno 14] PYCURL ERROR 6 - "Couldn't resolve host 'apt.sw.be'"

Cause:

YUM could not connect to the specified host. This could be due to several reasons to include (but not limited to):

The host is down
The host name in the repository file is not correct
The DNS resolution in your network for this host if failing
The repository file is not correctly formatted

Check for problems with the above and retry.

Errno 14 - PYCURL ERROR 22 - "The requested URL returned error: 401 Unauthorized

Example error output:

http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 401 Unauthorized"

Cause:

Check your browser's proxy configuration settings. If they are enabled, that means your network requires a proxy configuration for browsing the Internet. You need to specify one for YUM as well as detailed in Section I step 2.

Errno 14 - PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"

Example error output:

[Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"

Cause:

The proxy server configuration in /etc/yum.conf is incorrect or the proxy server is blocking the request to connect to the Oracle repository. Check that you have the correct proxy server specified and that there are no mistakes in the configuration entry in /etc/yum.conf. If the configuration is correct, work with your network or security team to have the proxy server configured to allow YUM access to the Oracle repository. Also check that the connection is not being blocked by a firewall.

Additional RPM and Repository Documents:

Doc ID 1473002.1 - Exadata YUM Repository Population and Linux Database Server Updating

Doc ID 1564054.1 - Can YUM repository server be one of the Exadata compute node?

Doc ID 1617265.1 - Exadata: Missing Dependency of exadata-sun-computenode-exact if manually upgrade RPM

Doc ID 2151708.1 - How-To - Creating a Local Repository from a Compute Node Base Repository ISO

Attachments

This solution has no attachment