Oracle ORA-03113 and ORA-07445 ACCESS_VIOLATION?

I don't think you can ever call something like this an "application issue". You'll probably need to convince the DBA that this is a database issue so he can talk to Oracle support, or at least look it up on Metalink or something. You may have scared him off when you started talking about IIS, .

NET, etc. See if you can reproduce the error only in SQL*Plus, that should get his attention.

I don't think you can ever call something like this an "application issue". You'll probably need to convince the DBA that this is a database issue so he can talk to Oracle support, or at least look it up on Metalink or something. You may have scared him off when you started talking about IIS, .

NET, etc. See if you can reproduce the error only in SQL*Plus, that should get his attention. As for actually solving the problem, you'll probably either need to patch, upgrade, or find some way to avoid the issue. Try rewriting your query in some trivial way and it may work.

I usually end up working around these issues instead of actually solving them.

2 Worthwhile checking the query plan for anything ugly or unexpected. Could try moving the CURRENT_TIMESTAMP predicates out to the WHERE clause rather than the INNER JOIN. Finally, ask the DBA if he can tell you whether it is failing on the PARSE (interpreting the query), execute or fetch (getting the rows).

If nothing else, it will force him to do some investigation. – Gary Myers Sep 1 '10 at 7:10 Bang on! Comment out the CURRENT_TIMESTAMP line and it runs... – Peter Goras Sep 1 '10 at 7:53 The 7445 error is often a symptom of bugs in Oracle.

I just had a very similar issue resolved by Oracle support. It actually started happening right after the most recent Critical Patch Update. – DCookie Sep 1 '10 at 17:25.

We were able to reproduce the same using SQL Developer and so found the issue. ...INNER JOIN IIL_RUN_STA_VALS IRSV ON ILRN. ILRN_ID = IRSV.

ILRN_ID AND CURRENT_TIMESTAMP BETWEEN IRSV. TRANS_FROM AND IRSV. TRANS_TO this line is the culprit.

There was an index on the two date columns, TRANS_FROM and TRANS_TO. We droppped this. It worked.

After a bit more investigation we found that with few rows in the join, the index was not used but as the number of rows in the join increased, the query plan would change and the offending index would be used. This explained why it was an intermittent problem. But clearly a suboptimal query plan shouldn't cause Oracle to die with an ORA-07445... Will log with Oracle support.

Thanks all!

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.