Examine this list of possible tasks:
1. Ensure thatSTATISTICS_LEVELis set toTYPICALorALL.
2. Ensure thatTIMED_STATISTICSis set toTRUE.
3. SetMAX_DUMP_FILE_SIZE to UNLIMITEDandDIAGNOSTIC_DESTto an
appropriate destination.
4. Ensure thatSQL_TRACEis set toTRUE.
5. Enable tracing at the database instance level by using
theDBMS_MONITOR.DATABASE_TRACE_ENABLEprocedure.
6. Enable tracing in the required session by using
theDBMS_SESSION.SET_SQL_TRACEprocedure.
7. RunTKPROFwith theEXPLAINparameter on the output trace file.
8. Run thetrcsessutility on the output trace files, and then runTKPROFon the output of
thetrcsessutility.
Select the minimum tasks to perform, in the correct order, to generate both a formatted trace
file with timing information and an explain plan for each SQL statement for all
sessions.(Choose the best answer.)
A.
1, 2, 5, 8
B.
1, 3, 6, 7
C.
2, 4, 5, 8
D.
1, 3, 4, 5, 6, 7
E.
1, 2, 4, 8
imo A – correct.
there mustn’t be the 4th cuz it’s about individual session tracing and have to be the 8th cuz we need trcsess to consolide files.
A
A but why not E ? beacuse restart required ??
Extract from documentation: The SQL_TRACE parameter is deprecated. Oracle recommends that you use the DBMS_MONITOR and DBMS_SESSION packages instead. SQL_TRACE is retained for backward compatibility only.