Your database has the SRV1 service configured for an application that runs on middle-tier
application server. The application has multiple modules. You enable tracing at the service level
by executing the following command:
SQL > exec DBMS_MONITOR.SERV_MOD_ACT_TRACE_ENABLE (‘SRV1’);
The possible outcome and actions to aggregate the trace files are as follows:
1. The command fails because a module name is not specified.
2. A trace file is created for each session that is running the SRV1 service.
3. An aggregated trace file is created for all the sessions that are running the SRV1 service.
4. The trace files may be aggregated by using the trcess utility.
5. The trace files be aggregated by using the tkprof utility.
Identify the correct outcome and the step to aggregate by using tkprof utility?
A.
1
B.
2 and 4
C.
2 and 5
D.
3 and 4
E.
3 and 5
Explanation:
Tracing information is present in multiple trace files and you must use thetrcsesstool
to collect it into a single file.
Incorrect:
Not 1: Parameter service_name
Name of the service for which tracing is enabled.
module_name
Name of the MODULE. An optional additional qualifier for the service.
Note:
* The procedure enables a trace for a given combination of Service, MODULE and ACTION name.
The specification is strictly hierarchical: Service Name or Service Name/MODULE, or Service
Name, MODULE, and ACTION name must be specified. Omitting a qualifier behaves like a wildcard, so that not specifying an ACTION means all ACTIONs. Using the ALL_ACTIONS constant
achieves the same purpose.
* SERV_MOD_ACT_TRACE_ENABLE Procedure
This procedure will enable SQL tracing for a given combination of Service Name, MODULE and
ACTION globally unless an instance_name is specified.* DBMS_MONITOR.SERV_MOD_ACT_TRACE_ENABLE(
service_name IN VARCHAR2,
module_name IN VARCHAR2 DEFAULT ANY_MODULE,
action_name IN VARCHAR2 DEFAULT ANY_ACTION,
waits IN BOOLEAN DEFAULT TRUE,
binds IN BOOLEAN DEFAULT FALSE,
instance_name IN VARCHAR2 DEFAULT NULL);
4 – TRUE
Tracing information is present in multiple trace files and you must use the trcsess tool to collect it into a single file.
2 – TRUE
trace can be activated for multiple sessions based on various combinations of the service_name, module, action columns in the V$SESSION view,
Activating trace on multiple sessions means that trace information is spread throughout many trace files. For this reason Oracle 10g introduced the trcsess utility, which allows trace information from multiple trace files to be identified and consolidated into a single trace file. The trcsess usage is listed below.
B
B.
2 and 4
A
Module name is mandatory parameter. It fails otherwise. Tested!
http://docs.oracle.com/cd/B19306_01/appdev.102/b14258/d_monitor.htm#i1002459
Answer is A. It fails!
SUN, you are seeing a different procedure SERV_MOD_ACT_STAT_ENABLE
B Correct Answer
B
Tracing information is present in multiple trace files and you must use the trcsess tool to collect it into a single file.
Answer: B
Answer A
http://docs.oracle.com/cd/B19306_01/appdev.102/b14258/d_monitor.htm#i1002459
“module_name : Name of the MODULE. An additional qualifier for the service. It is a required parameter.”
Answer is B .
module_name is an optional additional qualifier.
http://docs.oracle.com/cd/B19306_01/appdev.102/b14258/d_monitor.htm#i1002459
ERV_MOD_ACT_TRACE_ENABLE Procedure Parameters
————————————————–
Parameter Description
service_name Name of the service for which tracing is enabled.
module_name Name of the MODULE. An optional additional qualifier for the service.
B
able 99-11 SERV_MOD_ACT_TRACE_ENABLE Procedure Parameters
Parameter Description
service_name
Name of the service for which SQL trace is enabled
module_name
Name of the MODULE for which SQL trace is enabled. An optional additional qualifier for the service. If omitted, SQL trace is enabled or all modules and actions in a given service.
Tracing information is present in multiple trace files and you must use the trcsess tool to collect it into a single file.
B
B: tested:
SQL> select name from v$services;
NAME
—————————————————————-
pdb1
cdb12cXDB
cdb12c
SQL> exec DBMS_MONITOR.SERV_MOD_ACT_TRACE_ENABLE (‘CDB12C’);
PL/SQL procedure successfully completed.
SQL> exec DBMS_MONITOR.SERV_MOD_ACT_TRACE_DISABLE(‘CDB12C’);
PL/SQL procedure successfully completed.
trcess is wrong: trcsess
may be: C, because trcess is wrong. Binary tkprof is still availably in 12c
“trcess” might be a typo, these questions have a lot of typos… anyone met the question during the exam to confirm?