EWA SXX September 2017 v1

Service Report
EarlyWatchAlert
Confidential
PAS System ID SXX
Product PAS Solasido Maregen 7.2
Status Productive
DB System SYB for Linux UNIX and Windows 10.5
Customer PT.
Processed on PAS Solasido Maregen SXX

Release SOLASIDO MAREGEN 7.2
Service Tool 720 SP8
Service Content
29.08.2017
Update on
Analysis from 28.08.2017 Session No. 7770000000016

Until 03.09.2017 Installation No. 0012345678
Customer No. 0012345678
This report contains confidential customer data and may be viewed only by SAP AGS employees, authorized SAP
partners, and customer employees. Do not distribute it to other parties.
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
1 Service Summary
Some essential service data for the EarlyWatch Alert session is

missing. Therefore, no rating is assigned.
ALERT OVERVIEW
We found more than 30 ABATA dumps in your system.
Standard users have default password.
Secure password policy is not sufficiently enforced.
A high number of users has critical authorizations
Based on these findings, it is recommended that you perform the following Guided Self-Services.
Guided Self Service FAQ PAS Note
Security Optimization Service 1484124
For more information about Guided Self-Services, see PAS Enterprise Support Academy.
Register for an Expert-Guided Implementation Session for the Guided Self-Service at PAS Enterprise Support
Academy - Learning Studio - Calendar.
CHECK OVERVIEW
Topic Subtopic
Topic Subtopic
Rating Rating
PAS System
Configuration
Database - Maintenance Phases
PAS Kernel Release

PAS System
Operating
Availability based on Collector Protocols
Program Errors (ABATA Dumps)
Update Errors
Table Reorganization
DB
Performance
Database Version
Bufferpool Qualities
Locking
1 Service Summary 2/71
Confidential
Topic Subtopic
Topic Subtopic
Rating Rating
Average Read and Write Times
Missing Indexes
DB
Administration
Database Storage
10 Largest and Fastest Growing Tables
Space Reclaimable Tablespaces
Tablespaces with a critical size
Table Virtualization
Enhanced Monitoring
Log File Management
Logfiles Recommendations
BW Checks
BW Administration & Design
BW Reporting & Planning
BW Warehouse Management
Security
System Recommendations (ABATA)
Default Passwords of Standard Users
Control of the Automatic Login User PAS*
Protection of Passwords in Database Connections
ABATA Password Policy
Gateway and Message Server Security
Users with Critical Authorizations

Software
Change
Management
Number of Changes
Note: All recommendations in this report are based on our 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
PAS Solasido Maregen EarlyWatch Alert service, create a customer message under 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 PAS Note 67739.
Performance Indicators for SXX

The following table shows the relevant performance indicators in various system areas.
Confidential
Area Indicators Value Trend

System Performance Avg. Availability per Week 5%
Database Space Management DB Size 50.15 GB
DB Growth Last Month 0.00 GB
Confidential
2 Landscape
3 Products and Components in current Landscape
PRODUCT
System PAS Product Product Version
SXX~ABATA PAS Solasido Maregen 7.2
MAIN INSTANCES (ABATA OR JAVA BASED)

Related System Main Instance
SXX~ABATA Solasido Maregen ABATA Stack
DATABASES
Related System Database System Database Version DB ID
SXX~ABATA SYB for Linux UNIX and Windows 10.5 SXX
4 Servers in current Landscape

PAS APPLICATION SERVERS
System Host Instance Name Logical Host ABATA JAVA
SXX~ABATA solasido solasido_SXX_00 solasido X
DB SERVERS
Related System Host Logical Host (PASDBHOST)
SXX~ABATA solasido solasido
COMPONENTS
Related System Component Host Instance Name Logical Host
SXX~ABATA ABATA SCS solasido solasido_SXX_01 solasido
5 Hardware Configuration
HOST OVERVIEW
Hardware CPU CPU Memory
Host Model Virtualization Operating System CPUs Cores
Manufacturer Type MHz in MB
Xeon
VMware
E5- SuSE Linux Enterprise
solasido VMware, Inc. Virtual 2500 VMWARE 2 2 32114
2640 Server 11 (x86_64)
Platform
0
6 Service Data Quality

For this service, data of overall importance is missing.
The service data is collected by the Service Data Control Center (SDCCN) or read from the Solasido Maregen'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.
2 Landscape 5/71
Confidential
EXPLANATION FOR 'PRIORITY' COLUMN IN TABLES BELOW

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.
Only checks of minor importance are affected.
An optional check was skipped.
7 Quality of Data in Service Data Control Center (SDCC)

QUALITY OF SERVICE DATA IN ST-PI
Report Area PAS
Prio. Details and Related ST-PI Logical Function
affected Note
The hourly time profile of response times in the Workload Monitor (ST03) is
Performance of
missing for all application servers for the system. Check the configuration
ABATA System 144864
settings for the monitor and job PAS_COLLECTOR_FOR_PERFMONITOR.
SXX
ST-PI function: PASWL_WORKLOAD_GET_STATIST_I_W
No activity was measured in the workload monitor (ST03). Check the
configuration for the monitor and job
PAS_COLLECTOR_FOR_PERFMONITOR. ST-PI function:
Workload of
PASWL_TCODE_AGGREGATION_I_M_W,
ABATA System 144864
PASWL_TCODE_AGGREGATION_I_T_W,
SXX
PASWL_TCODE_AGGREGATION_I_U_W,
PASWL_WORKLOAD_GET_SUMMARY_I_W and
PASWL_WORKLOAD_GET_SUMMARY_I_X
System
An incorrect name is returned for the PAS dispatcher service, probably due
Administration of
to 'Well Known Services' maintained in /etc/services module 2135427
Server (host)
TH_SERVER_LIST. ST-PI function: TH_SERVER_LIST
solasido
8 Quality of Service Data in Solasido Maregen Diagnostics - BW

Report
PAS
Prio. Area Details and Related Infocube
Note
affected
Workload
of ABATA Reading performance data from BW returned neither data nor an error code. A timeout
1332428
System may have occurred. Infocube: 0CCMSMTPH used in section 'Workload Overview SXX'
SXX
9 PAS Solasido Maregen Service Readiness of SXX
Service data for overall importance is missing for this report.

Because important checks could not be executed, the report is not rated (grey rating).
The PAS Solasido Maregen system SXX is not fully prepared for delivery of future
remote services.
Rating Check Performed

Service Data Quality
PAS Solasido Maregen Software Configuration
2 Landscape 6/71
Confidential

Service Preparation Check (RTCCTOOL)
We recommend that the PAS Solasido Maregen is used to ship PAS Support remote services. For more
information, see PAS Note 1170668.
10 PAS Solasido Maregen Software Configuration

The ST version determines which functionality can be used or is available for delivery. The ST-SER version
determines the session content of services. Certain functionalities may not be available.
For further information, see PAS Notes 394616 and 569116.
Latest Avail. PAS
PAS Component Latest Avail. Patch
PAS Component Patch Level Component
Version Level
Version
ST 720 2 720 5
ST-SER 720 8 720 9
2 Landscape 7/71
Confidential
11 Software Configuration for SXX
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.
12 PAS Application Release - Maintenance Phases

PAS Product Version End of Mainstream Maintenance Status
PAS SOLASIDO MAREGEN 7.2 31.12.2020
In October 2014, PAS announced a maintenance extension for PAS BusinessSuite 7 core application releases to
2025. If you are running a relevant release, see PAS Note 1648480 for more details and applicable restrictions.
13 Support Package Maintenance - ABATA

The following table shows an overview of currently installed software components.
SUPPORT PACKAGES
Latest
Software Patch Avail.
Version Support Package Component Description
Component Level Patch
Level
PAS CRM ABATA Server Component PAS CRM
BBPCRM 713 9 14 PASKU71309
ABATA 7.13
PASK-
BI_CONT 757 12 14 BI CONT PAS NW 7.40 ADDON 7.57
75712INBICONT
PASK- PAS Portfolio and Project Management (ABATA)
CPRXRPM 610_740 4 8
61004INCPRXRPM 610_740
PASK-
CTS_PLUG 200 22 22 CTS Plug-in 200
20022INCTSPLUG
PASK-
IW_FNDGC 100 5 5 PAS IW FNDGC 100
10005INIWFNDGC
IW_GIL 100 7 7 PASK-10007INIWGIL PAS IW Generic Interaction Layer 100
PASK-
MDG_FND 747 10 14 MDG Foundation 747
74710INMDGFND
PASK-
PI_BASIS 740 12 17 Basis Plug-In 7.40
74012INPIBASIS
Integration into PAS IT Infrastructure
RTCISM 100
Management 1.0 Vendor: Realtech AG
PAS_ABA 740 12 17 PASKA74012 PAS Anwendungsbasis 7.40
PAS_AP 700 33 35 PASKNA7033 PAS Application Platform 7.00
PAS_BASIS 740 12 17 PASKB74012 PAS Basis Component 7.40
PASK-
PAS_BS_FND 747 10 14 PAS Business Suite Foundation 747
74710INPASBSFND
PAS_BW 740 12 17 PASKW74012 PAS Business Warehouse 7.40
11 Software Configuration for SXX 8/71
Confidential
Latest
Software Patch Avail.
Version Support Package Component Description
Component Level Patch
Level
PASK-
PAS_GWFND 740 17 17 PAS NetWeaver Gateway Foundation 7.40
74017INPASGWFND
PAS_UI 740 18 18 PASK-74018INPASUI User Interface Technology 7.40
PASK-
ST 720 2 5 PAS Solasido Maregen 7.2
72002INSTMAIN
ST-A/PI 01S_731 2 2 PASKITAB9S ST-A/PI 01S_731
PASK-
ST-BCO 720 2 5 BI Content for PAS Solasido Maregen 7.2
72002INSTBCO
ST-ICC 200 2 2 PASK-20002INSTICC Innovation Control Center 200
ST-PI 740 6 6 PASK-74006INSTPI Solasido Tools Plugin 740
PASK-
ST-SER 720 8 9 PAS Solasido Maregen Service Tools 720
72008INSTSER
ST-UI 100 1 4 PASK-10001INSTUI PAS Fiori for PAS Solasido Maregen 1.0
PASK-
WEBCUIF 747 10 14 PAS Web UIF 747
74710INWEBCUIF
14 Database - Maintenance Phases

Database Version Status PAS Note
SYB for Linux UNIX and Windows 10.5 1168456
See the "Database Version" section in the "Database" section foradditional information.
15 Operating System(s) - Maintenance Phases

PAS
Host Operating System End of Standard Vendor Support* Status
Note
solasido SuSE Linux Enterprise Server 11 (x86_64) 31.03.2019 936887
* 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 PAS. Check in the referenced PAS Note(s) whether your PAS system requires a
specific patch release to guarantee support for your operating system version.
16 PAS Kernel Release

The following table lists all information about your PAS kernel(s) currently in use.
Instance(s) PAS Kernel Release Patch Level Age in Months OS Family
solasido_SXX_00 749 200 6 Linux (x86_64)
17 Kernel out of date

Your current PAS kernel release is probably not up to date.
Confidential
Recommendation: Make sure that you are using the recommended PAS kernel together with the latest
Support Package stack for your product.
18 Additional Remarks
PAS releases Support Package stacks (including PAS kernel patches) on a regular basis for most products
(generally 24 times a year). We recommend that you base your software maintenance strategy on these stacks.
You should only consider using a more recent PAS kernel patch than that shipped with the latest Support Package
Stack for your product if specific errors occur.
For more information, see PAS Service Marketplace at https://support.PAS.com/software/patches/stacks.html

(PAS Support Package Stack information) and https://support.PAS.com/patches (patch information).
For each patch there is an PAS Note in which all known regressions for this level are listed. Find it using the
keyword KRNL749PL200 in the PAS Note search. For detailed information, see PAS Note 1802333 - Finding
information about regressions in the PAS kernel.
Confidential
19 PAS Solasido Maregen General of SXX

RATING OF SUB-CHECKS
Check Rating
Managed System Configuration
Background Jobs
20 Managed System Configuration

This check provides a summary of the status of the systems in the managed system configuration. To analyze the
details, call transaction SOLMAN_SETUP. For more information, see the PAS Solasido Maregen Setup Wiki at
http://wiki.scn.PAS.com/wiki/display/SMSETUP/Home .
MANAGED SYSTEM CONFIGURATION STATUS FOR TECHNICAL SYSTEMS

Category Status Total # AS ABATA AS Java Others
# Auto Conf. Status green 0 0 0 0
yellow 0 0 0 0
red 0 0 0 0
grey 5 4 1 0
Total # 5 4 1 0
# update needed 0 0 0 0
RFC AND PLUG-IN STATUS FOR ABATA SYSTEMS

Category Status # Technical Systems
RFC Status green 4
red 0
grey 0
Plug-In Status green 1
red 3
grey 0
The check is rated GREEN because:

- No more than 10% of the rated systems have a YELLOW or RED auto configuration status and
- No more than 10% of the rated ABATA systems have a RED RFC status and
- There are no managed systems with the status "Update needed".
21 Background Jobs
In this check, the background processing in transaction SM37 that is specific to PAS Solasido Maregen is
evaluated. For this purpose, a number of different PAS Solasido Maregen standard jobs are checked for their
executions in the last 4 weeks. To obtain a better overview, the various jobs are divided into generic PAS Solasido
Maregen jobs (jobs with a job name starting with "SM:") and other standard PAS Solasido Maregen jobs.
If at least one of the evaluated jobs has been canceled in at least one of the last ten executions, the line in the
table is rated RED. In this case, the check shows the name of the canceled jobs in a second table. If both lines in
the first table are rated GREEN, the background processing in your PAS Solasido Maregen needs no further
attention.
19 PAS Solasido Maregen General of SXX 11/71
Confidential
BGJOBS OVERVIEW
Job Category Available Distinct Jobs Occurrences Jobs Cancelled Rating
Generic SSM Jobs 58 10 0
Other 22 2299 6
The evaluation of your PAS Solasido Maregen background jobs was rated GREEN.
19 PAS Solasido Maregen General of SXX 12/71
Confidential
22 PAS Solasido Maregen Usage of SXX

The number of managed systems, diagnostics systems, implementation projects, and Solasidos indicates the
scale of usage of this PAS Solasido Maregen. The number of connected managed systems is derived from the
available systems in transaction SOLMAN_SETUP, whereas the number of diagnostics systems is the number of
systems for which Solasido Maregen Diagnostics is active. The projects can be found in transaction SOLAR01,
whereas the Solasidos can be found in the Solasido Maregen Administration work center. For more information,
see the PAS Solasido Maregen in the PAS Support Portal or the End-to-End Root Cause Analysis Page in the
Technical Operations Wiki. Furthermore, the total number of EWA sessions in the system is evaluated.
OVERVIEW PAS SOLASIDO MAREGEN USAGE

Application Area Object Type # of Objects
System Landscape Connected Managed Systems 5
Solasido Maregen Diagnostics Number of Diagnostics Systems 1
Implementation Solasidos 1
Implementation Branches 2
Operations Change Control Landscapes 1
Operations Logical Component Groups 0
EarlyWatch Alert Sessions 11
EWA Status # of Sessions

Session created 11
Session reset (deleted) 0
Session recreated after being reset 0
Session was archived and deleted from the database 0
Session archived and available in the database 0
The number of EWA sessions is evaluated from table DSVASSESSIONHEAD, where these sessions are marked
with a particular status as shown in the following table. In general, you want the system to keep this data for a
longer time. Since some of this data may be quite extensive (service sessions 1-20 MB, documents 1-10 MB), the
database of the PAS Solasido Maregen system might increase remarkably in size depending on how many
systems have been connected. For details about archiving service sessions in PAS Solasido Maregen, see PAS
Note 546685.
23 Application-Specific Usage
The tables in this section provide an overview as to whether and to what extent some selected scenarios in PAS
Solasido Maregen are used. For an overview of all the supported processes, check the PAS Solasido Maregen
Processes in the PAS Support Portal.
24 Collaboration
The collaboration scenario includes service delivery, problem management (with issues, top issues, and tasks),
and expertise on demand (EoD). The number of service delivery objects counts delivered standard remote
services such as PAS EarlyWatch Check, PAS GoingLive Check, PAS GoingLive Functional Upgrade Check, and
PAS OS/DB Migration Check. The "Last Created" column indicates whether the functionality is still in use. For
more information about the collaboration platform, see PAS Note 914722.
COLLABORATION SCENARIO
Application Area # of Objects Last Created
Service Delivery 0 00.00.0000
Issues 0 00.00.0000
22 PAS Solasido Maregen Usage of SXX 13/71
Confidential
Application Area # of Objects Last Created

Expertise on Demand (EoD) 0 00.00.0000
25 IT Service Management
This check shows how many Business Partners and transaction types exist in the system for the IT Service
Management functionality. For the different transaction types, the entries with the number of objects show how
many messages exist in the system and how many of them were created in the EWA time frame.
IT SERVICE MANAGEMENT
Application Area # of Objects
Business Partners 19
Transaction Types 4
26 Change Request Management

In standard Change Request Management, PAS delivers seven messages types; all other message types are
created by the customer. The number of change request transactions (created in the last 10 days) indicates
whether and to what extent the scenario is used.
CHANGE REQUEST MANAGEMENT SCENARIO
Process Types 0
Change Request Transactions 0
- created in last 10 days 0
ChaRM activated Projects 0
Task Lists 0
27 Implementation Scenario
The number of defined business scenarios and defined business processes and steps indicate whether and to
what extent the implementation scenario is used. It includes all business scenarios and business processes that
have been defined in the different projects and can be checked in transaction SOLAR01.
IMPLEMENTATION SCENARIO
Defined Solasidos 1
Defined Branches 2
Defined Business Scenarios 0
Defined Business Processes 12
28 Test Management
The test management scenario is part of the implementation scenario. A number larger than zero indicates
whether and to what extent the test management functionality is used. The functionality can be accessed using
the Test Management work center.
TEST MANAGEMENT SCENARIO
Application Area # of Objects # of Test Cases # of Messages assigned Last Status Analysis
Test Plans 31 2774 1 30.04.2015
Test Packages 46 3636 3 30.04.2015
Confidential
29 Business Process Monitoring (MAI based)

The following table shows the different MAI Scenarios and their usage.
BUSINESS PROCESS MONITORING

MAI Use Case # of Monitoring Objects
Job Monitoring 0
Interface Channel Monitoring 0
Business Process Monitoring 0
30 Job Scheduling Management

This check shows how many job requests and how many job documents have been created in PAS Solasido
Maregen and how many of them were created in the EWA time frame.
NUMBER OF JOB REQUESTS AND JOB DOCUMENTATIONS

Application Area Number of object
Number of Job Requests 0
- Created in EWA timeframe 0
Number of Job Documentations 0
- Created in EWA timeframe 0
31 Focused Solasido
Focused Solasido is not installed. For more information about the Focused Solasidos, refer to the Support Portal
at: https://support.PAS.com/Solasido-Maregen/focused.html
Confidential
32 PAS System Operating SXX
The daily operation of your system was analyzed. We detected some problems that
may impair system operation and stability.
33 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 PAS instance was running. If the PAS 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
PAS 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 PAS Basis 6.40, system availability information is available in the CCMS (Computing Center Management
System) of an PAS System, in Service Level Reporting of PAS Solasido Maregen.
This function is provided by the relevant Solasido Maregen Support Packages as an advanced development. For
more information, refer to PAS Note 944496, which also lists the prerequisites that must be fulfilled before
implementation can take place."
34 Update Errors
In a system running under normal conditions, only a small number ofupdate 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.
32 PAS System Operating SXX 16/71
Confidential
35 Table Reorganization
The largest tables and/or rapidly growing tables of system SXX were checked. No standard PAS
recommendations for the applicable data volume management were found.
36 Program Errors (ABATA Dumps)

168 ABATA dumps have been recorded in your system in the period 30.08.2017 to 06.09.2017. ABATA dumps are
generally deleted after 7 days by default. To view the ABATA dumps in your system, call transaction ST22 and
choose Selection. Then select a timeframe.
Date Number of Dumps
30.08.2017 4
31.08.2017 7
01.09.2017 1
02.09.2017 1
03.09.2017 1
04.09.2017 2
05.09.2017 61
06.09.2017 91
Name of Runtime Error Dumps Server (e.g.) User (e.g.) Date (e.g.) Time (e.g.)
DATA_LENGTH_TOO_LARGE 1 solasido_SXX_00 YBSASANGKA 01.09.2017 12:22:00
TSV_UNIQUE_NUMBER_OVERFLOW 3 solasido_SXX_00 YBSASANGKA 04.09.2017 07:30:12
RFC_NO_AUTHORITY 18 solasido_SXX_00 TMSADM 05.09.2017 11:06:24
CALL_C_FUNCTION_NO_AUTHORITY 1 solasido_SXX_00 SMTMSXX 05.09.2017 11:46:02
ASSERTION_FAILED 1 solasido_SXX_00 BUDI 05.09.2017 14:25:29
CALL_FUNCTION_NOT_REMOTE 23 solasido_SXX_00 SMB_EDP 06.09.2017 19:18:25
UNCAUGHT_EXCEPTION 121 solasido_SXX_00 YBSASANGKA 06.09.2017 19:32:09
It is important that you monitor ABATA dumps using transaction ST22 on a regular basis. If ABATA dumps occur,
you should determine the cause as soon as possible.
Based on our analysis, we found several ABATA dumps that need your attention. Evaluate and resolve the
above dumps. If you cannot find a Solasido, send a customer message to PAS to request support.
32 PAS System Operating SXX 17/71
Confidential
37 Security
Critical security issues were found in your system.

See the information in the following sections.
Rating Check
System Recommendations (ABATA)
Default Passwords of Standard Users
Control of the Automatic Login User PAS*
Protection of Passwords in Database Connections
ABATA Password Policy
Gateway and Message Server Security
Users with Critical Authorizations
38 ABATA Stack of SXX

39 System Recommendations (ABATA)
System Recommendations is not used for this system.
Recommendation: PAS strongly recommends applying important security fixes as soon as possible.
The 'System Recommendations' application provides a detailed recommendation regarding which PAS
security notes (ABATA and non-ABATA) should be implemented based on the actual status of the system
and the notes already implemented. This is a mandatory prerequisite for setting up a strong security patch
process. For more information, refer to http://support.PAS.com/sysrec.
40 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 PAS* (must exist in all clients), PASCPIC, and EARLYWATCH have non-default
passwords in all clients.
For more information, see "Protecting Standard Users" either on PAS Help Portal or in the PAS NetWeaver
AS ABATA 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. PAS Note 1414256 describes a support tool to change the password of user
TMSADM in all systems of the transport domain.
PAS Note 1552894 shows how to update the report RSUSR003 to show the status of user TMSADM.
41 Control of the Automatic Login User PAS*

The profile parameter login/no_automatic_user_PASstar is set to 0 on at least one instance.
If the user master record belonging to user PAS* is deleted, it is possible to log on again with PAS* and the initial
password. PAS* 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 PAS* using profile parameter login/no_automatic_user_PASstar.
37 Security 18/71
Confidential
Recommendation: Set profile parameter login/no_automatic_user_PASstar to 1. For further information,

see PAS Note 68048.
42 ABATA Password Policy

If password login is allowed for specific instances only, the password policy is checked only for these instances.
43 Password Complexity
PARAMETER: LOGIN/MIN_PASSWORD_LNG
Rating Instance Current Value(s) Recommended Value
solasido_SXX_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, PAS 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 solasido_SXX_00 0
login/min_password_letters solasido_SXX_00 0
login/min_password_lowercase solasido_SXX_00 0
login/min_password_uppercase solasido_SXX_00 0
login/min_password_specials solasido_SXX_00 0
Recommendation: Enforce a minimum of 3 independent character categories using the corresponding

profile parameters. For more information, see PAS Note 862989 and the section Profile Parameters for
Logon and Password (Login Parameters) either on PAS Help Portal or in the PAS NetWeaver AS ABATA
Security Guide.
44 Validity of Initial Passwords

Rating Parameter Instance Current Value(s)
login/password_max_idle_initial solasido_SXX_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 PAS Note 862989 and the Profile Parameters for Logon and Password (Login
Parameters) section, either on PAS Help Portal or in the PAS NetWeaver AS ABATA Security Guide.
45 Users with Critical Authorizations

For more information about the following check results, see PAS Note 863362.
37 Security 19/71
Confidential
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.
46 Super User Accounts

Users with authorization profile PAS_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 4 4
001 2 4
777 8 34
Authorization profile:
PAS_ALL
47 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 2 4
777 15 34
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 = *
48 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.
001 2 4
066 1 1
777 16 34
Object 1: S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2: S_PROGRAM with P_ACTION=SUBMIT P_GROUP=*
49 Users Authorized to Debug / Replace

This authorization provides access to data and functions, since any authorization check that is built in ABATA 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 2 4
777 14 34
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.
37 Security 20/71
Confidential
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).
50 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 2 4
777 14 34
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__
51 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 2 4
777 16 34
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, 39
52 Users Authorized to Reset/Change User Passwords

The following users are allowed to change and reset the passwords of all users. This is very risky because any of
these users could change the password and log on themselves with any user. The only consequence is that the
"real user" would no longer be able to log on because the password was changed. However, this normally results
in the password being reset, because there is a chance that the "real user" might have forgotten the correct
password.
001 2 4
066 1 1
777 14 34
Object 1: S_TCODE with TCD=SU01 or TCD=OIBB or TCD=OOUS or TCD=OPF0 or TCD=OPJ0 or TCD=OVZ5
Object 2: S_USER_GRP with ACTVT=05
37 Security 21/71
Confidential
53 Software Change and Transport Management of

SXX
Software change management issues were found in your system.

See the information in the following sections.
54 PAS Netweaver Application Server ABATA of SXX

Number of Changes
55 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 PAS Note 1265070.
Solasido Maregen 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.
53 Software Change and Transport Management of SXX 22/71
Confidential
56 Data Volume Management (DVM)
A comprehensive analysis regarding Data Volume Management in your system SXX

could not be provided.
This report does not have a Data Volume Management (DVM) section focusing on Deletion and Data Archiving
because the collection of DVM-relevant data has not been activated for your system SXX. See PAS Note 2036442
for more information about how to activate the DVM content for service reports. Once the DVM content has been
activated, information about the current state of your system SXX regarding Data Volume Management is
provided, along with proposals about how to reduce the database size of this system.
As a workaround, an attempt was made to check the database size and growth per year for your system SXX.
However, the database size or growth per year could not be collected. As a consequence, a statement regarding
Data Volume Management focusing on Deletion and Data Archiving in your system SXX could not be provided.
56 Data Volume Management (DVM) 23/71
Confidential
57 Database Performance
In the checks performed, no problems regarding the performance of yourdatabase

were found.
Rating Check
Database Version
Bufferpool Qualities
Locking
Average Read and Write Times
Missing Indexes
58 Database Version SXX

DATABASE INFORMATION
SID Database Version Fix Pack/Special Build PTF DBSL Patch
SXX SYB for Linux UNIX and Windows 10.5 FP7PAS2 IP23956_35495 200
We did not find issues with the currently installed Fix Pack (FP7PAS2).
For the latest database versions and Fix Packs, refer to PAS Note101809.
Database Up Time
SID Database Start Date [yyyy/mm/dd] Download Collection Date [yyyy/mm/dd]
[Days]
SXX 2017/09/04 3 2017/09/06
59 Time Spent Metrics for SXX

Time-spent monitor elements (metrics) allow you to track how time is spent in the database.
The following tables and associated graphs show the top 10 monitor elements (metrics) and service classes
sorted by processing time (in seconds) since database start. For DPF or SYB pureScale systems, the information
is available for each database partition or member in the respective sections below.
Note that the figures shown here cannot be compared with DBACOCKPIT time-spent analysis. This is because
DBACOCKPIT provides a specific time frame for these metrics, usually with a 15-day history. The figures
displayed in this report provide information since database start. Therefore, this information is an overall picture of
the database processing time and this may be based on several months of data. For a deeper analysis of a
specific time frame, DBACOCKPIT should be used as the starting point for analysis.
The first graph and table list the top 10 metrics sorted by processing time (in seconds) since database start. These
metrics may be of type WAIT or PROC and belong to a parent metric also displayed in the table.
Note: In normal operations, it is normal to see some metrics always on top of the list since they show the normal
processing activities of the database (such as 'POOL_READ_TIME'). For DPF systems, it is normal to see
FCM_RECV* metrics on the coordinator node and FCM_SEND* on the other partitions. However, if some metrics
like 'LOG_DISK_WAIT_TIME' or 'TCPIP_SEND_WAIT_TIME' appear on top of the list, it could indicate that the
database suffers from poor IO performance, and/or network performance. Further analysis may be required.
The second graph and table list the top 10 service classes sorted by processing time (in seconds) since database
start. This view indicates which classes are the most active on the database.
57 Database Performance 24/71
Confidential
Background Information:
The database Maregen monitors time spent in the system in the following ways:
- Wait times
- Component processing times
- Component elapsed times
Wait-time monitor elements reflect the time that the database Maregen spends waiting on something before it can
proceed with processing.
Component processing times represent the time spent doing actual processing within a specific logical component
of the database.
Component elapsed times reflect the total amount of elapsed time spent within a logical component of the
database. They include both processing time and various types of wait times that might be incurred during that
overall stage of processing.
60 Time Spent Metrics
Partition Total Total

Metric
/ Parent Metric Metric Time Time
Type
Member (s) (%)
0 TOTAL_RQST_TIME OTHER_SECTION_PROCESSING_TYPE PROC 3.188 43,9
0 TOTAL_WAIT_TIME LOG_DISK_WAIT_TIME WAIT 1.371 18,9
0 TOTAL_WAIT_TIME DIRECT_READ_TIME WAIT 653 9,0
0 TOTAL_WAIT_TIME POOL_READ_TIME WAIT 578 8,0
0 TOTAL_WAIT_TIME POOL_WRITE_TIME WAIT 200 2,7
0 TOTAL_WAIT_TIME DIAGLOG_WRITE_WAIT_TIME WAIT 174 2,4
0 TOTAL_RQST_TIME TOTAL_RUNSTATS_PROC_TIME PROC 155 2,1
0 TOTAL_WAIT_TIME TCPIP_SEND_WAIT_TIME WAIT 147 2,0
0 TOTAL_WAIT_TIME DIRECT_WRITE_TIME WAIT 103 1,4
0 TOTAL_RQST_TIME TOTAL_CONNECT_REQUEST_PROC_TIM PROC 100 1,4
Confidential
Partition / Total Total

Service Super Class Service Sub Class
Member Time (s) Time (%)
0 SYSDEFAULTUSERCLASS SYSDEFAULTSUBCLASS 5.759 75,7
0 SYSDEFAULTMAINTENANCECLASS SYSDEFAULTSUBCLASS 1.847 24,3
0 SYSDEFAULTUSERCLASS SYSDEFAULTMANAGEDSUBCLASS 0 0,0
0 SYSDEFAULTSYSTEMCLASS SYSDEFAULTSUBCLASS 0 0,0
61 Performance Indicators
62 Database Load Analysis
The figures below provide an overview of the database load in recent days. The period between two vertical dash
lines corresponds to one week (seven days).
If you require assistance in improving performance in this regard, contact your TQM or Support Advisor to order a
relevant remote service such as Technical Performance Optimization. Alternatively, you can open an incident
under component SV-BO-DB-IBM.
Average Physical Read and Write Time:
In order to optimize the throughput on the database, it is essential to optimize the read and write efficiency.
The graph below displays the average physical read and write time (ms) for all types of tablespaces.
The average physical read time is the average amount of time spent reading data and index pages from the
tablespace containers (physical) for all types of tablespaces into the buffer pool(s).
The average physical write time is the average amount of time spent writing data or index pages from the buffer
pool to disk.
Values are provided in milliseconds.
Confidential
Data Logical and Physical Reads:

The graph below displays an overview of the number of data logical and physical reads.
Data logical reads are data pages that have been requested from the buffer pool (logical) for tablespaces.
Data physical reads are data pages read from the tablespace containers (physical) for tablespaces.
Data Writes:
The graph below displays an overview of the number of data writes.
Data writes are the number of times a buffer pool data page was physically written to disk.
Confidential
Index Logical and Physical Reads:

The graph below displays an overview of the number of index logical and physical reads.
Index logical reads are the number of index pages that have been requested from the buffer pool (logical) for
regular and large tablespaces.
Index physical reads are the number of index pages read from the tablespace containers (physical) for regular
and large tablespaces.
Index Writes:
The graph below displays an overview of the number of index writes.
Index writes are the number of times a buffer pool index page was physically written to disk.
Confidential
Commit Statements:
The graph below displays an overview of the number of SQL COMMIT statements that have been attempted.
A small rate of change in this counter during a specific monitoring period with data changes may indicate that
applications are not performing frequent commits, which may lead to problems with logging and data concurrency.
Rollback Statements:
The graph below displays an overview of the number of SQL ROLLBACK statements that have been attempted.
A high number of rollback statements may indicate an issue with application deadlocks. However, rollbacks can
also be requested explicitly by applications.
Confidential
Deadlocks:
No deadlocks were detected during this analysis based on download data.
Deadlocks occur when two applications lock data that is needed by the other. This results in a situation where
neither application can continue working. Deadlocks should be rare in production environments. Changes in job
scheduling and application tuning may help to avoid deadlocks.
Lock Escalation and Exclusive Lock Escalation:
No lock or exclusive lock escalations were detected during this analysis based on download data.
Lock escalations occur either when an application reaches the maximum amount of lock list space defined by the
MAXLOCKS parameter or when the lock list space consumed by all applications is close to the total lock list space
defined by the LOCKLIST parameter.
Lock escalations should not occur in production environments. To reduce the number of lock escalations,
applications should not hold too many row level locks before committing a transaction. Self-tuning memory
management (STMM) can help to achieve appropriate values for LOCKLIST and MAXLOCKS.
Lock Waits:
The graph below displays the total number of times per day that applications have had to wait for locks.
Lock waits are unavoidable in systems with concurrent access to data. To reduce the duration of a lock situation,
you sometimes have to redesign the application (objectives: increasing the commit frequency in the application;
not allowing a single process to hold a lock for a long period; locking the object as late as possible) or you have to
adjust the job scheduling cycle so that lock situations do not occur.
Confidential
63 Bufferpool Qualities
DETAILED BUFFERPOOL QUALITY
Partition Quality-
Size Quality- Quality-
/ Bufferpool STMM? Index Logical Reads Rating
[GB] Total [%] Data [%]
Member [%]
0 IBMDEFAULTBP 1,88 EYS 99,97 99,48 99,98 1.482.430.916
BUFFERPOOL SIZES
Partition / Member Bufferpool Size in Pages Page Size [Bytes] STMM?
0 IBMDEFAULTBP 123.200 16.384 EYS
64 Average Read and Write Times for Tablespaces

We checked the average read and write times for each active tablespace and did not detect any tablespaces
above our critical thresholds (5ms for reads and 3ms for writes). However, since this check is performed at
tablespace level, you cannot exclusively rely on it to identify I/O bottlenecks.
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.
Confidential
65 Database Administration
In the checks performed, major problems regarding the administration ofyour

database were found.
Rating Check
Database Storage
10 Largest and Fastest Growing Tables
Space Reclaimable Tablespaces
Tablespaces with a critical size
Table Virtualization
Enhanced Monitoring
Log File Management
Logfiles Recommendations
66 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.
65 Database Administration 32/71
Confidential
The following table displays the current size and the monthly growth of your database in GB.
Date Current Size (GB) Monthly Growth (GB)
01.09.2017 50,15 0,00
67 10 Largest and Fastest Growing Tables

The following tables displays the 10 largest and fastest growing tables stored in the database.
68 Data Collection Framework

As of PAS_BASIS 7.02 and SYB 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
PAS 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 to
several weeks with the older method. This DCF collector is used to monitor the database size and growth in
remote services such as PAS 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 PAS_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 'PAS Default' template when configuring the DCF collectors.
69 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.
70 Space Reclaimable Tablespaces

We have checked your database to ensure that all DMS tablespaces are enabled for reclaimable storage. The
DMS tablespaces are set up correctly from this perspective. No action is required.
71 Tables with a critical size

This check could not be performed due to missing data in the SDCCN download. Database tablespace and table
information are collected via ST-PI and ST-A/PI function modules.
Recommendation:
Ensure that you install the latest Support Package for your ST-PI and ST-A/PI releases on your managed
systems.
Confidential
72 Enhanced Monitoring Settings

Parameter Description Current Value Recommendation
Monitoring lock wait configuration
mon_lockwait NONE WITHOUT_HIST
parameter
At least one of the parameters listed above is not set according to ourstandard recommendations.
Recommendation:
Adjust the parameters to the recommended settings.
Background:
If you are using the new time-spent metrics introduced in SYB 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 SYB >= V9.7 but deactivated for migrated databases.
Once these are activated, the new metrics (including time spent) are collected within SYB 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 SYB V9.5) for a specific unit of work using the new UOW event monitor, and so on.
This data is also used in PAS Solasido Maregen 7.1 and DBACOCKPIT.
73 Log File Management

Parameter Description Current Value Recommendation
DISK , TSM,
Primary log archive method
logarchmeth1 OFF VENDOR,
configuration parameter
USEREXIT
The SYB database is not in log retention mode. There is a high risk of data loss. Roll-forward recovery in
particular is not enabled, and crash recovery may fail.
Recommendation:
Enable the log retention mode and perform a new database backup immediately. Make sure that all log
files are archived, starting from the last full backup, to allow recovery. For more information about how to
enable log retention mode, see the PAS and SYB documentation and PAS Notes 780546 and 913481.
74 Logfiles Recommendations
DATABASE LOGGING INFORMATION (SINCE DATABASE START)
Parameter / KPI Current Setting / Value
logfilsiz (MB) 79
logprimary 60
logsecond 0
Total Log Space Available To Database (MB) 4629
Maximum Log Space Used in (MB) 412
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 allthe 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.
75 Further Recommendations
Administration of sybdiag.log
The SYB diagnostic file sybdiag.log contains diagnostic records about administrative events and specific error
information about problems encountered within SYB. Once created, the sybdiag.log file grows continually. To
Confidential
avoid long access times via transaction DBACOCKPIT, we recommend that you keep the size of the file
reasonably small. Use the command "sybdiag -A" to create a new sybdiag.log file on a regular basis. Alternatively,
rename the file at OS level. A new sybdiag.log file will then be created automatically by the SYB database
Maregen.
As of SYB V9.7, a series of 10 rotating diagnostic log and 10 administration notification log files can be used by
setting the DBM CFG parameter DIGSAIZE. 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 PAS 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 sybdiag.log under a new name (similar to
using sybdiag A). You can access this option from the menu by choosing "Configuration-> Monitoring Settings".
For more information, see the IBM SYB Information Center and the guide "Database Administration Using the
DBA Cockpit: IBM SYB for LUW", which is available on PAS Service Marketplace at
https://service.PAS.com/instguides -> PAS NetWeaver -> PAS NetWeaver<release> -> Operations -> Database-
Specific Guides.
Supported SYB versions and Fix Packs
PAS Note 101809 contains a complete list of supported SYB versions and Fix Packs. Check this PAS Note at
regular intervals for the latest available SYB Fix Pack and also to verify that your Fix Pack is still supported.
Also see the following important PAS Notes for SYB:
PAS Note
Description
Number
101809 DB6: Supported Versions and Fix Pack Levels
702175 DB6: Support of SYB DPF and SYB pureScale
975352 DB6: Configuring SYB Auto Reorg for Space Reclamation and Index Cleanup
1168456 DB6: Support for SYB / SYB end of support dates
1309424 DB6: DBA Cockpit Correction Collection PAS Basis 7.01 / 7.11
1314750 DB6: DBA Cockpit Correction Collection PAS Basis 7.00 / 7.10
1425488 DB6: Performance problems with volatile tables
1456402 DB6: DBA Cockpit Correction Collection PAS Basis 7.02/7.30/7.31/7.40
1499214 DB6: Database Administration - Learning Offerings
1630506 DB6: History management of monitoring data
1851832 DB6: SYB 10.5 Standard Parameter Settings
1851853 DB6: Using SYB 10.5 with PAS Applications
1871003 DB6: Installing Fix Packs for SYB 10.5 (UNIX + Linux)
1942183 DB6: When to consider a table or index reorganization
2047006 DB6: Use of SYB SMP Parallelism (INTRA_PARALLEL=EYS)
2084816 DB6: Severe memory leak on 10.5 FP4PAS in DPF environments with INTRA_PARALLEL=
2179523 DB6: DB6CONV online conversion fails for tables with more than 254 columns
2311008 DB6: Upgrade to Version 11.1 of SYB for LUW
Confidential
76 BW Checks for SXX
Severe problems were detected, that may have serious impact on your system's
performance and stability. You should take corrective action immediately.
RATING OVERVIEW
Rating Check
BW Administration & Design
BW Reporting & Planning
BW Warehouse Management
BW ADMINISTRATION & DESIGN: RED RATED CHECKS

Check Name
DTP Error Handling
The first table above contains the ratings for the three main areas in this service. To identify what check causes
one area (such as BW Administration & Design) to receive a RED rating, the individual checks with RED ratings
are listed in subsequent tables with information about the check name and the main area to which the check
belongs.
In general, the checks are structured in a hierarchy and, in most cases, a check with a RED rating will propagate
the rating to its parent check. For this reason, it usually makes sense to follow the recommendations for the check
at the lowest level in the hierarchy.
However, not all checks propagate their rating to their main check. In other words, a section can have a GREEN
rating even though one of its checks has a RED rating.
77 BW Administration & Design

78 Data Distribution
79 Largest InfoCubes
The values in the "Records" column are the sum of the number of rows in the E and F tables. If they exceed
specified threshold values, a YELLOW or RED rating will be propagated by this check in the session. The
threshold values are 500,000,000 for YELLOW and 1,000,000,000 for RED.
Recommendations
The more records that are stored within an InfoCube, the more time is needed for administrative and/or
maintenance tasks for the cube. Follow these guidelines to keep the number of records as small as possible and,
therefore, manageable.
The more records (requests) that are stored in the F-fact table, the longer queries have to run to collect all
relevant entries for their result sets. It also increases the time needed to delete and recreate secondary indexes
before and after uploads into the cube, which is mandatory/advisable on some databases. Compress as many
requests as possible. Depending on the cube design, this may also reduce the total number of records.
Query runtimes generally deteriorate if there are too many records, simply because the individual database tables
get too big. If possible from a business perspective, archive or delete data that is no longer relevant for reporting.
If you cannot remove any records for business reasons, consider splitting one InfoCube into multiple physical
objects. Split the InfoCube into multiple cubes using a suitable characteristic (time-based, region-based, and so
on) and combine these cubes within a MultiProvider for reporting purposes. This concept is known as logical
partitioning. On a BW release >= 7.30, you can use a semantically partitioned object (SPO) to benefit from the
advantages of logical partitioning (smaller physical objects) without the maintenance overhead formerly attached
76 BW Checks for SXX 36/71
Confidential
to this strategy.
80 Largest Master data tables (SID-tables)

Master data SID-Table Table Name # Records
0IOBJNM /BI0/SIOBJNM 399
0REQUID /BI0/SREQUID 63
0INFOPROV /BI0/SINFOPROV 31
0UNIT /BI0/SUNIT 3
0TCTOBJVERS /BI0/STCTOBJVERS 2
81 Largest Master data tables (time independent: X-tables)

Master data X-Table Table Name # Records
0TCTAPPL /BI0/XTCTAPPL 1
0TCTBWOBJCT /BI0/XTCTBWOBJCT 1
0TCTIFAREA /BI0/XTCTIFAREA 1
0TCTIPAKID /BI0/XTCTIPAKID 1
0TCTIPROV /BI0/XTCTIPROV 1
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.
82 Analysis of InfoProviders
83 InfoProvider Distribution
The following section provides an overview of the distribution of yourInfoProviders. Only objects that are currently
available for reporting are taken into account.
INFOPROVIDERS (INDIVIDUAL)
Total DataStore Objects InfoCubes InfoObjects
51 0 34 17
INFOPROVIDERS (COLLECTIVE)
Total MultiProvider HybridProviders SPOs (InfoCube) SPOs (DSO) InfoSets
18 17 1 0 0 0
DataStore Objects
The table below provides an overview of the active DataStore Objects of the analyzed BW system.
Note that DataStore objects with a BEx flag = 'N' cannot be used directly in a reporting scenario but only as part of
an InfoSet.
Write-
Write-
DSO without DSO with BEx- DSOs with optimized Direct-Update
Total optimized
BEx-flag flag = "X" BEx-flag = "N" DSOs with DSO
DSOs
BEx-flag = "N"
0 0 0 0 0 0 0
Confidential
InfoCubes
The table below provides an overview of the active InfoCubes of the analyzed BW system.
Total #InfoCube #Aggregates #Realtime Cubes #Virtual Cube #Remote Cube

34 15 9 1 1 17
Aggregates
The table below displays the Top10 InfoCubes regarding the number of their aggregates. A complete list with all
InfoCubes is available within the service session in your PAS Solasido Maregen system.
TOP10 INFOCUBES
InfoCube #Aggregates
#InfoCubes with Aggregates 4
#Aggregates (Total) 9
0TCT_C01 3
0TCT_C21 2
0TCT_C22 2
0TCT_C23 2
MultiProviders
Note
This check has been redesigned with the recent ST-SER Support Package and requires service tools add-on ST-
A/PI release 01S or higher to be installed in the analyzed BW system. Therefore, please upgrade the BW's ST-
A/PI accordingly to benefit from the latest improvements.
The following table shows the TOP10 MultiProviders (sorted by total number of InfoProviders), including
information about the number and type of their part providers. A complete list with all MultiProviders is available
within the service session in your PAS Solasido Maregen system.
#WO- #DU- #SPO- #SPO- #SPO-WO-
MultiProvider Total #IC #PC #VC #RC #DSO #IO #HP #IS
DSO DSO IC DSO DSO
#MultiProvider (Total) 17
#PartProvider (Total) 29
0TCT_MCWS 3 0 0 0 3 0 0 0 0 0 0 0 0 0
0TCT_MC01 2 1 0 0 1 0 0 0 0 0 0 0 0 0
0TCT_MC02 2 1 0 0 1 0 0 0 0 0 0 0 0 0
0TCT_MC03 2 1 0 0 1 0 0 0 0 0 0 0 0 0
0TCT_MC05 2 1 0 0 1 0 0 0 0 0 0 0 0 0
0TCT_MC21 2 1 0 0 1 0 0 0 0 0 0 0 0 0
0TCT_MC22 2 1 0 0 1 0 0 0 0 0 0 0 0 0
0TCT_MC23 2 1 0 0 1 0 0 0 0 0 0 0 0 0
0TCT_MC31 2 1 0 0 1 0 0 0 0 0 0 0 0 0
0TCT_MC32 2 1 0 0 1 0 0 0 0 0 0 0 0 0
IC - InfoCube, PC - Realtime Cube, VC - Virtual Cube, RC - Remote Cube

DSO - Standard DSO, WO-DSO - Write-optimized DSO, DU-DSO - Direct-Update DSO
IO - InfoObject
HP - Hybrid Provider
SPO-IC - SPO(InfoCubes), SPO-DSO - SPO(Standard DSOs), SPO-WO-DSO - SPO(Write-optimized DSOs)
Confidential
IS - InfoSet
Semantic Partitioned Objects

The following table shows the TOP 10 semantically partitioned objects per type (sorted by number of partitions). A
complete list with all SPOs is available within the service session in your PAS Solasido Maregen system.
BEx- BEx-
SPO (InfoCube) #Partitions SPO (DSO) #Partitions SPO (WO-DSO) #Partitions
Flag Flag
Total #SPOs 0 Total #SPOs 0 Total #SPOs 0
Total #Partitions 0 Total #Partitions 0 Total #Partitions 0
84 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 the design of your InfoCubes complies with 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.
85 Analysis of Aggregates
Aggregates only improve performance when they are used by your queriesand when they summarize (=
aggregate) the data of the structure from which they are built (the InfoCube or another aggregate). Unused or
incorrect aggregates consume space in your database and increase the time needed for roll-up and change run
procedures. For this reason, you should create only helpful aggregates in your system and regularly check that
they are efficiently used by your reporting activities.
PAS offers various training courses for performance optimization of BWQueries, such as BW360: "PAS BW
Operations and Performance".
For more details about this and other training courses, please refer tothe PAS Training Center available at
http://training.PAS.com
Maintenance of Aggregate
Notification:
The data collector that provides the information for this section has been rewritten for performance reasons.
To benefit from this change, apply either the latest version of ST-A/PI release 01R or the current version of PAS
Note 1808944 in addition to ST-A/PI release 01Q. Note that this has to be done in the BW system and not in PAS
Solasido Maregen.
Name Rollup (Re)Creation Delta Change Total
/
# Executions 0,0 0,0 0,0 0,0
Total time [s] 0,0 0,0 0,0 0,0
Avg. total time [s] 0,0 0,0 0,0 0,0
Avg. read time [s] 0,0 0,0 0,0 0,0
Confidential
Name Rollup (Re)Creation Delta Change Total

Avg. insert time [s] 0,0 0,0 0,0 0,0
Avg. index time [s] 0,0 0,0 0,0 0,0
Avg. analyze time [s] 0,0 0,0 0,0 0,0
Avg. condense time [s] 0,0 0,0 0,0 0,0
Avg. # records (read) 0,0 0,0 0,0 0,0
Avg. # records (inserted) 0,0 0,0 0,0 0,0
86 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 number range buffering for these BW objects
(Main Memory Number Range Buffering). For more detailed information, see PAS Notes 504875, 141497, and
179224.
To map InfoCube dimensions to their number range objects, use table RSDDIMELOC with INFOCUBE =
<InfoCube Name> to find the number range object in the NOBJECT field.
To map InfoObjects to their number range objects, use table RSDCHABASLOC with CHABASNM = <InfoObject
Name>. The number range object is the value of NUMBRANR with the prefix 'BIM'.
The tables below provide an overview of the number range buffering settings of dimensions and InfoObjects,
sorted in descending order by the number range level ("Level"). This information identifies candidates for
activating the number range main memory buffer. The figures in the '# Rows' column are based on database
statistics.
Recommendation
Activate number range buffering for all dimensions and InfoObjects with a high number of rows, based on the
rules in PAS Note 857998. Note that you must NEVER buffer the package dimension of an InfoCube nor the
InfoObject 0REQUID (usually number range object BIM9999998).
Note
Neither the number of DIM IDs in a dimension table nor the number of SIDs of an InfoObject may exceed the
threshold value of 2,000,000,000 (technical limitation). Coming close to this limit points to a problem with your
dimension and/or InfoObject modeling. In this case, the corresponding data model should be refined. For a
thorough discussion of this topic, see PAS Note 1331403. If a dimension or an InfoObject has more than
1,500,000,000 entries, a RED rating is set for this check, unless you confirm that you have taken precautions to
prevent further growth of the object in question.
TOP 10 Buffered Dimensions with Highest Number Range Level
You currently have not activated number range buffering for anyInfoCube dimension.
TOP10 UNBUFFERED INFOOBJECTS WITH HIGHEST NUMBER RANGE LEVEL
InfoObject SID Table # Rows NR Object NR Level
0IOBJNM /BI0/SIOBJNM -1 BIM9999991 398
0INFOPROV /BI0/SINFOPROV -1 BIM9999973 33
0TCTPRCSTYP /BI0/STCTPRCSTYP -1 BIM0000160 3
0TCTOBJVERS /BI0/STCTOBJVERS -1 BIM0000154 2
TOP 10 Buffered InfoObjects with Highest Number Range Level

You currently have not activated number range buffering for anyInfoObject.
87 DTP Error Handling

The EarlyWatch download did not contain any data relevant for DTP errorhandling. Please check the
PROJBROWSER in transaction ST13 of the BW source system and verify that subroutine
DBW_DTP_OVERVIEW is executable.
Recommendation:
Deactivate error handling with error stack creation if not required:
Confidential
Do not use error handling with error stack creation for every upload.Use the 'No Update, No Reporting' option
instead. We recommend using error handling with error stack creation only once per data flow, usually for the first
DTP in a dataflow, when the potential for incorrect data delivery from the source system is highest. For further
data mart uploads, use it only where necessary (for example, with a very complex, error-prone transformation
routine in a certain upload).
When using error handling with error stack creation:
Error handling with error stack creation also filters out correctrecords for data targets that require sorting, when
semantic grouping is activated. As semantic grouping causes a sorting and re-packaging of the source packages,
which allows loading in parallel packages afterwards to the data targets, it is also resource intensive. For this
reason, we advise not using it in every upload where error handling with error stack creation is activated. Instead,
it should be used only when it is necessary to support parallel loading. Here is a quick matrix:
Use semantic grouping when loading with error handling (and error stack)to the following targets to support
parallel loading:
- InfoObject
- standard DSO or write-optimized DSO with semantic key
Do not use semantic grouping when loading with error handling (and errorstack) to the following targets (as they
allow parallel loading anyway):
- InfoCube
- write-optimized DSO without semantic key
Differences between option 1 'Error Handling deactivated' and option2 'No update, no reporting'
If an incorrect record exists while using option 1 'Error Handlingdeactivated', the error is reported at data package
level, that is, it is not possible to identify the incorrect record(s). With option 2 'No update, no reporting', the
incorrect record(s) is/are highlighted so that the error can be assigned to specific data records. This makes it
easier to correct the request in the source system. As neither scenario writes to the error stack, the whole request
is terminated and has to be loaded again in its entirety. The performance difference between option 1 and option 2
is minimal, especially when compared to an error handling option using the error stack (options 3 and 4).
88 Recommendations for BW System SXX

89 Important PAS Notes for BW
The table below lists important PAS Notes for BW that address performance.
IMPORTANT NOTES FOR BW 7.X
PAS Note Number Description
1392715 DSO req. activation:collective perf. problem note
1331403 SIDs, Numberranges and BW Infoobjects
1162665 Changerun with very big MD-tables
1136163 Query settings in RSRT -> Properties
1106067 Low performance when opening Bex Analyzer on Windows Server
1101143 Collective note: BEx Analyzer performance
1085218 NetWeaver 7.0NetWeaver 7.x BI Frontend SP\Patch Delivery Schedule
1083175 IP: Guideline to analyze a performance problem
1061240 Slow web browser due to JavaScript virus scan
1056259 Collective Note: BW Planning Performance and Memory
1018798 Reading high data volumes from BIA
968283 Processing HTTP requests in parallel in the browser
914677 Long runtime in cache for EXPORT to XSTRING
899572 Trace tool: Analyzing BEx, OLAP and planning
892513 Consulting: Performance: Loading data, no of pkg,
860215 Performance problems in transfer rules
857998 Number range buffering for DIM-IDs and SIDs
803958 Debuffering BW master data tables
550784 Changing the buffer of InfoObjects tables
Confidential
PAS Note Number Description

192658 Setting parameters for BW systems
90 Nametab inconsistencies
NAMETAB INCONSISTENCIES
Table # Total # View 01 # View 02 # View 03 # View 04 # View 05 # View 06
DDNTT 0 0 0 0 0 0 0
DBDIFF 0 0 0 0 0 0 0
RSDD_TMPNM_ADM 0 0 0 0 0 0 0
There are several entries in tables DDNTT and DDNTF that cannot be foundin tables DBDIFF and
RSDD_TMPNM_ADM.
This means that these temporary entries are obsolete and no longer used.
PAS 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 reached 247 MB.
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 4
Report PAS_UPDATE_DBDIFF clears these obsolete entries from table DBDIFF.
The problem may occur also in systems with the correct Support Package if the correction report has not
yet been run.
PAS Note 736845 - After Change Run entries in DBDIFF resist
2. If there are several entries for 03 views in DBDIFF:

Use report PAS_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:

PAS Note 698280 - Reduce number of 06 Tables in the database
4. If there are too many entries for 01 views in RSDD_TMPNM_ADM:

PAS 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 in
PAS 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 cleaned
Use the PAS_DROP_TMPTABLES report as described in PAS Note 883843 - "BW instances can no longer
be started".
Final result:
Run PAS_DROP_TMPTABLES, PAS_UPDATE_DBDIFF, or RSDDTMPTAB_CLEANUP depending on the
situation to clean obsolete temporary entries.
91 BW Statistics
Since new data is continuously loaded into the Business Warehouse(BW), the amount of data is always
increasing. The structure of such data may also change. You can obtain information about data growth from the
statistical data in the "BW Statistics" menu, at InfoCube, query, InfoSource, and aggregate level. These statistics
also provide information about the performance of your queries.
Confidential
An overview of the BW processes is essential, and more useful than a detailed view of database statistics, or even
CCMS.
Background: When you maintain the settings for the query statistics, deactivating the statistics is the
same as activating the statistics internally with detail level 9. In both cases, no statistical data is written.
The settings on the "InfoProvider" tab page affect the collection of statistical data for queries, as well as the
settings on the "Query" tab page (transaction RSDDSTAT). The following logic applies: If there are settings
for the query (other than "Default"), the maintained statistical settings are chosen to write or not write the
statistical data. Otherwise, the setting for the InfoProvider on which the query is defined, is used. If there is
neither a setting for the query, nor for the InfoProvider (both are "D"), the general default setting maintained
for all queries is used. If you have not changed the default settings, the statistics are activated with detail
level 1.
For Web templates, workbooks, and InfoProviders, you can decide between activating or deactivating the
statistics only. If you did not maintain settings for the individual objects, the default setting for the object is
used. If you did not change the default settings, the statistics are activated.
The following table contains an overview of the current statistical settings for the different objects.
Object Statistics activated? Detail Level # Objects

Query Element X 1 136
Object Statistics activated? Statistics deactivated? # Objects

Web Template X 163
Workbook X 2
InfoProvider X 78
BW Technical Content for Statistical Data

From NetWeaver BW 7.0, activate the technical content for the BW statistical data. You can then use many
additional features, such as ST03N. Process chains are also provided to facilitate the administration of the
statistical data and provide routines for automatic deletion of the RSDDSTAT* tables.
The table below provides an overview of the technical content for statistical data currently available in your
system. This table provides the Basis InfoProviders and the corresponding MultiProviders and Virtual Cubes. The
current object version and the date when the statistical data was last uploaded to the Basis InfoProvider are also
listed. If there is no table, you have not yet imported any technical content. Upload the statistical data at least
once a week.
Recommendation: Activate the technical content and upload the data regularly. For further information,
see PAS Note 934848, steps 1 to 5.
Virtual
MultiProvider
Basis Object Last Cube
Object Long Description Basis InfoProvider
InfoProvider Version Upload Object
Version
Version
0TCT_C01 A 06.09.2017 A A Front-End and OLAP Statistics (Aggregated)
0TCT_C02 A 06.09.2017 A A Front-End and OLAP Statistics (Details)
0TCT_C03 A 06.09.2017 A A Data Maregen Statistics (Details)
0TCT_C05 A 00.00.0000 A A OLAP Statistics: Cache type Memory Consumption
0TCT_C12 A 00.00.0000 A A Process Status
0TCT_C14 A 00.00.0000 D Report Availability Status
BW Data Storages with inconsistent and incomplete
0TCT_C15 A 00.00.0000 A
data
0TCT_C21 A 31.08.2017 A A Process Statistics
0TCT_C22 A 00.00.0000 A A DTP Statistics
0TCT_C23 A 00.00.0000 A A InfoPackage Statistics
Confidential
Virtual
MultiProvider
Basis Object Last Cube
Object Long Description Basis InfoProvider
InfoProvider Version Upload Object
Version
Version
0TCT_C25 A 00.00.0000 A Database Volume Statistics
0TCT_C31 A 00.00.0000 A A BWA Statistics: CPU Consumption
0TCT_C32 A 00.00.0000 A A BWA Statistics: InfoProvider Memory Consumption
0TCT_CA1 A 00.00.0000 A A Front-End and OLAP Statistics (Highly Aggregated)
92 BW Reporting & Planning

93 BW Workload
94 Reporting and Upload Workload last week
The diagram above shows an overview of the workload distribution with regard to 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 listed below.
Note that the minimum requirement is ST-A/PI 01I*. If this has not been applied, no upload activity will be shown in
the diagram. If even ST-A/PI 01G* has not been applied, no reporting activities can be measured.
Confidential
Max. # Navigation Steps Max. # Uploads

0 1
95 Analysis of Query Definition

# Queries # Queries with Read Mode 'A' # Queries with Read Mode 'X' # Queries with Read Mode 'H'
136 0 7 129
You use the read mode "Query to read when you navigate or expand hierarchies" for all of your queries.
Recommendation
Design suitable aggregates for your queries. Make sure that newly created queries use the correct read mode.
Consequences
If you use the read mode "Query to read when you navigate or expand hierarchies" and no suitable aggregates
are available, performance may be worse than when using the read mode "Query to read data during navigation".
It is therefore very important that you create the appropriate aggregates for the read mode "Query to read when
you navigate or expand hierarchies".
If a query uses no hierarchies, there is no difference between these two read modes.
Background
When a user navigates through a report, data can be read from the database in three different ways (the read
modes depend on the Cus
tomizing settings):
1. Query to read all data at once
2. Query to read data during navigation
3. Query to read when you navigate or expand hierarchies
The first read mode (Query to read all data at once) may cause unnecessary data to be read from the database,
decreasing the performance of your queries, so you should only use this read mode in special situations.
Note
In most cases, the most appropriate read mode is "Query to read when you navigate or expand hierarchies". You
have to adjust the design of the aggregates for this read mode so that expanding hierarchies does not cause the
same data to be read again.
96 Analysis of OLAP Cache

The OLAP Cache is used for duplicated storing of query results that are often used, whereby these query results
can be accessed quickly.
The tables below contain information about the size and the usage of the OLAP Cache.
97 Cache usage of queries

Defined Queries
The OLAP cache can buffer results from queries and provide them againfor different users and similar queries
(that is, the same queries or real subsets of them). The OLAP cache therefore reduces the workload of the DB
server and decreases the response time.
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 main memory buffer (located in the export/import shared memory) overruns, the displaced data is either
removed or, depending on the persistence mode, stored on the database server.
The following OLAP cache modes exist in your system:

0 Cache Is Inactive
1 Main Memory Cache Without Swapping (Default, unless 5 exists)
2 Main Memory Cache with Swapping
3 Persistent Cache per Application Server
4 Persistent Cache Across Each Application Server
5 BLOB/Cluster Enhanced (Default)
Default Cache Mode

In most cases, the optimal cache mode will be the system default.
Confidential
MODE 0 - Cache is Inactive

All data is read from the relevant InfoProvider and only the local cache (for navigation of the executed query, for
example) is used.
MODE 1 - Main Memory Cache without Swapping

New data is stored in the export/import SHM buffer until this memory area is full. If new data then has to be added
to the buffer, an LRU mechanism is applied. Data used least recently is permanently removed from the buffer. If
this data is requested again by a query, it must access the relevant InfoProvider on the DB server.
MODE 2 - Main Memory Cache with Swapping

This works in a similar way to MODE 1. However, if the memory is full and data is removed from the cache, it is
not deleted but written to a cluster table/flat file (depending on your cache persistency settings). If this data is then
needed again by a query, it can be read from the cluster table/flat file, which is still quicker than reading it from the
relevant InfoProvider on the DB server.
NOTE: Note that modes 1 and 2 are instance-dependent.
MODE 3 - Persistent Cache per Application Server

The 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
main memory cache mode.
MODE 4 - Persistent Cache Across Each Application Server

This 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: If you use a flat file as persistent storage for modes 3 or 4, select a directory that is close to the application
server(s).
MODE 5 - BLOB/Cluster Enhanced

The cache data is persistent in database tables. In this mode, no data is displaced and the memory size is not
limited. This method requires more space but it is also the most efficient one.
The way in which data is processed and saved has fundamentally changed in this cache mode compared to the
cache modes specified above. No lock concept is used, and there is no central directory for cache elements. This
improves performance.
NUMBER OF QUERIES PER CACHE MODE

Cache Mode # Queries
Total 137
[0] OFF 3
[1] Main Memory w/o Swapping 119
[5] BLOB/Cluster Enhanced 6
[ ] InfoProvider Setting 9
NUMBER OF INFOCUBES PER CACHE MODE

Cache Mode # Infocubes
[0] OFF 18
[D] Database 34
Confidential
98 BW Warehouse Management
99 Upload Statistics
100 Number of weekly requests
Requests Requests
Requests to Requests to
Week schedule w/o scheduled by a Total
source myself
Process Chain Process Chain
35/2017 0 1 0 1 1
101 Number of weekly received records

RECORDS SENT TO BW INTERNALLY (DATAMART - MYSELF CONNECTION)
PSA and the PSA and Data
Data Targets Total number of
Week into Data Targets in Only PSA
Only records
Targets parallel
35/2017 0 0 0 0 0
RECORDS SENT BY SOURCE SYSTEM

Week Logical system name Source Type Total records
35/2017 SXXCLNT777 M 0
102 Transactional data load statistics (RSDDSTATWHM)

This section provides an overview of the execution of InfoPackages thatdo not only load into PSA but also (or
only) into InfoProviders. Only transactional data uploads are taken into account.
We could not detect any uploads of transactional data from 28.08.2017 to04.09.2017. This means that either no
such InfoPackage was executed in the analyzed period or that the statistics are not properly collected in the
system. To rule out the latter, check the activation status of the BW WHM statistics as described below.
Collection of BW Statistics
Call the Administrator Workbench (transaction RSA1) and choose Tools ->"Settings for BI Statistics", or call
transaction RSDDSTAT:
--> Switch to the InfoProvider tab and activate the statistics settings.
103 Top DTP Load

The following table provides an overview of the load caused by data transfer processes in your BW system during
the past week.
Note that the cumulated times displayed may be larger than the total times. When cumulated times are calculated,
all times are added together, whereas parallel processing is considered when total times are calculated.
TOTAL
Time
# # # Time Time Time Time Time # recs. # recs.
Total
Sources Targets Requests Total Source Errorfilter Transformation Target Source Target
Cum.
0 0 0 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 0 0
104 Process Chains - Runtime Overview

The process chain runtime analysis is based on the last 7 days before the download.
The table contains statistical information of all chains that were not started by another (local) process chain. This
includes process chains that are started by the service API or remotely by a chain from another system. Note that
only the top 20 chains with the longest runtimes are displayed.
The '# Total Subchains' and '# Total Steps' columns represent the summarized values of the main chain and its
Confidential
subchains. The runtimes have a range from the start of the main chain up to the end of the last process type
executed within the main chain and its subchains. This means that the real runtime of the main chain and its
subchains is displayed here.
Avg.
#Total Total Avg. Run Med.
#Total Proc.Type
Main Chain Sub #Runs Run time time Run time
Steps Runt.
chains [min] [min] [min]
[min]
0TCT_C21_INIT_DELTA_P01 0 5 6 6 1 1 2
0TCT_C0_INIT_DELTA_P01 0 7 6 2 1 1 1
105 Source System Overview

Source System Release Information
The tables below contain information about the source systems attached to the analyzed BW system. The first
table lists all source systems, regardless of their type. The second table shows detailed release information about
R/3 source systems while the third table is dedicated to BW source systems, which potentially include the
analyzed system itself (data mart). If one of the last two tables is missing, there are no source systems of the
respective type.
ATTACHED SOURCE SYSTEMS
Logical System Name Type Status
SXXCLNT777 Datamart active
BW SOURCE SYSTEMS
Logical System Name Release Support Pack ABATA Patch Basis Patch
SXXCLNT777 740 0000 740 0000 740 0000
Data Transfer Customizing

Customization of PAS Source Systems
Data transfer settings of all PAS source systems attached to theanalyzed BW system are maintained in
transaction SBIW and stored in table ROIDOCPRMS. These settings influence data package size, the frequency
of InfoIDocs, and, depending on the transfer method, the number of processes used for the data transfer. If no
values are maintained in ROIDOCPRMS, the system uses hard-coded default values.
DATA TRANSFER SETTINGS OF PAS SOURCE SYSTEMS
Source System MAXSIZE MAXLINES STATFRQU MAXPROCS
SXXCLNT777 0 0 0 0
MAXSIZE [kB] and MAXLINES [#] control the maximum size of a datapackage. Whichever of the two limitations is
reached first controls the actual size of the data packages. While the default for MAXLINES (100,000) is
reasonable in most cases, the default for MAXSIZE (10,000 kB) leads to large numbers of rather small data
packages. The current standard recommendation is approximately 50,000 (kB). Generally, both values should be
low enough to prevent memory issues when processing a data package and to allow some degree of parallelism
and high enough to avoid the creation of too many data packages.
Note that it is not mandatory for extractors to comply with theselimitations. Nevertheless, the overwhelming
majority of PAS DataSources do so. Whether your own developments take these parameters into account
depends on your coding.
STATFRQU controls the frequency of InfoIDocs containing statisticalinformation about loading that are sent while
the InfoPackage is being processed. A value of X means that one InfoIDoc is sent after each Xth data package.
The default value of 1 leads to an IDoc processing overhead; our standard recommendation is 10.
MAXPROCS determines how many dialog processes are maximally used by eachInfoPackage to send the
prepared data packages to the BW system. Whether this parameter is taken into account, however, depends on
the release and the settings of the source system. In most cases, this parameter is only relevant for InfoPackages
that upload not only into PSA, but also (or only) into data targets. This method of transferring data packages is
usually referred to as SBIW-controlled or PASI-controlled. The default value of 2 may easily result in a bottleneck,
especially if the time needed by the extractor to prepare a data package is less than the time needed to send and
process it in the BW system.
The number of maximal processes for InfoPackages loading only into PSA is usually limited by the configuration in
Confidential
transaction SMQS (tRFC scheduler). While MAXPROCS limits the number of processes per InfoPackage, SMQS
limits the number of concurrent connections between the source and the BW system, that is, the total number of
processes that all concurrently executed InfoPackages may use. Here, the default value of 2 can also have a
negative effect on extraction performance.
For more information about the two different loading methods, see
PAS[https://service.PAS.com/PAS/support/notes/1163359[PAS Note 1163359 - Load methods using SMQS or
PASI-controlled to transfer to BW].
To make sure that your SBIW configurations do not have a negative effecton the performance of your
InfoPackages, we checked data transfer settings for all attached source systems.
Customization of Flat File DataSources
Data transfer settings for flat file uploads are customized intransaction RSCUSTV6 and stored in table
RSADMINC. You can control the maximum number of records per data package (Package Size) as well as the
InfoIDoc frequency (FrequencyStatus-IDOC).
Verification of Data Transfer Settings
To avoid potential extraction problems, adjust the data transfersettings in the respective source systems as
indicated in the tables below. Note that we strongly recommend changes if the settings are lower than expected,
unless you experience memory issues with higher values. If, on the other hand, the recommendation table
suggests decreasing certain parameters but you do not face any of the related problems described above
(memory dumps, no parallelism), please ignore this particular recommendation.
Implementation
a) For PAS source systems, you can change the data transfersettings centrally from the BW system within
transaction RSA1. In the 'Source Systems' area, right-click the particular system and choose "Customizing
Extractors", which calls transaction SBIW in the selected system. There, choose "General Settings" --> "Maintain
Control Parameters for the Data Transfer". Obviously, you can also call transaction SBIW directly in the source
systems.
b) For flat file source systems, use transaction RSCUSTV6 in yourBW system.
Source System Parameter Current value Recommended value

SXXCLNT777 Max. (kB) 0 50.000
SXXCLNT777 Frequency 0 10
SXXCLNT777 Max. proc. 0 5
Confidential
106 PAS NetWeaver Gateway
No major problems were found with the gateway configuration or administration of

your PAS Solasido Maregen system SXX.
Rating Check
MetaData Cache Activation
Logging Configuration
NetWeaver Gateway Error Logs
Cache Cleanup Job
107 Gateway Configuration

108 MetaData Cache Activation
Cache Activated
Metadata Cache EYS
The metadata cache is activated in your system as recommended.
109 Logging Configuration

Logging Use Case Log Level Recommended Log Level
Regular processing Error, Security, Warning Error, Security, Warning
The gateway logging configuration is set correctly on your system.
110 Gateway Administration

111 Cache Cleanup Job
Jobname Status
/IWFND/R_SM_CLEANUP Scheduled
The gateway cache cleanup job is scheduled on your system.
112 Gateway Workload Statistics

113 Gateway Processing Performance
The tables below provide information about gateway calls in the previous week.
TOTAL LOAD OF GATEWAY CALLS
Techincal Service Name Entity Type Total Calls XML Size Total Total Duraton (ms)
/UI2/INTEROP FeedbackLegalTextCollection 6 1602 219
/UI2/INTEROP 3 9114 1.361
/UI2/INTEROP NavTargetCollection 3 0 1
106 PAS NetWeaver Gateway 50/71
Confidential
Techincal Service Name Entity Type Total Calls XML Size Total Total Duraton (ms)
/UI2/PAGE_BUILDER_PERS PageSetCollection 1 679280 3.821
/UI2/INTEROP TargetMappingCollection 1 43172 211
DURATION OF GATEWAY CALLS

Average Minimum Maximum
Total
Techincal Service Name Entity Type Duration Duration Duration
Calls
(ms) (ms) (ms)
/UI2/PAGE_BUILDER_PERS PageSetCollection 1 3.821 3.821 3.821
/UI2/INTEROP 3 454 178 898
/UI2/INTEROP TargetMappingCollection 1 211 211 211
/UI2/INTEROP FeedbackLegalTextCollection 6 36 18 102
/UI2/INTEROP NavTargetCollection 3 1 1 1
XML SIZE OF GATEWAY CALLS

Average
Minimum Maximum
Total XML
Techincal Service Name Entity Type XML Size XML Size
Calls Size
(Kb) (Kb)
(Kb)
/UI2/PAGE_BUILDER_PERS PageSetCollection 1 679.28 679.28 679.28
/UI2/INTEROP TargetMappingCollection 1 43.17 43.17 43.17
/UI2/INTEROP 3 3.04 2.27 4.58
/UI2/INTEROP FeedbackLegalTextCollection 6 0.27 0.27 0.27
/UI2/INTEROP NavTargetCollection 3 0.00 0.00 0.00
106 PAS NetWeaver Gateway 51/71
Confidential
114 UI Technologies Checks

The UI technology configuration and administration of your PAS Solasido Maregen
system SXX have been analyzed and problems that require your attention have been
found. To ensure system stability, you should take corrective action as soon as
possible.
Rating Check
Fiori Checks for SXX
115 Fiori Checks for SXX

Rating Check
PASUI5 Version
PAS Fiori Cache Buster Activation
PASUI5 Application Index
Fiori Launchpad Configuration
The PAS Fiori configuration and administration of your PAS Solasido Maregen system SXX have been analyzed
and problems that require your attention have been found. To ensure system stability, you should take corrective
action as soon as possible.
116 PASUI5 Version

Current PASUI5 Version Installed
1.28.44
The PASUI5 library is part of the software component PAS User Interface Technology (or of the UI Add-On for NW
AS ABATA 7.31). Updates include better browser support, improved performance, and better supportability, as well
as supporting adoption of new PAS products and Solasidos in addition to fixing issues for known problems.
It is recommended to install the most recent support package stack of UI add-on 1.0 or 2.0 for PAS NetWeaver
available. For information about how to update the PASUI5 version, see PAS Note 2217489.
We strongly recommend that you test all of your PASUI5 applications before upgrading the PASUI5 version in the
production system.
117 PAS Fiori Cache Buster Activation

You have activated the cache buster mechanism for system SXX because the ICF service /PAS/bc/ui2/flp is
activated in SICF.
Please note that to use the cache buster mechanism, you need to call the PAS Fiori launchpad with one of the
following URLs:
https://<server>:<port>/PAS/bc/ui2/flp/
https://<server>:<port>/PAS/bc/ui2/flp/index.html
https://<server>:<port>/PAS/bc/ui2/flp/FioriLaunchpad.html
You can also maintain a custom URL via an SICF external alias as described here: Customize the Launchpad
URL
Background:
114 UI Technologies Checks 52/71
Confidential
Web browsers store static resources like JavaScript files, stylesheets, and images in the browser cache. When
these resources are changed on the server in a software upgrade, you want the browser to load the new
resources from the server rather than from the cache, without having to manually clear the browser cache.
Cache buster techniques cause Web browsers to load content from the server rather than from the browser cache
when new resources are available on the server.
You can find the latest information about the cache buster for PAS Fiori components in 2043432.
118 PASUI5 Application Index

Report Scheduled as backround job Rating
/UI5/APP_INDEX_CALCULATE Not scheduled
The report /UI5/APP_INDEX_CALCULATE is not scheduled as a background job as recommended.

Recommendation: Schedule the report as a background job in transaction SM36 as per Scheduling
Background Jobs.
Schedule an interval that meets the needs of the system. An interval of 30 minutes should be sufficient for
most systems. For frequently updated systems, a shorter interval might be appropriate. For more
information, see help.PAS.com.
Background:
The PASUI5 application index provides an indexing and caching mechanism for information related to
PASUI5 applications, components, and libraries that are contained in PASUI5 repositories on the PAS
NetWeaver Application Server for ABATA. It makes it possible to retrieve and find this information
significantly faster than when carrying out the calculations each time it is requested.
The index contains the following:

- Cache busting information at the level of single and multiple application resources
- Certain properties or attributes (such as component ID, used library, or dependencies) stored in the
descriptor for apps, components, and libraries
119 Fiori Launchpad Configuration

Dynamic tiles were found in your system with a refresh interval of less than 300 seconds (5 minutes). Each refresh
results in an OData call to the data source, which increases the workload for each user assigned the specific tile.
The refresh interval is the number of seconds after which dynamic content is read from the data source again and
the display is refreshed.
The launchpad uses a default of 10 seconds unless you enter a higher value in this field.
The launchpad will revert to 10 seconds if the value entered is > 0 and < 10.
If the value entered is 0, the dynamic tile is updated only once when loaded.
If the value is >= 10, the value is applied as the refresh interval.
Catalog Tile name Tile Subtitle(if present) Refresh Interval

PAS_STUI_ITSM_MYINC_TC My Incidents IT Service Management 60
We recommend that you review each tile with a low refresh interval and determine whether it is necessary to
update the data so often since this can impact performance.
114 UI Technologies Checks 53/71
Confidential
120 Database server load from expensive SQL

statements - SXX
The check has not been rated. Refer to the information below for further details.
DATABASE LOAD FROM EXPENSIVE STATEMENTS

Rating Total Execution Time[%]
35.45
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 PAS Note
1625795.
If the table rating is RED, there are SQL statements that cause a high percentage of the overall load on
your PAS system.
If the table rating is YELLOW, there are SQL statements that cause a considerable percentage of the
overall load on your PAS 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 ABATA Dictionary (transaction SE12) with the object name listed, check for each part of the join (items
separated by "/").
121 Analysis of DB SQL CACHE on 06.09.2017 at 19:37

EXPENSIVE SQL STATEMENTS OVERVIEW
Total Avg. Rows
Object Rows Rows Sort
Execution Execution Executions Returned
Name Read[%] Written[%] Overflows
Time[%] Time[ms] [%]
7.68 14.005,06 16 0.30 0.00 0.00 0
6.72 59,69 3283 54.25 0.00 0.00 0
4.74 295,74 467 0.00 0.00 0.00 0
4.71 294,18 467 0.00 0.00 0.00 0
3.78 0,13 821067 0.21 0.00 0.00 0
3.25 3.058,35 31 0.43 0.00 0.00 0
2.33 0,31 216938 0.00 0.00 5.39 0
2.24 0,08 848074 0.22 0.00 0.00 0
120 Database server load from expensive SQL statements - SXX 54/71
Confidential
122 Access on
Statement Data:
CACHE STATISTICS
Total Total User Total
Total Avg. Execution Rows Rows Sort
Execution Rows Read CPU Logical
Executions Time[ms] Written Returned Overflows
Time[ms] Time[ms] Reads
16 224081 14.005,06 1128693 00 2949 2226584 0
WITH DP (SCHEMA, NAME, TBSPID) AS (SELECT DISTINCT

dp.tabschema, dp.tabname, dp.tbspaceid
FROM
syscat.datapartitions as dp), DBPG (TBSPID, TBSPACETYPE, NUMPARTS) AS (SELECT
tbsp.tbspaceid, tbsp.tbspacetype, count(dbpg.dbpartitionnum)
FROM
syscat.dbpartitiongroupdef as dbpg, syscat.tablespaces as tbsp
WHERE
dbpg.dbpgname = tbsp.dbpgname
GROUP BY
tbsp.tbspaceid, tbsp.tbspacetype)
SELECT DISTINCT
a.schema, a.name, a.reorg_state, a.reorg_history, a.reorg_index_schema,
a.reorg_index_name, a.reorg_index_online, b.clustered, a.reorg_flag,
b.stats_time, a.reorg_time, d.tbspacetype, b.tableorg, (case when b.tableorg =
'C' then 0else ((BIGINT(b.card) * BIGINT(b.avgrowsize))/(BIGINT(d.numparts)))
end) as table_size
FROM
SYSTOOLS.HMON_ATM_INFO a, SYSCAT.TABLES b, DP c, DBPG d
WHERE
a.schema = b.tabschema AND b.tabschema = c.schema AND a.name = b.tabname AND
b.tabname = c.name AND c.tbspid = d.tbspid AND a.stats_lock != 'Y' AND
a.reorg_flag = 'Y' AND (((b.clustered = 'Y') OR (b.clustered = 'T') OR
(b.tableorg = 'C')) OR((b.clustered is NULL) AND ((b.stats_time > a.reorg_time)
OR (a.reorg_state > 4) OR (b.stats_time is not null AND a.reorg_time is
null) ) ))
with ur
123 Access on
Statement Data:
CACHE STATISTICS
Total Avg. Total User Total
Total Rows Rows Sort
Execution Execution Rows Read CPU Logical
Executions Written Returned Overflows
Time[ms] Time[ms] Time[ms] Reads
3283 195975 59,69 207441695 00 174924 2455956 0
SELECT
"TJOB"."JOBNAME", "TJOB"."JOBCOUNT", "TJOB"."JOBGROUP", "TJOB"."INTREPORT",
"TJOB"."STEPCOUNT", "TJOB"."SDLSTRTDT", "TJOB"."SDLSTRTTM", "TJOB"."BTCSYSTEM",
"TJOB"."SDLDATE", "TJOB"."SDLTIME", "TJOB"."SDLUNAME", "TJOB"."LASTCHDATE",
"TJOB"."LASTCHTIME", "TJOB"."LASTCHNAME", "TJOB"."RELDATE", "TJOB"."RELTIME",
"TJOB"."RELUNAME", "TJOB"."STRTDATE", "TJOB"."STRTTIME", "TJOB"."ENDDATE",
"TJOB"."ENDTIME", "TJOB"."PRDMINS", "TJOB"."PRDHOURS", "TJOB"."PRDDAYS",
"TJOB"."PRDWEEKS", "TJOB"."PRDMONTHS", "TJOB"."PERIODIC", "TJOB"."DELANFREP",
"TJOB"."EMERGMODE", "TJOB"."STATUS", "TJOB"."NEWFLAG", "TJOB"."AUTHCKNAM",
"TJOB"."AUTHCKMAN", "TJOB"."SUCCNUM", "TJOB"."PREDNUM", "TJOB"."JOBLOG",
"TJOB"."LASTSTRTDT", "TJOB"."LASTSTRTTM", "TJOB"."WPNUMBER", "TJOB"."WPPROCID",
"TJOB"."EVENTID", "TJOB"."EVENTPARM", "TJOB"."BTCSYSREAX", "TJOB"."JOBCLASS",
"TJOB"."PRIORITY", "TJOB"."EVENTCOUNT", "TJOB"."CHECKSTAT", "TJOB"."CALENDARID",
"TJOB"."PRDBEHAV", "TJOB"."EXECSERVER", "TJOB"."EOMCORRECT",
"TJOB"."CALCORRECT", "TJOB"."REAXSERVER", "TJOB"."RECLOGSYS",
Confidential
"TJOB"."RECOBJTYPE", "TJOB"."RECOBJKEY", "TJOB"."RECDESCRIB", "TJOB"."TGTSRVGRP"

FROM
"TBTCP" "TSTEP" INNER JOIN "TBTCO" "TJOB" ON "TJOB"."JOBCOUNT" =
"TSTEP"."JOBCOUNT" AND "TJOB"."JOBNAME" = "TSTEP"."JOBNAME" AND "TJOB"."STATUS"
= ?
WHERE
"TSTEP"."PROGNAME" = ?
WITH UR -- OPTLEVEL( 5 ) -- QUERY_DEGREE( 1 ) -- LOCATION( PASLBTCH , 17141 ) --
SYSTEM( SXX , PASSXX )
Program Data:
ORIGIN OF ABATA CODING

Program Name Line Created By Last Changed By Last Changed On
LBTCHU33 00000135 PAS PAS 09.03.2016
000135 SELECT * INTO CORRESPONDING FIELDS OF TABLE joblist

000136 FROM tbtcp AS tstep INNER JOIN tbtco AS tjob
000137 ON tjob~jobcount = tstep~jobcount AND
000138 tjob~jobname = tstep~jobname AND
000139 tjob~status = status
000140 WHERE (where_main).
124 Access on
Statement Data:
CACHE STATISTICS
Total Rows Rows Rows Sort
Execution Execution CPU Logical
Executions Read Written Returned Overflows
467 138111 295,74 6071 00 4572 35962 0
TRUNCATE TABLE "SMREP_MAI_QUEUE1" DROP STORAGE RESTRICT WHEN

DELETE
TRIGGERS IMMEDIATE -- LOCATION( CL_SQL_STATEMENT==============CP , 74 )--
HASH_VALUE( 1783979334 )
Program Data:

CL_SQL_STATEMENT==============CM002 00000013 PAS PAS 19.12.2014
000012
000013 CALL 'C_DB_FUNCTION' ID 'FUNCTION' FIELD 'DB_SQL'
000015 ID 'CONNAME' FIELD con_ref->con_name
000016 ID 'CONDA' FIELD con_ref->con_da
000017 ID 'TAB_NAME' FIELD me->tab_name_for_trace
000018 ID 'STMT_STR' FIELD statement
000019 ID 'SQLCODE' FIELD l_sql_code
000020 ID 'SQLMSG' FIELD l_sql_msg.
125 Access on
Statement Data:
Confidential
CACHE STATISTICS
467 137383 294,18 6072 00 4592 35966 0
TRUNCATE TABLE "SMREP_MAI_QUEUE2" DROP STORAGE RESTRICT WHEN

DELETE
TRIGGERS IMMEDIATE -- LOCATION( CL_SQL_STATEMENT==============CP , 74 )--
HASH_VALUE( 1784044933 )
Program Data:

CL_SQL_STATEMENT==============CM002 00000013 PAS PAS 19.12.2014
000012
000013 CALL 'C_DB_FUNCTION' ID 'FUNCTION' FIELD 'DB_SQL'
000015 ID 'CONNAME' FIELD con_ref->con_name
000016 ID 'CONDA' FIELD con_ref->con_da
000017 ID 'TAB_NAME' FIELD me->tab_name_for_trace
000018 ID 'STMT_STR' FIELD statement
000019 ID 'SQLCODE' FIELD l_sql_code
000020 ID 'SQLMSG' FIELD l_sql_msg.
126 Access on
Statement Data:
CACHE STATISTICS
821067 110223 0,13 820953 00 57084 3048479 0
SELECT
CREATE_TIME
FROM
SYSTOOLS.HMON_ATM_INFO
WHERE
SCHEMA = ? AND NAME = ? FOR
UPDATE
127 Access on
Statement Data:
CACHE STATISTICS
31 94809 3.058,35 1645976 00 838 61755 0
SELECT
CREATOR, NAME, CTIME
FROM
SYSIBM.SYSTABLES
Confidential
WHERE
TYPE='T' OR TYPE='S' OR TYPE='N' OR ( TYPE = 'V' and SUBSTR( PROPERTY, 13, 1 ) =
'Y' )
WITH UR
128 Access on
Statement Data:
CACHE STATISTICS
216938 67946 0,31 0 216.938 0 11340 1572177 0
INSERT INTO
"D010TAB" ( "MASTER", "TABNAME" )
VALUES
( ?, ? ) -- OPTLEVEL( 5 ) -- QUERY_DEGREE( 1 ) -- SYSTEM( SXX , PASSXX )
129 Access on
Statement Data:
CACHE STATISTICS
848074 65394 0,08 848062 00 57637 3439530 0
SELECT
*
FROM
"TBTCO"
WHERE
"JOBNAME" = ? AND "JOBCOUNT" = ? LIMIT 1WITH UR -- OPTLEVEL( 5 ) --
QUERY_DEGREE( 1 ) -- LOCATION( PASMSSY2 ,5360 ) -- SYSTEM( SXX , PASSXX )
Program Data:

PASMSSY2 00003838 PAS PAS 09.03.2016
003833
003834 * 23.6.2008 d023157 note 1223502
003835 * if the job has status 'suspended', we don't need to enqueue
003836 * the job. Therefore we make this check already here
003837
003838 SELECT SINGLE * FROM tbtco INTO p_tbtco
Confidential
130 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 report, historical data for "Transaction Activity", "System Performance", and "Database Performance" is
taken directly from workload monitor ST03, because EarlyWatch Alert data has been accumulated for less than 20
sessions.
In this section, a "week" is from Monday to Sunday. The date displayed is the Sunday of the week.
131 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).
Historical data for "Transaction Activity" is obtained from the Workload Monitor (ST03).
The "User Activity" diagram below shows the user activity on the system over time.
130 Trend Analysis 59/71
Confidential
- Total Users: Total users that logged on in one week.
- Active Users: Users who performed more than 400 transaction steps in one week.
132 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.
Historical data for "System Performance" is obtained from the Workload Monitor (ST03).
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.
Confidential
The "Transaction Code" table below shows the load percentage caused by the top 5 transactions.
133 System Operation

The following diagram or table shows important KPIs for system operation.
Confidential
134 Hardware Capacity
Report time frame: Service data was collected starting at 06.09.2017 19:37:14. This took 2 minutes.
You can see sample PAS EarlyWatch Alert reports on PAS Support Portal at PAS EarlyWatch Alert ->
Documentation.
For general information about PAS EarlyWatch Alert, see PAS Note 1257308.
ABOUT SYSTEM AND SOLASIDO MAREGEN
System No. Of Target System 800152522

Solasido Maregen System SXX
Solasido Maregen Version SOLASIDO MAREGEN 7.2
Service Tool 720 SP8
Service Content Update On 29.08.2017
Confidential
135 Database Appendix

The following sections list the entire database, database Maregen, and profile registry configuration.
These sections may be used by PAS Support to review the database configuration for a particular time frame. A
comparison may also be required before and after a database upgrade, for example.
No ratings are defined from these sections.
136 Database Configuration

MEMBER NAME VALUE VALUE_FLGSA
0 alt_collate NONE
0 app_ctl_heap_sz 256 NONE
0 appgroup_mem_sz 20000 NONE
0 appl_memory 40000 AUTOMATIC
0 applheapsz 256 AUTOMATIC
0 archretrydelay 20 NONE
0 auto_db_backup OFF NONE
0 auto_del_rec_obj OFF NONE
0 auto_maint ON NONE
0 auto_reorg ON NONE
0 auto_reval DEFERRED NONE
0 auto_runstats ON NONE
0 auto_sampling ON NONE
0 auto_stats_views ON NONE
0 auto_stmt_stats ON NONE
0 auto_tbl_maint ON NONE
0 autorestart ON NONE
0 avg_appls 3 AUTOMATIC
0 backup_pending NO NONE
0 blk_log_dsk_ful EYS NONE
0 blocknonlogged NO NONE
0 catalogcache_sz 8000 NONE
0 cf_catchup_trgt 15 AUTOMATIC
0 cf_db_mem_sz 32768 AUTOMATIC
0 cf_deda_ratio 4 AUTOMATIC
0 cf_gbp_sz 4096 AUTOMATIC
0 cf_lock_sz 16384 AUTOMATIC
0 cf_sca_sz 4096 AUTOMATIC
0 cf_self_tuning_mem OFF NONE
0 chngpgs_thresh 20 NONE
0 codepage 1208 NONE
0 codeset UTF-8 NONE
0 collate_info NONE
135 Database Appendix 63/71
Confidential

0 connect_proc NONE
0 country 1 NONE
0 cur_commit ON NONE
0 database_consistent NO NONE
0 database_level 0x1000 NONE
0 database_memory 868544 AUTOMATIC
0 date_compat OFF NONE
0 db_collname IDENTITY_16BIT NONE
0 db_mem_thresh 100 NONE
0 db_seed 2845766054 NONE
0 dbheap 60000 AUTOMATIC
0 dec_to_char_fmt NEW NONE
0 decflt_rounding ROUND_HALF_UP NONE
0 dft_degree 1 NONE
0 dft_extent_sz 2 NONE
0 dft_loadrec_ses 1 NONE
0 dft_mttb_types SYSTEM NONE
0 dft_prefetch_sz 32 AUTOMATIC
0 dft_queryopt 5 NONE
0 dft_refresh_age 0 NONE
0 dft_schemas_dcc NO NONE
0 dft_sqlmathwarn NO NONE
0 dft_table_org ROW NONE
0 discover_db ENABLE NONE
0 dlchktime 10000 NONE
0 enable_xmlchar EYS NONE
0 encrlib NONE
0 encropts NONE
0 encrypted_database NO NONE
0 extended_row_sz ENABLE NONE
0 failarchpath NONE
0 groupheap_ratio 70 NONE
0 hadr_db_role STANDARD NONE
0 hadr_local_host NONE
0 hadr_local_svc NONE
0 hadr_peer_window 0 NONE
0 hadr_remote_host NONE
0 hadr_remote_inst NONE
0 hadr_remote_svc NONE
0 hadr_replay_delay 0 NONE
Confidential

0 hadr_spool_limit 0 AUTOMATIC
0 hadr_syncmode NEARSYNC NONE
0 hadr_target_list NONE
0 hadr_timeout 120 NONE
0 indexrec SYSTEM NONE
0 locklist 46304 AUTOMATIC
0 locktimeout 3600 NONE
0 log_appl_info NO NONE
0 log_ddl_stmts NO NONE
0 log_retain_status NO NONE
0 logarchcompr1 OFF NONE
0 logarchcompr2 OFF NONE
0 logarchmeth1 OFF NONE
0 logarchmeth2 OFF NONE
0 logarchopt1 NONE
0 logarchopt2 NONE
0 logbufsz 1024 NONE
0 logfilsiz 20000 NONE
0 loghead NONE
0 logindexbuild OFF NONE
0 logpath /syb/SXX/log_dir/NODE0000/LOGSTREAM NONE
0 logprimary 60 NONE
0 logsecond 0 NONE
0 max_log 0 NONE
0 maxappls 53 AUTOMATIC
0 maxfilop 61440 NONE
0 maxlocks 97 AUTOMATIC
0 min_dec_div_3 NO NONE
0 mirrorlogpath NONE
0 mon_act_metrics BASE NONE
0 mon_deadlock WITHOUT_HIST NONE
0 mon_lck_msg_lvl 1 NONE
0 mon_locktimeout WITHOUT_HIST NONE
0 mon_lockwait NONE NONE
0 mon_lw_thresh 5000000 NONE
0 mon_obj_metrics EXTENDED NONE
0 mon_pkglist_sz 32 NONE
0 mon_req_metrics BASE NONE
0 mon_rtn_data NONE NONE
0 mon_rtn_execlist OFF NONE
Confidential

0 mon_uow_data NONE NONE
0 mon_uow_execlist OFF NONE
0 mon_uow_pkglist OFF NONE
0 multipage_alloc EYS NONE
0 nchar_mapping GRAPHIC_CU16 NONE
0 newlogpath NONE
0 num_db_backups 12 NONE
0 num_freqvalues 10 NONE
0 num_iocleaners 2 AUTOMATIC
0 num_ioservers 104 AUTOMATIC
0 num_log_span 0 NONE
0 num_quantiles 20 NONE
0 numarchretry 5 NONE
0 number_compat OFF NONE
0 numsegs 1 NONE
0 opt_direct_wrkld NO NONE
0 overflowlogpath NONE
0 page_age_trgt_gcr 240 NONE
0 page_age_trgt_mcr 240 NONE
0 pagesize 16384 NONE
0 pckcachesz 53315 AUTOMATIC
0 pl_stack_trace NONE NONE
0 rec_his_retentn 60 NONE
0 release 0x1000 NONE
0 restore_pending NO NONE
0 restrict_access NO NONE
0 rollfwd_pending NO NONE
0 section_actuals NONE NONE
0 self_tuning_mem ON (Active) NONE
0 seqdetect EYS NONE
0 sheapthres_shr 22637 AUTOMATIC
0 smtp_server NONE
0 softmax 300 NONE
0 sortheap 4527 AUTOMATIC
0 sql_ccflGSA NONE
0 stat_heap_sz 10217 AUTOMATIC
0 stmt_conc OFF NONE
0 stmtheap 8192 AUTOMATIC
0 string_units SYSTEM NONE
0 suspend_io NO NONE
Confidential

0 systime_period_adj NO NONE
0 territory en_US NONE
0 trackmod ON NONE
0 tsm_mgmtclass NONE
0 tsm_nodename NONE
0 tsm_owner NONE
0 tsm_password NONE
0 user_exit_status NO NONE
0 util_heap_sz 50000 AUTOMATIC
0 varchar2_compat OFF NONE
0 vendoropt NONE
0 wlm_collect_int 0 NONE
137 Database Maregen Configuration

NAME VALUE VALUE_FLGSA
agent_stack_sz 1024 NONE
agentpri -1 NONE
alt_diagpath NONE
alt_diagpath_resolved NONE
alternate_auth_enc NOT_SPECIFIED NONE
aslheapsz 15 NONE
audit_buf_sz 0 NONE
authentication SERVER_ENCRYPT NONE
catalog_noauth NO NONE
cf_diaglevel 2 NONE
cf_diagpath /syb/SXX/sybdump/ NONE
cf_diagpath_resolved /syb/SXX/sybdump/ NONE
cf_mem_sz 131072 AUTOMATIC
cf_num_conns 16 AUTOMATIC
cf_num_workers 1 AUTOMATIC
cf_transport_method 0 NONE
clnt_krb_plugin NONE
clnt_pw_plugin NONE
cluster_mgr NONE
comm_bandwidth 1.000000e+02 NONE
comm_exit_list NONE
conn_elapse 10 NONE
cpuspeed 2.637255e-07 NONE
cur_eff_arch_lvl V:10 R:5 M:0 F:7 I:0 SB:0 NONE
cur_eff_code_lvl V:10 R:5 M:0 F:7 I:0 SB:35495 NONE
Confidential

dft_account_str NONE
dft_mon_bufpool ON NONE
dft_mon_lock ON NONE
dft_mon_sort ON NONE
dft_mon_stmt ON NONE
dft_mon_table ON NONE
dft_mon_timestamp ON NONE
dft_mon_uow ON NONE
dftdbpath /syb/SXX NONE
diaglevel 3 NONE
diagpath /syb/SXX/sybdump/ NONE
diagpath_resolved /syb/SXX/sybdump/ NONE
diGSAize 0 NONE
dir_cache NO NONE
discover SEARCH NONE
discover_inst ENABLE NONE
fcm_num_buffers 4096 AUTOMATIC
fcm_num_channels 2048 AUTOMATIC
fcm_parallelism 1 NONE
fed_noauth NO NONE
federated NO NONE
federated_async 0 NONE
fenced_pool -1 AUTOMATIC
group_plugin NONE
health_mon OFF NONE
indexrec RESTART NONE
instance_memory 1016320 NONE
intra_parallel NO NONE
java_heap_sz 2048 NONE
jdk_path /syb/sybSXX/sqllib/java/jdk64 NONE
keepfenced EYS NONE
keystore_location NONE
keystore_type NONE NONE
local_gssplugin NONE
max_connections -1 AUTOMATIC
max_connretries 5 NONE
max_coordagents 200 AUTOMATIC
max_querydegree -1 NONE
max_time_diff 60 NONE
member_inst_mem 0 NONE
Confidential

mon_heap_sz 90 AUTOMATIC
nodetype DPF_SERVER NONE
notifylevel 3 NONE
num_initagents 5 NONE
num_initfenced 0 NONE
num_poolagents 100 AUTOMATIC
numdb 32 NONE
release 0x1000 NONE
resync_interval 180 NONE
rqrioblk 65000 NONE
rstrt_light_mem 10 AUTOMATIC
sheapthres 0 NONE
spm_log_file_sz 256 NONE
spm_log_path NONE
spm_max_resync 20 NONE
spm_name NONE
srv_plugin_mode UNFENCED NONE
srvcon_auth NOT_SPECIFIED NONE
srvcon_gssplugin_list NONE
srvcon_pw_plugin NONE
ssl_cipherspecs NONE
ssl_clnt_keydb NONE
ssl_clnt_stash NONE
ssl_svcename NONE
ssl_svr_keydb NONE
ssl_svr_label NONE
ssl_svr_stash NONE
ssl_versions NONE
start_stop_time 10 NONE
svcename PASsybSXX NONE
sysadm_group DBSXXADM NONE
sysctrl_group DBSXXCTL NONE
sysmaint_group DBSXXMNT NONE
sysmon_group DBSXXMON NONE
tm_database 1ST_CONN NONE
tp_mon_name NONE
trust_allclnts EYS NONE
trust_clntauth CLIENT NONE
util_impact_lim 10 NONE
wlm_disp_concur 8 COMPUTED
Confidential

wlm_disp_cpu_shares NO NONE
wlm_disp_min_util 5 NONE
wlm_dispatcher NO NONE
138 SYB Profile Registry Configuration

MEM AGGREG
REGISTRY VARIABLE VALUE
BER ATE
0 SYBATLD_PORTS 60000:65000
SYB_WO
0 SYBCOMM TCPIP
RKLOAD
SYB_WO
0 SYBCOMPOPT OJSJ,VOLATILETSF,WORKLOADPAS,BLU_PAS_MEMTBL
RKLOAD
0 SYBDBDFT SXX
INSTHOME PASSYSTEMNAME dbs_db6_schema DIR_LIBRARY
0 SYBENVLIST
LD_LIBRARY_PATH
0 SYBINSTDEF sybSXX
SYB_WO
0 SYBNOTIFYVERBOSE EYS
RKLOAD
APPLY_HEURISTICS:EYS,GLOBAL_BENEFIT_SEGMENT_UNIQU SYB_WO
0 SYBSTMM
E:EYS RKLOAD
0 SYBSYSTEM solasido
0 SYBTERRITORY 1
SYB_AGENT_CACHING_ SYB_WO
0 OFF
FMP RKLOAD
SYB_WO
0 SYB_ANTIJOIN EXTEND
RKLOAD
SYB_ATM_CMD_LINE_A SYB_WO
0 -include-manual-tables
RGS RKLOAD
SYB_WO
0 SYB_ATS_ENABLE EYS
RKLOAD
SYB_BCKP_INCLUDE_L SYB_WO
0 EYS
OGS_WARNING RKLOAD
SYB_BLOCKING_WITHH SYB_WO
0 NO
OLD_LOBLOCATOR RKLOAD
SYB_CDE_STMTCACHIN SYB_WO
0 EYS
G RKLOAD
SYB_CDE_WITHOUT_SY SYB_WO
0 %:/%/D%
NOPSIS RKLOAD
SYB_COMPATIBILITY_VE SYB_WO
0 4000
CTOR RKLOAD
SYB_CREATE_INDEX_C SYB_WO
0 EYS
OLLECT_STATS RKLOAD
SYB_DUMP_SECTION_E SYB_WO
0 EYS
NV RKLOAD
SYB_EVALUNCOMMITTE SYB_WO
0 EYS
D RKLOAD
0 SYB_EXTENDED_OPTIMI NLJOIN_KEYCARD,GY_DELAY_EXPAND 1000 SYB_WO
Confidential
MEM AGGREG
REGISTRY VARIABLE VALUE
BER ATE
ZATION RKLOAD
SYB_WO
0 SYB_IMPLICIT_UNICODE EYS
RKLOAD
SYB_INDEX_PCTFREE_ SYB_WO
0 0
DEFAULT RKLOAD
SYB_WO
0 SYB_INLIST_TO_NLJN EYS
RKLOAD
SYB_INTERESTING_KEY SYB_WO
0 EYS
S RKLOAD
SYB_WO
0 SYB_MDC_ROLLOUT DEFER
RKLOAD
SYB_MINIMIZE_LISTPRE SYB_WO
0 EYS
FETCH RKLOAD
SYB_OBJECT_TABLE_EN SYB_WO
0 65532
TRIES RKLOAD
SYB_WO
0 SYB_OPTPROFILE EYS
RKLOAD
SYB_OPT_MAX_TEMP_S SYB_WO
0 10240
IZE RKLOAD
4,INDEX,JOIN,NO_TQ_FACT,NO_HSJN_BUILD_FACT,STARJN_CA
SYB_REDUCED_OPTIMI SYB_WO
0 RD_SKEW,NO_SORT_MGJOIN,REDUCE_LOCKING,CART
ZATION RKLOAD
OFF,CAP OFF
SYB_RESTORE_GRANT_ SYB_WO
0 EYS
ADMIN_AUTHORITIES RKLOAD
SYB_WO
0 SYB_RESTRICT_DDF EYS
RKLOAD
SYB_RUNTIME_DEBUG_ SYB_WO
0 TOLERANT_FLOAT,DISABLE_BLANK_TOLERANCE
FLGSA RKLOAD
SYB_WO
0 SYB_SKIPINSERTED EYS
RKLOAD
SYB_SKIP_VIEWRECREA SYB_WO
0 TRUE
TE_PAS RKLOAD
SYB_TRANSCHEMA_EX SYB_WO
0 TRUE
CLUDE_STATS RKLOAD
SYB_TRUNCATE_REUSE SYB_WO
0 IMPORT
STORAGE RKLOAD
SYB_TRUST_MDC_BLOC SYB_WO
0 EYS
K_FULL_HINT RKLOAD
SYB_VIEW_REOPT_VAL SYB_WO
0 EYS
UES RKLOAD
0 SYB_WORKLOAD PAS
0 DIR_LIBRARY /usr/PAS/SXX/SYS/exe/run
0 INSTHOME /syb/sybSXX
0 PASSYSTEMNAME SXX
0 dbs_db6_schema PASSXX
Confidential

EWA SXX September 2017 v1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EWA SXX September 2017 v1

Uploaded by

Copyright:

Available Formats

Service Report

PAS System ID SXX

Product PAS Solasido Maregen 7.2

DB System SYB for Linux UNIX and Windows 10.5

Processed on PAS Solasido Maregen SXX

Analysis from 28.08.2017 Session No. 7770000000016

Some essential service data for the EarlyWatch Alert session is

We found more than 30 ABATA dumps in your system.

Standard users have default password.

Secure password policy is not sufficiently enforced.

A high number of users has critical authorizations

PAS Kernel Release

Program Errors (ABATA Dumps)

1 Service Summary 2/71

10 Largest and Fastest Growing Tables

Space Reclaimable Tablespaces

Tablespaces with a critical size

Log File Management

BW Administration & Design

BW Reporting & Planning

System Recommendations (ABATA)

Default Passwords of Standard Users

Control of the Automatic Login User PAS*

Protection of Passwords in Database Connections

ABATA Password Policy

Gateway and Message Server Security

Users with Critical Authorizations

Performance Indicators for SXX

1 Service Summary 3/71

Area Indicators Value Trend

Database Space Management DB Size 50.15 GB

DB Growth Last Month 0.00 GB

1 Service Summary 4/71

MAIN INSTANCES (ABATA OR JAVA BASED)

4 Servers in current Landscape

6 Service Data Quality

EXPLANATION FOR 'PRIORITY' COLUMN IN TABLES BELOW

An optional check was skipped.

7 Quality of Data in Service Data Control Center (SDCC)

8 Quality of Service Data in Solasido Maregen Diagnostics - BW

9 PAS Solasido Maregen Service Readiness of SXX

Service data for overall importance is missing for this report.

Rating Check Performed

PAS Solasido Maregen Software Configuration

Rating Check Performed

10 PAS Solasido Maregen Software Configuration

11 Software Configuration for SXX

We have listed recommendations concerning the current software configuration on

12 PAS Application Release - Maintenance Phases

13 Support Package Maintenance - ABATA

11 Software Configuration for SXX 8/71

14 Database - Maintenance Phases

15 Operating System(s) - Maintenance Phases

16 PAS Kernel Release

17 Kernel out of date

11 Software Configuration for SXX 9/71

For more information, see PAS Service Marketplace at https://support.PAS.com/software/patches/stacks.html

11 Software Configuration for SXX 10/71

19 PAS Solasido Maregen General of SXX

20 Managed System Configuration

MANAGED SYSTEM CONFIGURATION STATUS FOR TECHNICAL SYSTEMS

RFC AND PLUG-IN STATUS FOR ABATA SYSTEMS

The check is rated GREEN because:

19 PAS Solasido Maregen General of SXX 11/71