To analyze the statistics data, you have the following options:
● Using the database tables or the predefined views
● Using the technical content
● In BI Administration Cockpit
To analyze the statistics data for selected queries or Web templates, you have the following options:
● Using the query monitor (transaction RSRT1)
● Using BEx Web
The statistics data is spread over a number of different database tables.
It is therefore easiest to use two predefined views (RSDDSTAT_OLAP and RSDDSTAT_DM). You use Data Browser (transaction SM16) to do this.
● View RSDDSTAT_OLAP contains the data from the events in the areas for the front end and calculation layer in the analytic engine (Front End/Calculation Layer):
Field |
Description |
SESSIONUID |
UID of the user session (a role area) |
STEPUID |
UID of the user step |
HANDLEID |
Counter for the runtime object |
HANDLETP |
Type of runtime object |
EVENTID |
ID (NUMC9) of the event from the RSDDSTATEVENTS table |
UNAME |
User name |
STEPTP |
Type of step (RSDDSTATSTEPTP table) |
STEPCNT |
Ascending count of steps |
UTIME |
Time (type TIMS) from STARTTIME field |
CALDAY |
Calendar day (type DATS) from STARTTIME field |
RUNTIME |
Duration of a step in seconds |
INFOPROV |
InfoProvider (if valid) |
OBJNAME |
Name of the runtime object (such as query or Web template) |
OBJPROP |
Properties of the object encoded as CHAR10 Example for queries: ● Read mode (see data element RSRREADMODE) ● Mode for data integrity (see data element RRACTUALDATA) ● Delta cache on/off (see data element RRDELTACACHE) ● Partition mode (see data element RRSPPARTIONMODE) ● Cache mode (see data element RSRCACHEMODE) ● Persistence mode (see data element RSRPERSISTMODE) |
STATLEVEL |
Statistics detail level (0, 1, 2) |
EVTIME |
(Net) Runtime of event |
EVCOUNT |
Counter for this event (not required for all events) |
EVENTIDCNT |
Number of calls for this event (for internal use only) |
STARTTIME |
Start time of step in yyyymmddhhmmss,mmmuuun format |
● View RSDDSTAT_DM contains the event data from the area for the aggregation layer and analytic engine:
Field |
Description |
STEPUID |
UID of the user step |
HANDLEID |
Counter for the runtime object |
HANDLETP |
Type of runtime object |
DMUID |
UIP for data manager access |
ACCESSCNT |
Data access counter (for example, database, BI Accelerator, RFC) during a data manager event |
UNAME |
User name |
UTIME |
Time (type TIMS) from STARTTIME field |
CALDAY |
Calendar day (type DATS) from STARTTIME field |
OBJNAME |
Name of the runtime object (such as query or Web template) |
INFOPROV |
InfoProvider |
PARTPROV |
If INPROV is a MultiProvider, PARTPROV specifies the InfoProvider contained in it |
AGGREGATE |
Technical name of the aggregate or BIA index (if applicable) |
TABLTP |
Type of fact table (F or E) if InfoCube or aggregate accessed |
TIMEDMPREP |
Preparation time of data access, for ACCESSCNT = 0 only, since not parallel |
TIMEDMPOST |
Postprocessing time for data, for ACCESSCNT = 0 only, since not parallel |
TIMEREAD |
Data read time (database, RFC for example) |
TIMESID |
Time for calculation/determination of new SIDs |
TIMENAVATTR |
Time for reading master data |
TIMEHIERARCHY |
Time for hierarchy handling |
DBSEL |
Number of records read from the database |
DBTRANS |
Number of records transferred |
WP_ID |
ID of the work process where the (possibly parallel) data read access was made |
STARTTIME |
Start time of step in yyyymmddhhmmss,mmmuuun format |
With predefined queries and Web templates for technical content, you can analyze the data from BI query runtime statistics for queries and BI Web applications. The data is stored in the relevant InfoProvider objects for technical content.
Prerequisites for this are that you have activated the technical content (see Installing BI Content) and the BI administrator role is assigned.
You can analyze the data from BI query runtime statistics in BI Administration Cockpit based on objects for technical content.
Using the statistics data in the query monitor, you can perform an ad hoc analysis at query runtime (see Query Monitor).
...
1. Select a query and choose Execute + Debug. The Debug Options dialog box appears.
2. Select the flag for debug option Display Statistics Data and run the query.
3. When the query is run and is displayed with the various navigation steps, press F3 (Back).
The Statistic Data for Query Runtime screen appears. The data for the area for the front end and calculation layer of the analytic engine (Front End/Calculation Layer), and the data for the area for the aggregation layer of the analytic engine are displayed on two separate tab pages.
Using the URL parameter "&profiling=x", you can analyze the BI query runtime statistics of a Web template for the administrator in expert mode.
We only recommend using this setting if performance problems arise for a particular Web template.
More information: Displaying BI Query Runtime Statistics on the Web