Re: I think Oracle is not doing the correct decision rejecting error information
Date: Tue, 10 Jun 2014 19:43:53 -0400
Message-ID: <CAGYrQyuiqnc-thTrqvac=iDok+wSXhr80opdRq76+R+Xkn2bHg_at_mail.gmail.com>
Hi Niall, the problem, is the the increasing complexity in Oracle database, are generating more bugs, as I perceive as database administrator based on the problems we have; on oracle 11g on upgrades in example we have a log migrating from 10 to 11, problems we didn't have on 9i, we choose to export and import, and even in there we found another problems, and we was using of course the last version 11.2.0.3 in that moment.
Second the fault of information in metalink for ora-600 I got, in example is the problem in performance in oracle 11g where the value of system statistics is wrong multiplied by a factor by mistake, and a solution appeared several months after the bug. And this caused a real serious problem in performance.
Maybe you are true dbas can solve them, but I honestly I can't hardly solve them, and I can tell I'm one of the best of the worst in small database administration, at least I can get the idea,
Then I was thinking Oracle should be more interested in receiveing error-reports from customer who are interested in giving it to them. to detect and solve bugs earlier. Because when I tried to upload them, they said it was not in my metalink license, and I was asking why Oracle is not interested in gathering bugs as soon as possible.
That was only my opinion :)
2014-06-10 7:27 GMT-04:00 Niall Litchfield <niall.litchfield_at_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 Wed Jun 11 2014 - 01:43:53 CEST