SAP Support Service Document - Lenoir-Rhyne...

Service Report

Service CenterTelephoneFax

Date of Session 8.02.2007 <dat_dummy> Session No.Date of Report 8.03.2007 Installation No.Author EarlyWatch Alert Service Customer No.

<Watermark>

SAP EarlyWatch Alert

SAP System ID ABC

SAP Component NW

Release 04

Status Productive

DB System ORACLE 9.2.0.8.0

Customer

1 Service Summary

1 Service Summary

During this EarlyWatch Alert Session, we detected potential problems concerning your system.We recommend that you take corrective action as soon as possible.

Note: All recommendations provided in this report are based on our general experience only. We advise you to test our recommendations before using them in your production system. Also note that EarlyWatch Alert is an automatic service.Section Overview

Rating Checked AreaSystem ConfigurationSystem PerformanceWorkload DistributionSAP System OperatingDatabase SettingsDatabase AdministrationBW ChecksSecurity Checks

Note: For more information about EarlyWatch Alert, a sample EarlyWatch Alert report with explanations is available in the Media Library on SAP Service Marketplace (http://service.sap.com/ewa). This provides an overview of the check rating strategy and the KPIs that trigger the EWA alerts.

Alert Message OverviewPriority Description New AlertMedium There are security issues in your system. NewMedium Your database is growing very rapidly. New

Note: If you need help investigating the alerts listed, order an EarlyWatch contract by contacting your local support organization, or by creating a customer message in component XX-SER-TCC. If you already have such a contract, a detailed analysis can be performed during the next Service Session. Please address the topic during the preparation of the session. Note: If you experience serious performance problems, create a customer message on component XX-SER-TCC with priority 'high' or 'very high'.

EarlyWatch Alert Report , , 8.03.2007 2

2 Performance Indicators

2 Performance IndicatorsThe following table shows the relevant performance indicators in various system areas.

Area Indicators Value TrendSystem Performance Active Users 18 downHardware Capacity Max. CPU Utilization on DB Server 74 % steady

Max. CPU Utilization on Appl. Server 74 % steadyDatabase Space Management DB Size 355.52 GB steady

Last Month DB Growth 118.63- GB steadyQuery Performance Avg. Total Runtime of the BW Queries 11.5 s down

Avg. Database Runtime of the BW Queries 8.0 s steady

3 Recommended ServiceThe analysis of your SAP EarlyWatch Alert service session has shown that your installation has a high optimization potential. Therefore, SAP would highly recommend you to perform following service:

Service Issue Scope Benefit Average Consulting Days

SAP Security Optimization Service

Some users have critical authorizations in certain transactions

Increase of security in your SAP System

Avoids severe security problems in your SAP solution

1

Special BI Service

A special BI service based on the BI Key Performance Indicators is recommended

To find details about this BI service, please have a look at chapter 'BI - KPIs'

BI Service type dependent

-

4 System ConfigurationTo ensure optimal support of your SAP system, the SAP components, database, and operating system used must all be supported. Detailed information about SAP's platform support is available on SAP Service Marketplace at http://service.sap.com/platforms.

Rating CheckHardware ConfigurationSoftware ConfigurationSAP Service Preparation

5 Hardware ConfigurationThe table below shows the detected hardware configuration:

HARDWARE CONFIGURATIONServer Type Server OS OS Version Number of CPUs Memory [MB]Others usnasap101 AIX 5.3 8 8192Database Server usnasap123 AIX 5.3 14 18432

DATABASE SYSTEMDatabase Server Database System Current Versionusnasap123 ORACLE 09.2.0

6 Software ConfigurationThe table below shows the installed software components. The "Rating" column is filled only for the SAP R/3 Plug-In (PI) and SAP Basis Plug-In (PI_BASIS), and is based on the maintenance schedule.

COMPONENTSComponent Component Release Patch Level RatingBI_CONT 353 0003PI_BASIS 2005_1_640 0003SAP_ABA 640 0013


4 System Configuration

Component Component Release Patch Level RatingSAP_BASIS 640 0013SAP_BW 350 0013ST-A/PI 01H_BCO640 0000ST-PI 2005_1_640 0004

7 SAP Kernel Release

Your SAP kernel release (release 640, patch level 151) is not up to date.

Recommendation: Ensure that you are using the latest SAP kernel. See SAP Notes 19466 and 138704. (These notes refer to further SAP Notes, depending on your system characteristics.)

8 SAP Service PreparationFor detailed information about the required steps, see SAP Note 91488 (SAP Support Services: Central preparation note). Please ensure that all the functionality mentioned in the SAP Note is up to date, especially connections, collectors, and service tools.9 SAP Service Tools

Before we can deliver any services, the latest version of the SAP Service tools must be available in your system.

The last run of report RTCCTOOL was 20.11.2006.

Recommendation: You should run report RTCCTOOL, as described in the SAP Note 91488, to update tool release information. In case of missing transports detected by RTCCTOOL, implement the recommendations given by the tool.



10 BW Workload11 Workload per User and Navigation Steps

This overview takes into account the following:- The number of users who execute queries (grand total)- This number is grouped according to InfoConsumer, Executive, and Power User (totals), depending on their number of navigation steps- The InfoConsumer is divided again according to the number of navigation steps (subtotals).- The timeframe is the last complete week from Monday to Sunday.

User/Consumer NumberGrand total: Users performing queries 92Total: Info Consumer [1 - 400 Nav Steps/ week] 91...Sub total: Info Consumer 1-10 Nav Steps/ week 29...Sub total: Info Consumer 11-50 Nav Steps/ week 41...Sub total: Info Consumer 51-100 Nav Steps/ week 10...Sub total: Info Consumer 101-200 Nav Steps/ week 8...Sub total: Info Consumer 201-300 Nav Steps/ week 2...Sub total: Info Consumer 301-400 Nav Steps/ week 1Total: Executive [401 - 1200 Nav Steps/ week] 0Total: Power User [> 1200 Nav Steps/ week] 1

12 Reporting and Upload Workload last week

The diagram above shows an overview of the workload distribution regarding reporting and upload activities from the last week. Note that the values shown do not reflect the actual values. In each case, we have taken the highest value and considered it to be "100". The other values show the ratio to the maximum values.

Maximum values are given below.

Note that the minimum requirement is ST-A/PI 01G*. If this has not been applied, no reporting activity will be shown in the diagram.

max. value # Nav. Steps max. value # Uploads422 2

13 History of Activity and Average Response TimesThe following graphics or tables show the system activity, which is the number of dialog steps and the average response times for the past 20 weeks.



The top table or graphic compares the total system activity to the dialog activity in the time window specified. The bottom table shows the average CPU, DB, and wait times as parts of the average response time for dialog tasks in the time window specified.

14 BW Runtime StatisticsThe performance of your queries and upload was analyzed with respect to average runtime and total workload. The following table provides an overview of your system activity and performance from the BW point of view.

Note: All queries using the 'Read API' of your system (such as from connected SAP-APO or SAP-SEM systems) are named 'RSDRI_QUERY,' so you cannot locate them in your BW system. Please note that the following chapters only contain queries/InfoCubes for which the statistics indicators are set.

15 Top InfoProviderThe following table lists the top 5 InfoProviders regarding the number of uploaded records.

TOP INFOPROVIDERS PER UPLOAD VOLUMEInfoProvider # InfoSources # Requests # Records written Total Time [sec]0BWTC_C02 1 1 452 37.6

The following table lists the top five InfoProviders based on the number of query hits.


14 BW Runtime Statistics

TOP INFOPROVIDERS PER NUMBER OF QUERIESInfoProvider Navigation

StepsAvg.

runtime [s]Runtime

[%]Avg. time OLAP [s]

Avg. time DB [s]

Avg. Frontend time

[s]

Avg. # Frontend

cellsYMPAPL_1 1108 21.60 33 10.70 9.50 0.90 0YM13_INV 1420 16.20 32 0.50 15.00 0.60 1YM_PTFINV 2756 7.00 27 0.10 5.60 0.30 448ZMORDINV 1032 3.90 6 0.10 1.30 0.30 1147YMPAPO_1 5 418.60 3 1.70 412.80 0.90 0

16 Frontend Distribution

# Queries BEX WEB ODBO API47 1 42 4 0

The table above provides an overview of the front-end distribution. It contains the total number of queries executed over the last complete week (Monday to Sunday) and the number of queries executed from the different front ends.

17 Query Profile Check18 Queries

The table below gives an overview of the query runtimes in regard to the use of the OLAP Cache. This means the line 'Cache Queries' summarizes all the queries which used the OLAP Cache, whereas 'DB Queries' directly accessed the database. Please note that all queries using the 'Read API' (Queries named 'RSDRI_QUERY') cannot use the OLAP Cache. Therefore these queries are listed separately. If there were no queries in the last seven days which used the OLAP Cache, accessed the database or used the 'Read API', the corresponding summary line is not displayed.

Task Type Nav. Steps

Runtime > 20 seconds [%]

Avg. Runtime [s]

Avg. Time OLAPINIT [s]

Avg. Time OLAP [s]

Avg. Time DB [s]

All Queries 6676 5 11.54 0.24 2.02 8.01DB Queries 4077 8 16.27 0.21 1.31 13.12Cache Queries

2599 1 4.11 0.30 3.13 0.00

The following table provides a summary of query runtimes and distinguishes between the different front ends. (BEX, WEB, ODBO and API).If no queries were started with one of the given options over the last seven days, the corresponding summary line is not displayed.



Avg. Runtime [s]


Avg. Time OLAP [s]

Avg. Time DB [s]

All Queries 6676 5 11.54 0.24 2.02 8.01WEB Queries

3727 9 17.45 0.21 3.57 12.90





Avg. Runtime [s]


Avg. Time OLAP [s]

Avg. Time DB [s]

BEX Queries

3 0 6.30 0.27 0.30 1.70

ODBO Queries

2946 1 4.06 0.29 0.07 1.84

19 Top Time Queries by Total WorkloadThe total workload caused by queries is defined as the sum of the total runtimes of all queries. The following query profile lists the queries, as a percentage of total runtime, that contribute the greatest amount to the total workload.

Query name InfoCube Nav. Steps

Runtime [%]

Avg. runtime

[s]

Avg. DB

time [s]

Avg. OLAP

time [s]

Avg. Frontend

time [s]

Avg. # Frontend

cells

Total 5692 100 12.12 8.29 2.23 0.54 1786ZYMPAPL_1_Q0001 YMPAPL_1 875 27 21.29 11.74 8.00 0.87 0ZYM13_INV_Q0007 YM13_INV 546 21 26.63 25.30 0.35 0.86 0ZYM_PTFINV_Q0001 YM_PTFINV 669 17 17.53 16.69 0.22 0.52 0ZYM_PTFINV_Q0001_FS YM_PTFINV 2040 10 3.51 1.96 0.05 0.28 606ZYMPAPL_1_Q0006 YMPAPL_1 124 7 40.33 0.66 38.44 1.18 0ZYM13_INV_Q0008 YM13_INV 391 6 10.08 8.57 0.85 0.44 0ZZMORDINV_Q0001_FSF ZMORDINV 846 5 3.96 1.03 0.04 0.27 1399ZYM13_INV_Q0015 YM13_INV 143 3 14.83 13.83 0.49 0.39 0ZYMZO_1_Q0008 YMZO_1 56 2 25.76 10.07 1.04 5.40 138307YYMPAPO_1_Q0002 YMPAPO_1 2 2 555.18 543.10 3.97 1.06 0

20 Top Time Queries by DB LoadThe total database workload generated by the BW system is the sum of the total database access times of all queries. The following query profile lists the queries, as percentages of total database access time, that make up the largest part of the database load.

Query name InfoCube Navigations Db load in [%] Avg. DB time [s] Avg. Runtime [s]Total 5519 100 8.77 11.68ZYM13_INV_Q0007 YM13_INV 546 29 25.30 26.63ZYM_PTFINV_Q0001 YM_PTFINV 669 23 16.69 17.53ZYMPAPL_1_Q0001 YMPAPL_1 875 21 11.74 21.29ZYM_PTFINV_Q0001_FS YM_PTFINV 2040 8 1.96 3.51ZYM13_INV_Q0008 YM13_INV 391 7 8.57 10.08ZYM13_INV_Q0015 YM13_INV 143 4 13.83 14.83YYMPAPO_1_Q0002 YMPAPO_1 2 2 543.10 555.18YYMPAPO_1_Q0001 YMPAPO_1 3 2 325.99 327.59ZYM13_INV_Q0017 YM13_INV 4 2 221.59 223.60ZZMORDINV_Q0001_FSF ZMORDINV 846 2 1.03 3.96

21 Top Time Queries by Average Runtime

The ten queries whose average runtimes have the highest optimization potential are listed here.

Query name InfoCube Avg. Runtime [s]

Avg. DB time [s]

Avg. OLAP time [s]

Avg. Frontend time [s]

Avg. # Frontend cells

Total 34.43 24.75 7.39 1.24 10368YYMPAPO_1_Q0002 YMPAPO_1 555.17 543.10 3.97 1.06 0ZYO13_ITM_Q0003 YO13_ITM 375.17 372.95 0.61 0.44 0YYMPAPO_1_Q0001 YMPAPO_1 327.59 325.99 0.17 0.73 0ZYM13_INV_Q0017 YM13_INV 223.60 221.59 0.66 0.43 0ZYM_OO_Q0002 YM_OO 165.34 65.34 77.94 0.74 0ZZM_MAT_Q0002 ZM_MAT 149.65 115.61 10.26 0.32 0ZYMPAPL_1_Q0006 YMPAPL_1 40.33 0.66 38.44 1.18 0ZZMORDINV_Q0002 ZMORDINV 28.09 27.37 0.29 0.39 0ZYM13_INV_Q0007 YM13_INV 26.63 25.30 0.35 0.86 0ZYMZO_1_Q0008 YMZO_1 25.76 10.07 1.04 5.40 138307



22 BEX - Queries by Total Workload (TOP 10 per Runtime%)The table below contains data about the 10 queries that consumed the most time, with regard to runtime.Note that this table contains data about single executions of your queries. This means the data is not summarized, and the name of a query may appear several times.


Runtime [%]

Avg. runtime

[s]

Avg. DB

time [s]

Avg. OLAP

time [s]

Avg. Frontend

time [s]

Avg. # Frontend

cells

Total 3 100 6.30 1.70 0.30 3.94 455ZYM13_INV_Q0040 YM13_INV 3 100 6.30 1.70 0.30 3.94 455

23 WEB - Queries24 WEB Templates (TOP 10 per Runtime)

The following table lists the top 10 templates that contribute the greatest amount to the total workload.

Template Name (Page ID) Runtime [s]

# Executions [Sessions]

# Navigation

Steps [Queries]

Avg. runtime for one

NavStep [s]

Max. runtime for one

NavStep [s]

Avg. Template

prepare time [s]

Avg. Template

render time [s]

Total 65019.10

3725 3727 17.45 2051.11 0.32 0.34

<undefined> 64384.99

3395 3397 18.95 2051.11 0.27 0.31

ZEXCELPRINT_PORTRAIT 324.88 158 158 2.06 20.95 0.79 0.59ZEXCELPRINT_LANDSCAPE 264.09 148 148 1.78 6.19 0.66 0.69ZMIG_BW_PRINTFITTO_TMPL 45.14 24 24 1.88 5.16 1.23 0.10

25 WEB - Queries by Total Workload (TOP 10 per Runtime%)

The table below contains data about the 10 queries that consumed the most time, with regard to runtime.Note that this table contains data about single executions of your queries. This means the data is not summarized, and the name of a query may appear several times.


Runtime [%]

Avg. runtime

[s]

Avg. DB

time [s]

Avg. OLAP

time [s]

Avg. Template

prepare [s]

Avg. Template render [s]

Total 2759 100 21.71 15.95 4.71 0.33 0.38ZYMPAPL_1_Q0001 YMPAPL_1 875 31 21.29 11.74 8.00 0.39 0.48ZYM13_INV_Q0007 YM13_INV 546 24 26.63 25.30 0.35 0.35 0.50ZYM_PTFINV_Q0001 YM_PTFINV 669 20 17.53 16.69 0.22 0.32 0.19ZYMPAPL_1_Q0006 YMPAPL_1 124 8 40.33 0.66 38.44 0.43 0.75ZYM13_INV_Q0008 YM13_INV 391 7 10.08 8.57 0.85 0.21 0.23ZYM13_INV_Q0015 YM13_INV 143 4 14.83 13.83 0.49 0.15 0.24YYMPAPO_1_Q0002 YMPAPO_1 2 2 555.18 543.10 3.97 0.62 0.44YYMPAPO_1_Q0001 YMPAPO_1 3 2 327.59 325.99 0.17 0.58 0.15ZYM_OO_Q0002 YM_OO 2 2 482.78 196.02 233.81 0.54 0.21ZYM13_INV_Q0017 YM13_INV 4 1 223.60 221.59 0.66 0.30 0.13

26 WEB Templates - Multiple Query/View usage

Several Web items can use the same data provider if there is no need for independent navigation in a template. Based on our experience, independent navigation is not required in most cases, and you can therefore avoid the multiple query execution by assigning a query or view to just one data provider, which is used by all web items.27 WEB Templates - Design StatisticsTEMPLATE COMPLEXITY REGARDING DIFFERENT QUERIES/VIEWS# of Queries / Views # of Web Templates01 002 003 004 005 006 0



# of Queries / Views # of Web Templates07 008 009 010 0> 10 0

28 WEB Templates - Unused Data ProvidersTOP10 NUMBER OF UNUSED DATA PROVIDERS PER TEMPLATETemplate # unused Data ProvidersZMIG_BW_CENTERFRAME 1

TOTAL NUMBER OF UNUSED DATA PROVIDERSTotal number of unused Data Providers

1

Recommendation:Unused data providers consume OLAP initialization runtime and can cause transport problems. In particular, if you have several templates that contain unused data providers, we recommend that you delete them to obtain an optimized and clean template implementation.Using BW 3.x, unused data providers must be deleted manually from the HTML code in the Application Designer. As of the BI in SAP NetWeaver 2004, there is a delete function in the data provider's context menu.

29 ODBO - Queries by Total Workload (TOP 10 per Runtime%)The table below contains data about the 10 queries that consumed the most time, with regard to runtime.Note that this table contains data about single executions of your queries. This means the data is not summarized, and the name of a query may appear several times.

Query name InfoCube Navigation steps

Runtime [%]

Avg. runtime

[s]

Avg. DB

time [s]

Avg. OLAP

time [s]

Avg. ODBO

Time [s]

Avg. Prepare Axis [s]

Total 2946 100 4.06 1.84 0.07 0.10 0.15ZYM_PTFINV_Q0001_FS YM_PTFINV 2040 60 3.51 1.96 0.05 0.10 0.02ZZMORDINV_Q0001_FSF ZMORDINV 846 28 3.96 1.03 0.04 0.08 0.07ZYMZO_1_Q0008 YMZO_1 56 12 25.76 10.07 1.04 0.38 5.94ZYM_OO_Q0002 YM_OO 4 0 6.62 0.00 0.00 0.39 5.26

30 Analysis of MultiProvider QueriesDuring parallel processing of MultiProvider queries, subprocesses that process the partial accesses to the InfoProviders in the MultiProvider are separated from a parent process. The parent process provides a synchronization point where the overall result is collected. In contrast to sequential processing, which permits partial results to reach the OLAP processor, parallel processing requires that the overall result first be collected at the synchronization point.

To avoid an overflow of the process memory, parallel processing is cancelled as soon as the collected result contains 30,000 rows or more and there is at least one subprocess not finished. The MultiProvider query is then restarted automatically and processed sequentially.

This strategy explains why sequential processing can appear to be faster than parallel processing in the case of queries like these. What appears to be parallel processing corresponds to sequential processing plus the preceding phase of parallel processing up to the termination.

Recommendation: Please check whether parallel processing is deactivated. Otherwise, consider deactivating parallel processing for those queries that are MultiProvider queries and have large result sets. Furthermore, starting with BW 3.0B Support Package 14 (BW 3.1 Support Package 8), you can set parameters to define the size of the maximum permissible interim overall result, that is, you can change the default valid value of 30,000 rows. For further details, please refer to SAP Notes 622841, 607164, and 630500. Please note that it is generally recommended that the number of base InfoProviders of a MultiProvider is not more than 10. A larger number of base InfoProviders is likely to result in a scenario where there are a lot more base InfoProviders than there are available dialog processes, resulting in limited parallel processing and many pipelined subqueries. Details can be found in SAP Note 629541.



31 Queries with more than 30000 rows accessing a MultiProviderQuery name # Query

exec.Total

runtime [s]DB

Time [s]OLAP

Time [s]Frontend Time [s]

# Frontend cells

# QDBTRANS

ZYM13_INV_Q0008 4 213.30 25.05 183.69 0.21 0 622553ZYM13_INV_Q0015 3 29.38 13.86 15.08 0.29 0 152331ZYMPAPL_1_Q0001 14 493.55 468.70 22.47 0.11 0 210597ZYM_PTFINV_Q0001 1 62.20 57.55 3.60 1.02 0 33187ZYM_PTFINV_Q0002 1 27.02 24.72 1.86 0.24 0 32585

The table below contains a list of all Multiproviders, the number of their Infoprovider, and the name of their queries.

Query MultiProvider # InfoProviderZYM13_INV_Q0008 YM13_INV 10ZYM13_INV_Q0015 YM13_INV 10ZYMPAPL_1_Q0001 YMPAPL_1 3ZYM_PTFINV_Q0001 YM_PTFINV 9ZYM_PTFINV_Q0002 YM_PTFINV 9

32 Upload of transactional dataThis section provides an overview of the upload of transactional data from 19.03.2007 to 26.03.2007.

Please note that 'Time Target' can be bigger than the total time. This is because when the data is loaded to the target, the insert can be done in parallel.

Total # of Requests

Total time [h]

Time Source [h]

Time Transfer [h]

Time PSA [h]

Time Update [h]

Time Target [h]

# records inserted

Total 2 0.0 0.0 0.0 0.0 0.0 0.0 894

In the tables below, you can see an overview of the runtime in special areas for the TOP 5 requests in the last 7 days (19.03.2007 - 26.03.2007).

SUMMARYInfo-Source #

Targets#

RequestsRecords

writtenTime

Source [sec]

Time Transfer

Rules [sec]

Time PSA

[sec]

Time Update

Rules [sec]

Time Target

[sec]

Time Total [sec]

0BWTC_C02 1 1 452 10.1 0.2 0.0 0.3 22.0 37.60BWTC_C05 1 1 442 3.4 0.0 0.0 0.1 4.6 12.8

TOP 5 REQUESTS WITH HIGH RUNTIME IN UPDATE RULESRequest-ID

Target Info-Source Records written

Time Source

[sec]

Time Transfer

Rules [sec]

Time PSA

[sec]

Time Update

Rules [sec]

Time Target

[sec]

Time Total [sec]

65857 0BWTC_C02 0BWTC_C02 452 10.1 0.2 0.0 0.3 22.0 37.665856 0BWTC_C05 0BWTC_C05 442 3.4 0.0 0.0 0.1 4.6 12.8

TOP 5 REQUESTS WITH HIGH RUNTIME IN SOURCE SYSTEMRequest-ID


Time Source

[sec]

Time Transfer

Rules [sec]

Time PSA

[sec]

Time Update

Rules [sec]

Time Target

[sec]

Time Total [sec]


TOP 5 REQUESTS WITH HIGH RUNTIME IN DATA TARGETRequest-ID


Time Source

[sec]

Time Transfer

Rules [sec]

Time PSA

[sec]

Time Update

Rules [sec]

Time Target

[sec]

Time Total [sec]


33 Number Range Buffering for BW Objects



For each characteristic and dimension, BW uses a number range to uniquely identify a value (SIDs and DIM-IDs). If the system creates a high amount of new IDs periodically, the performance of a data load may decrease.

To avoid the high number of accesses to the NRIV table, activate the number range buffering for these BW objects (Main Memory Number Range Buffering). For more detailed information, see SAP Notes 504875, 141497, and 179224.

The tables provide an overview of the number range buffering, setting of dimensions, and InfoObjects based on the highest number range level ("Level"). The purpose of this information is to identify the candidates for activating the number range main memory buffer.

Recommendation:Activate number range buffering for all dimensions and InfoObjects, with a high number of rows, based on the rules mentioned in Note 857998.

Note: A package dimension must not be buffered!

TOP10 UNBUFFERED DIMENSIONS WITH HIGHEST NUMBER RANGE LEVELInfoCube Dimension Rows Object Level Buffered Buffer Size0BWTC_C02 0BWTC_C024 629238 BID0001142 674193 0100025 1000252 8495 BID0004427 206000 0100026 1000263 9784 BID0004434 177000 0100111 1001112 2835 BID0005162 134000 00BWTC_C02 0BWTC_C021 123526 BID0001141 132486 0100004 1000042 7927 BID0004494 127000 0100147 1001472 7502 BID0005669 104000 0100027 1000273 1842 BID0004440 99000 0100025 1000253 1842 BID0004428 99000 0100026 1000262 626 BID0004433 97000 0

TOP10 BUFFERED DIMENSIONS WITH HIGHEST NUMBER RANGE LEVELInfoCube Dimension Rows Object Level Buffered Buffer SizeZCORDINV ZCORDINV3 1 BID0001311 252481 100YC12_DEL YC12_DEL2 49780 BID0000746 181286 100YC13_INV YC13_INV2 51090 BID0000775 176399 100YC_OO YC_OO3 1 BID0000730 141937 100YC_OO YC_OO2 1 BID0000729 125860 100ZCORDINV ZCORDINV2 1 BID0001310 120108 100ZCHSTLI ZCHSTLI2 1 BID0001370 109527 100YC12_DEL YC12_DEL3 24551 BID0000747 103245 100YC13_AGR YC13_AGR2 36620 BID0000766 98250 100ZCHSTLI ZCHSTLI3 1 BID0001371 88330 100

TOP10 UNBUFFERED INFOOBJECTS WITH HIGHEST NUMBER RANGE LEVELInfoObject SID Table Rows Object Level Buffered Buffer SizeYDOC_NUM1 /BIC/SYDOC_NUM1 10769585 BIM0000802 12270434 00AC_DOC_NO /BI0/SAC_DOC_NO 2838940 BIM0000963 5373185 0YPAOBJNR /BIC/SYPAOBJNR 4211590 BIM0000804 4783483 00REFER_DOC /BI0/SREFER_DOC 2484486 BIM0000533 3047153 00DOC_NUMBER /BI0/SDOC_NUMBER 2630186 BIM0000362 2713585 00REF_DOC_NO /BI0/SREF_DOC_NO 1327628 BIM0000908 1940988 00DOC_NUM /BI0/SDOC_NUM 1723056 BIM0000361 1729291 00DELIV_NUMB /BI0/SDELIV_NUMB 1120222 BIM0000345 1613569 00BILL_NUM /BI0/SBILL_NUM 1551025 BIM0000714 1551355 0YRBELN /BIC/SYRBELN 1214712 BIM0000806 1481971 0

TOP10 BUFFERED INFOOBJECTS WITH HIGHEST NUMBER RANGE LEVELInfoObject SID Table Rows Object Level Buffered Buffer Size0MAT_SALES /BI0/SMAT_SALES 152286 BIM0000437 201646 100YSALFORCE /BIC/SYSALFORCE 116770 BIM0000723 120506 1000MAT_PLANT /BI0/SMAT_PLANT 91450 BIM0000942 95285 1000CUST_SALES /BI0/SCUST_SALES 64504 BIM0000336 68268 1000MATERIAL /BI0/SMATERIAL 49762 BIM0000426 57121 1000CUSTOMER /BI0/SCUSTOMER 19576 BIM0000325 20392 1000GL_ACCOUNT /BI0/SGL_ACCOUNT 10330 BIM0000985 11107 100ZFORMCODE /BIC/SZFORMCODE 5761 BIM0001177 6747 1000COSTELMNT /BI0/SCOSTELMNT 2502 BIM0000215 3071 100



InfoObject SID Table Rows Object Level Buffered Buffer Size0COORDER /BI0/SCOORDER 767 BIM0000212 1467 100

34 Process Chains - Runtime OverviewThe Process Chain Runtime Analysis is based on the last 7 days before the download.

The table contains statistical information of all chains which aren't started by another local process chain. This includes process chains which are started by the Service API Interface or remotely by a chain from another system. Please note that only the top 20 chains having the longest runtimes are displayed.

The columns '# Total Subchains', '# Total Steps' represent the summarized values of the main chain and their subchains. The runtimes are the range from the start of the main chain up to the end of the last process type executed within the main chain and their subchains. This means the real runtime of the main chain and their subchains is displayed here.

Main Chain #Total Subchains

#Total Steps

#Runs Total Runtime

[min]

Avg. Runtime

[min]

Med. Runtime

[min]

Avg. Proc.Type

Runt. [min]ZBWD_SD_DM 7 44 14 1809 130 104 130ZBWD_SD 6 38 14 457 33 14 33ZBWW_HSE_KEEP 10 91 1 273 273 273 314ZBWD_SD_V3 6 17 14 203 15 11 29ZBW_STATISTICS_TRANS 9 105 7 90 13 13 13ZBWD_FI_DM 5 30 7 69 10 11 10ZTEMP_APD_SD_CARYOVR 0 4 2 41 21 21 21ZBWD_CR 0 3 7 4 1 1 1

The following table displays the statistical information based on the actual defined chain hierarchy. The columns '# Subchains' and '# Steps' are based on the subchain itself only.Only the top three main process chains with the highest number of executions are displayed. For each main process chains only the first ten subchains with the highest runtimes are shown.

Parent Chain Level

Chain # Subcha

ins

# Steps

# Runs

Total Runti

me [min]

Avg. Runti

me [min]

Med. Runti

me [min]

Avg. Proc.Ty

pe Runt. [min]

0 ZBWD_SD_DM 1 2 14 1809 130 104 130ZBWD_SD_DM 1 ZBWD_DM_SD_DELTA

_LOAD6 7 14 1808 130 104 156

ZBWD_DM_SD_DELTA_LOAD

2 ZBWD_DM_SD_OO 0 3 14 1109 80 73 79


2 ZBWD_DM_SALES_ORD

0 10 14 553 40 18 50


2 ZBWD_DM_SLS_INV_ROLLUP

0 4 14 142 11 11 15


2 ZBWD_DM_SALES_INVOICE

0 5 14 142 11 12 11


2 ZBWD_DM_SALES_DELIV

0 8 14 115 9 6 9


2 ZBWD_DM_SD_SRI 0 5 14 110 8 7 8

0 ZBWD_SD 4 10 14 457 33 14 33ZBWD_SD 1 ZBWD_DELTA_LOAD 2 3 14 425 31 11 34ZBWD_SD 1 ZBWD_RFC_LIS_APPL

_110 2 28 121 5 2 5

ZBWD_SD 1 ZBWD_RFC_LIS_APPL_12

0 2 28 113 5 1 4

ZBWD_SD 1 ZBWD_RDC_LIS_APPL_13

0 2 28 20 1 1 1

ZBWD_DELTA_LOAD 2 ZBWD_SD_TRANS_LOAD

0 14 14 415 30 10 45

ZBWD_DELTA_LOAD 2 ZBWD_SD_INV_TRANS_LOAD

0 5 14 60 5 3 5

0 ZBWW_HSE_KEEP 10 11 1 273 273 273 314ZBWW_HSE_KEEP 1 ZBW_DBSTATS_SD 0 9 1 164 164 164 483ZBWW_HSE_KEEP 1 ZBW_ZCORDINV_COM

PRESS0 9 1 98 98 98 174



Parent Chain Level

Chain # Subcha

ins

# Steps

# Runs

Total Runti

me [min]

Avg. Runti

me [min]

Med. Runti

me [min]

Avg. Proc.Ty

pe Runt. [min]

ZBWW_HSE_KEEP 1 ZBW_DBSTATS_FI 0 3 1 32 32 32 37ZBWW_HSE_KEEP 1 ZBW_IDX_CREATE_S

D0 9 1 7 7 7 21

ZBWW_HSE_KEEP 1 ZBW_IDX_DROP_SD 0 9 1 3 3 3 13ZBWW_HSE_KEEP 1 ZBW_COMPRESS_FI 0 3 1 3 3 3 3ZBWW_HSE_KEEP 1 ZSD_PSA_DELETE 0 19 1 2 2 2 3ZBWW_HSE_KEEP 1 ZBW_IDX_CREATE_FI 0 4 1 1 1 1 1ZBWW_HSE_KEEP 1 ZBW_PSA_DELETE_FI 0 11 1 1 1 1 1

35 Change-Run AnalysisTotal maintenance time of all change-runs within one week.

Week # Change-Runs Total Runtime [min]12.2007 19 34511.2007 17 21310.2007 18 39109.2007 19 40708.2007 18 37607.2007 18 26106.2007 14 124605.2007 19 16504.2007 19 23403.2007 18 341


36 Workload Distribution

36 Workload DistributionThe performance of your system was analyzed with respect to workload distribution. We did not detect any major problems that could affect the performance of your SAP System.

Rating CheckWorkload by Application ModuleDB Load Profile

37 Workload by Application ModuleThe following graphics or tables show how each application module contributes to the total system workload. Two workload aspects are shown:- CPU time: Total CPU load on all servers in the system landscape- Database time: Total database load generated by the applicationThe #Customer# section contains all programs and transactions that start with Y or Z. The #Others# section contains all programs that cannot be assigned to an SAP standard application module (for example, an industry solution or a third party add-on development).

Module CPU Time in %BC 52.0Others 30.3BC-MID 13.7BW 3.9


36 Workload Distribution

Module DB Time in %Others 39.9BC 39.8BC-MID 15.6BW 4.7

38 DB Load ProfileThe following table or diagram shows the DB load caused by Dialog, RFC, and Background tasks over different time frames.The data given in the table represents the average number of database processes occupied by each task type in the database during the given time frames.These statistics are calculated as a weekly average, which means the average values over six working days with a unit of one hour. Periods between 00:00-06:00 and 21:00-24:00 contain an average value per hour.By comparing the load profiles for dialog and background activity, you have an overview of the amount of background activity during online working hours.


39 SAP System Operating

39 SAP System OperatingYour system was analyzed with respect to daily operation. We detected some problems that may impair system operation and stability. To ensure system stability, you should take corrective action as soon as possible.

Rating CheckSystem AvailabilityUpdate ErrorsTable ReorganizationABAP Dumps

40 Update ErrorsIn a system running under normal conditions, only a small number of update errors should occur. To set the rating for this check, the number of active users is also taken into consideration.We did not detect any problems.

41 TransportsThe following graphics contain information about the number of objects which were transported to the SAP system. The three graphics/tables show objects in total, programs and table (content).


39 SAP System Operating

42 Program Errors (ABAP Dumps)10 ABAP dumps have been recorded in your system since 21.03.2007. ABAP dumps are deleted after 7 days by default.To view the ABAP dumps in your system, call transaction ST22 and choose “Selection”. Then select a timeframe.

ABAP DUMPS PER DAYDate Quantity of Dumps

03/20/2007 003/21/2007 403/22/2007 403/23/2007 103/24/2007 103/25/2007 0

DETECTED ABAP DUMPSError Number Server (e.g.) User (e.g.) Date (e.g.) Time (e.g.)TSV_TNEW_BLOCKS_NO_ROLL_MEMORY 4 usnasap123 US1592172 03/21/2007 14:18:47UNCAUGHT_EXCEPTION 4 usnasap123 US1599967 03/22/2007 19:31:42SYSTEM_CORE_DUMPED 1 usnasap101 US2WBAIG0 03/23/2007 16:52:48TIME_OUT 1 usnasap123 ALEREMOTE 03/24/2007 19:31:09


43 Security Checks

43 Security ChecksCritical security issues were detected in your system. We determined that several users have critical authorizations for certain transactions. See the information in the following checks.SAP offers a complete Security Optimization service for your system, which covers all of R/3 Basis and other SAP products. We recommend that you make use of this service.For more information, see SAP Service Marketplace at http://www.service.sap.com/SOS.

Rating CheckUsers Authorized to Display all TablesUsers Authorized to Start all ReportsUsers Authorized to Debug / ReplaceUsers Authorized to Display Other Users Spool RequestUsers Authorized to Administer RFC ConnectionsUsers Authorized to Reset/Change User PasswordsPassword of One or More Standard Users is not Changed

44 Password of One or More Standard Users is not ChangedEvaluated Risk - HighRecommendation: Change the standard password for users SAP* DDIC, SAPCPIC, and EARLYWATCH in all clients. Do not delete the SAP* user because this enables the use of the hard-coded SAP* user. For more information, see the SAP Security Guides on SAP Service Marketplace at: http://www.service.sap.com/securityguide.

Client User000 SAPCPIC320 SAPCPIC066 EARLYWATCH


45 Hardware Capacity

45 Hardware CapacityWe have checked your system for potential CPU or memory bottlenecks and found that the hardware of your database and application servers is sufficient for the current workload.

Server Max. CPU load [%]

Date Rating

RAM [MB]

Max. Paging [% of RAM]

Date Rating

usnasap101

18 03/19/2007

8192 0 03/21/2007

usnasap123

74 03/25/2007

18432 0 03/21/2007


46 Database Settings

46 Database SettingsWe have detected some problems with the settings of the database. These settings may affect performance.

Rating CheckDatabase Key Performance IndicatorsLocally managed Temp TablespaceDatabase ParametersOptimizer Statistics

47 Load per userThe following table provides an overview of the load caused by different database users.

Listed for each database user is the:(a) Percentage of executed statements(b) Number of block reads from disk (indicative for the I/O load caused by this database user)(c) Number of buffers accessed(d) Number of records returned as obtained from the shared pool (Oracle view V$SQL) at the time of the download

The first line with the name TOTAL indicates the total number of (a), (b), (c) and (d) for all the user names.

48 User name Executions Disk reads Buffer gets Rows processed

TOTAL (not a user name!) 1882491299 55777616 9947217155 5093278823

SYS 2% 1% 13% 9%OPS$ORAPWH 0% 0% 0% 0%OPS$PWHADM 0% 0% 0% 0%SAPBIW 98% 27% 65% 73%THEGUARD 0% 72% 23% 17%

49 File System Response TimesYour file system read response times do not meet the standard requirements.

Recommendation: Check the disks where the data files named in the following table are located. All datafiles with a high average read time and a noticeable impact on the total read time of your system are listed in this table.

DATAFILES WITH HIGH AVERAGE READ TIME PER BLOCKFile name Blocks

readAvg. read time (ms)

Total read time per datafile (ms)

/oracle/PWH/sapdata1/biw_49/biw.data49

50196646 264 13251914544


78018544 191 14901541904


77675545 184 14292300280


75837626 174 13195746924


98598203 139 13705150217

/oracle/PWH/sapdata2/biw_2/biw.data2 102701910 124 12735036840/oracle/PWH/sapdata2/biw_1/biw.data1 140915515 108 15218875620

50 Database Parameters


46 Database Settings

We noticed that the following database parameters, which are currently active in your system, do not follow our standard recommendations. These standard recommendations cannot take into account possible special aspects for your system. Deviations from those standard recommendations may be necessary in your case. We therefore advise you to discuss theses parameter settings in your next Service session.

Based on the fact that you intend to use OLAP operations in your NetWeaver system's database, the recommended parameter settings are optimized for OLAP operations as listed in SAP Note 632556. While these settings should also provide adequate performance for OLTP database operations for most database accesses, some accesses may yield better results with the parameter settings listed in SAP Note 124361. This means that, depending on the priorities you assign to the OLTP or OLAP operations in your system (which we are not able to ascertain from the technical data available in a remote service session), the parameter settings in SAP Note 124361 may be preferable. In this case, ignore the following parameter recommendations.

NOTE FOR ORACLE PARAMETER SETTINGSNote number

Description

332696 ORA-00600 [2865], star_transformation_enabled632556 Oracle 9.2.0.* database parameter settings for BW

Parameters Description Current value Recommended value

parallel_max_servers Parallel Query: Maximum number of parallel execution servers

48 Please check SAP note 0632556

processes Maximum number of database shadow/background processes


sessions Maximum number of concurrent database sessions


To provide special functionality or control system behavior, Oracle has a number of events. These can be activated in the configuration file and/or dynamically in the server manager or sqlplus.

In general, these events and parameters should only be activated on request. When they are no longer needed, they should be removed. However, there might be the need to activate some events during normal database operation.

The following table displays the values for the parameter "event" as found in your system:

Parameter Current Valueevent 10028 trace name context forever, level 1

10191 trace name context forever, level 138060 trace name context forever, level 138069 trace name context forever, level 1

The following table lists events that may have to be activated. Please check the mentioned SAP Notes for details.

Event Note number for Event Description10027 596420 System downtime during deadlock (ORA-60)38068 176754 Problems with CBO and RBO

The following table lists events we found to be activated in your system, but which should only be activated in special circumstances. Please check whether there are special reasons to set these events. If they are no longer needed, they should be removed.

Event38060

51 Database AdministrationIn the checks performed, problems regarding the administration of your database were found.

Rating CheckDatabase GrowthBackup FrequencyArchive Frequency


51 Database Administration

Rating CheckFreespace in TablespacesSpace Critical Objectsbrconnect -f check (sapdba -check) schedule

52 Database GrowthThe following figure shows the development of the size of your database in GB.

An overview of the freespace development of your database in GB is shown here.

The following table shows you the current size and the monthly growth of your database in GB.

Date Current Size in GB Monthly Growth in GB04/18/2006 13.38 0.6005/31/2006 13.18 -0.2006/30/2006 100.72 87.5407/31/2006 200.87 100.1508/31/2006 256.84 55.9709/30/2006 475.59 218.7510/31/2006 570.98 95.3911/30/2006 765.99 195.0112/31/2006 560.60 -205.3901/31/2007 471.97 -88.6302/28/2007 353.34 -118.6303/25/2007 355.52

Your database is growing at a rate of more than 30 GB of data per month.


51 Database Administration

Recommendation: Analyze the top growing tables and check that the table growth is really necessary for your business process. Set up a archiving project that allows you to archive data periodically to keep the database at a manageable size.Note: Data archiving is particularly important before SAP Basis Release upgrades, conversion, or migration projects.

53 Oracle ReleaseIn general, we recommend that you install the most current Oracle patch set as soon as possible (see SAP Note 415900). Therefore, check SAP Note 539921 from time to time for the latest patch set for Oracle 9.2.0. Note that in addition to the patch set, further bug fixes might be available and recommended. See the following SAP Notes:

For patch set 9.2.0.3 - 610445: Merge fix for Oracle 9.2.0.3For patch set 9.2.0.4 - 695080: Merge fix for Oracle 9.2.0.4For patch set 9.2.0.5 - 755629: KKO merge fix for Oracle 9.2.0.5For patch set 9.2.0.6 - 834100: Merge fix for Oracle 9.2.0.6For patch set 9.2.0.7 - 896903: Optimizer Merge fix for Oracle 9.2.0.7

54 Desupport of multibyte character sets as of Oracle 10gAn important SAP Note is available concerning systems that run with an Oracle database and that make use of setting the database code page to one of the following multibyte character sets:

JA16SJIS JapaneseKO16KSC5601 KoreanZHS16CGB231280 Simplified ChineseZHT16BIG5 Traditional Chinese

This SAP Note is:

Note 858869: Desupport of multibyte character sets as of Oracle 10g.(see also related note 695899)

The database settings as shown above have been set by many Asian customers to allow third-party tools to connect to their databases. With Oracle 10 clients or kernel release 7.00, the settings above are no longer supported and a Unicode conversion of the systems prior to an upgrade becomes mandatory for these systems.

55 Important Notes for OracleTo optimize system performance and to prevent data loss or system downtime, implement the following SAP Notes as soon as possible.

Note number

Description

858869 Desupport of multibyte character sets as of Oracle 10g871455 Performance when accessing DBA_SEGMENTS


56 Business Information Warehouse

56 Business Information WarehouseSevere problems were detected, that may have serious impact on your system's performance and stability. You should take corrective action immediately.

Rating CheckBW Application ChecksData DistributionAnalysis of InfoprovidersAnalysis of AggregatesSource System SettingsRecommendations for BWFrontend ServersPlanning Performance

57 BW Application Checks for PWHThe BW application was analyzed with respect to design and data distribution. We did not detect any major problems that could affect the performance of your system.58 Analysis of OLAP Cache

The OLAP Cache is used for duplicated storing of often used data, whereby this data can be accessed quickly.In the tables below, you can find information regarding the size and the usage of the OLAP Cache.Cache usage of queriesDefined Queries

The OLAP Cache can buffer results from queries and can provide them again for different users and similar queries (that is, same queries or real subsets of them). The OLAP Cache reduces the workload of the DB server.The OLAP Cache can store the query results with their navigation statuses in the memory of the application server; the data can also be stored in database tables and files.When the buffer (Export/Import Shared Memory) memory overruns, it stores the displaced data - depending on the persistence mode - on the database server.

The following OLAP Cache modes exist:0 Cache is Inactive1 Main Memory Cache Without Swapping2 Main Memory Cache With Swapping3 Cluster / Flat File Cache for Each Application Server4 Cluster / Flat File Cache Across Each Application Server

What is the best cache mode?This greatly depends on the requirements. The fastest cache mode is always the usage of the main memory. However, if several application servers are in use, the cache has to be filled for each query on each application server. In this case, it might be better to use the cross-application-server cache mode (flat file/cluster table). An alternative might be to use logon groups and to ensure that users executing the same/similar queries work on the same application server.

MODE 0 - Cache is Inactive All data is read from the relevant InfoProvider.

MODE 1 - Main Memory Cache without SwappingNew data is stored in the export/import SHM buffer until this memory area is full. If then new data has to be added to the buffer, an LRU mechanism is applied. Least recently used data is DISPLACED from the buffer and lost. If this data is needed again by a query, it must access the relevant InfoProvider on the DB server.

MODE 2 - Main Memory Cache with SwappingThis works in a similar fashion to MODE 1. HOWEVER in this scenario if the memory is full, data is not DISPLACED and lost but written to a cluster table/flat file. Then if this data is needed again by a query, it can be read from this file, which is still quicker than reading this from the relevant InfoProvider on the DB server.



MODE 3 - Cluster/Flat File Cache for Each Application ServerThe cache data is kept persistently in a cluster table or in flat files for each application server. The overall data quantity is only restricted by the database or file system. Swapping does not occur in the same way as with the cache main memory mode.

MODE 4 - Cluster/Flat File Cache Application Server-ExtensiveThis mode is the same as the mode described above (cluster/flat file for each application server), the only difference being that the cache entries of all of the application servers in a system are used together.

NOTE: FOR MODE 1 and 2, remember that MEMORY is INSTANCE DEPENDENT.

NUMBER OF QUERIES PER CACHE MODECache Mode # QueriesTotal 180OFF 01 1462 343 04 0

NUMBER OF INFOCUBES PER CACHE MODECache Mode # InfocubesTotal 69OFF 01 342 353 04 0

Executed Queries

Task type Nav. Steps Accessed DB [%] Accessed Cache [%] RSDRI Queries [%]All Queries 6676 61 39 0

There are two types of caches: The local cache and the transactional cache (OLAP Cache). The local cache belongs to a query session and therefore cannot be used by other sessions. The OLAP Cache can store query data on the application server and can have a swap file or use a swap cluster table.

The OLAP Memory Cache is located in the Export/Import buffer SHM (parameter rsdb/esm/buffersize_kb). As the global cache size is a logical value and the Export/Import SHM gives a physical limit, we recommend that you do not set the global cache parameter to a higher value than the Export/Import SHM buffer.

Note: The OLAP Cache was optimized in SAP BW 3.0B SP19, SAP BW 3.1C SP13, and SAP BW 3.5 SP02. For more information, see SAP Note 683194.

Rating Description Current Value RecommendationCache active ActiveCache Persistence Mode Flat FileFlat File Name BW_OLAP_CACHE



Rating Description Current Value RecommendationComprehensive Flat File Name for AppServerLocal Cache Size (MB) 100Global Cache Size (MB) 200

59 Data Distribution60 Largest ODS tablesODS Name ODS Table name No of recordsZOHSTLII /BIC/AZOHSTLII00 34024444YOPAPL_2 /BIC/AYOPAPL_200 30616050YO11_SCL /BIC/AYO11_SCL00 16877028YO_OO_I /BIC/AYO_OO_I00 14338252YO11_ITM /BIC/AYO11_ITM00 13498023YO12_ITM /BIC/AYO12_ITM00 11057837YO11_SRI /BIC/AYO11_SRI00 107416880FIGL_O02 /BI0/AFIGL_O0200 10697281YOPAOC_1 /BIC/AYOPAOC_100 10107754YO13_ITM /BIC/AYO13_ITM00 8661444

Large ODS Objects can have a negative impact on reporting and upload performance. Please pay attention to more detailed recommendations in subsequent sections of this report.

With BW release 3.x parallel ODS Data Activation can fail on large ODS Objects with a deadlock on the Oracle database.

Recommendation: Please follow the implementation description in SAP Note 634458 "ODS object: Activation fails - DEADLOCK" and 84348 "Oracle deadlocks, ORA-00060".

61 Largest InfoCubesInfoCube Name No of recordsYC11_ORD 23743474YCPAPL_1 16069421ZC_OO 15215471ZCINVL05 13741030ZCINVL04 12958370ZCORD_L06 11325095ZCODI_L06 10223447ZCORD_L07 10196204ZCODI_L07 9579417ZCPAPLL07 9161759

Large InfoCubes require high effort in administration and have a long runtime during maintenance activities.

Recommendation: Please consider splitting a large InfoCube into small InfoCubes (such as separated by a time characteristic like 0CALYEAR). You can use MultiProviders as query targets to obtain all data in your query result.

62 Largest AggregatesInfocube Aggregate Name No of recordsZCINVL04 100123 8946973ZCINVL05 100125 8905517ZCINVL06 100126 4404831ZCINVL05 100103 3533970ZCINVL04 100097 3531850ZCODI_L07 100195 3512065ZCODI_L06 100139 3284100ZC_OO 100155 2460809ZCODI_L07 100200 2204225ZC_OO 100147 2188598

Large aggregates need high runtime for maintenance like change runs and rollup of new data.

Recommendation: Please check section: "Analysis of Aggregates" for further hints.

63 Largest Master data tables (SID-tables)Master data SID-Table Table Name No of recordsYDOC_NUM1 /BIC/SYDOC_NUM1 10769585



The table contains a list of the largest SID tables in your system.

Recommendation: Please ensure that you have switched on number range buffering for all InfoObjects where a high number of tuples are loaded. This is described in SAP Note 130253 "Notes on upload of transaction data into the BW."

64 Largest Master data tables (time independent: X-tables)Master data X-Table Table Name No of records0DOC_NUMBER /BI0/XDOC_NUMBER 21987740MAT_SALES /BI0/XMAT_SALES 152285YSALFORCE /BIC/XYSALFORCE 1167700MAT_PLANT /BI0/XMAT_PLANT 895300CUST_SALES /BI0/XCUST_SALES 64504

The table above shows the largest tables with time-independent navigational attributes. The usage of navigational attributes in aggregates will increase the runtime of the change run.65 Largest Master data tables (time dependent: Y-tables)Master data Y-Table Table Name No of records0PERSON /BI0/YPERSON 16870COSTCENTER /BI0/YCOSTCENTER 8130ORGUNIT /BI0/YORGUNIT 10EMPLOYEE /BI0/YEMPLOYEE 10HRPOSITION /BI0/YHRPOSITION 1

The table above shows the largest tables with time-dependent navigational attributes. Time-dependent navigational attributes can have a negative impact in the runtime of queries.

Recommendation: Please consider the usage of such objects carefully.

66 Largest Hierarchy tables (I-tables)Master data Hierarchy Table Name No of records0MAT_SALES /BI0/IMAT_SALES 3561580PROD_HIER /BI0/IPROD_HIER 44104YPRODH2 /BIC/IYPRODH2 5770REASON_CDE /BI0/IREASON_CDE 1720BUS_AREA /BI0/IBUS_AREA 122

Large hierarchy I-Tables will have a negative impact on the runtime of queries using those hierarchies.

Recommendation: Please see SAP Note:738098 "Performance problems with hierarchies"

67 Analysis of InfoProviders68 InfoProvider Distribution

The following section provides an overview of the distribution of your InfoProviders. Note that the following overview table takes into account only objects that can currently be used for reporting.

InfoProviders

BasisCubes

MultiProviders

Aggregates

Virtual

Cubes

Remote

Cubes

Transactional Cubes

ODS Object

s

Info Object

s

InfoSets

327 46 23 153 0 0 0 23 78 4

Aggregates

The table below displays the top 3 InfoCubes regarding the number of their aggregates.

InfoCube # AggregatesZCODI_L07 9ZCODI_L06 9ZCODI_A07 9

ODS Objects

The following table gives a summary of the ODS objects.



Description:BEx IndicatorWith the BEX indicator, you can determine whether the ODS object is immediately available for BEX queries. If the ODS object is not used for reporting, but only as a data container, you can delete the BEx Reporting indicator. The advantage is that no SIDs are generated, which leads to a better activation performance. If your ODS object reporting requirements are very "simple," in other words, if you are only selecting a limited number of records, you can use InfoSets for reporting on ODS objects even if the BEx reporting indicator is switched off. Please note that the loaded values are not checked for their correctness if SIDs are not generated. If you update the data of the ODS object in other data targets (DataMart functionality), SIDs are generated during this update should the BEx reporting indicator not be set. Additionally, it is possible to set the BEx reporting indicator even if the ODS object already contains data. In this case, the system generates the SIDs.

Unique Data RecordsIf each key field combination is only loaded once, you can set the indicator 'Unique Data Records,' which leads to a performance enhancement during activation. The system then does not need to check the existence of a record in the active data table and therefore a mass insert into the active table can be executed directly (otherwise, checks are first carried out to establish whether the datasets are already available in the active data table and then the dataset is marked either for update or insert). Additionally the data is not sorted.Attention: If the indicator 'Unique Data Records' is activated, the BW system does not guarantee unique records by deleting duplicates with regard to the ODS object key fields. Therefore the DataSource has to make sure that unique records are always delivered. If this is not the case, the ODS data activation will terminate.

# ODS Objects

# ODS Objects with BEX flag

# ODS Objects with unique flag

# Transactional ODS Objects

40 23 6 2

69 Dimensions with line item and high cardinality flag

We checked for InfoCubes that contain dimensions with an active "High-Cardinality" indicator and determined that the current settings are the same as our recommended settings.

Background: When this indicator is set, the database will create B*-tree indexes instead of bitmap indexes for this dimension. This can lead to a reduction in performance, as only bitmap indexes can be used for a Star-join access, which is the most effective way of selecting data.

70 InfoCube Design of Dimensions

We checked for InfoCubes with one or more dimensions containing 30% or more entries compared to the number of records in the fact tables and found that your InfoCubes' design is according to our recommendations.

Explanation: The ratio between the number of entries in the dimension tables and the number of entries in the fact table should be reasonable. If an InfoObject has almost as many distinct values as there are entries in the fact table, the dimension this InfoObject belongs to should be defined as a line item dimension. Instead of creating a dimension table that has almost as many entries as the fact table, the system then writes the data directly to the fact table.On the other hand, if there are several dimension tables with very few entries (for example, less than 10), those small dimensions should be combined in just one dimension.

In order to obtain this information for your InfoCubes:- Call transaction RSRV.- Choose "All Elementary Tests" - "Database."- Double-click the line "Database Information about InfoProvider Tables."- In the window on the right, choose "Database Information about InfoProvider Tables."- Enter the InfoCube name and choose "Execute Tests."- After the analysis finishes, choose "Display Messages" and open the analysis tree with the correct time stamp.

71 InfoCube partitioningInfoCube Range partition used Partitioning Valid From Partitioning Valid ToZCODI_A06 0CALMONTH 200607 200612ZCODI_L06 0CALMONTH 200607 200612

We have determined that the partitioning validity has been exceeded for the InfoCubes in the table above. These InfoCubes are currently active and have a range partitioning validity date of last year or before.

If you exceed the validity date for range partitioning, a single, new, and ever-growing partition will be created, which will contain all the latest data and all the previous data since the validity date was exceeded. This can lead to performance problems since the partition can grow quite large and will be accessed continually for the most



recent information. It will contain all of the data added to the cube since the validity date was exceeded.

Number of InfoCubes partitioned until this year10

F-Fact table partitioningTable names No. of Partitions/BIC/F100146 286/BIC/F100147 286/BI0/F0BWTC_C02 232/BI0/F0BWTC_C05 231/BI0/F0BWTC_C04 225/BI0/F0BWTC_C03 223/BIC/FYC11_ORD 197/BI0/F0BWTC_C09 174/BIC/F100155 147/BIC/F100156 116/BI0/F0BWTC_C11 107/BIC/F100104 96/BIC/F100071 94/BIC/F100102 88/BIC/F100098 86/BIC/F100096 85/BIC/F100069 83/BIC/F100103 79/BIC/F100070 76/BIC/F100097 75/BIC/F100105 61/BIC/F100072 60/BIC/FZC_OO 59/BIC/F100099 59/BIC/F100145 59/BIC/F100144 59/BIC/FZCORD_L07 54/BIC/FZCORD_A07 53/BIC/F100205 52/BIC/F100207 52/BIC/F100026 50/BIC/F100025 50/BIC/F100027 49/BIC/F100202 49/BIC/F100203 49/BIC/F100204 49/BIC/FZCSRIA07 45/BIC/FYC13_AGR 45/BIC/F100077 44/BIC/FZCINVL07 43/BIC/F100091 43/BIC/FZCSRIL07 43/BIC/F100164 41/BIC/FZCINVA07 41/BIC/F100165 39/BIC/F100125 39/BIC/F100126 38/BIC/F100123 38/BIC/F100093 37/BIC/F100085 36/BIC/F100092 36/BIC/FZCDELL07 34/BIC/F100079 34/BIC/F100167 32

The tables listed in the table 'F-Fact tables' have more than 30 partitions.

Recommendation: To avoid performance issues when these tables are read, we recommend that you use compression on the InfoCubes of these F-Fact tables. Please see SAP Note 590370 for further details.



Empty F-Fact table PartitionsF-fact table No.Empty Partitions/BI0/F0BWTC_C11 4/BIC/FZCORD_L07 2/BIC/FZCORD_A07 2/BIC/FZCDELL07 2/BIC/FZCINVA07 2/BIC/F100062 1/BIC/F100024 1/BI0/F0BWTC_C09 1/BI0/F0BWTC_C05 1

The #Empty Partitions# table contains up to ten F-fact tables with the highest number of empty partitions. There are 21 F-fact tables in total that contain empty partitions in your system. To check for tables with empty partitions, use report SAP_DROP_EMPTY_FPARTITIONS. See SAP Note 430486 for the appropriate recommendations for an overview or repair of F-fact tables in a BW InfoCube.

Note: If the values shown in the table above do not seem reasonable when compared to report SAP_DROP_EMPTY_FPARTITIONS, the database statistics are probably not up to date and we were therefore not able to collect the most current data. To fix this, refresh the statistics.

E-Fact-Table partitioning (Search for E Fact tables with many parts )

There is no action currently required as we have not found any E-Fact tables with 100 partitions or more.

72 Analysis of AggregatesAggregates only improve performance when they are used by your queries and when they summarize the data of the structure they are built from (the InfoCube or another aggregate). Unused or incorrect aggregates consume space on your database and increase the time needed for the roll-up and the change run procedure. For this reason, you should create proper aggregates in your system and regularly check that you are using the proper aggregates.We offer the following training courses for performance optimization: TEWA50 SAP BW Query tuning with aggregates.For more details about training, refer to the Internet address http://service.sap.com/empoweringworkshops73 Aggregates suggested for deactivation

We have found aggregates that are not used during query execution ("Number of calls" is equal to zero), or that are almost as large as the parent aggregate they are built from (the "Average reduce factor" is too low).

Recommendation: Consider deactivating or deleting the aggregates listed below.Note: Do not deactivate an aggregate that has been created to improve the performance of master data activation. This kind of aggregate (Basis aggregate) does not contain any navigational attributes or hierarchies. This means it is not affected during master data activation. Aggregates that must be recalculated during master data activation can access the Basis aggregate instead of the InfoCube during master data activation.

Cube name Aggr.-cube # entries Average reduce factor # calls Created at Last CallYC12_DEL 100020 147931 79 0 23.01.2007 ..0YC13_AGR 100025 4247937 2 1811 10.09.2006 25.03.2007YC13_AGR 100111 84588 1 426 31.10.2006 03.03.2007YC13_INV 100012 1718210 2 9638 18.01.2007 26.03.2007YC13_INV 100106 1696534 1 94 05.02.2007 01.03.2007YC13_INV 100114 51855 1 68 05.02.2007 03.03.2007YCPAPL_1 100028 20376 1 1300 14.01.2007 26.03.2007ZCDELA07 100166 32795 20 0 23.01.2007 ..0ZCDELL07 100167 131987 102 0 23.01.2007 ..0ZCINVA04 100116 100496 1 282 31.10.2006 03.03.2007ZCINVA05 100117 111371 1 214 31.10.2006 03.03.2007ZCINVA06 100118 63685 1 214 31.10.2006 03.03.2007ZCINVA07 100173 28073 1 164 19.01.2007 03.03.2007ZCINVA07 100171 25844 1 212 19.01.2007 01.03.2007ZCINVL04 100123 8945325 2 44 31.10.2006 06.03.2007ZCINVL07 100176 2138688 2 872 19.01.2007 26.03.2007ZCINVL07 100180 1272107 2 5378 19.01.2007 26.03.2007ZCINVL07 100179 1216995 1 212 19.01.2007 01.03.2007ZCINVL07 100181 0 0 198 19.01.2007 03.03.2007


http://service.sap.com/empoweringworkshops


Cube name Aggr.-cube # entries Average reduce factor # calls Created at Last CallZCODI_A06 100129 377182 1 3401 10.12.2006 26.03.2007ZCODI_A06 100152 120022 1 68 10.12.2006 23.03.2007ZCODI_A06 100132 38251 1 20846 10.12.2006 26.03.2007ZCODI_A07 100186 349526 2 3222 27.12.2006 26.03.2007ZCODI_A07 100191 145361 1 42 27.12.2006 23.03.2007ZCODI_A07 100189 60849 1 16393 27.12.2006 26.03.2007ZCODI_L06 100139 13500750 1 3401 10.12.2006 26.03.2007ZCODI_L06 100154 7149655 2 8317 10.12.2006 26.03.2007ZCODI_L06 100159 1862139 1 68 10.12.2006 23.03.2007ZCODI_L06 100141 699920 1 20785 10.12.2006 26.03.2007ZCODI_L07 100195 10351102 2 3196 27.12.2006 26.03.2007ZCODI_L07 100201 2415924 1 42 27.12.2006 23.03.2007ZCODI_L07 100198 965680 1 17226 27.12.2006 26.03.2007ZCORD_A06 100134 123998 2 111 12.12.2006 13.03.2007ZCORD_A07 100204 98119 1 102 27.12.2006 13.03.2007ZCORD_L07 100207 923215 2 102 27.12.2006 13.03.2007ZCPAPLA07 100221 7990 47 0 23.03.2007 ..0ZCPAPLA07 100209 1970 1 188 10.03.2007 26.03.2007ZCPAPLL07 100220 136819 66 0 23.03.2007 ..0ZCPAPLL07 100216 13207 694 0 10.03.2007 ..0ZCPAPLL07 100217 13207 1 154 10.03.2007 23.03.2007ZCPAPLL07 100214 10826 1 182 10.03.2007 26.03.2007ZCSRIL07 100165 244813 14 0 02.01.2007 ..0ZC_OO 100156 3316409 1 68 10.12.2006 23.03.2007

74 Aggregates Maintenance

The tables below show an overview of maintenance costs for your aggregates in the last six weeks.The first table shows the sum of all aggregates for each InfoCube. The second table shows up to 20 aggregates that required the most total maintenance time. In addition, we analyzed the three aggregates with the most "total time" in more detail.

CUBES [14.03.2007 05:42:03 26.03.2007 04:56:02]InfoCube Nr. of

AggregatesTotal time

[sec]% Rollup time

% (Re)creation time

% Delta Change-run time

Records inserted

Total 52 16812.5 13342801YC13_INV 8 8383.4 11 89 0 12894367YC13_AGR 5 1851.4 86 0 14 61717ZCINVL07 8 1533.7 100 0 0 237149ZCINVA07 8 1223.1 100 0 0 14051ZCPAPLL07 6 943.7 100 0 0 35746ZCPAPLA07 6 787.4 100 0 0 6046YCPAPL_1 4 459.8 100 0 0 20ZCDELL07 1 369.7 100 0 0 10673ZCSRIL07 1 306.1 100 0 0 23903ZCDELA07 1 282.1 100 0 0 2261ZCSRIA07 1 262.2 100 0 0 1712YCZO_1 1 171.0 13 87 0 55156YC12_DEL 1 147.3 88 0 12 0YC11_SR 1 91.6 93 0 7 0

AGG. [14.03.2007 05:42:03 26.03.2007 04:56:02]InfoCube Aggregate Total time

[sec]% Rollup time

% (Re)creation time


Records inserted

Total 16812.5 13342801YC13_INV 100060 2361.6 8 92 0 4125936YC13_INV 100012 2166.1 8 92 0 3436420YC13_INV 100106 1515.7 11 89 0 3393068YC13_INV 100010 867.3 11 89 0 544713YC13_INV 100013 746.3 13 87 0 953134YC13_AGR 100025 536.6 78 0 22 36206YC13_AGR 100026 489.8 76 0 24 16692YC13_AGR 100027 398.2 100 0 0 7257YC13_INV 100114 393.2 19 81 0 103710



InfoCube Aggregate Total time [sec]

% Rollup time

% (Re)creation time


Records inserted

ZCDELL07 100167 369.7 100 0 0 10673ZCINVL07 100176 338.8 100 0 0 74909ZCSRIL07 100165 306.1 100 0 0 23903ZCDELA07 100166 282.1 100 0 0 2261ZCSRIA07 100164 262.2 100 0 0 1712YC13_INV 100014 247.9 30 70 0 337386YC13_AGR 100024 230.2 100 0 0 474ZCINVL07 100180 220.6 100 0 0 47355ZCPAPLL07 100215 202.3 100 0 0 16224YC13_AGR 100111 196.6 83 0 17 1088ZCINVL07 100182 195.0 100 0 0 23530

75 Source System SettingsUpload customizing BW (SBIW)

In every SAP source system, part of the ROIDOCPRMS table controls the data transfer from the source system to the system. The table contains the following information:MAXSIZE - Maximum size of a data package in KBSTATFRQU - Number of packets that are transferred before statistical information is sentMAXLINES - Maximum number of records sent in one data packageMAXPROCS - Maximum number of dialog work processes for each upload request used to send the data to the systemTo ensure the performance and stability of the upload process, it is important that this table is set up correctly. We have checked the setup of this table for all source systems connected to the system.

Recommendation: To avoid potential extraction problems, change the entries in table ROIDOCPRMS in the different source systems as explained in the table below.

Consequences: If the setting for MAXSIZE is too large, data packets will also be very large. A system timeout may occur for work process(es) on the server assigned to these packets, or there may be problems with the memory. If the setting for MAXLINES is too large, the high number of records for each data packet might lead to dumps in the source system or memory problems on the server. If the values are too small, several small data packets are created, which increases the upload time. Note that you do not have to reduce the values if you have enough resources available (memory, work processes) and your parameter settings are tested carefully.

Implementation: To implement those settings you have two possibilities:a) Modify all source systems centrally using the Administration Workbench ofCall transaction RSA1, click a source system using the secondary mouse button, and choose #Customizing for Extraction#. The system navigates directly to the selected source system in transaction SBIW. Choose General Settings -> Maintain Control Parameters for the Data Transfer.b) Maintain the settings in the different R/3 source systems.Call transaction SBIW and choose General Settings ->Maintain Control Parameters for the Data Transfer.

Note: If table ROIDOCPRMS is empty, the systems use default values during runtime. The defaults are 10,000 for MAXSIZE and 100,000 for MAXLINES. The default for MAXSIZE is small whereas the default for MAXLINES is reasonable for most systems. In some cases, it may be necessary to set the values for some of the parameters outside our recommended range.One example of this is the MAXPROCS parameter (maximum number of dialog work processes for each upload request). This parameter limits the use of resources during an upload in order to prevent a resource bottleneck occurring in the system. If you reduce the setting for this parameter, the upload performance may suffer even though there are enough system resources available.If you use your as a DataMart, you have to maintain this table in the system as well.

System name Parameter name Current value Recommended valueP60CLNT320 maxsize 000000 20000P60CLNT320 statfrqu 00 10P60CLNT320 maxprocs 00 3

76 Important Notes for Source System Upload SettingsTo optimize upload performance and to prevent any loading problems for the R/3 source systems, check and implement the following SAP Notes as soon as possible.



Note Number

Description

327828 Performance of BW supply systems385741 Collective runs are not deleted351936 Problems with different collective runs

77 Recommendations for BW78 General Parameters

The table shown here provides an overview of the Customizing parameters of the table 'RSADMIN' of which some or all are considered INVALID.

Each parameter is assigned a rating in the column 'Invalid,' which details the reason for the parameters validity. Additionally, a check is made as to whether a duplicate exists. Only parameters that are invalid/duplicates and/or have an OSS note available will be displayed.

The validity rating is explained below, sequence 0-5 :Invalid 0 = This means the parameter is valid and used correctly.Invalid 1 = This parameter is invalid and you should reconsider the setting, because it is either not recognized as existing or your current release does not support the use of this parameter.Invalid 2 = This parameter is invalid and you should reconsider the setting, because a value is mandatory for this parameter but none was found.Invalid 3 = This parameter is invalid and you should reconsider the setting, because it is not relevant for your current database.Invalid 4 = This parameter is invalid and you should reconsider the setting, because your current support package does not support its use.Invalid 5 = This parameter is invalid and you should reconsider the setting, because your SAPI release is not sufficient.

Recommendation: Please verify if the parameters showing as invalid can be removed or have to be changed. If duplicates exist, please remove the incorrect version.

PARAM_NAME VALUE OSS_NOTE INVALID DUPLICATEBW_USER BIWREMOTE 410952 0CR_MAXWPC 6 534630 0CR_RFCGROUP PARALLEL_GENERATORS 534630 0CSV_MIMETYPE 705011 2IS_MO_AUTH_CHECK 766432 2ORA_CUBEINDEX_INITRANS 20 750033 0ORA_ODS_TABLE_INITRANS 20 831234 0REUSE_XL_INSTANCE 709141 2

79 BW Support PackageThe Support Package applied to your BW release 3.50 is not up-to-date.

Recommendation: Apply the most recent Support Package.Implementation: For information about implementing SAP Support Packages, see SAP Note 97621. Also check the SAP Notes mentioned in the following tables.

BW CURRENT SUPPORT PACKAGEProduct Release Support Package Level BI Content Add-on Add-on Support Package3.50 13 353 0003

BW AVAILABLE SUPPORT PACKAGESProduct Release Support Package Level Notes3.50 17 872277

BW AVAILABLE CONTENT ADD-ONSBI Content Add-ons Content Support packages Notes353 7 786286702 4 908488703 1 908176

Please also check if you need to update your applied Support Package Stack (SP Stack).

SP Stacks are released quarterly as a set of support packages and patches offered for a product version and its



underlying components. The contained support packages must be used in the given combination. We recommend regular application of these SP Stacks.

More information can be found in service marketplace under Quick Link /sp-stacks.80 Important notes for BWThe table below lists important SAP Notes for BW that deal with performance and data security.

Note Number

Description

0309824 BW problem message / Support Packages, Patches0166433 Options to find aggregates0423099 "Low Speed Connection" Parameter and BEx Analyzer0558994 General information on BW front-end patches0550669 Compressed transfer of BW Web Applications0567747 Composite note BW 3.x performance: Extraction0567746 Composite note BW 3.x performance: Query0567745 Composite note BW 3.x performance: DB-specific

DATA CONSISTENCYNote Number Description Area598691 Check: InfoObjects with ALPHA and fields without ALPHA Check Tools323140 DUPREC short dump when loading master data Data Loading529789 BW extraction/extractor checker differences Data Loading487393 Incorrect values with star_transformation_enabled=true Database534295 Incorrect values in the BW environment Database565086 Composite SAP note: Incorrect data in DataMart or Query Query

81 BI - KPIs

There are BW Key Performance Indicators that exceed their reference value. This indicates severe problems, or at least optimization potential for performance, data volumes, and administration.Based on these key figures, we recommend that you order the corresponding services for further analysis. The table below shows the KPIs, their observed value, and the reference limit. The last column contains the Service Code for finding the appropriate service in the second table, "Available Services".

RECOMMENDATIONSKPI Description Observed Reference Rating Recommended

ServicesNrDelAggr (#)

Nr of Aggregates recommended to delete

43 20 YELLOW E1

AVAILABLE SERVICESService Code

Service Name Description Link

G1 General link to support services

http://service.sap.com/supportservices

SAFEGUARDINGS1 EarlyWatch Service Remote analysis of system

parameters and technical performance tuning

http://service.sap.com/safeguarding

OPTIMIZATIONO1 BPPO - Extraction and

LoadingOptimization of critical load path http://service.sap.com/bppo

O2 BPPO - Query Tuning Optimization of query execution http://service.sap.com/bppoO3 BPPO - Planning and

SimulationOptimization of Planning and Simulation Application

http://service.sap.com/bppo

O4 SAP Remote Performance Optimization

http://service.sap.com/rpo

O5 SAP System Administration for BI

Knowledge transfer for optimal business process administration

http://service.sap.com/sysadmin

O6 SAP Data Volume Management for SAP BW

Analysis of disk space saving potential

http://service.sap.com/dma

EMPOWERINGE1 TEWA50 - Query tuning

with aggregatesWorkshop - Efficient Aggregate Control and Query Tuning

Official classroom training - TEWA50

E2 PDEBW2 - BI Reporting Authorizations

Workshop - Reporting Authorization Setup and Optimization

Official classroom training - PDEBW2


http://service.sap.com/dma

http://service.sap.com/sysadmin

http://service.sap.com/rpo




http://service.sap.com/safeguarding




82 Nametab inconsistenciesNAMETAB INCONSISTENCIESTable # Total # View 01 # View 02 # View 03 # View 04 # View 05 # View 06DDNTT 1953 0 47 1566 0 0 340DBDIFF 4629 301 47 1565 1371 1345 0RSDD_TMPNM_ADM 697 307 47 1 1 1 340DBA_VIEWS 0 0 0 0 0 0 0

There are several entries in tables DDNTT and DDNTF that cannot be found in tables DBDIFF and RSDD_TMPNM_ADM (or in the DB_VIEWS of Oracle).This means that these temporary entries are obsolete and no longer used.

SAP Note: 449891 Temporary database objects in BW 3.x

Actions:1. If there are too many entries in DBDIFF:After a change run, obsolete entries may still appear in table DBDIFF.This table has buffer mode FULL => for example: one day it grew up to 247MB.The problem is solved in the following Support Packages:- BW 3.0B Support Package 22- BW 3.10 Support Package 16- BW 3.50 Support Package 4Report SAP_UPDATE_DBDIFF clears these obsolete entries from table DBDIFF.The problem may occur also in systems containing the correct Support Package if the correction report has not yet been run.SAP Note: 736845 After Change Run entries in DBDIFF resist

2. If there are several entries for 03 views in DBDIFF:Use report SAP_UPDATE_DBDIFF to clean DBDIFF.The report checks temporary objects in table RSDD_TMPNM_ADM and deletes any unnecessary ones.

3. If there are several entries for 06 views in RSDD_TMPNM_ADM:SAP Note: 698280 Reduce number of 06-er Tables in the database

4. If there are too many entries for 01 views in RSDD_TMPNM_ADM:SAP Note: 811354 Usage of complex queries reduces the performance of the database

5. If there are too many entries for 03 views in RSDD_TMPNM_ADM:Use the function module RSDDTMPTAB_CLEANUP as described inSAP Note: 867000 Inconsistencies in temporary tables of TYPE 06

6. If there are too many entries for 03 views in DDNTT and DDNTF compared to the number of entries in DBDIFF/RSDD_TMPNM_ADM.Several obsolete entries in the dictionary tables that are not cleanedUse the SAP_DROP_TMPTABLES report as described inSAP Note: 883843 "BW instances can no longer be started"

Final result:Run SAP_DROP_TMPTABLES, SAP_UPDATE_DBDIFF or RSDDTMPTAB_CLEANUP depending on the situation to clean obsolete temporary entries.

83 Frontend ServersTo ensure the best performance and stability on your frontend servers, you must install the most recent frontend server release and patch level.

From frontend server 2.0B patch level 6 onwards, the installation data of the frontend server is written to the BW server table RSFEC.

During this session, we downloaded and checked the most recent information (in a time frame of two weeks) with respect to the frontend server release and patch level used and the installation of a maximum of 100 frontend servers.

Even though we checked up to 100 frontend servers, other frontend servers may still have severe problems. We cannot check frontend servers with an older release or patch level than frontend server 2.0B patch level 6.



The following table gives an overview of the results.

SUMMARY OF CHECKED PCSRating Number of PCs checkedGreen 0Yellow 0Red 6

For more information about the problems we detected, please refer to the following sections.84 PCs with outdated Patch LevelThe frontend patch installed on some of your frontend servers is not current.

Recommendation: Immediately update the frontend servers listed in the following table to the newest frontend patch available.

PC Name Current Frontend Release

Current Frontend Patch

Recommended Frontend Release

Recommended Frontend Patch

Rating

USCORCLKWKS234 3.50 6 3.50 9 RedUSCORCRFWKS004 3.50 6 3.50 9 RedUSCORCRFWKS040 3.50 6 3.50 9 RedUSCORCRFWKS069 3.50 6 3.50 9 RedUSCORCRFWKS070 3.50 6 3.50 9 RedUSCORCRFWKS074 3.50 6 3.50 9 Red

85 PCs with old SAP GUI installationAvailable SAP GUI releases for your BW release SAP GUI version support timeline6.20 SAP GUI 6.20 support is planned to be "long term".6.40 SAP GUI 6.40 support ends on December 31, 2007.


86 Trend Analysis

86 Trend AnalysisThis section contains the trend analysis for key performance indicators (KPIs). Diagrams or tables are built week by week after activating the EarlyWatch Alert Service.

87 System ActivityThe following diagrams or tables contain data about system activity:

- Total Activity: Transaction steps performed each week (in thousands) - Dialog Activity: Transaction steps performed in dialog task each week (in thousands) - Peak Activity: Transaction steps in hour during the peak hour; this peak hour is calculated as the hour with the maximum dialog activity in the ST03 time profile divided by 5 (work days) - Total Users: Users that logged on in the week - Active Users: Users that have performed more than 400 transaction steps in the week

88 Response TimesThe following diagram or table show the development of the response times: - Average response time in dialog task (total, DB and CPU parts) - Average response times for database requests - Average response times for the top 5 transactions


86 Trend Analysis

Transaction Code Load (%)RSA1 38.1SESSION_MANAGER 15.7RSPCM 13.2RSANWB 10.7RSAN_WB_TST 8.0

89 System OperationThe following diagram or table shows important KPIs for system operation.

Note: The column 'Availability' is filled for systems with SAP Basis 4.6 and higher.


86 Trend Analysis

90 Hardware Capacity


SAP Support Service Document - Lenoir-Rhyne...

Documents

Transcript of SAP Support Service Document - Lenoir-Rhyne...