Kommentare zu: Oracle CPUs and problems on some platforms http://blog.red-database-security.com/2007/06/14/oracle-cpus-and-problems-on-some-platforms/ Sat, 22 Nov 2008 09:49:44 +0000 http://wordpress.org/?v=2.2.1 Von: Noons http://blog.red-database-security.com/2007/06/14/oracle-cpus-and-problems-on-some-platforms/#comment-4 Noons Fri, 15 Jun 2007 03:25:21 +0000 http://blog.red-database-security.com/2007/06/14/oracle-cpus-and-problems-on-some-platforms/#comment-4 "Before applying a patch on a production system you should always perform tests." So, what are we supposed to test? The entire application set that may be executing in a server? Every time a CPU comes out? And who pays for that testing? Do we get a discount on the maintenance fees of Oracle for that? Or is it that we should run every possible command available against any resource that the database might be using? As in running nmap, an obvious (not!) choice for testing after a patch is applied? No thanks, that is very simply not the solution. I'll take the obvious, sensible and much cheaper option: NONE of the CPUs are ever applied to my systems! I'll apply patches to specific problems, when and if found. Rather than pay through the nose to trace Oracle's own problems... “Before applying a patch on a production system you should always perform tests.”

So, what are we supposed to test?
The entire application set that may be executing in a server?
Every time a CPU comes out? And who pays for that testing? Do we get a discount on the maintenance fees of Oracle for that?

Or is it that we should run every possible command available against any resource that the database might be using? As in running nmap, an obvious (not!) choice for testing after a patch is applied?

No thanks, that is very simply not the solution.
I’ll take the obvious, sensible and much cheaper option: NONE of the CPUs are ever applied to my systems!

I’ll apply patches to specific problems, when and if found. Rather than pay through the nose to trace Oracle’s own problems…

]]>