earlywatch alert-uky production 1 service summary update errors table reorganization hardware...

1

SAP Support Mailbox

From: Batch ID for Basis <[email protected]>Sent: Monday, April 20, 2015 9:49 PMSubject: R3D - Critical (Yellow) - SAP EarlyWatch Alert

Analysis from 04/13/2015 Until 04/19/2015

Report: R3D, Not ProductiveInstallation: 0020171817

Session: 0010000007376

EarlyWatch Alert-UKY Production

1 Service Summary

This EarlyWatch Alert session detected issues that could potentially affect your system. Take corrective action as soon as possible.

Alert Overview

Gateway Access Control List (reg_info/sec_info) contains trivial entries

Transport request have been created or changed in production

Some tablespaces with long read or write times were detected.

Hardware resources may have been exhausted with the risk of performance degradation.

Standard users have default password.

Secure password policy is not sufficiently enforced.

A high number of users has critical authorizations

Protection of Passwords in Database Connections

Perform the following Guided Self Services.

Guided Self Service FAQ SAP Note

Security Optimization Service 696478

Transport Execution Analysis 1621722

For more information about Guided Self-Services, see SAP Enterprise Support Academy.

2

Register for an Expert-Guided Implementation Session for the Guided Self-Service at SAP Enterprise Support Academy - Learning Studio - Calendar.

Check Overview Topic Rating Topic Subtopic

Rating Subtopic

SAP System Configuration

Database - Maintenance Phases

Operating System(s) - Maintenance Phases

Performance Overview

Performance Evaluation

Workload Distribution

Workload by Application Module

DB Load Profile

SAP System Operating

Availability based on Collector Protocols

Program Errors (ABAP Dumps)

Update Errors

Table Reorganization

Hardware Capacity

DB Performance

Database Version

Locking

Average Read and Write Times

Missing Indexes

DB Administration

Database Growth and Freespace

10 Largest and Fastest Growing Tables

Tablespaces with a critical size

Tables with a critical size

Table Virtualization

Enhanced Monitoring

Log File Management

Logfiles Recommendations

Database Backup History

Database Server Load From Expensive SQL Statements

Expensive SQL Statements

Database Server Load

Security

Default Passwords of Standard Users

Control of the Automatic Login User SAP*


3

Check Overview Topic Rating Topic Subtopic

Rating Subtopic

ABAP Password Policy

Users with Critical Authorizations

Software Change Management

Number of Changes

Failed Changes

Note: The recommendations in this report are based on general experience. Test them before using them in your production system. Note that EarlyWatch Alert is an automatic service.

Note: If you have any questions about the accuracy of the checks in this report or the correct configuration of the SAP Solution Manager EarlyWatch Alert service, create a customer message on component SV-SMG-SER-EWA.

Note: If you require assistance in resolving any concerns about the performance of the system, or if you require a technical analysis of other aspects of your system as highlighted in this report, create a customer message on component SV-BO. For details of how to set the appropriate priority level, see SAP Note 67739.

Performance Indicators for R3D The following table shows the relevant performance indicators in various system areas.

Area Indicators Value Trend

System Performance Active Users (>400 steps) 29

Avg. Availability per Week 100 %

Avg. Response Time in Dialog Task 588 ms

Max. Dialog Steps per Hour 904

Avg. Response Time at Peak Dialog Hour 502 ms

Avg. Response Time in RFC Task 10872 ms

Max. Number of RFCs per Hour 1125

Avg. RFC Response Time at Peak Hour 5382 ms

Hardware Capacity Max. CPU Utilization on DB Server 11 %

Database Performance Avg. DB Request Time in Dialog Task 135 ms

Avg. DB Request Time for RFC 51 ms

Avg. DB Request Time in Update Task 217 ms

4

Area Indicators Value Trend

Database Space Management DB Size 267.48 GB

DB Growth Last Month 0.43 GB

2 Landscape

2.1 Products and Components in current Landscape Product SID SAP Product Product Version R3D SAP ERP ENHANCE PACKAGE 6.06 Main Instances (ABAP or Java based) SID Main Instance R3D SAP ECC Server R3D Add-on: DMIS - 2.0 Databases SID Database System Database Version R3D DB2 for Linux UNIX and Windows 9.7

2.2 Servers in current Landscape SAP Application Servers SID Host Instance Name Logical Host ABAP JAVA R3D r3dev r3dev_R3D_00 r3dev

DB Servers SID Host Logical Host (SAPDBHOST) R3D r3dev r3dev

2.3 Hardware Configuration Host Overview

Host Hardware Manufacturer Model CPU

Type Virtualization Operating System

No. of CPUs

Memory in MB

r3dev IBM 8205-E6B POWER7 SPLPAR,

UNCAPPED AIX 6.1 16 16384

3 Service Preparation and Data Quality of R3D

5

Configuration hints for optional service data are provided.

SAP ERP ENHANCE PACKAGE system R3D is not fully prepared for delivery of future remote services.

Rating Check Performed

Service Data Quality

ST-PI and ST-A/PI Plug-Ins

Service Preparation Check (RTCCTOOL)

Service Data Control Center

Hardware Utilization Data

In preparation for SAP services, ensure that connections, collectors, and service tools are up to date. These functionalities are explained in SAP Notes 91488 and 1172939.

3.1 Service Data Quality The service data is collected by the Service Data Control Center (SDCCN) or read from the Solution Manager's BW or Configuration and Change Database (CCDB).

This section comprehensively shows issues with the data quality and provides hints on how to resolve them.

Legend for 'Priority' in Service Data Quality Prio. Explanation: Impact of Missing or Erroneous Data

Overall important data are missing. Detecting a critical situation may fail. Report cannot be rated green or yellow.

Data for an important chapter are missing. Some issues may not be detected. Report cannot be rated green.

Some important check could not be processed. The report can be rated green nevertheless.

Only checks of minor importance are affected.

An optional check was skipped.

3.1.1 Quality of Service Data in Solution Manager Diagnostics - BW

Prio. Report Area affected Details and Related Infocube SAP

Note

Workload of ABAP System R3D

Reading performance data from BW returned neither data nor an error code. A timeout may have occurred. Infocube: 0CCMSMTPH used in section 'Workload

1332428

6

Prio. Report Area affected Details and Related Infocube SAP

Note

Overview R3D'.

3.2 ST-PI and ST-A/PI Plug-Ins The table below shows the service plug-ins implemented and their releases and patch levels. These recommendations are derived from report RTCCTOOL. For more information about RTCCTOOL, see SAP Note 309711.

Rating Plug-In Release Patch Level Release Rec. Patch Level Rec.

ST-A/PI 01R_731 1 01R_731 1

ST-PI 2008_1_700 11 2008_1_700 11

3.3 Hardware Utilization Data

Host Operating System Performance Data

r3dev AIX 6.1 --

Hardware capacity checks could not be run successfully due to missing data. See SAP Note 1309499.

4 Software Configuration For R3D

We have listed recommendations concerning the current software configuration on your system.

Your system's software versions are checked. If known issues with the software versions installed are identified, they are highlighted.

4.1 Codepage Technology Support It was not possible to detect whether you are using other codepage technologies in addition to Unicode. We support and fully recommend Unicode in systems involving multiple languages. As of SAP NetWeaver Release 7.0, Unicode is the only supported

7

and available codepage technology.

We can only ensure data consistency in installations with multiple languages if the entire system is based on Unicode. See SAP Note 838402 -> Attachments -> "Customer Letter" for information about our supported codepage technologies. Recommendation: If you are using a codepage technology other than Unicode, we recommend that you review our disclaimer, which you can find at: /unicode -> Unicode Media Library -> SAP ERP 6.0 and MDMP -> "Disclaimer: MDMP with SAP 6.0". For more information about how to migrate to Unicode completely, see the document "Roadmap: From MDMP to SAP ERP 6.0 Unicode", which you can find at the path above.

We recommend that you review SAP Note 179991, which contains recommendations relevant to your SAP component. If you are not using multiple languages, ignore this recommendation.

4.2 SAP Application Release - Maintenance Phases

SAP Product Version End of Mainstream Maintenance Status

EHP6 FOR SAP ERP 6.0 12/31/2025

In October 2014, SAP announced a maintenance extension for SAP Business Suite 7 core application releases to 2025. If you are running a relevant release, see SAP Note 1648480 for more details and applicable restrictions.

4.3 Support Package Maintenance - ABAP The following table shows an overview of currently installed software components.

Support Packages

Software Component Version Patch

Level

Latest Avail. Patch Level

Support Package Component Description

DMIS 2011_1_731 7 8 SAPK-11607INDMIS DMIS Component

EA-APPL 606 12 14 SAPK-60612INEAAPPL

SAP R/3 Enterprise PLM, SCM, Finance

EA-DFPS 606 12 14 SAPK-60612INEADFPS

SAP R/3 Enterprise Defense Forces & Public Security

EA-FINSERV 606 12 14 SAPK-60612INEAFINSRV

SAP R/3 Enterprise Financial Services

EA-GLTRADE 606 12 14 SAPK-60612INEAGLTRAD

SAP R/3 Enterprise Global Trade

EA-HR 606 41 48 SAPK-60641INEAHR SAP R/3 Enterprise Human Resources

EA-IPPE 406 7 8 SAPK-40607INEAIPPE

SAP R/3 Enterprise Integrated Product and Process Engineering

EA-PS 606 12 14 SAPK-60612INEAPS SAP R/3 Enterprise

8

Support Packages


Level



Public Services

EA-RETAIL 606 12 14 SAPK-60612INEARETAIL

SAP R/3 Enterprise Retail

ECC-DIMP 600 13 26 SAPK-60013INECCDIMP

ECC Discrete Industries Mill Products

ERECRUIT 606 12 14 SAPK-60612INERECRUIT SAP E-Recruiting

FI-CA 606 12 14 SAPK-60612INFICA FI-CA, Contract Accounts Receivable and Payable (virtuell)

FI-CAX 606 12 14 SAPK-60612INFICAX

FI-CAX: Extended FI-CA

FINBASIS 600 25 26 SAPK-60025INFINBASIS

SAP R/3 Enterprise FINBASIS

HCLRL 402_600 7 SAPK-40207INHCLRL

INSURANCE 600 13 26 SAPK-60013ININSURANC

INSURANCE SAP Insurance

IS-CWM 600 13 26 SAPK-60013INISCWM

IS-CWM Catch Weight Management

IS-H 606 15 SAPK-60615INISH IS-Hospital IS-M 600 13 26 SAPK-60013INISM IS Media

IS-OIL 600 13 26 SAPK-60013INISOIL

IS-OIL SAP OIL & GAS Upstream / Downstream

IS-PS-CA 606 12 14 SAPK-60612INISPSCA

IS-PS-CA, Tax&Revenue; Campus Management

IS-UT 600 13 26 SAPK-60013INISUT IS-UT

LSOFE 606 6 7 SAPK-60606INLSOFE

Learning Solution - Front End

MDG_APPL 606 12 14 SAPK-60612INMDGAPPL MDG Applications

MDG_FND 731 12 14 SAPK-73112INMDGFND MDG Foundation

OTEXBAS 1000_700 1 SAPK-30401INOTEXBAS

Opentext Basis Add On

OTEXEIM 0350_605 0 Otexeim OTEXERP 1000_600 0 DOCU LINK ERP OTEXRL 1000_700 0 Otexrl

PI_BASIS 731 12 15 SAPK-73112INPIBASIS SAP R/3 Basis Plug-In

PLMWUI 702 12 14 SAPK-70212INPLMWUI PLM WUI

SAP_ABA 731 12 15 SAPKA73112 SAP Application Basis

SAP_AP 700 31 32 SAPKNA7031 SAP Application Platform

9

Support Packages


Level



SAP_APPL 606 12 14 SAPKH60612 SAP R/3 Standard SAP_BASIS 731 12 15 SAPKB73112 SAP Basis Component

SAP_BS_FND 731 12 14 SAPK-73112INSAPBSFND

SAP Business Suite Foundation

SAP_BW 731 12 15 SAPKW73112 SAP Business Information Warehouse

SAP_HR 604 79 86 SAPKE60479 SAP R/3 Standard HR SEM-BW 600 25 26 SAPKGS6025 SAP SEM Server

SMERP 610_700 4 4 SAPK-61004INSMERP SMERP

SMFND 610_700 4 4 SAPK-61004INSMFND SMFND

SPINGTK 203_700 0 Spinifexit-generic Reporting by SpinifexIT Pty Ltd

ST-A/PI 01R_731 1 2 SAPKITAB9N SAP Service Tools for Applications Plug-In

ST-PI 2008_1_700 11 11 SAPKITLRDK SAP Solution Tools Plug-In

USC2B 100 1 1 SAPK-10001INUSC2B Usc2b

WEBCUIF 731 12 14 SAPK-73112INWEBCUIF SAP Web UIF

4.4 Database - Maintenance Phases

Database Version End of Standard Vendor Support* Comment Status SAP

Note

DB2 for Linux, UNIX and Windows 9.7 See Relevant SAP

Note

1168456

* Maintenance phases and duration for the DB version are defined by the vendor. Naming of the phases and required additional support contracts differ depending on the vendor. Support can be restricted to specific patch levels by the vendor or by SAP.

The end of vendor support dates given in this table are the regular End-of-Support dates published by IBM. If you have obtained your DB2 license from SAP ("application-specific license" (ASL) or "OEM license", as explained in SAP Note 1260217), refer to the SAP Note listed in the table.

See the "Database Version" section in the database section for additional information.

4.5 Operating System(s) - Maintenance Phases

10

Host Operating System

End of Standard Vendor Support* Comment Status SAP

Note

r3dev AIX 6.1 Not Yet Defined by Vendor

1179765

* Maintenance phases and duration for the OS version are defined by the vendor. Naming of the phases and required additional support contracts differ depending on the vendor. Support can be restricted to specific patch levels by the vendor or by SAP. Check in the referenced SAP Note(s) whether your SAP system requires a specific patch release to guarantee support for your operating system version.

4.6 SAP Kernel Release The following table lists all information about your SAP kernel(s) currently in use.

Instance(s) SAP Kernel Release Patch Level Age in Months OS Family

r3dev_R3D_00 721_EXT_REL 300 11 AIX

4.6.1 Kernel out of date

Your current SAP kernel release is probably not up to date.

Recommendation: Make sure that you are using the recommended SAP kernel together with the latest Support Package stack for your product.

4.6.2 Additional Remarks

SAP releases Support Package stacks (including SAP kernel patches) on a regular basis for most products (generally 2–4 times a year). We recommend that you base your software maintenance strategy on these stacks.

You should only consider using a more recent SAP kernel patch than that shipped with the latest Support Package Stack for your product if specific errors occur.

For more information, see SAP Service Marketplace at http://service.sap.com/sp-stacks (SAP Support Package Stack information) and http://service.sap.com/patches (patch information).

5 Hardware Capacity

11

We have checked your solution for potential CPU or memory bottlenecks and found that the hardware resources may have been exhausted. An increase in the workload may have a negative impact on performance.

No CPU virtualization data is available for at least one shared CPU pool LPAR (SPLPAR).

Recommendation: For more information about providing the data required for SAP services, see SAP Notes 994025 and 1147334.

5.1 Overview System R3D General This analysis focuses on the workload during the peak working hours (9-11, 13) and is based on the hourly averages collected by SAPOSCOL. For information about the definition of peak working hours, see SAP Note 1251291.

CPU If the average CPU load exceeds 75%, temporary CPU bottlenecks are likely to occur. An average CPU load of more than 90% is a strong indicator of a CPU bottleneck.

Memory If your hardware cannot handle the maximum memory consumption, this causes a memory bottleneck in your SAP system that can impair performance. The paging rating depends on the ratio of paging activity to physical memory. A ratio exceeding 25% indicates high memory usage (if Java has been detected 0%) and values above 50% (Java 10%) demonstrate a main memory bottleneck.

Server Max. CPU load [%] Date Rating RAM

[MB] Max. Paging [% of RAM] Date Rating

r3dev

16384 0

6 Business Key Figures System errors or business exceptions can be a reason for open, overdue, or unprocessed business documents or long-lasting processes. SAP Business Process Analysis, Stabilization and Improvement offerings focus on helping you to find these documents (as it may directly or indirectly negatively impact business).

This section provides an example of indicators, and its findings are a basis of further SAP offerings. In the example below, the backlog of business documents is compared to daily or weekly throughput or set in relation to absolute threshold numbers.

It provides business information to discuss possible technical or core business improvement process potential.

SAP tools and methods can help to monitor and analyze business processes in more detail.

NOTE: Overdue or exceptional business documents are often caused by system errors, such as user handling issues, configuration or master data issues, or open documents on inactive organizational units or document types, that can be included in the measurements. These documents are rarely processed further by the business departments and often do not have a direct impact on customer satisfaction, revenue stream, or working capital. Nevertheless, these documents can have negative impacts on other areas such as supply chain planning accuracy, performance (of other transactions, reports, or processes), and reporting quality.

12

6.1 SAP Business Process Analytics With SAP Business Process Analytics in SAP Solution Manager, you can continuously analyze the above key figures and around 750 additional out-of-the-box key figures for continuous improvement potential in your SAP business processes.

With SAP Business Process Analytics, you can perform the following functions:

(1) Internal business process benchmarking (across organizational units, document types, customers, materials, and so on) for a number of exceptional business documents and/or for the cumulated monetary value of these documents.

(2) Age analysis to measure how many open documents you have from the previous years or months.

(3) Trend analysis for these business documents over a certain time period.

(4) Create a detailed list for all of these exceptional business documents in the managed system, enabling a root cause analysis to find reasons why these documents are open, overdue, or erroneous.

SAP Business Process Analytics can help you to achieve the following main goals:

- Gain global transparency of business-relevant exceptions to control template adherence

- Improve process efficiency and reduce process costs by reducing system issues and eliminating waste (for example, user handling, configuration issues, and master data issues)

- Improve working capital (increase revenue, reduce liabilities and inventory levels)

- Ensure process compliance (support internal auditing)

- Improve supply chain planning (better planning results and fewer planning exceptions)

- Improve closing (fewer exceptions and less postprocessing during period-end closing)

SAP also provides business process improvement methodology to help you identify and analyze improvement potential within your business processes using Business Process Analytics in SAP Solution Manager and visualize it for your senior management.

For more information, navigate to the following link: here.

6.2 SAP Active Global Support Follow-Up Opportunities In general, SAP Active Global Support provides several self-assessments or guided services to encourage customers to benefit from an SAP Business Process Stabilization and/or Business Process Improvement project. If you have an SAP Enterprise Support contract, SAP Active Global Support provides you with the following offering for obtaining business process analytics and implementing improvements:

- SAP Expert Guided Implementation Business Process Analytics and Improvement (SAP EGI Portfolio Overview)

13

- CQC Business Process Analytics and Improvement (fact sheet).

If you have an SAP Max Attention Contract, contact your Technical Quality Manager (TQM) for information about how SAP Active Global Support can help you obtain business process analytics and implement improvements.

7 Workload of System R3D This chart displays the main task types and indicates how their workload is distributed in the system. The table below lists the detailed KPIs.

Response Time Components In Hours Task Type Response Time Wait Time CPU Time DB Time GUI Time RFC 369.2 0.0 0.8 1.7 0.0 BATCH 34.9 0.0 3.3 19.5 0.0 Others 6.5 0.0 0.3 1.4 1.1

7.1 Workload By Users User activity is measured in the workload monitor. Only users of at least medium activity are counted as 'active users'.

Users Low Activity Medium Activity High Activity Total Users

dialog steps per week 1 to 399 400 to 4799 4800 or more

measured in system 43 22 7 72

7.2 Workload Distribution R3D The performance of your system was analyzed with respect to the workload distribution. We did not detect any major problems that could affect the performance of your SAP system.

14

7.2.1 Workload by Application Module

The following diagrams 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 application

All programs that are not classified in the SAP Application Hierarchy (transaction SE81) are summarized in the "Un-Assigned" category. Customer programs, industry solutions, and third-party add-on developments fall into this category.

7.2.2 DB Load Profile

The number of work processes creating database load in parallel is not significantly high.

The following diagram shows the DB load caused by dialog, RFC, HTTP(S), and background tasks, over different time frames.

15

The data provided in the diagram represents the average number of database processes occupied by each task type in the database during the specified time frames.

These statistics are calculated as a weekly average, the average values over six working days with a unit of one hour.

By comparing the load profiles for dialog and background activity, you can get an overview of the volume of background activity during online working hours.

8 Performance Overview R3D

The performance of your system was analyzed with respect to the average response times and total workload. We did not detect any major problems that could affect the performance of your system.

Rating Check

Performance Evaluation

The following table shows the average response times for various task types:

Averages of Response Time Components in ms Task type

Dialog Steps

Response Time

CPU Time

Wait Time

Load Time

DB Time

GUI Time

DIALOG 33689 588.5 35.5 1.2 10.0 135.3 122.1 RFC 122259 10,872.4 24.2 0.7 0.6 50.9 0.0 UPDATE 408 244.7 12.3 3.6 3.7 217.2 0.0 UPDATE2 341 278.8 17.8 16.5 4.1 215.9 0.0

16

Averages of Response Time Components in ms Task type

Dialog Steps

Response Time

CPU Time

Wait Time

Load Time

DB Time

GUI Time

BATCH 86049 1,461.5 136.3 0.4 3.9 816.6 0.0 SPOOL 10082 10.5 0.4 3.6 0.1 2.8 0.0 HTTP 21916 177.0 5.5 1.9 4.7 22.0 0.0

8.1 Performance Evaluation The measured times are compared against reference times to provide a rating.

- If the number of dialog steps in an hour is less than 1000, this hour is not considered.

- If the total number of transaction steps is less than 24000, the rating for the task is not performed (indicated by a gray icon in the table).

The table below shows that no problem is expected on the application or database servers.

Task Steps Application Server Performance Database Server Performance

Dia 33689

Upd 408

HTTP 21916

HTTPS 0

The ratings in the table above are determined by comparisons against the reference table below.

If the dialog response times are very poor, it will cause a RED rating for the entire check.

Task Reference for Avg. Response Time (ms) Yellow Rating

Reference for Avg. Response Time (ms) Red Rating

Reference for Avg. DB time (ms) Yellow Rating

Reference for Avg. DB time (ms) Red Rating

Dia 1200 3600 600 1800

Upd 2400 3600 1200 1800

HTTP 1200 3600 600 1800

HTTPS 1200 3600 600 1800

8.2 Transaction Profile Check

17

The following tables show the response times and the number of dialog steps for the transactions that cause the heaviest workload in your system.

8.2.1 Transactions by Total Workload

The following tables list the activities with the highest contribution to the total workload.

Workload by Transaction (Batch)

Transaction Dialog Steps

Total Resp. Time in %

Total Resp. Time in s

Total CPU Time in s

Total DB Time in s

RSDBAJOB 7 45.6 67,961.0 8,306.0 54,817.2 SWNC_TCOLL_STARTER 5200 21.0 31,334.0 584.0 2,066.3 SRT_WS_IDP_SWITCH_BD_CONT 84 3.5 5,248.0 1.0 14.1 SAPRSLOG 7 2.4 3,561.0 246.0 3,268.7 RSAL_BATCH_TOOL_DISPATCHING 336 1.6 2,451.0 254.0 1,359.9 ZCM_ENROLLMENT_REPORT_NEW 42 1.4 2,076.0 290.0 1,955.3 PFCG_TIME_DEPENDENCY 28 1.4 2,043.0 560.0 848.0 (BATCH) 35654 1.0 1,537.0 220.0 667.1 RS_CI_DELETE 7 0.7 1,046.0 0.0 1,045.4 RSBTCRTE 25212 0.7 1,041.0 380.0 302.1

1.4% of the total response time in the above table is caused by customer transactions.

8.2.2 Transactions by DB Load

The following transaction profiles list the transactions that have the greatest share in the database load, sorted by percentage of total database access times.

Database Load by Transactions (Batch)

Transaction Dialog Steps

Total DB Time in %

Total DB Time in s

RSDBAJOB 7 73.1 54,817.0 SAPRSLOG 7 4.4 3,269.0 SWNC_TCOLL_STARTER 5200 2.8 2,066.0 ZCM_ENROLLMENT_REPORT_NEW 42 2.6 1,955.0 RSAL_BATCH_TOOL_DISPATCHING 336 1.8 1,360.0 RS_CI_DELETE 7 1.4 1,045.0 PFCG_TIME_DEPENDENCY 28 1.1 848.0 (BATCH) 35654 0.9 667.0 RHAUTUPD_NEW 49 0.8 618.0 RSBTONEJOB2 2016 0.5 411.0

2.6% of the total database time in the above table is caused by customer transactions.

8.3 RFC Load by Initiating Action The load in task type RFC is shown. In the workload monitor, this information is shown as 'Load from External Systems'. The calling system can be an application server of the system itself or any external system using

18

the RFC interface. The 'Initial Action' is the calling program initiating the RFC. The total response time for each initial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table. The average times (per dialog step) are shown in milliseconds [ms]. Calls from external systems are shown if they account for at least 8h or 5% of the total RFC load. Local calls are shown if they account for at least 24h or 20% of the total RFC load.

Load Overview Initial System Load [s] Load % Local system R3D 3,153 25.79 Sum of external systems 9,074 74.21 RFC load (sum of above) 12,227 100.00 RFC load in Performance Overview 1,329,249 10,871.46 Load of all task types in Performance Overview 1,512,391 12,369.32

Top 20 RFC Calls From External Systems - Average Times [ms]

Initial System Initial Action


% of RFC Load

Avg. Response Time

Avg. CPU Time

Avg. DB Time

Avg. Roll Wait Time

SMD EFWK RESOURCE MANAGER 7,489 61.25 564.8 44.8 130.5 0.3 SRD CLEAN_REQREQ_UP 767 6.27 1,141.6 101.1 123.0 0.4 SRD SAPMHTTP 210 1.72 789.0 41.8 493.6 1.0 SMX SAP_CCMS_CPH_MINCOLL 118 0.96 305.5 2.9 4.0 0.2 SMP SAP_CCMS_MONI_BATCH_DP 87 0.71 522.4 4.2 9.2 0.2 SRD BBP_VENDOR_GET_DATA_JOB 80 0.65 713.1 102.3 433.5 0.2 SRD BBP_GET_STATUS_2 74 0.61 27.7 4.1 9.2 0.2 SMX LDAPSYNC_PHASE_2_3_T 50 0.41 72.7 10.2 39.0 0.7 SMX ZBA_CUA_ROLES_EXTRACT 42 0.34 3,000.9 34.3 2,429.9 0.3 SRD BBP_VENDOR_GET_DATA_JOB_INVOICE 34 0.28 607.2 174.1 332.2 0.8 SMD LANDSCAPE FETCH 32 0.26 652.2 10.6 92.6 0.2 SMP LANDSCAPE FETCH 23 0.19 726.0 17.2 113.4 0.2 SMP SMWP_BATCH 19 0.15 313.8 3.6 3.5 0.3 SMP EFWK RESOURCE MANAGER 9 0.08 59.9 4.1 48.3 0.2 SMX SAP_CCMS_CPH_HRCOLL 6 0.05 550.7 6.4 2.5 0.2

19

Top 20 RFC Calls From External Systems - Average Times [ms]



% of RFC Load

Avg. Response Time

Avg. CPU Time

Avg. DB Time

Avg. Roll Wait Time

R3P STMS 5 0.04 589.8 4.4 66.8 0.2 SRD BBP_PD 5 0.04 940.6 28.0 580.6 0.2 SMD DIAGLS_COMPUTE_STATUS 5 0.04 651.4 1.4 1.3 0.3 SMX ZBA_CUA_USER_AUDIT 4 0.03 595.9 18.6 74.0 0.1 SMX SU01 4 0.03 666.5 23.3 385.8 1.3 Top 20 RFC Calls From Local System - Average Times [ms]



% of RFC Load

Avg. Response Time

Avg. CPU Time

Avg. DB Time

Avg. Roll Wait Time

R3D SAP_COLLECTOR_PERFMON_SWNCCOLL 840 6.87 512.9 211.2 137.3 1.3 R3D CUA_RSBTONEJOB2_100 587 4.80 783.2 5.0 11.1 1.2 R3D PFCG 444 3.63 29,618.7 3,146.7 10,090.9 1.4 R3D SUIM 246 2.01 81,954.3 3,396.7 35,679.0 1.3 R3D SEU_INT 242 1.98 1,100.8 183.6 183.4 0.6 R3D RS_CALL_PROGRAMM_INDEX_DELTA 224 1.84 436.5 42.8 132.1 0.5 R3D SAP_COLLECTOR_PERFMON_RSAMON40 182 1.49 540.9 1.7 2.4 0.6 R3D PA40 144 1.18 74.5 5.6 13.4 1.5 R3D SAPMHTTP 67 0.55 1,029.9 128.8 493.8 0.3 R3D SNOTE 52 0.43 404.4 30.0 105.7 7.0 R3D PA30 34 0.28 64.3 6.0 19.9 1.5 R3D SE37 29 0.24 1,454.5 142.5 456.8 0.5 R3D SE24 15 0.13 515.6 41.3 163.3 0.3 R3D SE38 15 0.12 2,437.8 118.3 2,182.5 0.2 R3D WB_NEW_WINDOW 9 0.08 783.6 205.0 28.3 0.4 R3D ZBC_CCMS_MONITORING 9 0.07 27.1 2.4 1.8 0.2 R3D XK02 3 0.02 715.0 37.5 538.0 0.5 R3D SE10 3 0.02 304.0 20.0 121.9 0.3 R3D SAP_COLLECTOR_PERFMON_RSDB_PAR 3 0.02 20.7 2.7 12.4 0.5 R3D SWDD 2 0.01 517.3 3.3 8.7 0.0

9 SAP System Operating R3D

Your system was analyzed with respect to daily operation problems. We did not detect any major problems that could affect the operation of your SAP System.

20

9.1 Availability based on Collector Protocols

A value of 100% means that the collector was available all day. "Available" in the context of this report means that at least one SAP instance was running. If the SAP collector was not running correctly, the values in the table and graphics may be incorrect.

To check these logs, call transaction ST03N (expert mode) and choose "Collector and Performance DB -> Performance Monitor Collector -> Log".

This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour.

The job does NOT check availability; it carries out only general system tasks such as collecting and aggregating SAP performance data for all servers/instances. The log does not contain any direct information about availability; it contains only information about the status of the hourly statistical data collection.

As of SAP Basis 6.40, system availability information is available in the CCMS (Computing Center Management System) of an SAP System, in Service Level Reporting of SAP Solution Manager.

This function is provided by the relevant Solution Manager Support Packages as an advanced development. For more information, refer to SAP Note 944496, which also lists the prerequisites that must be fulfilled before implementation can take place."

9.2 Update Errors In 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.

9.3 Table Reorganization The largest tables and/or rapidly growing tables of system R3D were checked. No standard SAP recommendations for the applicable data volume management were found.

21

9.4 Transports Transports were not found in the period analyzed.

9.5 Program Errors (ABAP Dumps) 17 ABAP dumps have been recorded in your system in the period 04/13/2015 to 04/17/2015. ABAP dumps are generally deleted after 7 days by default. To view the ABAP dumps in your system, call transaction ST22 and choose Selection. Then select a timeframe.

Date Number of Dumps

04/13/2015 10

04/14/2015 1

04/15/2015 3

04/16/2015 2

04/17/2015 1

Name of Runtime Error Dumps Server (e.g.) User (e.g.)

Date (e.g.)

Time (e.g.)

OBJECTS_OBJREF_NOT_ASSIGNED 10 r3dev_R3D_00 AFTA222 04/13/2015 15:49:59

CALL_FUNCTION_PARM_UNKNOWN 3 r3dev_R3D_00 WMI228 04/15/2015 15:28:27

OBJECTS_OBJREF_NOT_ASSIGNED_NO 2 r3dev_R3D_00 AFTA222 04/16/2015 17:09:52

LOAD_PROGRAM_LOST 2 r3dev_R3D_00 AFTA222 04/17/2015 14:23:39

It is important that you monitor ABAP dumps using transaction ST22 on a regular basis. If ABAP dumps occur, you should determine the cause as soon as possible. Based on our analysis, we expect no serious problems at the moment.

10 Security

Critical security issues were found in your system. See the information in the following sections.

22

Rating Check

Default Passwords of Standard Users

Control of the Automatic Login User SAP*


ABAP Password Policy

Gateway and Message Server Security

Users with Critical Authorizations

10.1 ABAP Stack of R3D

10.1.1 Default Passwords of Standard Users

Standard users have default passwords.

Recommendation: Run report RSUSR003 to check the usage of default passwords by standard users. Ensure that users SAP* (must exist in all clients), SAPCPIC, and EARLYWATCH have non-default passwords in all clients. For more information, see "Protecting Standard Users" either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide. Make sure that the standard password for user TMSADM has been changed in client 000, and delete this user in any other client. SAP Note 1414256 describes a support tool to change the password of user TMSADM in all systems of the transport domain. SAP Note 1552894 shows how to update the report RSUSR003 to show the status of user TMSADM.

10.1.2 Control of the Automatic Login User SAP*

The profile parameter login/no_automatic_user_sapstar is set to 0 on at least one instance. If the user master record belonging to user SAP* is deleted, it is possible to log on again with SAP* and the initial password. SAP* then has the following attributes: - The user has all authorization, as authorization checks cannot be executed. - You cannot change the standard password. You can deactivate the special attributes of SAP* using profile parameter login/no_automatic_user_sapstar.

Recommendation: Set profile parameter login/no_automatic_user_sapstar to 1. For further information, see SAP Note 68048.

10.1.3 Protection of Passwords in Database Connections

Database user passwords of connected systems can be found in table DBCON. At least one critical record was found in table DBCON. This indicates that at least the manual postprocessing step of SAP Note 1823566 was not performed.

23

Recommendation: Apply SAP Security Note 1823566 and make sure that you execute the valid manual postprocessing step if you apply the Note correction or the corresponding support package.

Note: This Note is valid for all ABAP installations that use database connections, including when the text focuses on SAP Solution Manager. The Note refers to SAP Solution Manager because typically, many DB connections are maintained. If this recommendation is displayed, there are DB connections with passwords on the analyzed system. Although transaction DBCO (which you use to maintain such DB connections) does not show the passwords, you can find the obfuscated passwords using transaction SE16 for table DBCON with the field value PASSWORD <> space.

10.1.4 ABAP Password Policy

If password login is allowed for specific instances only, the password policy is checked only for these instances.

10.1.4.1 Password Complexity

Parameter: login/min_password_lng Rating Instance Current Value(s) Recommended Value

r3dev_R3D_00 6 8

The current system settings allow a password length of fewer than 8 characters. This allows weak passwords. Attackers may successfully recover these passwords and gain unauthorized access to the system.

Recommendation: Assign a minimum value of 8 to the profile parameter login/min_password_lng.

In addition, SAP provides options to enforce complex passwords. Find the current settings of the corresponding profile parameters in the following table.

Parameter Instance Current Value(s)

login/min_password_digits r3dev_R3D_00 0

login/min_password_letters r3dev_R3D_00 0

login/min_password_lowercase r3dev_R3D_00 0

login/min_password_uppercase r3dev_R3D_00 0

login/min_password_specials r3dev_R3D_00 0

Recommendation: Enforce a minimum of 3 independent character categories using the corresponding profile parameters. For more information, see SAP Note 862989 and the section Profile Parameters for Logon and Password (Login Parameters) either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide.

10.1.4.2 Validity of Initial Passwords

Rating Parameter Instance Current Value(s)

24

Rating Parameter Instance Current Value(s)

login/password_max_idle_initial r3dev_R3D_00 0

Initial passwords are valid for more than 14 days.

Recommendation: Proceed as follows: -- Handle users of type C (Communication) with initial passwords because they will be locked if the above profile parameter is set. Use transaction SUIM/report RSUSR200 in each client to find users of type C (Communication). If these users are active and in use, switch the user type to B (System). This has no negative effect. -- Restrict the password validity to 14 days or less. Note that the value 0 grants unlimited validity. -- For more information, see SAP Note 862989 and the Profile Parameters for Logon and Password (Login Parameters) section, either on SAP Help Portal or in the SAP NetWeaver AS ABAP Security Guide.

10.1.5 Gateway and Message Server Security

10.1.5.1 Gateway Security

Enabling an Initial Security Environment

Parameter: gw/acl_mode Rating Instance Current Value Recommended Value

r3dev_R3D_00 0 1

Recommendation: Parameter gw/acl_mode can be set to 1 to activate a more secure default behavior if either of the access control lists defined by gw/sec_info and gw/reg_info does not exist. SAP recommends setting gw/acl_mode to 1 to establish an additional line of defense should any of the access control lists be missing. For more information, see SAP Note 1480644.

Gateway Access Control Lists

Parameters: gw/sec_info gw/reg_info Rating Instance Error Condition

All instances gw/reg_info and gw/sec_info are defined reg_info Rating Instance Error Condition File does not exist (default)

All instances P TP=* sec_info

Rating Instance Error Condition File does not exist (default)

All instances

P TP=* USER=* USER-HOST=* HOST=*

Recommendation: The profile parameters gw/sec_info and gw/reg_info provide the file names of the corresponding access control lists. These access control lists are critical to controlling RFC access to your system, including connections to RFC servers. You should create and maintain both access control lists, which you can do using transaction SMGW. For more information, see "Configuring Connections between SAP Gateway and External Programs Securely" on SAP Help Portal.

10.1.6 Users with Critical Authorizations

25

For more information about the following check results, see SAP Note 863362.

Recommendation: Depending on your environment, review your authorization concept and use the Profile Generator (transaction PFCG) to correct roles and authorizations. You can use the User Information System (transaction SUIM) to check the results. For each check, you can review the roles or profiles that include the authorization objects listed in the corresponding section.

10.1.6.1 Super User Accounts

Users with authorization profile SAP_ALL have full access to the system. There should be a minimum of such users. The number of users with this authorization profile is stated for each client.

Client No. of Users Having This Authorization No. of Valid Users Rating

000 12 15

001 1 1

100 20 537

300 25 213743

Authorization profile: SAP_ALL

10.1.6.2 Users Authorized to Change or Display all Tables

Unauthorized access to sensitive data is possible if too many users have this authorization. The specified number of users for each client have the checked authorization.


001 1 1

100 196 537

300 436 213743

Authorization objects:

Object 1: S_TCODE with TCD=SE16, TCD=SE16N, TCD=SE17, TCD=SM30, or TCD=SM31

Object 2: S_TABU_DIS with ACTVT = 03 or 02 and DICBERCLS = *

10.1.6.3 Users Authorized to Start all Reports

This authorization allows critical functions and reports that do not contain their own authorization checks to be executed. The specified number of users for each client have the checked authorization.


26


001 1 1

100 164 537

300 88 213743


Object 1: S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38

Object 2: S_PROGRAM with P_ACTION=SUBMIT P_GROUP=*

10.1.6.4 Users Authorized to Debug / Replace

This authorization provides access to data and functions, since any authorization check that is built in ABAP can be bypassed. In addition, you can change data during processing, which may lead to inconsistent results. The specified number of users for each client have the checked authorization.


001 1 1

100 159 537

300 90 213743


Object 1: S_DEVELOP with ACTVT=02 (change) and OBJTYPE=DEBUG

Note: If you do not want to disable development in your system, you have to exclude the OBJTYPE=DEBUG with ACTVT=02 from the profile and allow any other object type for S_DEVELOP. This means that development and debugging with visualization is still possible. You can achieve this by linking two authorizations to the object S_DEVELOP: one with all object types (except for "DEBUG") and all activities, and another for the object type DEBUG only and all activities (except for 02).

10.1.6.5 Users Authorized to Display Other Users Spool Request

This authorization allows unauthorized access to sensitive data contained in spool requests. The specified number of users for each client have the checked authorization.


001 1 1

100 136 537

27


300 98 213743


Object 1: S_TCODE with TCD = SP01 or SP01O

Object 2: S_ADMI_FCD with S_ADMI_FCD = SP01 or SP0R

Object 3: S_SPO_ACT with SPOACTION = BASE and DISP and SPOAUTH = * or __USER__

10.1.6.6 Users Authorized to Administer RFC Connections

If too many users have this authorization, two problems can occur: - Unauthorized access to other systems - Malfunction of interfaces if invalid connection data is entered

The specified number of users for each client have the checked authorization.


001 1 1

100 153 537

300 73 213743


Object 1: S_TCODE with TCD=SM59

Object 2: S_ADMI_FCD with S_ADMI_FCD = NADM

Object 3: S_RFC_ADM with ACTVT NE 03

11 Software Change and Transport Management of R3D

Software change management issues were found in your system. See the information in the following sections.

28

11.1 SAP Netweaver Application Server ABAP of R3D

Rating Check Performed

Number of Changes

Failed Changes

11.1.1 Number of Changes

Performing changes is an important cost driver for the IT department. It is only acceptable to make a large number of software and configuration changes in exceptional situations, such as during go-live for an implementation project.

No data from the managed system could be found in the configuration and change database (CCDB). Check whether the diagnostics setup for the managed system has been performed as described in SAP Note 1472465. Solution Manager Diagnostics provides valuable features for root cause analysis and is an important data source for various support services. The CCDB data is required here to check the configuration of the managed system.

11.1.2 Number of Transport Requests

The following diagram contains information about the number of transport requests per day that were imported into the SAP system in the last week.

Date Workbench and Relocation Requests

Customizing Requests

Transport of Copies

04/13/2015 0 4 0

04/14/2015 0 4 0

29

Date Workbench and Relocation Requests

Customizing Requests

Transport of Copies

04/15/2015 6 2 0

04/16/2015 8 0 0

04/17/2015 1 1 0

11.1.3 Number of Transported Objects

The following diagram contains information about the number of objects per day that was imported into the SAP system in the last week.

Date Objects in Workbench and Relocation Requests

Objects in Customizing Requests

Objects in Transport of Copies

04/13/2015 0 20 0

04/14/2015 0 23 0

04/15/2015 15 16 0

04/16/2015 73 0 0

04/17/2015 1 1 0

11.1.4 Failed Changes

In this check, we analyzed the number of failed changes in system R3D during the last week.

30

Rating Item Value Explanation

Transport requests with import errors

0 Number of transport requests with import errors that were not resolved within one hour.

Overtakers and bypassed transport requests

0

If an old object version overwrites a newer one we count this as a transport sequence error. We count both the overtaker transport and the bypassed transport. Each transport is only counted once.

12 Data Volume Management (DVM)

A statement regarding Data Volume Management on your system R3D could not be provided.

This report does not have a Data Volume Management (DVM) section because your SAP Solution Manager system does not fulfill the technical requirements, or the ST-A/PI release on your system R3D is too low (or could not be identified). For more information, see SAP Note 2036442. As a workaround, an attempt was made to check the database size and growth per year for your system R3D. However, the database size or growth per year could not be collected. As a consequence, a statement regarding Data Volume Management in your system R3D could not be provided.

13 Database Performance

In the checks performed, problems regarding the performance of your database were found.

Rating Check

Database Version

Locking

31

Rating Check

Average Read and Write Times

Missing Indexes

13.1 Database Version R3D

SID Database Version Fix Pack level Build Level DBSL Patch

R3D DB2 for Linux UNIX and Windows 9.7 8 s130316 220

For the latest database versions and Fix Packs, see also SAP Note 101809. For more information about known errors in DB2 Fix Packs, see SAP Note 1346902.

SID Database Start Date [yyyy/mm/dd]

Database Up Time [Days]

Download Collection Date [yyyy/mm/dd]

R3D 2015/04/09 12 2015/04/20

13.1.1 Average Read and Write Times for Tablespaces

Tablespace Partition

Avg. Read Time [ms]

Read Time Threshold [ms]

Avg. Write Time [ms]

Write Time Threshold [ms]

% of Total Reads

R3D#ES731I 0 2.73 10.00 7.27 5.00 14.92

We have checked active tablespaces for poor performance. Tablespaces with long read or write times were detected. This may be due to a non-optimal storage layout.

Note: To avoid unrealistic figures and to ensure that only active tablespaces are checked, the analysis is restricted to 95% of the total workload. The remaining tablespaces are considered inactive.

Recommendation: For optimal I/O performance, ensure the following: - Each tablespace should consist of several containers, distributed over your SAP data directories in a round-robin fashion. - DB2_PARALLEL_IO is enabled only for tablespaces with one container per RAID device or stripe set. - Individual containers are not too large. Avoid too many levels of striping. - All containers for one DB2 stripe set are the same size. If some containers are smaller, parallel prefetching may not be optimal. - If the operating system and file system type allow direct (DIO) or concurrent (CIO) I/O, deactivate file system caching at database level (see tablespace snapshot) to avoid double buffering. System caching should only be active for dedicated tablespaces used to store LONG/LOB data only. For more information, see the document "Creating table spaces without file system caching" in the IBM Information Center.

32

14 Database Administration

In the checks performed, problems regarding the administration of your database were found.

Rating Check

Database Growth and Freespace

10 Largest and Fastest Growing Tables

Tablespaces with a critical size

Tables with a critical size

Table Virtualization

Enhanced Monitoring

Log File Management

Logfiles Recommendations

Database Backup History

14.1 Database Storage These two graphs show your database growth and free space development over the past few months.

Note: If limited history is displayed (for example 1 or 2 months), it is most likely due to the setting of the DCF collector 'Tablespaces (Storage)' in DBACOCKPIT. Go to transaction DBACOCKPIT -> Configuration -> Data Collection Framework using the Webdynpro. Check the retention ('Days Kept in History' column). The default is 90 days but you can increase this value to a longer timeframe.

33

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

Date Current Size (GB) Monthly Growth (GB)

02/01/2015 266.65 0.00

03/01/2015 267.06 0.40

04/01/2015 267.48 0.43

14.2 10 Largest and Fastest Growing Tables The following tables displays the 10 largest and fastest growing tables stored in the database.

Table Name Tablespace Size (GB)

34

Table Name Tablespace Size (GB)

WBCROSSGT R3D#SOURCED 16.45

REPOLOAD R3D#EL731D 12.32

BSIS R3D#BTABD 10.01

REPOSRC R3D#ES731D 7.43

CMACDB_FEESM R3D#BTABD 5.64

ZZSPLITA R3D#ZTABD 4.75

GMIA R3D#ZGMIAD 4.71

DFKKOP R3D#BTABD 4.69

D010TAB R3D#ES731D 4.67

E071K R3D#STABD 4.49

Name Tablespace Monthly Growth (GB)

/1CN/CMFSAPI4TRU R3D#STABD 0.00

/1CN/CMFSAPI4TRF R3D#STABD 0.00

/1CN/CMFSAPI4TQU R3D#STABD 0.00

/1CN/CMFSAPI4TFX R3D#STABD 0.00

/1CN/CMFSAPI3TUS R3D#STABD 0.00

/1CN/CMFSAPI3TCT R3D#STABD 0.00

/1CN/CMFSAPI2TRM R3D#STABD 0.00

/1CN/CMFSAPI2TGR R3D#STABD 0.00

/1CN/CMFSAPI1FFX R3D#STABD 0.00

/1CN/CMFSAPI1FDT R3D#STABD 0.00

14.3 Data Collection Framework As of SAP_BASIS 7.02 and DB2 V9.5, a new infrastructure is used to manage the history of data. This infrastructure is called the data collection framework (DCF). The DCF collects the data independently of the SAP system. The history data for the database objects (tables and indexes) is collected with this DCF infrastructure. The default retention of the DCF collector that stores tablespace details is currently set to 14 days, as opposed

35

to several weeks with the older method. This DCF collector is used to monitor the database size and growth in remote services such as SAP EarlyWatch Alert. Limited reporting of such data is therefore available with the default settings. Recommendation: To overcome this, we recommend that you change the default setting of the DCF collector 'Tablespaces (Storage)' (or 'Tablespaces' depending on your SAP_BASIS release) from 14 days to at least 90 days for 'Days Kept in History'. Note that the additional space impact for longer history is low. We also recommend that you use at least the 'SAP Default' template when configuring the DCF collectors.

14.4 Tablespaces with a critical Size No DMS tablespaces were found for which the 'Used Size' or 'Total Size' is critical.

Note: Make sure the relevant file systems are large enough to allow further tablespace growth.

14.5 Tables with a critical size Your system was checked for tables that have reached their size limits. No tables were critical. For technical reasons (expensive operation to check all tables in the system), we could not check whether all tables are already enabled for 'Large RIDs'.

Background: For tables that are not enabled for 'Large RIDs', the size restrictions of DB2 V8 64, 128, 256, or 512 GB still apply (depending on whether they are stored in tablespaces of page size 4, 8, 16, or 32 KB). This is the case even if the tablespaces have been converted to type 'Large'. Even if such tables are far smaller than the old size limits, they could still be affected. Once all pages below the old size limit are occupied by tables enabled for 'Large RIDs', even small tables that are not enabled for 'Large RIDs' cannot grow any further, leading to SQL errors, or even to unplanned downtime.

Recommendation: Convert ALL DMS tablespaces to type 'Large' (if not already done) and enable ALL tables for 'Large RIDs' as soon as possible, to benefit from the increased table and tablespace size limits. This is especially important for tablespaces that only contain a single table and are close to the former V8 size limit. Such tables require at least a reorganization of their indexes before they can grow beyond the V8 size limit.

To check whether a tablespace has been converted to type 'Large', use the following command: SELECT tbspace FROM syscat.tablespaces WHERE datatype = 'L'

To convert a tablespace to type 'Large', use the following command: db2 alter tablespace <tablespace> convert to large It is not necessary to convert SYSCATSPACE to large.

With the following SQL statement, you can count the number of tables that are not yet enabled for 'Large RIDs': select large_rids, count(*) as number from sysibmadm.admintabinfo where tabschema not like 'SYSIBM%' group by large_rids

To ease the task of converting tablespaces to type 'large' and reorganizing tables/indexes, SAP has developed the tool 'Large RID Tool'. It can be found as an attachment to SAP Note 1108956. The PDF document that is also attached describes the use in detail and offers the possibility to reorganize tables/indexes via a convenient front end. See the following article in SDN, which describes the tool in more detail: http://scn.sap.com/people/johannes.heinrich/blog/2007/11/14/new-tool-for-activation-of-large-record-identifiers-in-db2-9-for-linux-unix-and-windows

36

14.6 Enhanced Monitoring Settings

Parameters Description Current Value Recommendation

MON_LOCKWAIT Monitoring lock wait configuration parameter WITHOUT_HIST NONE

MON_LW_THRESH Monitoring lock wait threshold configuration parameter 300000000 5000000

At least one of the parameters listed above is not set according to our standard recommendations.

Recommendation: Adjust the parameters to the recommended settings.

Background: If you are using the new time-spent metrics introduced in DB2 V9.7, you first need to ensure that the new in-memory metrics are activated in the database configuration. These are activated by default for new databases created on DB2 >= V9.7 but deactivated for migrated databases.

Once these are activated, the new metrics (including time spent) are collected within DB2 memory and can be accessed in any number of ways. You can look at the current in-memory values using one of the new table functions (that is, look for the ones with the prefix MON_GET_*) for any connection, unit of work, and so on, or from the package cache. You can also collect data for a specific execution using the activity event monitor (introduced in DB2 V9.5) for a specific unit of work using the new UOW event monitor, and so on. This data is also used in SAP Solution Manager 7.1 and DBACOCKPIT.

14.7 Log File Management The DB2 database is running in log retention mode as recommended. Ensure that all log files are archived starting from the last complete backup to allow any kind of recovery.

14.8 Logfiles Recommendations Database Logging Information (Since Database Start) Parameter / KPI Current Setting / Value logfilsiz (MB) 64 logprimary 20 logsecond 150 Total Log Space Available To Database (MB) 10816 Maximum Log Space Used in (MB) 487 Maximum Secondary Log Space Used in (MB) 0 Maximum Number of Secondary Log Files Used 0

The "log_dir" directory should have at least enough space to hold all the primary and secondary log files. As a safety margin, twice this size is recommended. The "log_archive" directory should be large enough to store all the log files from three workdays.

37

14.9 Further Recommendations Administration of db2diag.log The DB2 diagnostic file db2diag.log contains diagnostic records about administrative events and specific error information about problems encountered within DB2. Once created, the db2diag.log file grows continually. To avoid long access times via transaction DBACOCKPIT, we recommend that you keep the size of the file reasonably small. Use the command "dbdiag -A" to create a new db2diag.log file on a regular basis. Alternatively, rename the file at OS level. A new db2diag.log file will then be created automatically by the DB2 database manager. As of DB2 V9.7, a series of 10 rotating diagnostic log and 10 administration notification log files can be used by setting the DBM CFG parameter DIAGSIZE. Its value determines the combined, overall size of the database diagnostic and administration notification log files. In this way, these log files can be used in a rotating order with a fixed maximum size. As of SAP Basis Release 7.02, the Web dynpro-based DBA Cockpit offers a "Weekly Switch" of the database diagnostic log as an alternative way of archiving the db2diag.log under a new name (similar to using db2diag –A). You can access this option from the menu by choosing "Configuration-> Monitoring Settings". For more information, see the IBM DB2 Information Center and the guide "Database Administration Using the DBA Cockpit: IBM DB2 for LUW", which is available on SAP Service Marketplace at https://service.sap.com/instguides -> SAP NetWeaver -> SAP NetWeaver<release> -> Operations -> Database-Specific Guides.

Supported DB2 versions and Fix Packs SAP Note 101809 contains a complete list of supported DB2 versions and Fix Packs. Check this SAP Note at regular intervals for the latest available DB2 Fix Pack and also to verify that your Fix Pack is still supported.

Also see the following important SAP Notes for DB2:

SAP Note Number Description

101809 DB6: Supported Fix Packs for DB2 UDB for UNIX and Windows

975352 DB6: Configuring DB2 Auto Reorg for space reclaim and index cleanup

1168456 DB6: End-of-Support Dates

1309424 DB6: DBA Cockpit Correction Collection SAP Basis 7.01 / 7.11

1314750 DB6: DBA Cockpit Correction Collection SAP Basis 7.00 / 7.10

1329179 DB6: DB2 V9.7 Standard Parameter Settings

1346902 DB6: Known Errors and available Fixes in DB2 9.7 for LUW

1351160 DB6: Using DB2 9.7 with SAP Software

1425488 DB6: Performance problems with volatile tables

1456402 DB6: DBA Cockpit Correction Collection SAP Basis 7.02/7.30/7.31

1499214 DB6: Database Administration - Learning Offerings

1630506 DB6: History management of monitoring data

38

SAP Note Number Description

1837312 DB6: Upgrade to Version 10.5 of DB2 for LUW

1929142 DB6: DROP INDEX may result in database marked as bad

1942183 DB6: When to consider a table or index reorganization

15 Database server load from expensive SQL statements - R3D

The SQL statements identified did not lead to performance problems. The load overview is listed in the table below for reference, and further details of the most expensive statements are included at the end of the section.

Database Load From Expensive Statements Rating Total Execution Time[%]

49.69

The table above shows the cumulative amount of problematic statements identified. If the database was inactive for more than one day before the analysis was performed, the information provided may not be entirely accurate.

Note: The overall section rating is linked to the above table rating; the ratings are described in SAP Note 1625795. If the table rating is RED, there are SQL statements that cause a high percentage of the overall load on your SAP system. If the table rating is YELLOW, there are SQL statements that cause a considerable percentage of the overall load on your SAP system. If the table rating is GREEN, your system SQL statement cache contains no significant problems. If the table rating is UNRATED, the analysis of your system's SQL statement cache found that the total SQL statements were <= 1,000,000, or statements per day were below 500,000 or some analysis data was unavailable for evaluation.

The following table lists the load of each SQL statement individually. The load of the statement is evaluated against the total load since database startup.

Note: If an object name in this table contains the character "/", it may indicate a join. If an object is not in the ABAP Dictionary (transaction SE12) with the object name listed, check for each part of the join (items separated by "/").

39

15.1 Analysis of DB SQL CACHE on 04/20/2015 at 04:29 Expensive SQL Statements Overview

Object Name Total Execution Time[%]

Avg. Execution Time[ms]

Executions Rows Read[%]

Rows Returned [%]

Rows Written[%]

Sort Overflows

SYSDUMMY1 22.08 73.99 284916 0.07 0.07 0.00 0 SYSAUDITPOLICIES 21.74 10,381,620.50 2 0.01 0.05 0.00 0 SYSAUDITPOLICIES 3.69 1,763,789.50 2 0.00 0.00 0.00 0 ARFCSSTATE 2.18 661.47 3149 14.30 62.43 0.00 0

15.1.1 Access on SYSDUMMY1

Statement Data:

Cache Statistics

Total Executions

Total Execution Time[ms]


Rows Read

Rows Written

Rows Returned

Total User CPU Time[ms]

Total Logical Reads

Sort Overflows

284916 21079867 73.99 1349505 0 284916 111231 11783785 0

Program Data:

Origin of ABAP coding

Program Name Line Created By

Last Changed By

Last Changed On

CL_SQL_STATEMENT==============CM004 00000022 SAP SAP 12/11/2012

000021 000022 CALL 'C_DB_FUNCTION' ID 'FUNCTION' FIELD 'DB_SQL' 000023 ID 'FCODE' FIELD c_fcode_prepare_and_open 000024 ID 'CONNAME' FIELD me->con_ref->con_name 000025 ID 'CONDA' FIELD me->con_ref->con_da 000026 ID 'TAB_NAME' FIELD me->tab_name_for_trace 000027 ID 'STMT_STR' FIELD statement 000028 ID 'HOLD_CURSOR' FIELD hold_cursor 000029 ID 'INVALS' FIELD me->parameters->param_tab 000030 ID 'CURSOR' FIELD l_cursor 000031 ID 'SQLCODE' FIELD l_sql_code 000032 ID 'SQLMSG' FIELD l_sql_msg.

15.1.2 Access on SYSAUDITPOLICIES

Statement Data:

Cache Statistics

40

Total Executions



Rows Read

Rows Written

Rows Returned


Total Logical Reads

Sort Overflows

2 20763241 10,381,620.50 212840 0 190036 187 34468 0

Program Data:

Origin of ABAP coding

Program Name Line Created By

Last Changed By

Last Changed On

CL_SQL_STATEMENT==============CM004 00000022 SAP SAP 12/11/2012

000021 000022 CALL 'C_DB_FUNCTION' ID 'FUNCTION' FIELD 'DB_SQL' 000023 ID 'FCODE' FIELD c_fcode_prepare_and_open 000024 ID 'CONNAME' FIELD me->con_ref->con_name 000025 ID 'CONDA' FIELD me->con_ref->con_da 000026 ID 'TAB_NAME' FIELD me->tab_name_for_trace 000027 ID 'STMT_STR' FIELD statement 000028 ID 'HOLD_CURSOR' FIELD hold_cursor 000029 ID 'INVALS' FIELD me->parameters->param_tab 000030 ID 'CURSOR' FIELD l_cursor 000031 ID 'SQLCODE' FIELD l_sql_code 000032 ID 'SQLMSG' FIELD l_sql_msg.

15.1.3 Access on SYSAUDITPOLICIES

Statement Data:

Cache Statistics

Total Executions



Rows Read

Rows Written

Rows Returned


Total Logical Reads

Sort Overflows

2 3527579 1,763,789.50 22 0 0 224 128 0

Program Data:

Origin of ABAP coding Program Name Line Created By Last Changed By Last Changed On LSDB2U38 00000078 SAP SAP 11/20/2013

000079 id 'STATTXT' field sql_statement 000080 id 'ROWNUM' field record_count 000081 id 'SQLERR' field sql_error_number 000082 id 'ERRTXT' field sql_error_text.

15.1.4 Access on ARFCSSTATE

Statement Data:

41

Cache Statistics

Total Executions



Rows Read

Rows Written

Rows Returned


Total Logical Reads

Sort Overflows

3149 2082973 661.47 258048919 0 258047973 215043 127751447 0

Program Data:

Origin of ABAP coding Program Name Line Created By Last Changed By Last Changed On /SDF/LIS_ABAPU15 00000119 SAP SAP 07/02/2012

000116 000117 000118 *Taken from SM58 000119 select * from arfcsstate 000120 into table arfcistate 000121 where arfcreturn = space. "#EC CI_NOFIRST

16 Trend Analysis This section contains the trend analysis for key performance indicators (KPIs). Diagrams are built weekly once the EarlyWatch Alert service is activated.

In this section, a "week" is from Monday to Sunday. The date displayed is the Sunday of the week.

16.1 System Activity The following diagrams show the system activity over time.

The "Transaction Activity" diagram below depicts transaction activity in the system over time.

- 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 thousands) 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 working days per week.

(Peak Activity is absent if "Activity Data" is taken from ST03 data directly).

42

The "User Activity" diagram below shows the user activity on the system over time.

- Total Users: Total users that logged on in one week.

- Active Users: Users who performed more than 400 transaction steps in one week.

16.2 Response Times The following diagrams show how the response time varies over time. The "System Performance" diagram below shows the average response time in dialog tasks for the previous week.

43

The "Database Performance" diagram below shows the average DB response time in dialog tasks.

The "Top 5 transactions" diagram below shows the average response time in dialog tasks for the top 5 transactions.

44

The "Transaction Code" table below shows the load percentage caused by the top 5 transactions.

Transaction Code Load (%)

PA30 38.7

{_MSS_EMPLOYEE_RELAT 16.4

PA40 13.7

SE10 3.0

SESSION_MANAGER 2.9

45

16.3 Application profile

46

In the following, we analyzed the trend within the following time frames:

Short term: From calendar week 12/2015 to 15/2015

Long term: From calendar week 04/2015 to 15/2015

The table below shows the time profile of the top applications by total workload during the analyzed period.

Top Applications by Response Time

Task Type Application


% of Total Load

Avg. Resp. Time in ms

Long Term Growth (%/year)

Short Term Growth (%/year)

Avg. DB Time in ms

Avg. CPU Time in ms

Dialog SAPMSEU0 24981 9 829 84.7 4,766.5 157 40 Dialog ZHRPA_1042S 20552 7 11292 217.8- 2,321.7- 241 235 Dialog SFP 13108 5 3639 73.4 311.7- 260 113 Dialog ZPANAYA_EXTRACT_PROG 10192 4 1274019 0.0 0.0 171792 300280 Dialog SESSION_MANAGER 10146 4 685 90.0- 490.6- 80 20 Dialog ZCA_CENTRAL_INTERFAC 9504 3 5981 137.0- 1,120.2- 761 126 Dialog PC00_M10_CALC 9217 3 1460 28.0 170.9- 134 126 Dialog ZFI_DAILY_BAL_DISP 8080 3 3951 613.9 329.8 129 29 Dialog SE10 7923 3 455 104.6 746.6 229 84 Dialog RSABAPPROGRAM 7781 3 245 57.1 483.0 101 31 Dialog SE37 7510 3 446 340.3- 1,286.0 123 16 Dialog RSTPDAMAIN 7368 3 152 1.9- 482.7 10 9 Dialog PA30 6511 2 912 105.8 1,777.3 143 33 Dialog PT60 6504 2 8765 448.0- 178.0 173 5233 Dialog ZHRBN_ACA_ENGINE 5960 2 2577 1,077.6- 1,229.8- 114 55 Dialog ZRWTEST0111NSC_ENRO2 5402 2 26482 257.4 176.5- 11819 4783 Dialog ZFI_INTEREST_POSTING 4850 2 3754 269.4 2,689.3 89 14 Dialog SE11 4706 2 300 208.0- 173.6 261 13 Dialog SE09 4415 2 1806 110.4- 509.9 1090 359 Dialog SE24 3921 1 336 157.2- 326.1 124 91

The graph below shows how the average response time of the top five applications varies over time. Data is normalized to 100% equaling the average value.

47

16.4 System Operation The following diagram or table shows important KPIs for system operation.

16.5 Hardware Capacity The following diagram or table shows CPU max load from database server and all Appl servers.

48

Report time frame: Service data was collected starting at 04/20/2015 04:27:24. This took 12 minutes.

You can see sample EarlyWatch Alert reports on SAP Service Marketplace at /EWA -> Library -> Media Library.

General information about the EarlyWatch Alert is available at SAP Note 1257308.

earlywatch alert-uky production 1 service summary update errors table reorganization hardware...

Documents