You could of course attempt to trace the connection with sqlnet.log (usually generated into the client application's folder when there are problems). That way you will know not only the Oracle error, but also the lower level network error (if ever there was one). That may give you a hint of where to target your efforts.
Main Topics
Browse All Topics





by: DiscoNovaPosted on 2008-10-21 at 07:52:29ID: 22767774
I believe that the client application is saying "This may have corrupted data", because I think I've never seen such an error message from Oracle, even though the ORA-03114 is very familiar.
The problem is that there are a million and a one possibilities that might cause the connection to disrupt. From a bug in the client application up to the possibility that there are mice moving between the walls and moving the ethernet cables a couple of millimeters causing disruptions.
What the application needs to do is live with the possibility that connection might break; thus - use transactions need to be sized correctly for the application so that after a commit the database is in a stable state (if there is no COMMIT and the connection breaks, the changes are rolled back, and the client application can attempt to do the changes again after from the beginning of the transaction once it re-establishes connection).