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

Asset ID:	1-72-1617265.1
Update Date:	2017-09-14
Keywords:

Solution Type Problem Resolution Sure

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

Applies to:

Exadata Database Machine V2 - Version All Versions and later
Linux OS - Version Oracle Linux 5.0 and later
Information in this document applies to any platform.

Symptoms

After upgrade to image 11.2.3.3.0 on DB node, try to upgrade iptables fail with error:

[root@exadatadb01 ~]# yum localinstall iptables-1.4.7-9.el5_9.x86_64.rpm
Setting up Local Package Process
Examining iptables-1.4.7-9.el5_9.x86_64.rpm: iptables-1.4.7-9.el5_9.x86_64
Marking iptables-1.4.7-9.el5_9.x86_64.rpm as an update to iptables-1.3.5-9.2.0.1.el5_8.x86_64
Resolving Dependencies
--> Running transaction check
--> Processing Dependency: config(iptables) = 1.3.5-9.2.0.1.el5_8 for package: exadata-sun-computenode-exact
--> Processing Dependency: iptables = 1.3.5-9.2.0.1.el5_8 for package: exadata-sun-computenode-exact
---> Package iptables.x86_64 0:1.4.7-9.el5_9 set to be updated
--> Finished Dependency Resolution
exadata-sun-computenode-exact-11.2.3.3.0.131014.1-1.x86_64 from installed has depsolving problems
--> Missing Dependency: iptables = 1.3.5-9.2.0.1.el5_8 is needed by package exadata-sun-computenode-exact-11.2.3.3.0.131014.1-1.x86_64 (installed)
exadata-sun-computenode-exact-11.2.3.3.0.131014.1-1.x86_64 from installed has depsolving problems
--> Missing Dependency: config(iptables) = 1.3.5-9.2.0.1.el5_8 is needed by package exadata-sun-computenode-exact-11.2.3.3.0.131014.1-1.x86_64 (installed)
Error: Missing Dependency: iptables = 1.3.5-9.2.0.1.el5_8 is needed by package exadata-sun-computenode-exact-11.2.3.3.0.131014.1-1.x86_64 (installed)
Error: Missing Dependency: config(iptables) = 1.3.5-9.2.0.1.el5_8 is needed by package exadata-sun-computenode-exact-11.2.3.3.0.131014.1-1.x86_64 (installed)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest

[root@exadatadb01 ~]#

Changes

Upgrade to image 11.2.3.3.0 and try to upgrade RPM package(s).

Cause

exadata-sun-computenode-exact-11.2.3.3.0.131014.1-1.x86_64 RPM package was introduced to keep RPM packages integrity in system as Exadata shipped images exactly.

Solution

Note: If you are not sure the package you desire to get upgraded is allowed to be or not, then please contact Oracle Support before executing below workaround.

To workaround the restriction, erase the exadata-sun-computenode-exact-11.2.3.3.0.131014.1-1.x86_64 RPM package by:

[root@exadatadb01 ~]# rpm -e exadata-sun-computenode-exact-11.2.3.3.0.131014.1-1.x86_64 --nodeps

Then upgrade the RPM package you desired.

Note: It is not possible/necessary to re-install exadata-sun-computenode-exact-11.2.3.3.0.131014.1-1.x86_64 RPM package after you manually modified any RPM package.

References

<NOTE:1556257.1> - Exadata YUM Repository Population, One-Time Setup Configuration and YUM upgrades

Attachments

This solution has no attachment