Default KPIs for BW
This is a completed list of delivered default KPIs for BW monitoring.
KPI name |
Description | Unit |
Monitoring area |
Long description |
Collected on |
Collected for |
Server-specification |
Collector |
Profile |
Recommended period |
---|---|---|---|---|---|---|---|---|---|---|
BW_12503CNT |
Java Stack: Number of OLAP stats with event 12503 |
Count |
JAVAST |
This KPI displays the number of OLAP statistics with the event number 12503 in the table RSDDSTAT_OLAP. The event number 12503 represents a successful end of the web template. When a web template with v7 starts, it first creates an entry for the event number 12502 in the table RSDDSTAT_OLAP. If the web template finishes successfully, a new entry with the event number 12503 is created. If this template fails on Java Stack, only an entry for the event number 12502 is available in the table RSDDSTAT_OLAD. Here, an entry with the event number 12503 is not available. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_JAVAST_EVT |
BW_5MIN |
5 minutes |
BW_12503CNT_NOTA |
Java Stack: Number of 12503 events on non-authorized node |
Count |
JAVAST |
This KPI displays the number events with the number 12503 that occurred on a non-authorized node. The event number 12503 represents a successful end of the web template. When a web template with v7 starts, it first creates an entry for the event number 12502 in the table RSDDSTAT_OLAP. If the web template finishes successfully, a new entry with the event number 12503 is created. If this template fails on Java Stack, only an entry for the event number 12502 is available in the table RSDDSTAT_OLAD. Here, an entry with the event number 12503 is not available. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_JAVAST_EVT |
BW_5MIN |
5 minutes |
BW_12503CXMN_AVG |
Java Stack: Average number of 12503 events per node |
Count |
JAVAST |
This KPI displays the average number of events with the number 12503 in the last X minutes per node. The default value is 60 minutes. You can adjust this value via the collector parameter JAVASTACK_COUNT_12503_X_MINUTES. |
Central system |
System |
Any server |
/DVD/MON_BW_CL_COL_JAVAST_EVT |
BW_5MIN |
5 minutes |
BW_12503CXMN_MAX |
Java Stack: Maximum number of 12503 events per node |
Count |
JAVAST |
This KPI displays the maximum number of events with the number 12503 in the last X minutes per node. The default value is 60 minutes. You can adjust this value via the collector parameter JAVASTACK_COUNT_12503_X_MINUTES. |
Central system |
System |
Any server |
/DVD/MON_BW_CL_COL_JAVAST_EVT |
BW_5MIN |
5 minutes |
BW_12503CXMN_MIN |
Java Stack: Minimum number of 12503 events per node |
Count |
JAVAST |
This KPI displays the minimum number of events with the number 12503 in the last X minutes per node. The default value is 60 minutes. You can adjust this value via the collector parameter JAVASTACK_COUNT_12503_X_MINUTES. |
Central system |
System |
Any server |
/DVD/MON_BW_CL_COL_JAVAST_EVT |
BW_5MIN |
5 minutes |
BW_12503CXMN_MNV |
Java Stack: Minimum variance of 12503 events per node |
Count |
JAVAST |
This KPI displays the minimum variance for events with the number 12503 in the last X minutes per node. The default value is 60 minutes. You can adjust this value via the collector parameter JAVASTACK_COUNT_12503_X_MINUTES. |
Central system |
System |
Any server |
/DVD/MON_BW_CL_COL_JAVAST_EVT |
BW_5MIN |
5 minutes |
BW_12503CXMN_MXV |
Java Stack: Maximum variance of 12503 events per node |
Count |
JAVAST |
This KPI displays the maximum variance for events with the number 12503 in the last X minutes per node. The default value is 60 minutes. You can adjust this value via the collector parameter JAVASTACK_COUNT_12503_X_MINUTES. |
Central system |
System |
Any server |
/DVD/MON_BW_CL_COL_JAVAST_EVT |
BW_5MIN |
5 minutes |
BW_12503HEAPMAX |
Java Stack: Maximum amount of heap for all nodes |
Count |
JAVAST |
This KPI displays the maximum amount of heap from all nodes. For example, if there are 10 nodes for the BW system, instead of capturing and storing the memory of each node, the collector captures the memory of the most loaded node. If the value remains at 84%, the memory consumption is too high. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_JAVAST_EVT |
BW_5MIN |
5 minutes |
BW_12503MISSUSR |
Java Stack: No. of users with 12502 and without 12503 after X mins |
Count |
JAVAST |
This KPI shows how many users have sessions with the event number 12502, but not followed by the event number 12503 after X minutes (5 minutes by default). This means that a web template has failed. A timeout occurs after 15 minutes, so a Java Stack session cannot take more than 15 minutes. However, a Java Stack session should only take a few seconds to 1 minute because it is a user tool (not batch processing). To enable monitoring of all KPIs on Java Stack, you need at least BW730SP8 and BI JAVA SP7 Patch 30. For more information, see the OSS Note 1069253 – BEx Web 7.x: Monitoring server node memory use in OLAP stats. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_JAVAST_EVT |
BW_5MIN |
5 minutes |
BW_12505NO |
Java Stack: Number of rejected queries (event 12505) |
Count |
JAVAST |
This KPI must be always zero. If there is an issue with the memory of the Java Stack (for example, the garbage collection did not finish as expected), this KPI will be greater than zero. If the memory on Java Stack is above the threshold of the parameter RSADMIN, Java Stack will reject the request (the web template will not run) and create a new entry with the event number 12505 in the table RSDDSTAT_OLAP. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_JAVAST_EVT |
BW_5MIN |
5 minutes |
BW_12640NO |
Java Stack: Number of cache refreshes (event 12640) |
Count |
JAVAST |
This KPI displays the total number of cache refreshes on Java Stack. A cache refresh occurs when Java Stack is restarted or, in exceptional cases, if you are manually forced to refresh the parameter RSADMIN. If no manual refresh occurs, This KPI displays all Java Stack restarts. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_JAVAST_EVT |
BW_5MIN |
5 minutes |
BW_9000DMMISS |
BW: Number of queries failing on DM (BWA, DB, HANA) |
Count |
BW |
When a query fails in the data manager (database or BWA), there is an entry in rsddstat_olap with the event 9000 but there are no entries in rsddstat_dm. Queries can fail on the database (e.g. dump signal 11), on BWA (e.g. if all memory is used) or on HANA. This KPI shows how stable or unstable the database and BWA are. A restart of BWA will cause several queries to fail, causing this value to increase. Failures can be due to a reorganization, a memory issue, a corrupted BWA index or a query above the safety belt of 40 million cells. No reaction is expected if there are only 1 or 2 failures, but if many queries fail at the same time, it is a general issue that needs to be addressed in order to prevent reoccurrence. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_RSDDSTATS |
BW_5MIN |
5 minutes |
BW_AGGR_USAGE |
BW: Aggregate usage |
Count |
BW |
This KPI displays the number of aggregates used by comparing rsddstataggrdir field usage per aggregate with the previous snapshot every 5 minutes. In addition, the table /DVD/MON_BWAGGRU is updated with the number of hits per aggregate per day. This allows you to identify which aggregates are not used and can be disabled to improve the runtime of change runs and rollups. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_AGGR_USAGE |
BW_5MIN |
5 minutes |
BW_DURATTRIBCHAN |
BW: Duration running attribute change run |
s |
BW |
During a change run, many BW jobs are locked, so it is important that the runtime of attribute change runs is not too long. This KPI displays the runtime of the currently running job BI_PROCESS_ATTRIBCHAN, BI_STRU* or BI_CHANGERUN_RESTART. The value of the KPI is only calculated for the running jobs and not the finished jobs, so the final actual runtime will be higher than the last value captured, but within the same range. If the runtime is too long, you can inform administrators, who can decide whether to drop aggregates if a change is too long-running (e.g. the job BICHNG). To do so, perform the following checks:
|
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_BATCH |
BW_5MIN |
5 minutes |
BW_DURCOMPRESS |
BW: Duration of the longest-running cube compression |
s |
BW |
This KPI displays the longest-running cube compression, i.e. the longest-running BI_*COMP* job. The value of the KPI is only calculated for the running jobs and not the finished jobs, so the final actual runtime will be higher than the last value captured, but within the same range. By calculating this value every few minutes, the application can raise an alert if there is a long-running cube compression and use ABAP SQL traces to investigate the performance of this cube compression. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_BATCH |
BW_5MIN |
5 minutes |
BW_DURDBINDEX |
BW: Duration of longest-running DB indexing |
s |
BW |
The SAP standard is to drop indexes before the load and recreate the indexes after the load in the process chain. This is fine for full loads, but for deltas, it can take hours to recreate the indexes. The time saved by loading a small delta can be much lower than the time it takes to recreate the indexes. This KPI displays the longest-running job BI_PROCESS_INDEX*. The value of the KPI is only calculated for the running jobs and not the finished jobs, so the final actual runtime will be higher than the last value captured, but within the same range. By calculating this value every few minutes, the application can correlate these long-running jobs and any other issues on the system. If this is not required, you can disable this KPI and instead perform a daily check of the job BI_PROCESS_INDEX*. |
Remote system |
System |
|
/DVD/MON_BW_CL_COL_BATCH |
BW_5MIN |
5 minutes |
BW_DURLOADING |
BW: Duration of longest-running DTP |
s |
|
This KPI displays the longest-running DTP, for example the longest-running BIDTPR_* job. The value of the KPI is only calculated for the running jobs and not the finished jobs, so the final actual runtime will be higher than the last value captured, but within the same range. By calculating this value every few minutes, the application can raise an alert if there is a long-running DTP and use ABAP SQL traces to investigate the performance of this DTP. |
Remote system |
System |
|
/DVD/MON_BW_CL_COL_BATCH |
BW_1HOUR |
1 hour |
BW_DURLOADIP |
BW: Duration of longest-running InfoPackage |
s |
BW |
This KPI displays the longest-running InfoPackage. From the enqueue of the running IP, CrystalBridge® Monitoring checks the start time and calculates the delay between the start time and the current time. By calculating this value every few minutes, the application can raise an alert if there is a long-running InfoPackage and use ABAP SQL traces to investigate the performance of this InfoPackage. See the table BW InfoPackages to view the top N requests, request number, number of packets, runtime, InfoPackage and DataSource. Only InfoPackages with more than 50 packets or a duration greater than 1,800 seconds are recorded. Sometimes, values are incorrect because no enqueue is visible, which can lead to missing data. However, the trend is correct even if any data is missing. |
Remote system |
System |
|
/DVD/MON_BW_CL_COL_GET_IP |
BW_1HOUR |
1 hour |
BW_DURMDACTIVAT |
BW: Duration of the longest-running MD activation |
s |
BW |
This KPI displays the longest-running master data activation job during the change run, i.e. the longest-running BIACTI_* job. The value of the KPI is only calculated for the running jobs and not the finished jobs, so the final actual runtime will be higher than the last value captured, but within the same range. By calculating this value every few minutes, the application can raise an alert if there is a long-running master data activation and use ABAP SQL traces to create the required index (usually CHANGED OBJVERS) on the tables P, Q, X and Y. |
Remote system |
System |
|
/DVD/MON_BW_CL_COL_BATCH |
BW_1HOUR |
1 hour |
BW_DURODSACTIVAT |
BW: Duration of the longest-running ODS activation |
s |
BW |
This KPI displays the longest-running ODS (DSO) activation job. This applies to DSOs where activation occurs in batch and with at least two jobs in parallel (i.e. the runtime of the running BIBCTL* jobs). The value of the KPI is only calculated for the running jobs and not the finished jobs, so the final actual runtime will be higher than the last value captured, but within the same range. By calculating this value every few minutes, the application can raise an alert if there is a long-running DSO activation and use ABAP SQL traces to analyze the issue. For example, the system might hang due to a hanging backup, lock wait, network issue, missing database index or missing database statistics. For a package size of 2,000 rows, the normal runtime is between 20 and 60 seconds. Anything above 500 seconds must be investigated. |
Remote system |
System |
|
/DVD/MON_BW_CL_COL_BATCH |
BW_1HOUR |
1 hour |
BW_D_IP_ABTHRS |
BW: Number of IPs from previous day with more than X packets. |
Count |
BW |
This KPI displays the number of requests that were running yesterday (either started or finished yesterday) with more than 100 packets. 100 is a collector parameter and can be changed. The details are available in the Details tab within the detail table BW daily stats on InfoPackages or in the table /DVD/MON_BWDIP. The KPI uses the following tables or could use them in the future:
|
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_GET_D_IP |
BW_1DAY |
1 day |
BW_ETL_EXCEEDED_PC |
BW: Number of long-running process chains |
Number |
BW |
This KPI displays the total number of long-running process chains. By default, if a process chain runs for more than 60 minutes, the collector considers this process chain to be long-running. You can define the thresholds for long-running process chains in the input table /DVD/MON_BWPCINP. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_ETL_PC |
BW_1HOUR |
1 hour |
BW_ETL_FAILED_PC |
BW: Number of failed process chains |
Number |
BW |
This KPI displays the total number of failed process chains since the last run. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_ETL_PC |
BW_1HOUR |
1 hour |
BW_ETL_FINISHED_PC |
BW: Number of successfully finished process chains |
Number |
BW |
This KPI displays the total number of successfully finished process chains since the last run. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_ETL_PC |
BW_1HOUR |
1 hour |
BW_ETL_RUNNING_PC |
BW: Number of running process chains |
Number |
BW |
This KPI displays the total number of currently running process chains. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_ETL_PC |
BW_1HOUR |
1 hour |
BW_IP_MAX_PACKET |
BW IP max number of packets (multiplied by number of target) |
Count |
BW |
InfoPackage loads spend too much on enqueues when the number of packets multiplied by the number of targets is more than 1,000. 500 packets and one target will not lead to performance issues, but if 500 packets and 10 targets exist, most of the time will be spent on enqueues and not on processing the data. Below, when the number of packets is referred to, it is always multiplied by the number of targets. This KPI displays the highest number of packets (multiplied by the number of targets) in the running InfoPackages. From the enqueue of the running InfoPackages, CrystalBridge® Monitoring checks the packet number that is available in the monitor, and we multiply by the number of targets for this InfoPackage. If there are two InfoPackages running with more than 1,000 small packets, so many enqueues are processed that the system can become very slow and 100% of the dialog work processes can be used up rapidly. By calculating this value near real time, the application can raise an alert and review the package size (roosprms) and the number of rows in the InfoPackage. For full recovery loads, if the number of packets will be very high, it can be faster to stop the load and repeat it with fewer packets. See the Details tab > BW InfoPackages to check the following information for the top N requests:
|
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_GET_IP |
BW_1HOUR |
1 hour |
BW_NR_MAX_DIFF |
BW: Maximum incremental difference of all number ranges |
Value |
BW |
This KPI displays the maximum counter increase of all BW number ranges. The detail table Number range info contains a list of the related number ranges with their consumption and buffer settings. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_NUM_RANGE |
BW_1DAY |
1 day |
BW_NR_MAX_SPEED |
BW: Maximum incremental speed of number ranges per day |
Value/day |
BW |
This KPI displays the maximum counter increase of all BW number ranges, calculated as a daily increase. The detail table Number range info contains a list of the related number ranges with their consumption and buffer settings. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_NUM_RANGE |
BW_1DAY |
1 day |
BW_NR_OVER_THR |
BW: Count of number ranges which are over threshold |
Count |
BW |
This KPI displays the count of BW number ranges identified via the defined speed or difference threshold. Both thresholds are 0 by default. If needed, you can change these threshold values with the collector parameters DIFFERENCE_THRESHOLD or SPEED_THRESHOLD. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_NUM_RANGE |
BW_1DAY |
1 day |
BW_NR_TOTAL_DIFF |
BW: Sum of all incremental differences from number ranges |
Value |
BW |
This KPI displays the total increase of all BW number ranges. The detail table Number range info contains a list of the related number ranges with their consumption and buffer settings. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_NUM_RANGE |
BW_1DAY |
1 day |
BW_NR_TOTAL_SPEE |
BW: Incremental speed from all number ranges per day |
Value/day |
BW |
This KPI displays the total increase of all BW number ranges, calculated as a daily increase. The detail table Number range info contains a list of the related number ranges with their consumption and buffer settings. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_NUM_RANGE |
BW_1DAY |
1 day |
BW_PC_STEP_COUNT |
BW: Process chain step count |
Count |
BW |
This KPI displays the number of steps that have finished since the last execution of the agent. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_PC |
BW_1HOUR |
1 hour |
BW_PC_STEP_ERR |
BW: Process chain step error |
Count |
BW |
This KPI displays the number of steps that have finished with an error since the last execution of the agent. If there are several steps with errors in the last X minutes, this can indicate a general issue on the system, for example all BTC or DIA are used up, the transaction log is full or the rollup failed because it was locked by a failed Crystal Report. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_PC |
BW_1HOUR |
1 hour |
BW_QUERY_ERROR |
BW: Number of erroneous queries |
Number |
BW |
This KPI displays the total number of erroneous BW queries, i.e. queries that have failed or contain any errors. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_QUERY_RT |
BW_1HOUR |
1 hour |
BW_QUERY_LONG_RUN |
BW: Number of long-running queries |
Number |
BW |
This KPI displays the total number of long-running BW queries. By default, if a BW query runs for more than 60 seconds, the collector considers this query to be long-running. You can define the thresholds for long-running BW queries in the input table /DVD/MON_BWQLONG. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_QUERY_RT |
BW_1HOUR |
1 hour |
BW_QUERY_RUNTIME |
BW: Number of executed queries |
Number |
BW |
This KPI displays the total number of executed BW queries in the period defined by the collector parameter TIME_PERIOD_IN_SECS. By default, it checks all BW query executions in the last 5 minutes. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_QUERY_RT |
BW_1HOUR |
1 hour |
BW_RSICCONT_GR12 |
BW: Forecast RSICCONT growth in 12 months |
Count |
BW |
This KPI displays a forecasted value for the admin table RSICCONT over 12 months. The forecasted growth is calculated by examining the speed at which the number of rows in RSICCONT increases over a month. The forecast is adjusted every day. The admin table RSICCONT contains one entry per load request, and each request goes in one InfoProvider. When there are too many rows in the table RSICCONT for the same provider, the loads/monitor will generate many enqueues, which will slow down the system. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_RSICCONT |
BW_1DAY |
1 day |
BW_RSICCONT_MX12 |
BW: Forecast RSICCONT max. number of entries per cube in 12 months |
Count |
BW |
This KPI displays the current number of rows in RSICCONT plus the forecasted growth and gives the forecasted value over 12 months (see the KPI definition for RSICCONT growth over 12 months above). The table /DVD/MON_BWRSICC in the satellite system displays the number of entries per target. When the current value or forecasted value is above 6,000–7,000, consider executing the report RSSM_REDUCE_REQUESTLIST. For more information, see the OSS Note 1431315 – P24: Reducing very large request lists in InfoCubes and DSOs. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_RSICCONT |
BW_1DAY |
1 day |
BW_RSMONMESSPAC |
BW: Sum max. number of packets for all running PSA |
Count |
BW |
This KPI displays you if many InfoProviders have a high average number of packets. Here, when several InfoProviders run with a high number of packets, it creates many enqueues to process and can overload the enqueue processing. Alternatively, if one InfoProvider has a high number of packets, you receive an alert via the KPI BW_IP_MAX_PACKET. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_GET_IP |
BW_1HOUR |
1 hour |
BW_SID_GR12 |
BW: Forecast SID growth in 12 months |
Count |
BW |
This KPI displays a forecast of the system ID (SID) growth for the next 12 months. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_SID_GROWTH |
BW_1DAY |
1 day |
BW_SID_MX12 |
BW: Forecast SID max. level in 12 months |
Count |
BW |
This KPI displays a forecast of the maximum system ID (SID) level for the next 12 months. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_SID_GROWTH |
BW_1DAY |
1 day |
BW_SSQL_ALLNO |
BW: SQL – Total number of subqueries |
Count |
BW |
This KPI displays the number of queries on the database (running SQL statement, op mode 0) in order to correlate this data with performance issues if needed. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_RSDDSTATS |
BW_1HOUR |
1 hour |
BW_SSQL_ALLTIM |
BW: SQL – Total time spent on subqueries |
s |
BW |
This KPI displays the cumulated time of all queries running on the database (running SQL statement, op mode 0) in order to correlate this data with performance issues if needed. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_RSDDSTATS |
BW_1HOUR |
1 hour |
BW_SSQL_SQAR |
BW: SQL – Average runtime of small subqueries |
s |
BW |
This KPI displays the average runtime of small subqueries. By definition, small subqueries are those that scan fewer than 10 million rows and return fewer than 10,000 rows. Queries are split into subqueries – one per cube. The runtimes of each subquery are available in the table rsddstat_olap for the query along with the option to save all statistics. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_RSDDSTATS |
BW_1HOUR |
1 hour |
BW_SSQL_SQLO |
BW: SQL – No. of small, long-running subqueries (e.g. > 10 sec.) |
Count |
BW |
This KPI displays the number of small subqueries that have been running for more than 10 seconds. By definition, small subqueries are those that scan fewer than 10 million rows and return fewer than 10,000 rows. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_RSDDSTATS |
BW_1HOUR |
1 hour |
BW_SSQL_SQNO |
BW: SQL – No. of small subqueries |
Count |
BW |
This KPI displays the number of small subqueries. By definition, small subqueries are those that scan fewer than 10 million rows and return fewer than 10,000 rows. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_RSDDSTATS |
BW_1HOUR |
1 hour |
BW_SUBQ_ALLNO |
BW: Non-SQL – Total number of subqueries (BWA or HANA) |
Count |
BW |
This KPI displays the number of queries that are executed on BWA (non-SQL). This allows you to identify any period with too many queries in parallel and look for a workaround if the memory or performance are impacted. For example, you could remove the parallelization setting of some queries. This KPI also provides a benchmark that enables you to see what can be changed without risking degradation. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_RSDDSTATS |
BW_5MIN |
5 minutes |
BW_SUBQ_ALLTIM |
BW: Non-SQL – Total time spent on subqueries (BWA or HANA) |
s |
BW |
This KPI displays the cumulated time spent on BWA for all subqueries (non-SQL). This enables you to check if a certain limit has been reached. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_RSDDSTATS |
BW_5MIN |
5 minutes |
BW_SUBQ_SQAR |
BW: Non-SQL – Average runtime of small subqueries (BWA or HANA) |
s |
BW |
This KPI displays the average BWA runtime of small subqueries (non-SQL). By definition, small subqueries are those that scan fewer than 10 million rows and return fewer than 10,000 rows. These must run for one second on BWA. When using op mode 2 in BWA, queries are split into subqueries – one per cube. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_RSDDSTATS |
BW_5MIN |
5 minutes |
BW_SUBQ_SQLO |
BW: Non-SQL – No. of small, long-running subqueries (e.g. > 10 sec.) e.g. BWA |
Count |
BW |
This KPI displays the number of subqueries that have been running for more than 10 seconds (non-SQL) if the average is slow. By definition, small subqueries are those that scan fewer than 10 million rows and return fewer than 10,000 rows. For example, the impact on the business if different there are either 5 or 5,000 subqueries that are running too slowly. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_RSDDSTATS |
BW_5MIN |
5 minutes |
BW_SUBQ_SQNO |
BW: Non-SQL – No. of small subqueries (BWA or HANA) |
Count |
BW |
This KPI displays the number of small subqueries (non-SQL). By definition, small subqueries are those that scan fewer than 10 million rows and return fewer than 10,000 rows. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_RSDDSTATS |
BW_5MIN |
5 minutes |
FBW_BGPROC_SIZE |
BW background process size (total) |
MB |
BW |
This KPI displays the total size of following BW batch management tables:
|
Remote system |
System |
Any server |
/DVD/MON_CL_COL_TAB |
FS_BW |
1 day |
FBW_CHLG |
Changelog size (total) |
MB |
BW |
This KPI displays the total size of all BW changelog tables. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_PSACHLG |
FS_BW |
1 day |
FBW_PSA |
PSA table size (total) |
MB |
BW |
This KPI displays the total size of all PSA tables. |
Remote system |
System |
Any server |
/DVD/MON_BW_CL_COL_PSACHLG |
FS_BW |
1 day |
FBW_STAT_SIZE |
BW statistics size (total) |
MB |
BW |
This KPI displays the total size of BW statistics (OLAP) tables:
|
Remote system |
System |
Any server |
/DVD/MON_CL_COL_TAB |
FS_BW |
1 day |