RE: How to reproduce an ORA-7445?

  • From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
  • To: <Rich.Jesse@xxxxxx>, <oracle-l@xxxxxxxxxxxxx>
  • Date: Wed, 20 Dec 2006 10:08:23 -0700

Probably not much point at all because they're always going to ask for
it to be reproduced with tracing on and as a DBA that provides tech
support myself, I usually find myself in the same position.  It's often
very difficult if not impossible to troubleshoot a problem that can't be
reproduced and on top of that, there is the issue of triage - how much
time are you going to spend working on a problem that can't even be
reproduced when you've got 10 other fires to fight.  If it can't be
reproduced, then chances are it won't be a problem again anyway so your
time would be better spent elsewhere.  Of course, if it does end up
recurring, hopefully the next time you will have a better idea of what
to look for and compare with the first occurrence to see what the exact
conditions were that caused the problem - and each time you will
hopefully get closer to being able to reproduce it.


-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jesse, Rich

So what's the point of filing an SR unless the problem is 100%
reproducible?  I'm not trying to be sarcastic, just pragmatic.

Privileged/Confidential Information may be contained in this message or 
attachments hereto. Please advise immediately if you or your employer do not 
consent to Internet email for messages of this kind. Opinions, conclusions and 
other information in this message that do not relate to the official business 
of this company shall be understood as neither given nor endorsed by it.


Other related posts: