SQL tracing must be enabled for all current and future sessions that connect to the service ERP_SVC and register their module as BATCH_PROCESS and action as NIGHTLY_RUN. The tracing configuration must persist across session disconnects and instance restarts. Which procedure achieves this configuration?

The DBMSMONITOR.SERVMODACTTRACEENABLE procedure is designed specifically for this requirement. It enables SQL tracing for database sessions based on a combination of service name, module, and action. This configuration is persistent, meaning it is stored in the data dictionary and remains active across session disconnects and database instance restarts. New sessions matching the specified criteria will automatically have tracing enabled. This method provides a granular and persistent way to trace specific application components without manual intervention.

A. DBMSSESSION.SESSIONTRACEENABLE enables tracing only for the current session and is not persistent; it ends when the session disconnects.
C. DBMSAPPLICATIONINFO.SETACTION is used by an application to set the action name for its current session; it does not enable tracing.
D. DBMSSYSTEM.SETEV is an older, undocumented procedure for setting events in another session and is not the standard or supported method for persistent tracing.

1. Oracle Database PL/SQL Packages and Types Reference, 23ai. "DBMSMONITOR Subprograms". The documentation for SERVMODACTTRACEENABLE Procedure states it "Enables SQL tracing for a given service name, module, and action."

2. Oracle Database Performance Tuning Guide, 23ai. Chapter 12, "SQL Trace and TKPROF". Section "Enabling and Disabling SQL Trace for a Specific Service, Module, and Action". This section details the usage and persistence of this procedure.