10035 event tracing no more records sql_texts to alert.log
Cursordump is the way to go. Parse failures are actually not stored in data dictionary and therefore can not be identified through querying the data dictionary. As of Oracle 10g, event 10035 can be used to report on all failed parses. With 19.16 Release Update, Oracle does not record sql statements to alert.log. Any statement that fails at parsing stage, is recorded with the error number and the process OSPID. Also setting hidden "_kks_parse_error_warning" parameter to 1, does not help reporting the failed sql statements. I tried changing the levels(1-128) of tracing but I could not the be successful to detect the failed statements. It is recorded as below after 19.16 RU. Sql statement is no more recorded in alert.log. I have searched x$kglob table, which is the primary library cache object underneath v$sql view. kglnaobj column of x$kglob table can be used to detect these failing sql statements, but its data type is VARCHAR2(1000). For statements which are longer tha