Show TOC

Procedure documentationUser End to End Trace Locate this document in the navigation structure

 

This function in the SAP/Oracle DBA Cockpit lets you set the trace for individual users on the Oracle database. The Oracle database server writes a trace for all actions that the user executes.

Do not confuse this trace with SAP transaction ST05. Only use the trace when SAP/Oracle Development Support requests you to do so for problem diagnosis.

Prerequisites

The trace files are written to the directory specified by the Oracle parameter USER_DUMP_DEST, normally $ORACLE_HOME/saptrace/usertrace.

Caution Caution

When the trace is active, make sure that there is enough space in the file system containing the trace directory.

End of the caution.

There are the following restrictions for the trace:

  • It is only available as of SAP Kernel 7.1 and Oracle 10.2.0.2.

  • The SAP schema users of the database that is, SAP<SID>, SAPR3, or SAPSR3 must have the EXECUTE permissions to the package DBMS_MONITOR.

    This means that user SYS must have executed GRANT EXECUTE ON DBMS_MONITOR TO SAP<SID>.

Procedure

  1. Choose   Performance   Additional Functions   User End to End Trace   in the DBA Cockpit.

  2. Enter a user name in SAP user, paying attention to uppercase or lowercase.

  3. If you want to include wait information in the trace, select Tracing Waits.

  4. If you want to include bind information in the trace, select Tracing Binds.

  5. Choose Enable Trace to start the trace.

    You can see a list of all users with an active trace.

    Note Note

    The trace remains active even after a stop and restart of the database. Therefore, you have to explicitly turn it off.

    End of the note.

  6. To turn off the trace, select it from the list of active traces and choose Disable Trace. If required, you can turn off multiple or all traces.

    SAP/Oracle Development Support can evaluate the trace files using Oracle command line tools (such as trcsess).