EarlyWatchAlert
Confidential
Status Productive
Customer PT.
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
ALERT OVERVIEW
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
Update Errors
Table Reorganization
DB
Performance
Database Version
Bufferpool Qualities
Locking
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
Topic Subtopic
Topic Subtopic
Rating Rating
Average Read and Write Times
Missing Indexes
DB
Administration
Database Storage
Table Virtualization
Enhanced Monitoring
Logfiles Recommendations
BW Checks
BW Warehouse Management
Security
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.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
2 Landscape
3 Products and Components in current Landscape
PRODUCT
System PAS Product Product Version
SXX~ABATA PAS Solasido Maregen 7.2
DATABASES
Related System Database System Database Version DB ID
SXX~ABATA SYB for Linux UNIX and Windows 10.5 SXX
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
2 Landscape 5/71
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
2 Landscape 6/71
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
We recommend that the PAS Solasido Maregen is used to ship PAS Support remote services. For more
information, see PAS Note 1170668.
2 Landscape 7/71
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
Your system's software versions are checked. If known issues with the software versions installed are identified,
they are highlighted.
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.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
See the "Database Version" section in the "Database" section foradditional information.
* 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.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
Background Jobs
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.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
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
Application Area # of Objects
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
The daily operation of your system was analyzed. We detected some problems that
may impair system operation and stability.
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.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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.
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.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
37 Security
Rating Check
System Recommendations (ABATA)
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.
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
37 Security 19/71
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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.
001 2 4
777 8 34
Authorization profile:
PAS_ALL
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 = *
066 1 1
777 16 34
Authorization objects:
Object 1: S_TCODE with TCD=SE38 or TCD=SA38 or TCD=SC38
Object 2: S_PROGRAM with P_ACTION=SUBMIT P_GROUP=*
777 14 34
Authorization objects:
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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).
777 14 34
Authorization objects:
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__
777 16 34
Authorization objects:
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
066 1 1
777 14 34
Authorization objects:
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
57 Database Performance
Rating Check
Database Version
Bufferpool Qualities
Locking
Missing Indexes
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
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.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
65 Database Administration
Rating Check
Database Storage
Table Virtualization
Enhanced Monitoring
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.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
Recommendation:
Ensure that you install the latest Support Package for your ST-PI and ST-A/PI releases on your managed
systems.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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.
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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 Warehouse Management
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.
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
to this strategy.
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
InfoCubes
The table below provides an overview of the active InfoCubes of the analyzed BW system.
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
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
IS - InfoSet
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
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.
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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).
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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.
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
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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.
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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)
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.
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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).
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
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.
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
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
76 BW Checks for SXX 47/71
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
BW SOURCE SYSTEMS
Logical System Name Release Support Pack ABATA Patch Basis Patch
SXXCLNT777 740 0000 740 0000 740 0000
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
Rating Check
MetaData Cache Activation
Logging Configuration
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
Rating Check
Fiori Checks for SXX
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.
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.
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:
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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.
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 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.
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.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
The check has not been rated. Refer to the information below for further details.
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 "/").
120 Database server load from expensive SQL statements - SXX 54/71
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
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",
120 Database server load from expensive SQL statements - SXX 55/71
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
Program Data:
124 Access on
Statement Data:
CACHE STATISTICS
Total Avg. Total User Total
Total Rows Rows Rows Sort
Execution Execution CPU Logical
Executions Read Written Returned Overflows
Time[ms] Time[ms] Time[ms] Reads
467 138111 295,74 6071 00 4572 35962 0
Program Data:
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:
120 Database server load from expensive SQL statements - SXX 56/71
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
CACHE STATISTICS
Total Avg. Total User Total
Total Rows Rows Rows Sort
Execution Execution CPU Logical
Executions Read Written Returned Overflows
Time[ms] Time[ms] Time[ms] Reads
467 137383 294,18 6072 00 4592 35966 0
Program Data:
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
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
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
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
31 94809 3.058,35 1645976 00 838 61755 0
SELECT
CREATOR, NAME, CTIME
FROM
SYSIBM.SYSTABLES
120 Database server load from expensive SQL statements - SXX 57/71
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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
Total Avg. Total User Total
Total Rows Rows Rows Sort
Execution Execution CPU Logical
Executions Read Written Returned Overflows
Time[ms] Time[ms] Time[ms] Reads
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
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
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:
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
120 Database server load from expensive SQL statements - SXX 58/71
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
In this section, a "week" is from Monday to Sunday. The date displayed is the Sunday of the week.
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.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
- Active Users: Users who performed more than 400 transaction steps in one week.
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
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
The "Transaction Code" table below shows the load percentage caused by the top 5 transactions.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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.
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
Confidential
EarlyWatch Alert PT Selamanya Sentosa, Tbk 28.08.2017 - 03.09.2017
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