Database Reference
In-Depth Information
PARSE ERROR Entry Format
Failing parse calls due to incorrect syntax or insufficient privileges result in errors such as
“ORA-00942: table or view does not exist” or “ORA-00904: invalid identifier”. Such errors are
marked by
PARSE
ERROR
entries. Here's an example of a parse error due to an incorrectly spelled
column name:
PARSING IN CURSOR #6 len=93 dep=0 uid=30 oct=2 lid=30 tim=170048888062 hv=986445513
ad='676bb350'
INSERT INTO poem (author, txt) VALUES(:author, empty_clob())
RETURNING ROWID INTO :row_id
END OF STMT
PARSE #6:c=0,e=457,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=170048888050
=====================
PARSING IN CURSOR #7 len=198
dep=1
uid=0 oct=3 lid=0 tim=170048915712 hv=4125641360
ad='67b0c8d4'
…
PARSE ERROR #6:len=93 dep=0 uid=30 oct=2 lid=30 tim=170048972426 err=904
INSERT INTO poem (author, txt) VALUES(:author, empty_clob())
RETURNING ROWID INTO :row_id
As in the preceding example, the DBMS may need to run recursive SQL statements (
dep=1
)
to process the parse call in order to load the dictionary cache. Abbreviations used are analo-
gous to
PARSE
entries, except for the last field
err
, which indicates the ORACLE error number.
On UNIX systems, the error message text can be retrieved by calling
oerr
ora
error_number
from a shell command line. Where appropriate, the output of
oerr
also includes a probable
cause of the error and suggests an action. The same information is available by looking up the
error number in the
Oracle Database Error Messages
manual.
$ oerr ora 942
00942, 00000, "table or view does not exist"
// *Cause:
// *Action:
EXEC Entry Format
EXEC
entries have the same format as
PARSE
entries.
EXEC
is short for execution. The minimum
SQL trace level for enabling
EXEC
entries is 1.
INSERT
,
UPDATE
,
DELETE
,
MERGE
, PL/SQL, and DDL
operations all have an execution stage, but no fetch stage. Of course, recursive fetches at a
higher recursive call depth may occur on behalf of these operations. When formatting a trace
file containing a large number of these operations with TKPROF, you might want to sort the
statements with the option
exeela
(execute elapsed time). Execute elapsed time includes the
CPU time consumed by
EXEC
entries, though occasionally higher values of CPU than elapsed
time are reported.
FETCH Entry Format
FETCH
entries adhere to the same format as
PARSE
and
EXEC
entries. The minimum SQL trace
level for enabling
FETCH
entries is 1. When formatting a trace file where fetching contributes
