Shulou(Shulou.com)05/31 Report--

This article mainly explains "how to solve Oracle using errorstack to track tomcat error ORA-00903", the content of the article is simple and clear, easy to learn and understand, the following please follow the editor's ideas slowly in-depth, together to study and learn "how to solve Oracle using errorstack to track tomcat error ORA-00903" bar!

The phenomenon tomcat error log reports ORA-00903: invalid table name intermittently. There is no specific SQL and table name. You need to find out which code has written an invalid table name. You can track the error SQL through the errorstack provided by ORACLE. As the production data can not be extracted, the following are test environment test restore production errors. About setting errorstack for errorstack. When a specific ORA error occurs, the session, statement and trace file of each process are recorded. There is a location of the trace file in the alert log where the error record is recorded. You can also open errorstack for a separate session to track the session error message. You can turn on / * level 0 dump error stack only / * level 1 dump error stack and function call stack / * level 2 Level 1 + ProcessState/* level 3 Level 2 + Context area (show all cursors, highlight the current cursor) (1) alter session/systemalter session/system set events' trace name errorstack level 3' / * error_number is the number after the ORA error. (2) for oradebug/* to use oradebug, users need to have sysdba permissions: SQL > oradebug setospid/setmypid/setorapid; SQL > oradebug dump errorstack 3 can check the current system enabled errorstack status by using the following methods: SQL > set serveroutput onSQL > oradebug setmypidSQL > oradebug eventdump session/system; tracking SQL > alter system set events' 903 trace name errorstack level 3'

Alter log:

Tue Jun 09 14:23:44 2020OS Pid: 10855 executed alter system set events' 903 trace name errorstack level 3' tracking result

Alert log information:

Tue Jun 0914: 28:04 2020Errors in file / u01/app/oracle/diag/rdbms/honor/honor1/trace/honor1_ora_7205.trc:ORA-00903: invalid table name Tue Jun 0914: 28:06 2020Dumping diagnostic data in directory= [CDMP _ 20200609142806], requested by (instance=1, osid=7205), summary= [abnormal process termination].

View the corresponding trc tracking file:

* SESSION ID: (26.661) 2020-06-09 1414 SESSION ID: (26.661) 2020-06-09 1428 laze 04.303 QR * CLIENT ID: () 2020-06-09 1414 GLV 04.303 QR * SERVICE NAME: (honor) 2020-06-09 141414141414141414141414lv 04.303mm * MODULE NAME: (SQL*Plus) 2020-06-09 1414JV 2828 JV 04.303mm * ACTION NAME: () 2020-06-09 14:28:04 .303dbkedDefDump (): Starting a non-incident diagnostic dump (flags=0x0 Level=3, mask=0x0)-Error Stack Dump-ORA-00903: Spanish-Current SQL Statement for this session (sql_id=0vaqwchf1y3fq)-insert into null values (1)

Find the specific sql, take it to the developer, modify the relevant logic, and fix the error.

Close errorstack

SQL > alter system set events' 903 trace name errorstack off'; Thank you for your reading, the above is the content of "how to solve Oracle using errorstack to track tomcat error ORA-00903". After the study of this article, I believe you have a deeper understanding of how to solve the problem of Oracle using errorstack to track tomcat error ORA-00903. The specific use of the situation also needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.