How I can determine which SQL statement triggered an Oracle error?
You can generally look in the corresponding log or trace file to find out which SQL statement has triggered an error. If this is not possible in your particular case, you can activate a more precise logging process in Oracle for a specific error code (for example, tracing for ORA-00942 -> = 942): ALTER SYSTEM SET EVENTS = ‘ trace name errorstack forever, level 1’; If an SQL statement now triggers an error, Oracle creates a detailed trace file in the usertrace directory. This file includes, among other things, the triggering SQL statement.
Related Questions
- Processing of sql scripts created by Recovery for Oracle does not rebuild the database and/or produce any error messages. What is the problem with?
- MicroStation GeoGraphics has returned an Oracle error message. How can I determine what the error message really means?
- Can Web Cache be setup to determine failure of different Oracle Application Server components?