Re: How to reproduce an ORA-7445?
Well, never say never.
Usually you are correct. However, sometimes (very rare but if you are
an important customer and can escalate high) it's possible to get a
patch that you will have to test in your environment. This is when
problem occurs consistently in your environment and Oracle cannot
reproduce it in-house because it's just not feasible (no
hardware/resources/workload/whatever). Been there done that.
In your case, I understand that you've got the error only once. If
it's an NLS issue and you have it every now and again then you should
be able to figure out how to reproduce it.
On 12/20/06, Allen, Brandon <Brandon.Allen@(protected):
> 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@(protected)
> So what's the point of filing an SR unless the problem is 100%
> reproducible? I'm not trying to be sarcastic, just pragmatic.
The Pythian Group
Sr. Oracle DBA