RE: How to reproduce an ORA-7445?

  • From: <Joel.Patterson@xxxxxxxxxxx>
  • To: <Rich.Jesse@xxxxxx>, <oracle-l@xxxxxxxxxxxxx>
  • Date: Wed, 20 Dec 2006 14:02:56 -0500

NLS translation of dates in binds:

Not that I expect to be on target here, but I'll just ask if you are
using a driver... ie microsoft verses oracle.   Sometimes the
age/version and the make is the cause.

Joel Patterson
Database Administrator
904  727-2546

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jesse, Rich
Sent: Wednesday, December 20, 2006 11:51 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: How to reproduce an ORA-7445?

Hey all,

In our migration of a new ERP system in on AIX, a user hit an
ORA-7445 (with no parameters!).  I file an SR, upload the resulting
trace file, troubleshooting happens, and it's determined we've hit a BUG
due to issues with NLS translation of dates in binds.  I'm then told
that unless we can reproduce the problem, there will be no patch.

Setting aside my knee jerk of steam shooting out my ears, I started
thinking about this situation.  Applying the logic that it's only a bug
if it can be reproduced, I believe the only way I can attempt to
accomplish that is to trace every session, either at the client or the
server, just in case it errors out in the future.  And even then, that's
hardly guaranteed, as the issue could depend on factors only existing at
the time of the original error (e.g. SGA status, OS memory, etc).

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


"It's a Christmas Miracle!" -- Jenny Meyer, Better Off Dead


Other related posts: