Question : yum Install oracle-validated fails dependency on glibc

I am trying to install the oracle-validated rpm on a new Oracle Enterprise Linux 5.5 install. I have configured the public-yum.oracle.com repository. Durng dependency checks i get the follwoing output.

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
--> Finished Dependency Resolution
glibc-headers-2.5-49.x86_64 from el5_u5_base has depsolving problems
  --> Missing Dependency: glibc = 2.5-49 is needed by package glibc-headers-2.5-49.x86_64 (el5_u5_base)
glibc-devel-2.5-49.x86_64 from el5_u5_base has depsolving problems
  --> Missing Dependency: glibc = 2.5-49 is needed by package glibc-devel-2.5-49.x86_64 (el5_u5_base)
glibc-devel-2.5-49.i386 from el5_u5_base has depsolving problems
  --> Missing Dependency: glibc = 2.5-49 is needed by package glibc-devel-2.5-49.i386 (el5_u5_base)
Error: Missing Dependency: glibc = 2.5-49 is needed by package glibc-headers-2.5-49.x86_64 (el5_u5_base)
Error: Missing Dependency: glibc = 2.5-49 is needed by package glibc-devel-2.5-49.i386 (el5_u5_base)
Error: Missing Dependency: glibc = 2.5-49 is needed by package glibc-devel-2.5-49.x86_64 (el5_u5_base)
 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

I try to manually install the dependency on glibc and end up stuck at this message....

1:
2:
3:
4:
5:
6:
7:
[root@dac-pasdb01 Server]# yum install glibc
Loaded plugins: security
Setting up Install Process
Package matching glibc-2.5-49.x86_64 already installed. Checking for update.
Package matching glibc-2.5-49.i686 already installed. Checking for update.
Nothing to do
[root@dac-pasdb01 Server]#

Please help I am stuck. I have tried updating kernel headers and clearing the yum cache but no success.

Aaran

Answer : yum Install oracle-validated fails dependency on glibc

No, you should not remove any x86_64 packages as that will break your box.

The error gives you options to try to correct this issue i.e.using the --skip-broken
or running
"You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest

"
The install log file if any will likely reveal what it was checking.