Calendar
Juni 2007
M D M D F S S
« Mai   Jul »
 123
45678910
11121314151617
18192021222324
252627282930  

Oracle CPUs and problems on some platforms

During our security training we found an interesting forum entry (CPU Oct 2006 Problem) in Oracle Metalink. It seems that a portscan with nmap on AIX 5.2, OAS 10.1.2.0.2 CPUOCT06 causes a denial of service problem on port 443 (HTTPS). It’s not clear if this problem affects all platforms because nobody answered the forum entry.
Normally it is a good idea to apply CPUs as soon but sometimes new bugs are introduced. Often these problems are specific to a special platform. Another example of a bug which was introduced by the CPUOct2006, CPUJan2007 and CPUApr2007 was a rman problem on Windows 32 bit (Rman fails to restore in 9.2.0.8 with CPU patch installed on Windows platform).

Before applying a patch on a production system you should always perform tests.

1 Antwort auf “Oracle CPUs and problems on some platforms”

  1. Noons sagt:

    “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…

Antwort schreiben

Sie müssen als angemeldet sein, um einen Kommentar schreiben zu können.