Service Report: Earlywatch Alert

Service Report
EarlyWatch ® Alert
Confidential
SAP System ID XHP

Product SAP NetWeaver 7.5
Status PRODUCTIVE
DB System SAP ASE 16.0.02.04
Processed on SAP Solution Manager SMI

Release SOLUTION MANAGER 7.2
Service Tool 720 SP17

Service Content 13.04.2021
Analysis from 19.04.2021 Session No. 0010000000992

Until 25.04.2021 Installation No. 0020645487
Authorized for SAP employees delivering SAP Services and Support, authorized partners, and customer employees. Please
forward to authorized recipients only.
EarlyWatch Alert 20645487 - XHP 19.04.2021 - 25.04.2021
1 Service Summary
-
We did not detect any critical problems during the EarlyWatch Alert
service.
Note: If you send SAP EarlyWatch Alert data to SAP, this report can also be viewed in the SAP ONE Support Launchpad
in an interactive SAP Fiori application SAP Note 2520319 . Here is the link to the latest reports for this system: SAP
EarlyWatch Alert Workspace
Specific links to analytical detail pages in SAP EarlyWatch Alert Workspace are included in the respective sections or in
this report.
Check Overview
-
Topic Rating Topic Subtopic Rating Subtopic
SAP System Configuration - -
- - SAP Kernel Release for JAVA Stack
Hardware Capacity - -
Security - -
- - System Recommendations (JAVA)
- - Invoker Servlet
Software Change Management - -
Java System Data - -
- - Java VM Memory Performance
- - Java Workload Overview
- - Java Application Performance
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 SAP
Solution Manager EarlyWatch Alert service, create a customer message under component SV-SMG-SER-EWA.
Note: If you require assistance to resolve 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, please contact your customer representative (for
example, TQM or ESA). To contact the SAP Enterprise Support advisory team or Customer Interaction Center, please refer
to the local contact number specified in SAP Note 560499 . For details of how to set the appropriate priority level, see SAP
Note 67739 .
Confidential Service Summary 2/20

2 Landscape
-
2.1 Products and Components in current Landscape
-
Product
-
System SAP Product Product Version
XHP~JAVA SAP NetWeaver 7.5
Main Instances (ABAP or JAVA based)
-
Related System Main Instance
XHP~JAVA Adapter Engine (Java EE)
XHP~JAVA Advanced Adapter Engine Extended
XHP~JAVA Application Server Java
XHP~JAVA Business Process Management
XHP~JAVA Composition Platform
Databases
-
Related System Database System Database Version DB ID
XHP~JAVA SAP ASE 16.0.02.04 XHP
-
2.2 Servers in current Landscape
-
SAP Application Servers
-
System Host Instance Name Logical Host ABAP JAVA
XHP~JAVA gmxpivp00 gmxpivp00_XHP_00 gmxpivp00 -
DB Servers
-
Related System Host Logical Host (SAPDBHOST)
XHP~JAVA gmxpivp00 gmxpivp00
Components
-
Related System Component Host Instance Name Logical Host
XHP~JAVA Java SCS gmxpivp00 gmxpivp00_XHP_01 gmxpivp00
-
2.3 Hardware Configuration
-
Host Overview
-
Host Hardware Model CPU Type CPU MHz Virtualization Operating System CPUs Memory in
Manufactu MB
rer
gmxpivp00 VMware, Inc. VMware Xeon 2300 VMWARE SUSE Linux 4 32113
Virtual E7-8880 v3 Enterprise Server
Platform 11 (x86_64)
Confidential Landscape 3/20

3 Service Data Quality and Service Readiness

-
Some service data is missing for this report and not all checks could be performed.
This does not impact the report rating.
The system XHP is not fully prepared for delivery of future remote services .
Rating Check Performed

Service Data Quality
Service Preparation of XHP
-
3.1 Service Data Quality
-
For this service, only data of minor importance is missing. This section provides a comprehensive overview how the
content of the report is affected.
The service data is collected by the Service Data Control Center (SDCCN) or read from the Solution Manager's BW or
Configuration and Change Database (CCDB) .
Recommendation: To resolve issues with the service data quality follow the hints and SAP Notes provided below.
Explanation for 'Priority' Column In Tables Below
-
Prio. Explanation: Impact of Missing or Erroneous Data
Some important check could not be processed. The report can be rated green nevertheless.
-
3.1.1 Quality of Service Data in Configuration And Change Database
-
Prio. Report Area affected Details and Related CCDB Store SAP Note
Security of Java System XHP The data in the store is outdated.CCDB 1777751
Store: servlet_jsp used in section '
Security
-
3.2 Service Preparation of XHP
-
Hardware Utilization Data
In preparation for SAP services, ensure that connections, collectors, and service tools are up to date. These functionalities
are explained in SAP Notes 91488 and 1172939 .
Confidential Service Data Quality and Service 4/20

Readiness
4 Software Configuration for XHP

-
We have listed recommendations concerning the current software configuration on
your system.
Your system's software versions are checked. If known issues with the software versions installed are identified, they are
highlighted.
-
4.1 SAP Application Release - Maintenance Phases
-
SAP Product Version End of Mainstream Maintenance Status
SAP NETWEAVER 7.5 31.12.2024
In February 2020, SAP announced a maintenance extension for SAP Business Suite 7 core application releases to 2027. If
you are running a relevant release, see SAP Note 1648480 for more details and applicable restrictions.
-
4.2 Support Package Maintenance - JAVA
-
The following table shows an overview of currently installed Java stack software components.
Support packages
-
Component Version SP Latest Available SP
AJAX-RUNTIME 7.50 0 20
BI-BASE-E 7.50 0 20
BI-BASE-B 7.50 0 20
BI-BASE-S 7.50 0 20
BI_UDI 7.50 0 20
BI-WDEXT 7.50 0 20
BI-WDALV 7.50 0 20
BPEM-ACC 7.50 0 20
BPEM-BASE 7.50 0 20
BPEM-BUILDT 7.50 0 20
BPEM-COLLAB 7.50 0 20
BPEM-CONTENT 7.50 0 20
BPEM-CORE 7.50 0 20
BPEM-FACADE 7.50 0 20
BPEM-HIM 7.50 0 20
BPEM-MM 7.50 0 20
BPEM-MON 7.50 0 20
BPEM-PP 7.50 0 20
BPEM-WDUI 7.50 0 20
BPEM-CUUI 7.50 0 20
BRMS-BASE 7.50 0 20
BRMS-BUILDT 7.50 0 20
BRMS-CORE 7.50 0 20
BRMS-FACADE 7.50 0 20
BRMS-WDUI 7.50 0 20
BRMS-MON 7.50 0 20
CAF-MF 7.50 0 20
Confidential Software Configuration for XHP 5/20

CAF-UI 7.50 0 20
COLLAB-ADP 7.50 0 20
COMP_BUILDT 7.50 0 20
CU-BASE-JAVA 7.50 0 20
CU-BASE-WD-EXT 7.50 0 20
CU-BASE-WD 7.50 0 20
CU-WD4VC-ADPT 7.50 0 20
DATA-MAPPING 7.50 0 20
SAP_BUILDT 7.50 0 20
DI_CLIENTS 7.50 0 20
ECM-ADMIN 7.50 0 20
ECM-APPS 7.50 0 20
ECM-CORE 7.50 0 20
ECM-JEE-COMP 7.50 0 20
ECM-STORE 7.50 0 20
ENGINEAPI 7.50 0 20
EP-ADMIN 7.50 0 20
EP_BUILDT 7.50 0 20
EP-CONNECTIVITY 7.50 0 20
EP-RUNTIME 7.50 0 20
ESREG-BASIC 7.50 0 20
ESREG-SERVICES 7.50 0 20
UDDI 7.50 0 20
ESCONF_BUILDT 7.50 0 20
ESP_FRAMEWORK 7.50 0 20
WSRM 7.50 0 20
ESI-UI 7.50 0 20
ESMP_BUILDT 7.50 0 20
SAP_XIESR 7.50 0 20
FP-INFRA 7.50 0 20
FRAMEWORK-EXT 7.50 0 20
GWJPO 7.50 0 20
INTG_VIS_DCJ 7.50 0 20
INTG_VIS 7.50 0 20
J2EE-APPS 7.50 0 20
BASETABLES 7.50 0 20
CORE-TOOLS 7.50 0 20
ENGFACADE 7.50 0 20
J2EE-FRMW 7.50 0 20
LM-CORE 7.50 0 20
SERVERCORE 7.50 0 20
FRAMEWORK 7.50 0 20
JSPM 7.50 0 20
LM-TOOLS 7.50 0 20
LMCFG 7.50 0 20
LMCTC 7.50 0 20
LM-CTS 7.50 0 20
LM-CTS-UI 7.50 0 20
LM-MODEL-BASE 7.50 0 20
LM-MODEL-NW 7.50 0 20
LMNWABASICAPPS 7.50 0 20
LMNWABASICMBEAN 7.50 0 20
LMNWACDP 7.50 0 20
LMNWATOOLS 7.50 0 20

LMNWAUIFRMRK 7.50 0 20
LM-SLD 7.50 0 20
LMNWABASICCOMP 7.50 0 20
MESSAGING 7.50 0 20
MMR_SERVER 7.50 0 20
MOIN_BUILDT 7.50 0 20
NWTEC 7.50 0 20
SAP_XIGUILIB 7.50 0 20
PI-SCP-BUILDT 7.50 0 20
PI-SCP-EXT 7.50 0 20
EP-BASIS 7.50 0 20
EP-BASIS-API 7.50 0 20
CAF 7.50 0 20
ODATA-CXF-EXT 7.50 0 20
SUPPORTTOOLS 7.50 0 20
KM-KW_JIKS 7.50 0 20
UISAPUI5_JAVA 7.50 0 20
SEA-CORE 7.50 0 20
SEA-FACADE 7.50 0 20
SEA-UI 7.50 0 20
SECURITY-EXT 7.50 0 20
SERVICE-COMP 7.50 0 20
SOAMON 7.50 0 20
SOAMONBASIC 7.50 0 20
SWLIFECYCL 7.50 0 20
SR-UI 7.50 0 20
TM-WLUI 7.50 0 20
UKMS_JAVA 7.50 0 20
UMEADMIN 7.50 0 20
UWLJWF 7.50 0 20
VCCORERT 7.50 0 20
VCFREESTYLEKIT 7.50 0 20
VCBASE 7.50 0 20
VCKITBI 7.50 0 20
VCFRAMEWORK 7.50 0 20
VTP_BUILDT 7.50 0 20
WD-ADOBE 7.50 0 20
WD-APPS 7.50 0 20
WDEXTENSIONS 7.50 0 20
WD-FLEX 7.50 0 20
WD-RUNTIME 7.50 0 20
WD-RUNTIME-EXT 7.50 0 20
SAP-XI3RDPARTY 7.50 0 20
SAP_XIAF 7.50 0 20
SAP_XIADMIN 7.50 0 20
XI_CNT_SAP_BASIS 7.50 0 20
SAP_XIIGW_APPL 7.50 0 20
SAP_XIIGW_CORE 7.50 0 20
SAP_XITOOL 7.50 0 20
CFG_ZA 7.50 0 20
CFG_ZA_CE 7.50 0 20
JDK Version
-
Hostname Instance VM Vendor VM Version
Hostname Instance VM Vendor VM Version
gmxpivp00 gmxpivp00_XHP_00 SAP AG 8.1.010 25.51-b02
-
4.3 Database - Maintenance Phases
-
Database Version End of Standard Vendor Support* Status
SAP ASE SERVER 16.0 31.12.2025
* Maintenance phases and duration for the DB version are defined by the vendor. Naming of the phases and required
additional support contracts differ depending on the vendor. Support can be restricted to specific patch levels by the vendor
or by SAP. Check in the referenced SAP Note(s) whether your SAP system requires a specific patch release to guarantee
support for your database version.
-
4.4 Operating System(s) - Maintenance Phases
-
Host Operating System End of Standard End of Extended Vendor Comment Status SAP Note
Vendor Support*
Support*
gmxpivp00 SUSE Linux Enterprise 31.03.2019 31.03.2022 Limited (LTSS) 936887
Server 11 (x86_64)
* Maintenance phases and duration for the operating system version are defined by the vendor. Naming of the phases and
required additional support contracts differ depending on the vendor. Support can be restricted to specific patch levels by
the vendor or by SAP. Check in the referenced SAP Note(s) whether your SAP system requires a specific patch release to
guarantee support for your operating system version.
SUSE offers an optional fee-based "Long Term Service Pack Support" (LTSS) phase, which you can purchase to continue
receiving maintenance and critical security patches beyond the end of standard vendor support. While standard support for
SUSE Linux Enterprise Server 11 will end/ended on 31.03.2019, "Long Term Service Pack Support" for SUSE Linux
Enterprise Server 11 will end on 31.03.2022. For details on the scope of support and restrictions during the LTSS phase,
see https://www.suse.com/products/long-term-service-pack-support.
-
4.5 SAP Kernel Release for JAVA Stack
-
The following table lists all information about your SAP kernel(s) currently in use.
Installation Name SAP Kernel Release
XHP 745
-
4.5.1 Downward Compatible Kernel
-
SAP Note Number What to Do Description
1969546 Information Release Roadmap for Kernel 74x and 75x
2350788 Information Using kernel 7.49 instead of kernel 7.40, 7.41, 7.42 or 7.45
2556153 Information Using kernel 7.53 instead of kernel 7.40, 7.41, 7.42, 7.45, or 7.49
This kernel version was replaced by the downward-compatible kernel. You can continue to use your current kernel version,
but if an issue occurs with your current kernel, a fix will be provided for SAP kernel 749 or 753 only.
Recommendation : To avoid the potential risks associated with running an outdated SAP kernel version, replace this
version with downward-compatible SAP kernel 749 or 753. The downward-compatible kernel is a special validated SAP
kernel that improves the stability of your system.

5 Hardware Capacity
-
We have checked your system for potential CPU or memory bottlenecks and found
that the hardware is sufficient for the current workload.
Note: Hardware capacity evaluation is based on hosts for which data is at least partially available.
-
5.1 Overview System XHP
-
General This analysis focuses on the workload during the peak working hours (9-11, 13) and is based on the hourly
averages collected by SAPOSCOL. For information about the definition of peak working hours, see SAP Note 1251291 .
CPU If the average CPU load exceeds 75% , temporary CPU bottlenecks are likely to occur. An average CPU load of more
than 90% is a strong indicator of a CPU bottleneck.
Memory If your hardware cannot handle the maximum memory consumption, this causes a memory bottleneck in your
SAP system that can impair performance. The paging rating depends on the ratio of paging activity to physical memory. A
ratio exceeding 25% indicates high memory usage (if Java has been detected 0% ) and values above 50% (Java 10% )
demonstrate a main memory bottleneck.
Server Max. CPU Date Rating RAM [MB] Max. Paging [% of Date Rating Analysis Analysis
load [%] RAM] Start End
gmxpivp00 2 24.04.2021 32.113 0 - 19.04.2021 25.04.2021
Note: For virtualization or IaaS scenarios (for example, IBM PowerVM, VMware, Amazon AWS, ...) it is possible that the
CPU rating for some hosts is YELLOW or RED, even though the utilization value is quite low. In this case, the relevant host
could not use maximum usable capacity due to a resource shortage within the virtualized infrastructure (for example, IBM
PowerVM: Shared Pool CPU utilization).
Confidential Hardware Capacity 9/20

6 Security
-
No critical security issues were found in your system.
Rating Check
System Recommendations (JAVA)
Invoker Servlet
-
6.1 Invoker Servlet
-
The invoker servlet is intended to be used for rapid prototyping only and allows HTTP clients to invoke servlets that have
not been declared in the application's /WEB-INF/web.xml file.
A specially crafted URL using the invoker servlet feature can allow unauthenticated access to arbitrary servlets. In addition,
no authentication is needed to invoke these servlets.
SAP Note 1445998 provides further information.
Parameter EnableInvokerServletGlobally
-
Rating Current Value Recommended Value
false false
Confidential Security 10/20

7 Software Change and Transport

Management of XHP
-
Software change management issues were found in your system. See the information
in the following sections.
-
7.1 SAP Netweaver Application Server JAVA of XHP
-
Number of Changes
Enhanced Change and Transport System (CTS+)
-
7.1.1 Number of Changes
-
Performing changes is an important cost driver for the IT department. It is only acceptable to make a large number of
software and configuration changes in exceptional situations, such as during go-live for an implementation project.
Problems have been detected regarding the daily collection of data into the configuration and change database (CCDB).
This may lead to inaccurate or incomplete results of the service sessions.
Check the CCDB extractors using the extractor framework administration: 'Root Cause Analysis' work center -> Common
Tasks -> 'Extractor FWK Administration'. On the 'Managed System' tab page, select the managed system and filter by the
extractor name "CONFIGURATION*" to check the status of the CCDB extractors.
Check the status of the single stores using the application log of the Solution Manager: Transaction SLG1, object = 'CCDB',
subobject = '<SID>*', and date from = '<yesterday>'. Here you will find detailed error information about the config stores.
-
7.1.2 Enhanced Change and Transport System (CTS+)
-
The enhanced Change and Transport System (CTS+) enables you to transport Java objects and SAP-related non-ABAP
applications in your system landscape along with ABAP objects. The tracking and logging features of the ABAP Change
and Transport System are also available for non-ABAP applications in a central user interface. This provides maximum
transparency for all changes in the complete landscape, including ABAP and non-ABAP systems. CTS+ is SAP's
recommended tool for distributing changes across the transport landscape.
We could not determine whether CTS+ is used. Either it is not used or information about its usage is not available in SAP
Solution Manager.
If CTS+ is not configured, you should set it up as described in the online help http://help.sap.com/nwcts --> Application
Help.
If CTS+ is configured but this information is not available in SAP Solution Manager, repeat the managed system
configuration for this system in transaction SOLMAN_SETUP of your SAP Solution Manager. In step "Enter System
Parameters", section "CTS+ Reporting", select CTS+ as active and enter the communication system. Also run the
managed system configuration for the CTS+ communication system.
Confidential Software Change and Transport 11/20

Management of XHP
8 Database Administration for Java Instances

-
Some problems regarding the administration of your database were found.
Rating Check
Environment and Operation
ATM Configuration and Diagnostics
ASE Space Utilization
-
8.1 ASE Job Scheduler Java
-
Job Scheduler Scheduled / Unscheduled
ASE Job Scheduler
-
8.2 ASE Space Utilization Java
-
In this section, details about the database/device/file system utilization information are provided.
-
8.2.1 File System Utilization Java
-
The following table shows information about the size and free space of available file systems in the SAP ASE system.
File System Name File System Size (MB) File System Free (MB) Rating
10.64.82.126:/VOL_LNX_GMX_GMXPIVP00_SYBSYS 5120 4737
10.64.82.126:/VOL_LNX_GMX_GMXPIVP00_SYXHP_SAPDAT 53248 42815
A_1
10.64.82.126:/VOL_LNX_GMX_GMXPIVP00_SYXHP 15360 14603
10.64.82.126:/VOL_LNX_GMX_GMXPIVP00_SYXHP_SAP 63012 44067
LOG_1
10.64.82.126:/VOL_LNX_GMX_GMXPIVP00_SYSAPTMP 15360 14352
10.64.82.126:/VOL_LNX_GMX_GMXPIVP00_SYBTMP 10240 9736
There is currently more than 20% free space at file system level.
-
8.2.2 Database and Device Space Utilization Java
-
The following tables show information about database and device space utilization.
Database Space Utilization Details
Database ID Database Name Database Size (MB) Unreserved Space (MB) Free Log Space (MB) Rating
4 XHP 25528 18538 4608
1 master 300 267 269 -
3 model 24 10 11 -
6 saptempdb 5120 5086 5107 -
31516 sybsecurity 204 188 20 -
2 tempdb 3072 3059 3072 -
Device Space Utilization Details
Confidential Database Administration for Java 12/20

Instances
Device No. Device Name Physical Device Name Device Size (MB) Device Free Direct I/O
Space (MB) enabled
0 master /sybase/XHP/sybs 950 310 No
ystem/master.dat
3 tempdbdev /sybase/XHP/syb 3572 3059 No
temp/tempdbdev.dat
1 sysprocsdev /sybase/XHP/sybs 800 158 Yes
ystem/sysprocs.dat
2 systemdbdev /sybase/XHP/sybs 550 47 Yes
ystem/sybsysdb.dat
4 sybmgmtdev /sybase/XHP/syb 650 113 Yes
system/sybmgmtdb.dat
5 XHP_data_001 /sybase/XHP/sap 27576 18538 Yes
data_1/XHP_data
_001.dat
6 XHP_log_001 /sybase/XHP/sap 7608 4589 Yes
log_1/XHP_log_001.dat
7 saptools_data_001 /sybase/XHP/sapd 2548 2026 Yes
iag/saptools_dat
a_001.dat
8 saptools_log_001 /sybase/XHP/sapd 704.798828 203 Yes
iag/saptools_log_001.dat
9 sybsecurity_data_001 /sybase/XHP/sybs 704.798828 188 Yes
ecurity/sybsecur
ity_data_001.dat
10 sybsecurity_log_001 /sybase/XHP/sybs 520.478516 19 Yes
ecurity/sybsecur
ity_log_001.dat
11 saptempdb_data_001 /sybase/XHP/sap 5620 5086 Yes
temp/saptempdb_
data_001.dat
12 XHP /sybase/XHP/sap 5120 - Yes
log_1/XHP_log_002.dat
More than 20% free space is available in the productive ASE database .
-
8.3 ATM Configuration and Diagnostics Java
-
This section describes the Automatic Table Maintenance (ATM) configuration and
different tasks enabled in your SAP ASE system.
-
8.3.1 ATM Diagnostics Java
-
We were unable to read your ATM Diagnostics information. Please ensure that it is configured correctly, and the data is
collected for your system. If you face further issues, please create a customer message under component
SV-SMG-SER-EWA.
-
8.4 Environment and Operation Java
-
In this section, basic information about the database and its software environment is shown.
-
8.4.1 SAP Notes for SAP ASE Java
-
The following SAP Notes contain useful information about operating a system on SAP ASE.

Instances
SAP Note No. Description

2001472 SYB: Connection to Java system fails
1960922 SYB: EHP upgrade for Java system on ASE fails in task PREPARE_XI_TABLES_SYB
1606592 SYB: Installation of SAP ASE ISQL
1599814 SYB: Installing Service Packs for SAP ASE (UNIX + Linux)
1982469 SYB: Updating SAP ASE with saphostctrl / sapdbctrl
1748888 SYB: Inst.Systems Based on NW 7.3 and Higher: SAP ASE
1697542 SYB: System copy with target SAP Adaptive Server Enterprise
1554717 SYB: Planning information for SAP on ASE
1612437 SYB: System copy with SMIGR and table partitioning
1680803 SYB: SAP Adaptive Server Enterprise - Best Practice for SAP Business Suite and SAP BW
1581695 SYB: Configuration Guide for SAP ASE 16.0
1646155 SYB: Configuring auxiliary scan descriptors
1245200 DBA: ICF Service-Activation for WebDynpro DBA COCKPIT
1593987 SYB: Monitoring non-SAP ASE databases with the DBA Cockpit
1588316 SYB: Configure automatic database and log backups
1585981 SYB: Ensuring Recoverability for SAP ASE
1618817 SYB: How to restore an SAP ASE database server (UNIX)
1650511 SYB: High Availability Offerings with SAP Adaptive Server Enterprise
1590719 SYB: Updates for SAP Adaptive Server Enterprise (SAP ASE)
1642301 SYB: Collecting diagnostic data for Sybase ASE support
1777966 SYB: Check for incomplete index statistics
1539124 SYB: Database Configuration for SAP applications on SAP ASE
-
8.4.2 SAP Temporary database Java
-
Database Name Tempdb Size [GB] Recommended Size [GB]
saptempdb 5.00 5.00
The size of the saptempdb database is configured correctly in the system. We do not recommend any changes in this area.
-
8.4.3 Database Recovery Order Java
-
Verify your recovery order is set correctly. This ensures a database recovery order where the hard binding prohibits user
logins until all the databases are recovered.
Recommendation: Verify the database recovery order of the databases using the stored procedure and execute the
following commands to ensure the recovery order.
use master
go
exec sp_dbrecovery_order 'saptools', 1, null, strict
exec sp_dbrecovery_order '', 2, null, strict
exec sp_dbrecovery_order 'saptempdb', 3, null, strict
go
-
8.4.4 Table Options Java
-
We were unable to check whether your table options are set correctly.
To check the current settings of a table, use stored procedure sp_help. For more information, see SAP Note 2049506 .
-
Instances
8.4.5 Error Log Java

-
No errors were found in the database error log.
An analysis of the database error log was carried out for a time frame starting on 2021-04- to 2021-04-26. The analysis of
the database error log data shows no entries of the type "critical error" or "error" for the week prior to the session date.
There might be warnings in the error log within this time frame, although they are not evaluated in this check. Errors in the
error log are divided into the following categories:
Severity <= 16 --> warning
Severity 17, 18 --> error
Severity >= 19 --> critical error
-
8.4.6 Deferred Tables Java
-
Summary Number of Tables
Number of Tables 1331
Number of Deferred Tables 47
Number of Candidates 765
No issues with deferred tables were found. No action is necessary.
-
8.4.7 Database Release Java
-
SAP ASE product releases are denoted in the form "X.Y.Z", where 'X' represents the major release version, 'Y' represents
the intermediate release version, and 'Z' represents the maintenance release version. For example, the release of ASE
15.5 signifies an intermediate release.
SAP ASE is also introducing the term "release family", which denotes all the releases with the same major release number.
For example, ASE releases 15.0.1, 15.0.2, 15.0.3, and 15.5 all belong to the same release family since they all have the
same major release number of 15.
SAP ASE will issue end-of-life (EOL) notices only for a release family. On the EOL date, engineering support will end for all
the releases in the release family.
Customers are advised to move to the latest release within a release family to receive the most recent software bug fixes.
SAP may continue to provide bug fixes in the immediately prior intermediate or maintenance release for a limited time,
depending on customer need. If a new release is not available on all platforms and editions, that platform or edition's last
release is treated as the latest release and will continue to get bug fixes for a limited time after the next new release is
available, unless otherwise specified.
Release in use Comment
16.0.02.04
The current SAP ASE release is supported by SAP. To verify this, see SAP Note 1554717 .
The Electronic Binary Format (Build) is shown below.
Electronic Binary Format (Build)
EBF 26122 SMP

Instances
9 Java System Data for XHP

-
We did not detect any major problems that may affect your system performance,
stability, or administration.
Rating Check
Java VM Memory Performance
Java Workload Overview
Java Application Performance
-
9.1 Java VM Heap Size
-
The maximum heap size of the server nodes are listed in the following table. The maximum heap size of the dispatchers
are also listed for NetWeaver version 6.4 and 7.0.
Host Instance Node Maximum Heap Size (M)
gmxpivp00 gmxpivp00_XHP_00 server0 4096
-
9.2 Java VM Memory Performance
-
9.2.1 Garbage Collection Time hourly data
-
The time spent on garbage collection (GC) in the interval reported is not critical.
The graphic below provides hourly profile data for garbage collection (GC) time for each instance. Garbage collections
have a direct impact on system performance. The situation may be critical if Java server nodes spend a lot of time on the
garbage collections, especially at peak period.
-
9.3 Java Workload Overview
-
Confidential Java System Data for XHP 16/20
9.3.1 HTTP Sessions

-
The diagram displays a 24-hour profile for the average and maximum number of HTTP sessions.
-
9.3.2 User Logins
-
The diagram displays a 24-hour profile for the average and maximum number of user logins. This user login data refers not
only to the dialog user, but to all of the users that log on to the J2EE engine.
-
9.3.3 HTTP Requests
-
The distribution of HTTP requests to server nodes is even.
The table below provides the weekly average and maximum number of HTTP requests for each Java server node.
Note : If the system has more than 20 server nodes, only the data for the 10 server nodes with the highest values and the
10 server nodes with the lowest values is listed.

Host name Instance name Node name Average Max
gmxpivp00 gmxpivp00_XHP_00 SERVER0 69,33 244,00
-
9.3.4 Active Application Threads
-
The number of active application threads is not critical.
The table below provides the weekly average and maximum number of active application threads for each Java server
node.
Note : If the system has more than 20 server nodes, only the data for the 10 server nodes with the highest values and the
10 server nodes with the lowest values is listed.
Host name Instance name Node name Average Max Configured
gmxpivp00 gmxpivp00_XHP_00 SERVER0 9,24 13 300
-
9.4 Java Application Performance
-
Application performance can be assessed based on the average response time or on the accumulated response time of
the applications. The accumulated response time takes the average response time as well as the number of calls to an
application into account.
The following sections list different types of Java application components sorted by their accumulated response time. This
makes it possible to determine which Java application components cause the highest overall workload of the system.
-
9.4.1 Top WebDynpro Java Applications
-
Rank Name Acc. Resp. Time [s] Execus. Ave. Resp. Time [ms]
1 SAP.COM/TC~LM~ITSAM~UI~MAINF 79 188 422
RAME~WD/FLOORPLANAPP
Recommendations:
The table above lists the top Web Dynpro Java applications sorted by their accumulated response time. The average
response time and execution times are also listed. This information is very useful if you have performance problems
relating to Web Dynpro applications in the system. It can help to identify the applications with the highest workload in
the system and determine the possible root cause of the performance problem.
-
9.4.2 Top Servlets
-
Rank Name Acc. Resp. Time [s] Execs. Ave. Resp. Time [ms]
1 COM.SAP.ENGINE.S ERVICES.WEBSERVI 1542 65945 23
CES.SERVLET.SOAP SE RVLET
2 JEE_JSP_STARTPAGE_1476379303000 1227 20160 61
3 COM.SAP.ENGINE.HEARTBEAT.SERVERGRMGAPPLICA 728 10080 72
TION
4 COM.SAP.AII.ADAPTER.SOAP.WEB.MESSAGESERVLET 123 67 1829
5 COM.SAP.TC.WEBD YNPRO.SERVERIMP 92 198 466
L.WDC.DISPATCHE RSERV LET
6 COM.SAP.AII.IB.WEB.HMI.HMISERVLET 70 273 258
7 COM.SAP.AII.AF.APP.SERVLET.ADAPTERFR 28 168 168
AMEWORKSERVLET
8 COM.SAP.ENGINE.S ERVICES.SERVLETS 24 7754 3
_JSP.SERVER.SERV LE T.FORWARDSERVLE T
9 COM.SAP.LCR.GRMG.GRMGSERVLET 20 1973 10
10 COM.SAP.ENGINE.A PPLICATIONS.SECU 16 7754 2
RITY.LOGON.SAPML OG ONSERVLET
Recommendation:

The above table lists the top servlets sorted by their accumulated response time. The average response time and
execution times are also listed. This information is very useful if you have performance problems relating to servlets in
the system. It can help to identify the servlets with the highest workload in the system and determine the possible root
cause of the performance problem.
-
9.4.3 Top JCO Calls
-
1 JCO-PRO-400@GMXERPVP00|ZFI69_I 129 21 6147
NPUT_EXG_NOLOC
2 JCO-PRO-400@GMXERPVP00|/ARBA/R 41 8 5157
EMITTANCE_EXPORT
3 JCO-PRO-400@GMXERPVP00|/ARBA/P 25 8 3080
O_HEADER_STATUS
4 JCO-PRO-400@GMXERPVP00|ZFI69_INPUT_COMPLETO 17 7 2498
5 JCO-PRO-400@GMXERPVP00|DDIF_FIELDINFO_GET 0 28 15
6 JCO-PRO-400@GMXERPVP00|RFC_GET 0 14 7
_FUNCTION_INTERFACE
7 JCO-PRO-400@GMXERPVP00|/ARBA/A 0 9 2
DV_PAY_REMIT_EXPORT
Recommendation:
The above table lists the top JCo calls sorted by their accumulated response time. The average response time and
execution times are also listed. This information is very useful if you have performance problems relating to JCo calls
in the system. It can help to identify the JCo calls with the highest workload in the system and determine the possible
root cause of the performance problem.
-
9.4.4 Top SQL Statements
-
1 SELECT MIN ("PCNTR") FROM "BC_JMSQUEUE" 213 260534 1
WHERE "DSTID" = ? AND "PCNTR" > ? AND "ACK" = ?
AND "TXID" = ?
2 DELETE FROM "BC_MSG_VERSION" WHERE "MSG_ID" 46 7 6613
= ? AND "DIRECTION" = ?
3 DELETE FROM "BC_MSG_LOG" WHERE "MSG_ID" = ? 23 14 1616
AND "DIRECTION" = ?
4 SELECT "ID", "SCHEDULER_ID", "JOB_STATUS", 11 743 14
"PARENT_ID", "STARTED", "ENDED",
"JOB_DEFINITION_ID ", "VENDOR_DATA", "NODE",
"RETURN_CODE", "USER...
5 SELECT "JPL_APP_ACTN"."JP L_ID", 10 5070 2
"JPL_APP_PC"."JPL_ NAME", "JPL_APP_ACTN"."JP
L_NAME", "JPL_APP_ACTN"."JP L_DESC",
"JPL_APP_ACTN"."JP L_RUN_AS" F...
6 SELECT "PID", "NAMESP", "ATTR", "VAL" FROM 5 1122 5
"UME_STRINGS" WHERE "PIDH" = ? AND "ATTRH" = ?
AND "NAMESPH" = ? OR "PIDH" = ? AND "ATTRH" = ?
AN...
7 SELECT "CPATH", "LINKEDCPATH", "CID", 4 902 4
"PARENTCID", "CACHEMODE", "CTYPE" FROM
"J2EE_CONFIG" WHERE "PATHHASH" = ?
8 SELECT VALUE2 FROM MASTER.DBO.SYSC 2 1145 2
URCONFIGS WHERE CONFIG = (SELECT CONFIG
FROM MASTER.DBO.SYSC ONFIGURES WHERE NAME
= ? AND PARENT ! = ? AND ...

9 SELECT "FBLOB" FROM "J2EE_CONFIGENTR Y" 2 1225 2
WHERE "CID" = ? AND "NAMEHASH" = ? AND "NAME" =
? AND "ISFILE" = ?
10 IF EXISTS (SELECT ? WHERE ? = ?) SELECT ? ELSE 1 1145 1
SELECT ?
Recommendation:
The above table lists the top SQL statements sorted by their accumulated response time. The average response time
and execution times are also listed. This information is very useful if you have performance problems relating to SQL
statements in the system. It can help to identify the SQL statements with the highest workload in the system and
determine the possible root cause of the performance problem.
You can see sample SAP EarlyWatch Alert reports on SAP Support Portal at SAP EarlyWatch Alert -> Sample Reports.
For general information about SAP EarlyWatch Alert, see SAP Note 1257308 .
About System And Solution Manager

-
Solution Manager System SMI
Solution Manager Version SOLUTION MANAGER 7.2
Service Tool 720 SP17
Service Content Update On 13.04.2021

Service Report: Earlywatch Alert

Uploaded by

Document Information

Original Title

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

Service Report: Earlywatch Alert

Uploaded by

Copyright:

Available Formats

Service Report

SAP System ID XHP

Processed on SAP Solution Manager SMI

Service Tool 720 SP17

Analysis from 19.04.2021 Session No. 0010000000992

Confidential Service Summary 2/20

Confidential Landscape 3/20

3 Service Data Quality and Service Readiness

Rating Check Performed

Confidential Service Data Quality and Service 4/20

4 Software Configuration for XHP

Confidential Software Configuration for XHP 5/20

Confidential Software Configuration for XHP 6/20

Confidential Software Configuration for XHP 8/20

Confidential Hardware Capacity 9/20

Confidential Security 10/20

7 Software Change and Transport

Confidential Software Change and Transport 11/20

8 Database Administration for Java Instances

Confidential Database Administration for Java 12/20

Confidential Database Administration for Java 13/20

SAP Note No. Description

exec sp_dbrecovery_order 'saptools', 1, null, strict

exec sp_dbrecovery_order '', 2, null, strict

exec sp_dbrecovery_order 'saptempdb', 3, null, strict

8.4.5 Error Log Java

Confidential Database Administration for Java 15/20

9 Java System Data for XHP

9.3.1 HTTP Sessions

Confidential Java System Data for XHP 17/20

Confidential Java System Data for XHP 18/20

Confidential Java System Data for XHP 19/20

About System And Solution Manager

Confidential Java System Data for XHP 20/20

You might also like