Monitoring Query Runtime Statistics
You can monitor runtime trends and deviations from runtimes of successfully executed BW applications. These include BW applications, BW application objects, and InfoProviders. Select the relevant BW applications from:
Available BW applications (BW applications, BW application objects, and InfoProviders)
|
BW Applications |
BW Application Objects |
Info Providers |
|
Web templates Workbooks |
Queries Query views Planning functions Web items |
InfoObjects InfoCubes DataStore objects InfoSets MultiProviders Aggregation levels |
You use the time trends to analyze and optimize system performance. They also allow you to identify BI objects that are adversely affecting system performance.
- In the Detailed Navigation pane, under Query Runtime Statistics, select the <BI application>.NoteNote <BI application> can be BW application statistics, BW application object statistics, InfoProvider statistics. or Report data availability status
- On the <BI application> Statistics screen, in the BI Systems Selection area, select your BW System.
- On the <BI application> Statistics screen, in the BI Application Selection area, select your BWI application from the list.
You must choose at least one BW application to display the performance details.
- Choose Submit.
- Check the following iViews for BW applications:
Short-Term Trends in Total Runtimes of <BWI Applications>
You can view changes to the runtimes of BW applications successfully executed in the last 24 hours. This iView is graphical and provides the following information:
| Information | Description |
|---|---|
|
Total Time |
Total time taken (in seconds) to successfully execute individual processes (for example, data manager or OLAP processing) of the BW application. The value is rounded to the nearest second. |
|
Hour |
Hour during which the BI application was successfully executed.
If the BI application object was successfully executed during the third hour of 24 hours, the graph displays 3. |
|
<BW application> |
Technical names of up to five BW applications with the longest runtimes. |
Long-Term Trends in Total Runtimes of <BWI Applications>
You can view changes to the runtimes of BW applications successfully executed in the last 30 days. This iView is graphical and provides the following information:
| Information | Description |
|---|---|
|
Total Time |
Total time taken (in seconds) to successfully execute individual processes (for example, data manager or OLAP processing) of the BW application. The value is rounded to the nearest second. |
|
Calendar Day |
Date on which the BW application was successfully executed. The date format is day.month.year (DD.MM.YEAR). |
|
<BW application > |
Technical names of up to five BW applications with the longest runtimes. |
Runtimes of <BWI Applications>
You can view the durations for successfully executed BW applications. In this view, you can also see the runtimes for individual processes, such as data manager or OLAP processing. This iView is tabular and provides the following information:
| Information | Description |
|---|---|
|
Tp. (Type) |
Icon for BW application type. For example, |
|
<BW application> |
Technical name of the <BW application>. |
|
Total Time |
Total of all runtimes (in seconds) for the individual processes involved in successfully executing the BW application. |
|
Front-End Time |
Runtime (in seconds) for successful execution of the front-end processing for the BW application. Note
Note This only applies to BW applications.
|
|
OLAP Time |
Runtime (in seconds) for successful execution of the OLAP processing for the BI application. |
|
Data Manager Time |
Runtime (in seconds) for successful execution of the data manager processing for the BI object. |
|
Planning Time |
Runtime (in seconds) for planning activities involved in successful execution of BW applications. Note
Note This field is only relevant for to BW applications.
|
|
Other Times |
Runtime (in seconds) for activities that are not assigned to Front-End Time, OLAP time, Data Manger Time, Planning Time. Note
Note This field is only relevant for to BW applications.
|
|
Average <BW application> Count per hour during last 24 hours |
Average number of successful executions per hour of BW applications for the last 24 hours. |
|
Average <BW application> Count per day during last 30 days |
Average number of successful executions per day of BW applications for the last 30 days. |
|
Average <Bw application> Count per hour during last 30 days |
Average number of successful executions per hour of BW applications for the last 30 days. |
is displayed for a query.Deviations in Runtimes of <BWI Applications>
You can view the deviation between the short-term runtime (last hour) and long-term runtime (last 24 hours) of a successfully executed BW object. In this iView, you can also compare the short-term and long-term runtimes. This iView is tabular and provides the following information:
| Information | Description |
|---|---|
|
Tp. (Type) |
Icon for BW object type. For example, |
|
BW Application |
Technical name of the Bw application. |
|
Dev. in % (Deviation) |
Deviation (in percentage) between the short-term runtime (last hour) and long-term runtime (last 24 hours) of a successfully executed BW object. |
|
Short-Term Total Time |
Total time taken (in seconds) to successfully execute the BW object during the last 24 hours. The value is rounded to the nearest second. |
|
Long-Term Total Time |
Total time taken (in seconds) to successfully execute the BW object during the last 30 days. The value is rounded to the nearest second. |
is displayed for a query.Report data availability status of <BWI Applications>
You can view the deviation between the short-term runtime (last hour) and long-term runtime (last 24 hours) of a successfully executed BW object. In this iView, you can also compare the short-term and long-term runtimes. This iView is tabular and provides the following information:
| Information | Description |
|---|---|
|
Target Object Type |
Type (TLOGO) of Reporting Object |
|
Infoprovider |
Technical name of the Infoprovider on which Query is built |
|
Data target type |
Type (TLOGO) of the affected Data target that is part provider to InfoProvider |
|
Data target Name |
Technical Name of the affected data target that is part provider to InfoProvider.. |
|
Cause for data load failure |
Data will not be available for various reasons. Following reasons will be captured by this monitor: 1. Errors when loading data to PSA 2. Requests in Data target is not available for reporting 3. Process Chain was scheduled to run. But it was not run due to unexpected system behavior. 4. Predecessors of Data Load processes in Process Chain failed |
|
Timestamp of last failed load |
Date and time at which dataload to data target failed. The date format is day.month.year hours:minutes:seconds (DD.MM.YEAR HH:MM:SS), for example, 06.10.2006 22:26:34. |
|
Timestamp of last successful Load |
Date and time of last Successful data load to Data Target. The date format is day.month.year hours:minutes:seconds (DD.MM.YEAR HH:MM:SS), for example, 06.10.2006 22:26:34. |
|
Erroneous BW type |
Type (TLOGO) of the object responsible for report unavailability. If the cause of error is Process Chain, this field will have the value RSPC. |
|
Erroneous BW Object |
Technical name of the object responsible for report unavailability. If the cause of Data load error is Process Chain, this field will have the technical name of Process Chain |
|
Error Request ID |
Erroneous request ID |
|
No. of Err. Requests |
Number of requests in Data Target that are not available for Reporting. |
You can identify the BW applications that are adversely affecting system performance. You use the available report-report interfaces (RRIs) to further analyze these Bw applications to ascertain why they are affecting system performance.