Re: Time estimate for patches from Oracle

From: Rich Jesse <rjoralist_at_society.servebeer.com>
Date: Mon, 21 Apr 2008 10:56:13 -0500 (CDT)
Message-ID: <21139.12.17.117.251.1208793373.squirrel@12.17.117.251>


The last BUG I filed spent about 7 months in Development before the patch became available. Granted, this is for 10.1.0.5.0, which may or may not hold the same emphasis as 11g when it comes to patching, despite the fact that 10.1 is still "current". Also, the BUG I encountered affected the usability of trace files, so it was certainly not considered top priority. I don't think the timeliness was unreasonable for the issue.

In the past, I've attempted to escalate fixes that were already in Development, but was told that there is no escalation past that. A call to your account rep couldn't hurt...

GL!

Rich

> Okay, this will probably vary by a considerable margin.
>
> I was wondering what everybody's experience has been with getting a
> patch created by Oracle development and then finally made available.
>
> On April 12th my system suddenly became very unstable (11.1.0.6 on
> Windows 2003 Server). Filed a SR right away, and the following Monday
> I began attending the Oracle Collaborate conference here in Denver. On
> Wednesday I finally got some confirmation that it is a bug, not
> something I set wrong, and by Thursday Oracle development was supposed
> to working on writing a backport to some existing bugs that would fix
> my problem.
>
> Evidently they have now completed testing the backport, but it's still
> not available for me to access and apply yet. Needless to say my users
> are getting a bit annoyed. Last week they understood as I was gone,
> but this week they are expecting a fix ASAP. Any guesses from the list
> on when I might actually be able to get my system running again, so I
> can offer my users something?
>
> Thanks for any all guesses.
>
> --
> -- Bill Ferguson
> --
> http://www.freelists.org/webpage/oracle-l
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Mon Apr 21 2008 - 10:56:13 CDT

Original text of this message