Oracle’s incompetent patch-handling

My last post was about how Oracle decided to move smb.conf and the
private-dir for samba without moving the files for you, or even
informing you that this might be a good idea… Read more here:
http://posterous.mortencb.cx/samba-not-working-after-solaris-patching

Today we are patching all of our servers at work, and we came across
even more stupid stuff:

1) If you have ldap/client running and enabled, it is probably because
you are using it. But in one of the latest patches, Oracle decides
that disabling this service is probably a good thing. Even if you
check after patching, it is enabled, but after a reboot it is
magically disabled. This is extra fun if you login as a normal user
and use sudo to manage your servers… How can this pass QC?

2) If you have changed /usr/lib/sendmail to point to your own local
mailer, f.ex. your own compiled exim, this is also probably because
you want it like that. Often Oracle decides that it’s a good idea to
just change this back to point to sendmail. Which breaks your setup
spectacularly… Again, how can this pass QC?

3) In our setup /var/mail is a symlink to /export/mail which is a
gigantic zfs-disk from the SAN. In one of the latest patches, Oracle
decides that this symlink should just be removed. Not even replaced
with a normal folder or anything, just removed. Which breaks our
setup spectacularly… Again, how can this pass QC?

4) If you don’t use sendmail, but f.ex. exim instead like we do, you
have probably disabled the sendmail-services. In many patches, Oracle
thinks that it’s a very good idea to just enable these services for
you again. Don’t they think we know what we’re doing when we disable
them ourselves? Again, how can this pass QC?

I am so happy that we’re moving away from Oracle/Sun/Solaris, because
this is just getting worse and worse for each time we patch the
servers…

#oracle #fail

Tags: , ,

Leave a comment