Re: I think Oracle is not doing the correct decision rejecting error information
Date: Tue, 10 Jun 2014 12:27:49 +0100
Message-ID: <CABe10sbyVPVQSQaugmzN4XinWRFzOsmkwST-vqfNJb4GTZr2xg_at_mail.gmail.com>
I'm a little confused about what you are suggesting Oracle do. Oracle already provides mechanisms for uploading trace data to metalink. It also has various fault resolution options integrated with Cloud Control based on incident occurrence.
You seem to be suggesting, I think, that any time any customer hits an ORA-00600 (or presumably other error) whether or not it matters to the customer the trace file which may well contain sensitive data should be uploaded to Oracle. I think that's a step too far, even with an opt out. A metalink account and suitable bugs can (rarely) already let you see names of customers & their database schemas if you happen across them. I suspect with automated trawling that problem would get much worse.
On Tue, Jun 10, 2014 at 1:03 AM, Juan Carlos Reyes Pacheco < jcdrpllist_at_gmail.com> wrote:
> Only a comment.
> I have a metalink account but I don't have enough rights to upload
> database trace error files.
>
> I think Oracle should be crawling to customer to upload their error files,
> to have statistics about problems. But I don't see they do.
>
> Why?
> in the past 3 years I found mora than four ora-600 errors not registered
> in metalink, and my database is not an enterprise.
> If you add the complexity only oracle has because the numerous options
> the database has, the probability to have problems increases exponentially.
> Only in upgrading, exporting and importing I had seen there had appeared a
> lot of problem we are finding a way to workaround.
>
> This is about having a more stable database, I am using oracle from oracle
> 7 and I see a higher tendency to have errors, the strategy we do is to
> upgrade to one patch that solves the problem, but not the last, because
> another error can appear, because fro mthe day to the night sometimes
> appears some errors, like temporary growth when making rman backup, started
> in one of our customers and the bug spread to the other. Other example is
> one view started to not compile, etc, and I'm not a dba, I'm develoepr dba,
> so I can't make magic like you.
>
> note. We have a small standard database edition, but a lot of users and
> database.
>
-- Niall Litchfield Oracle DBA http://www.orawin.info -- http://www.freelists.org/webpage/oracle-lReceived on Tue Jun 10 2014 - 13:27:49 CEST