Oracle Exalytics Image Update Script Failed With Missing Dependency Errors

Asset ID:	1-72-1629053.1
Update Date:	2018-04-12
Keywords:

Solution Type Problem Resolution Sure

Solution 1629053.1 : Oracle Exalytics Image Update Script Failed With Missing Dependency Errors

Applies to:

Exalytics In-Memory Machine X3-4 - Version All Versions and later
Oracle Exalytics Software - Version 1.0.0.3.0 and later
Exalytics In-Memory Machine X2-4 - Version All Versions and later
Information in this document applies to any platform.

Symptoms

Attempted to install an Exalytics Patchset on a server with an external yum update channel configured. While running the upgrade script, it fails with missing dependency errors.

For example, when attempting to install Exalytics PS3, as described in the Exalytics Installation Guide, Step 3: Run the Oracle Exalytics Base Image 1.0.0.5 Upgrade Script, root user ran the command:

# rpm -Uv /tmp/exalytics_upgrade_bm_1.0.0.2_to 1.0.0.5/exalytics-scripts-1.0.0.5-xx.noarch.rpm

The "rpm -Uv" command completed but the log file shows missing dependency errors:

...
yum repolist ...
repo id repo name status
epel Extra Packages for Enterprise Linu enabled: 18,352
exalytics_1.0.0.5_x86_64_base Exalytics release 1.0.0.5 Base (x8 enabled: 5
oel5 Oracle Enterprise Linux 5 - x86_6 enabled: 3,187
oel5-updates Oracle Enterprise Linux 5 - x86_6 enabled: 3,358
repolist: 24,902
yum check-update ...
...
--> Finished Dependency Resolution
srptools-0.0.4-8.el5.x86_64 from oel5 has depsolving problems
--> Missing Dependency: libibumad.so.2(IBUMAD_1.0)(64bit) is needed by package srptools-0.0.4-8.el5.x86_64 (oel5)
libsdp-devel-1.1.108-0.14.g63e0cf1.x86_64 from installed has depsolving problems
--> Missing Dependency: libsdp = 1.1.108-0.14.g63e0cf1 is needed by package libsdp-devel-1.1.108-0.14.g63e0cf1.x86_64 (installed)
ibsim-0.5-2.el5.x86_64 from oel5 has depsolving problems
--> Missing Dependency: libibmad.so.2()(64bit) is needed by package ibsim-0.5-2.el5.x86_64 (oel5)
ibsim-0.5-2.el5.x86_64 from oel5 has depsolving problems

Changes

An external yum repository had been configured in the yum.conf file on the Exalytics server.

Cause

External yum repository was configured on the Exalytics server. An external yum repository is not currently certified, or supported, for Oracle Exalytics, reference <Note 1614293.1>, Oracle Exalytics: Can Linux Updates Or Yum Update Be Configured On Exalytics.

If changes were made to the yum.conf file to configure an external repository, the image update may fail, or may report misleading errors or missing dependencies. This problem can happen on any Exalytics server where an external yum repository has been configured.

Solution

To ensure correct installation of the image update, you must revert the yum.conf file to it's original configuration. A default (out of box) yum.conf file will show:

# more /etc/yum.conf
[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

If your yum.conf file is different, first make a backup copy of the current yum.conf file. Then create a new yum.conf as shown above.

Once the yum.conf file is set correctly, re-attempt the rpm upgrade (i.e. if PS3 upgrade, "rpm -Uv /tmp/exalytics_upgrade_bm_1.0.0.2_to 1.0.0.5/exalytics-scripts-1.0.0.5-xx.noarch.rpm").

You may confirm successful patch installation by checking the .log files in the /var/log/exalytics/ directory. For example, on PS3 upgrade, the file would be called "update-1.0.0.5.log" and a successful upgrade would show messages like:

================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
exalytics-container-bm x86_64 1.0.0.5-23 exalytics_1.0.0.5_x86_64_base 3.2 k
Installing for dependencies:
exalytics-flash x86_64 1.0.0.5-42 exalytics_1.0.0.5_x86_64_base 2.1 M
...
postInstall (exalytics-flash) 1; done

Installing : exalytics-container-bm 2/2

Installed:
exalytics-container-bm.x86_64 0:1.0.0.5-23

Dependency Installed:
exalytics-flash.x86_64 0:1.0.0.5-42

Complete!

Additionally, certain Linux packages will show an update corresponding to the date of the patch installation. For example, if you run command to check recently updated packages ('rpm -qa'), you should see results similar to:

# rpm -qa --last | grep ' Tue 04 Feb 2014'

exalytics-flash-1.0.0.5-42 Tue 04 Feb 2014 11:42:16 PM EST
exalytics-container-bm-1.0.0.5-23 Tue 04 Feb 2014 11:42:16 PM EST
exalogic.tools-1.0.0.5-3.0.exalytics Tue 04 Feb 2014 11:42:14 PM EST
exalogic-1.0.0.5-3.0.exalytics Tue 04 Feb 2014 11:40:46 PM EST
gpg-pubkey-1e5e0159-464d0428 Tue 04 Feb 2014 11:37:41 PM EST
exalytics-scripts-1.0.0.5-36 Tue 04 Feb 2014 11:27:14 PM EST

References

<BUG:18260751> - ENH: ADD PRE-REQ CHECK & BACKUP UTILITIES TO EXALYTICS IMAGE UPDATE SCRIPTS
<NOTE:1614293.1> - Oracle Exalytics: Can Linux Updates Or Yum Update Be Configured On Exalytics

Attachments

This solution has no attachment