Oracle Exadata and the glibc vulnerability (CVE-2015-7547)



I think most of us heard about the „glibc“ vulnerability (CVE-2015-7547). We had a lot of Exadata Servers  and so we discuss how we could install the new rpm’s.

Yes, it seems to be no problem while My Oracle Support Doc-ID 2108582.1 describes what we had to do and by the way at the end of this procedure you had to reboot every DB Node and also every Cell Server. (While rebooting the Cell Server please read before the Doc-ID. 1188080.1.)

The note 2108582.1 said it is not necessary to do a relink but is this correct?

I was a little bit confused and I checked the Oracle Documentation and My Oracle Support again and I found  another Doc ID 1467060.1 „Relinking Oracle Home FAQ ( Frequently Asked Questions) “ which said that if you install an OS Patch than Oracle recommend to do a relink.

And in the Oracle Database Administrator Guide  was written that Oracle recommend to do an relink after Patching the OS.

We found for us a solution because we install the new rpm’s in conjunction with the Jan-2016 Patchbundle. During the Patchbundle Installation the relink was done automatically.

Keep in mind that Oracle Documentation recommend to do a relink no matter what an MOS Doc-ID said.


Veröffentlicht von spa

Oracle and Unix Professional, main focus on Oracle HA - Systems including Exadata Systems

Kommentar verfassen

Trage deine Daten unten ein oder klicke ein Icon um dich einzuloggen:

Du kommentierst mit Deinem Abmelden /  Ändern )

Google Foto

Du kommentierst mit Deinem Google-Konto. Abmelden /  Ändern )


Du kommentierst mit Deinem Twitter-Konto. Abmelden /  Ändern )


Du kommentierst mit Deinem Facebook-Konto. Abmelden /  Ändern )

Verbinde mit %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d Bloggern gefällt das: