This section lists the important steps to troubleshoot SAP ME performance problems.
For ease of use in viewing an SAP Note, right click on the Note link and select Open in new window or Open in new tab.
2.1 System Wide Slowdown
A system-wide slowdown affects all areas of the software. First need to eliminate database as cause for slowdown. Database and Netweaver can be checked in parallel.
- Check database performance
To check database performance run diagnostics reports and perform MS SQL Server-Specific Tasks or Oracle-Specific Tasks.
- Check Wily if installed
You can find more information about using Wily to analyze SAP ME System on this page: Using Wily to Analyze SAP ME System.
- Check log files
See Important Log Files to Analyze ME application problems for more details.
- Check Netweaver settings
If the database checks have not resolved the performance issue, the following Netweaver settings should be checked:
-Garbage Collections settings.
2.2 Periodic System Wide Slowdown
In case of periodic slowdowns, make sure slowdown occurs across all shop floor users (people, machines).
- System wide slowdowns are usually database related since it is central to all application servers
- Partial system slowdowns are usually Netweaver related.
- Most ME installations have at least 2 Netweaver Java nodes.
The following items need to be checked in addition to those for the system-wide slowdown section above:
- Spikes in requests to ME application
You may use for this Transaction log as per SAP Note 1430326 (released internally) and SAP Note 1524180, and Built-In Diagnostic Tool.
- External factor outside the application
- Virtualized server (VMWare,etc.) for overload system with vendor tools.
- Whether other applications are accessing the ME database (reports, applications, antivirus, etc.) causing load problems.
- Customer IT landscape
- Network stability that can be investigated by means of NIPING tool - see SAP Note 500235 for details;
- Whether backups are occurring during slowdown period.
- ME functions that coincide with slowdown
- Customized background processes
- Archiving execution interval
- ODS script execution interval
2.3 Specific ME activity response time slow
- Specific functional area(s) affected, but performance is OK otherwise
- Need to identify all areas with slow response times and gather data accordingly
- Database query response times should be investigated
- Verify a slow functionality
Try to isolate to specific steps to reproduce if possible, determine which ME activity is slow.
- Investigate Slow Queries
- Obtain SQL Trace as per SAP Note 1266339. You can collect SQL trace for only one specific user as per SAP Note 2270991.
- Get execution plan.
Execution plan shows steps necessary to retrieve results from database.
- Analyze execution plan:
-- Look for full table scans which can slow query execution.
-- Determine if where clause has non-indexed columns.
-- Look for full index scans which can slow query execution. A full index scan means the query predicate is not selective enough or the indexes are insufficient for this query.
-- Slow queries may be caused by missing indexes or insufficient statistics.
-- Indexes should only be added if validated by SAP ME development team.
-- SAP ME development team should be involved in case query rewrite is needed.
- Check Netweaver Java Nodes
- Check garbage collection (GC) activity
-- Use Wily to check GC activity: Using Wily to Analyze SAP ME System
-- Use NW log to check GC activity: Important Log Files to Analyze ME application problems
- Use Wily to check execution thread resource consumption
- Use SAP JVM Profiler to analyze performance
If none of the steps above reveal the root cause, it may be needed to analyze the performance of with SAP JVM Profiler: Use SAP JVM Profiler for SAP ME Performance Analysis
SAP Note 1498757 - 'SAP ME 5.2 Survival Guide'
SAP Note 500235 - 'Network Diagnosis with NIPING'
SAP Note 1430326 - 'SAP ME Transaction Log'
SAP Note 1524180 - 'SAP ME 5.2: Diagnostic Guides and Reports'
SAP Note 1976371 - 'XMII_TRANSACTION table'