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
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?
2 and 4
2 and 5
3 and 4
3 and 5
Tracing information is present in multiple trace files and you must use the trcsess tool to collect it into a single
Not 1: Parameter service_nameName of the service for which tracing is enabled.
Name of the MODULE. An optional additional qualifier for the service.
* 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 wild-card, 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.
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);