What is the reason for this?

In a user session, tracing is enabled as follows:
SQL> EXECUTE
DBMS_TRACE.SET_PLSQL_TRACE(DBMS_TRACE.TRACE_ENABLED_LINES);
PL/SQL procedure successfully completed.

You executed the procedure as follows:
SQL> EXECUTE PROC10
PL/SQL procedure successfully completed.
When you examine the PLSQL_TRACE_EVENTS table, you find that no trace information was
written into it.
View the Exhibit.

What is the reason for this?

In a user session, tracing is enabled as follows:
SQL> EXECUTE
DBMS_TRACE.SET_PLSQL_TRACE(DBMS_TRACE.TRACE_ENABLED_LINES);
PL/SQL procedure successfully completed.

You executed the procedure as follows:
SQL> EXECUTE PROC10
PL/SQL procedure successfully completed.
When you examine the PLSQL_TRACE_EVENTS table, you find that no trace information was
written into it.
View the Exhibit.

What is the reason for this?

A.
The PROC10 procedure is created with the invoker’s right.

B.
The PROC10 procedure is not compiled with the DEBUG option.

C.
Tracing is not enabled with the TRACE_ENABLED_CALLS option.

D.
The TRACE_ENABLED parameter is set to FALSE for the session.



Leave a Reply 2

Your email address will not be published. Required fields are marked *


heena

heena

Any subprogram should be enabled with DEBUG option to trace calls, lines or events.
B