Ok guys this is crazy Has anyone ever come across a ORA-03113: produced
from running a SQL that leaves no trace file or core dumps

I have SQL from a canned application that worked fine until about a week
ago now when the SQL is called either through the app or run directly on
the server it produces a ORA-03113 followed by a not connected to oracle
message. I can see the server connect, watch the SQL call, and then the
server side process dies. Now if I set
STAR_TRANSFORMATION_ENABLED=FALSE the query will return results put the
performance hit is horrible


Windows 2000
Oracle 9.2.0.5

Thanks

Oracle LazyDBA home page