ORA-03113: end-of-file on communication channel
Posted: Thu 26 Apr 2012 21:41
Hello,
We have come across a strange issue where it seems that the generated SQL sent to Oracle is - for lack of a better term - crashing Oracle. It is simply a query on a single entity with one condition (WHERE clause).
If we leave out the condition, all rows are returned successfully as expected. However, with a condition that will return a record, we receive:
ORA-03113: end-of-file on communication channel
If we put in a condition that returns no records, the error is not received.
We were able to take the Linq query and get the generated SQL from query.ToString(), then paste that SQL into Oracle SQL Developer and execute it. When we do this, it closes the connection. Oracle just cannot handle the query and cannot even return an error message. It just simply closes the pipe and disconnects the client altogether. We see:
"No more data to read from socket" and "IO Error: Software caused connection abort: socket write error" and "Closed Connection".
What could be our next troubleshooting step?
Thanks in advance.
We have come across a strange issue where it seems that the generated SQL sent to Oracle is - for lack of a better term - crashing Oracle. It is simply a query on a single entity with one condition (WHERE clause).
If we leave out the condition, all rows are returned successfully as expected. However, with a condition that will return a record, we receive:
ORA-03113: end-of-file on communication channel
If we put in a condition that returns no records, the error is not received.
We were able to take the Linq query and get the generated SQL from query.ToString(), then paste that SQL into Oracle SQL Developer and execute it. When we do this, it closes the connection. Oracle just cannot handle the query and cannot even return an error message. It just simply closes the pipe and disconnects the client altogether. We see:
"No more data to read from socket" and "IO Error: Software caused connection abort: socket write error" and "Closed Connection".
What could be our next troubleshooting step?
Thanks in advance.