header stringlengths 12 160 | content stringlengths 15 265k |
|---|---|
## 3.13.2.3 Analysis of MVCC Issues | ## 3.13.2.3 Analysis of MVCC Issues
You have to find out which transactions are blocking the garbage collection and to which connection they are related.
The following queries will return the transaction that may block the garbage collection. You have to check both.
```
SELECT top 1 host, port, connection_id, transact... |
## 3.13.2.4 Solution of MVCC Issues | ## 3.13.2.4 Solution of MVCC Issues
Solving MVCC issues is similar to solving blocked transaction issues. Use the following approaches in the given order for transactions where you know the connection ID.
1. Contact the user to stop his activity.
2. Cancel the statement/cancel the internal transaction.
3. Cancel the c... |
## 3.13.3 Version Garbage Collection Issues | ## 3.13.3 Version Garbage Collection Issues
Alert 75 helps you to identify and resolve version space overflow issues.
## Context
The following steps allow you to check whether or not the issue you have is related to row store version space skew, that is, whether the row store version chain is too long. If you use exte... |
## 3.14 Statement Performance Analysis | ## 3.14 Statement Performance Analysis
This section gives an overview of issues and solutions concerning SQL statement performance.
For more information about optimizing and fine-tuning queries refer to the SAP HANA Performance Guide for Developers which includes sections such as:
## Ongoing Development of SQL Query Pr... |
## 3.14.1 SQL Statement Optimization | ## 3.14.1 SQL Statement Optimization
This section provides an overview of tools, traces and SAP HANA cockpit areas that can be used to identify critical SQL statements.
SQL statements that are not executed efficiently can cause local and system-wide problems. The most critical are the following areas:
- A long runtime... |
## 3.14.1.1 SQL Statements Responsible for Past Problems | ## 3.14.1.1 SQL Statements Responsible for Past Problems
Sometimes it is not possible to identify a critical SQL statement during runtime. In this case you can use the following approaches to identify one or several SQL statements that can have contributed to the problem.
You can identify a SQL statement either by its... |
## 3.14.1.2 SQL Statements Responsible for Current Problems | ## 3.14.1.2 SQL Statements Responsible for Current Problems
If problems like high memory consumption, high CPU consumption or a high duration of individual database requests are currently happening, you can determine the active SQL statements with the help of SAP HANA cockpit.
Check for the currently running SQL state... |
## 3.14.2 Analysis of Critical SQL Statements | ## 3.14.2 Analysis of Critical SQL Statements
When you have identified the SQL text and the related statement hash based on the tools and traces, you can collect more information about the SQL statement in order to identify the root cause of the performance problem and optimize the statement. The available analysis ap... |
## 3.14.2.1 SQL Plan Cache Analysis | ## 3.14.2.1 SQL Plan Cache Analysis
The SAP HANA SQL plan cache can be evaluated in detail for a particular statement hash.
Various options are available for analyzing the plan cache for a statement. In SAP HANA cockpit the link for SQL Plan Cache is available in the Monitoring tile. The two system views associated wi... |
## 3.14.2.1.1 Example: Reading the SQL Plan Cache | ## 3.14.2.1.1 Example: Reading the SQL Plan Cache
These examples aim to show you how to gain useful insights by analyzing the SQL plan cache.
## Execution in a Single-Host System
This example aims to show you how to interpret information about execution time. The following table is sorted by TOTAL_EXECUTION_TIME.
| US... |
## 3.14.3 Optimization of Critical SQL Statements | ## 3.14.3 Optimization of Critical SQL Statements
You can improve the general performance of the SAP HANA database by implementing various best practices, design principles, available features, and add-ons.
To enhance the performance of the SAP HANA database, we recommend you do the following:
- Optimize outlier queri... |
## 3.14.3.1 Outlier Queries | ## 3.14.3.1 Outlier Queries
Outlier queries are database statements that take much more time than usual and expected. This usually happens because extra work has to be performed during execution.
Besides heavy load on the machine by non-SAP HANA processes (which should not be the case on production systems) SAP HANA i... |
## 3.14.3.2 Data Manipulation Language (DML) Statements | ## 3.14.3.2 Data Manipulation Language (DML) Statements
Data Manipulation Language (DML) statements are often slowed down by lock-wait situations.
Check under Monitoring SQL Plan Cache and the view m_SQL_PLAN_CACHE to determine such issues:
## ξ Note
Only check entries that have TOTAL_LOCK_WAIT_COUNT greater than 0. F... |
## 3.14.3.3 Native HANA Models | ## 3.14.3.3 Native HANA Models
Creating native HANA models can be one way to improve performance compared to development options outside of the database, or in some cases also compared to pure SQL development.
Native HANA models can be developed in the new XS Advanced (XSA) development environment using SAP Web IDE fo... |
## 3.14.3.4 Developing Procedures | ## 3.14.3.4 Developing Procedures
SQL in SAP HANA includes extensions for creating procedures, which enables you to embed data-intensive application logic into the database, where it can be optimized for performance (since there are no large data transfers to the application and features such as parallel execution is ... |
## 3.14.3.5 Application Function Library (AFL) | ## 3.14.3.5 Application Function Library (AFL)
You can dramatically increase performance by executing complex computations in the database instead of at the application server level.
SAP HANA provides several techniques to move application logic into the database, and one of the most important is the use of applicatio... |
## 3.14.3.6 Aspects of Scalability | ## 3.14.3.6 Aspects of Scalability
Before you decide how to scale your SAP HANA implementation, there are a number of aspects that need to be considered, such as scaling data, performance, applications, and hardware.
## Scaling the Data
One technique you can use to deal with planned data growth is to purchase more phy... |
## 3.14.3.7 Further Recommendations | ## 3.14.3.7 Further Recommendations
In addition to the general recommendations for improving SAP HANA database performance, for specific scenarios, you can use further features and best practices to improve performance.
If appropriate, you can take the following actions to improve performance:
- For any required long-... |
## 3.15 Application Performance Analysis | ## 3.15 Application Performance Analysis
This section provides a high-level guide for analyzing the performance of SAP HANA-based applications.
When you have an SAP HANA-based application with unsatisfying performance, you should start a systematic investigation considering the various layers that are involved. Here we... |
## 3.15.1 SQL Trace Analysis | ## 3.15.1 SQL Trace Analysis
The first step in application performance analysis is to figure out if the database layer is causing performance problems for your application at all.
## Context
You should analyze how many and which database calls are made and what their contribution to the overall application performance... |
## 3.15.2 Statement Measurement | ## 3.15.2 Statement Measurement
Once you have determined which SQL statements are problematic you should first perform a sound measurement in order to get reliable performance numbers and to make sure that indeed your statements are causing the issues and not the current state of your SAP HANA system.
## Procedure
1. ... |
## 3.15.3 Data Analysis | ## 3.15.3 Data Analysis
The easiest way to analyze a poorly performing SQL statement is to look at the data flow as this can be matched with the understanding of the business/application needs.
## Procedure
1. Check the result size, that is the number of records and number of columns, returned by your SQL statement an... |
## 3.15.4 Source Analysis | ## 3.15.4 Source Analysis
Before conducting a detailed technical analysis, it is recommended to first analyze source artifacts (models, scripts, views) for possible performance-impacting aspects.
## Context
The actual activities depend on the respective artifact (models, scripts, views).
## Procedure
1. Graphical Calc... |
## 3.15.5 Technical Analysis | ## 3.15.5 Technical Analysis
The deepest level of performance analysis addresses the technical details of a database statement execution.
## Context
You should follow this in order to track down problematic performance symptoms from which you can derive possible root causes at higher levels.
There are a number of tool... |
## 3.16 System Hanging Situations | ## 3.16 System Hanging Situations
This section explains what checks to carry out and how to perform those checks if your SAP HANA instance is hanging. The database is said to be hanging when it no longer responds to queries that are executed against it.
## Context
The source of the system standstill might be related to... |
## 3.16.1 Transparent Huge Pages on Linux | ## 3.16.1 Transparent Huge Pages on Linux
Transparent Huge Pages (THP) is a feature that is generally activated for the Linux kernel shipped with SUSE Linux Enterprise Server (SLES) 11 and Red Hat Enterprise Linux (RHEL) 6 versions certified for usage with SAP HANA. Due to the special manner of SAP HANA's memory manag... |
## 3.16.2 CPU Power Saving | ## 3.16.2 CPU Power Saving
The Linux Kernel shipped with SUSE Linux Enterprise Server (SLES) 11 and Red Hat Enterprise Linux (RHEL) 6 versions certified for usage with SAP HANA contain a new cpuidle driver for recent Intel CPUs. This driver leads to a different behavior in C-states switching and causes performance deg... |
## 3.17 Troubleshoot System Replication | ## 3.17 Troubleshoot System Replication
This section describes how to analyze, avoid and solve problems related to system replication.
The following topics are covered:
- Performance: system replication appears to slow down transaction processing
- Setup and initial configuration problems
- Intermittent connectivity pr... |
## 3.17.1 Replication Performance Problems | ## 3.17.1 Replication Performance Problems
If system replication appears to slow down transaction processing, you can check the network and disk I/O on the secondary site.
A slow-down related to system replication can occur in the following scenarios:
- ASYNC replication mode is configured over long distances;
- multi... |
## 3.17.2 Setup and Initial Configuration Problems | ## 3.17.2 Setup and Initial Configuration Problems
This section outlines the analysis steps you need to take in case you face configuration problems during the initial HANA System Replication Setup.
The initial SAP HANA System Replication Setup steps are as follows:
- enabling the SAP HANA System Replication on the pr... |
## 3.17.3 Log Shipping Timeout | ## 3.17.3 Log Shipping Timeout
This section gives possible reasons why the log buffer may not be shipped in a timely fashion from the primary to the secondary site.
## Possible Cause 1: Synchronous Replication Mode and Log Area Full on the Secondary Site
If the system replication mode is set to SYNC - full sync , the ... |
## 3.17.4 Troubleshooting Cluster Management Problems | ## 3.17.4 Troubleshooting Cluster Management Problems
This topic gives hints about how to approach troubleshooting replication issues when a third-party cluster management solution is in use.
## SAP Python API and Third Party Solutions
SAP provides a Python-based API which can be used to manage high availability and d... |
## 3.17.5 LogReplay: Managing the Size of the Log File | ## 3.17.5 LogReplay: Managing the Size of the Log File
There is a risk in replication scenarios which use one of the logreplay operation modes of causing a disk full situation on the primary if the secondary system is not available for any reason; this can potentially lead to a complete freeze of the database.
The log... |
## 3.18 Network Performance and Connectivity Problems | ## 3.18 Network Performance and Connectivity Problems
This section covers the troubleshooting of problems on the network layer.
In cases where a subjectively slow performing system behaviour is experienced, but a first analysis of the SAP HANA resource utilization does not reveal any obvious culprits, it is often neces... |
## 3.18.1 Network Performance Analysis on Transactional Level | ## 3.18.1 Network Performance Analysis on Transactional Level
The following section should help you to perform an in-depth investigation on the network performance of specific clients.
## Prerequisites
SYSTEM administrator access using SAP HANA cockpit or hdbsql.
## Procedure
1. Use the monitoring view m_SQL_CLIENT_NE... |
## 3.18.2 Stress Test with NIPING | ## 3.18.2 Stress Test with NIPING
The SAP NIPING tool is a powerful tool which can be used to perform specific network stability tests.
## Prerequisites
You must have OS level access to the SAP HANA host and the client host.
## Procedure
Read SAP Note 500235 - Network Diagnosis with NIPING .
A stress test with SAP's N... |
## 3.18.3 Application and Database Connectivity Analysis | ## 3.18.3 Application and Database Connectivity Analysis
There are a number of ways to identify possible root causes for network communication issues between your application and the SAP HANA instance it is connecting to.
## Prerequisites
You have access to both the application and SAP HANA instance.
## Procedure
1. O... |
## 3.18.4 SAP HANA System Replication Communication Problems | ## 3.18.4 SAP HANA System Replication Communication Problems
Problems during initial setup of the system replication can be caused by incorrect configuration, incorrect hostname resolution or wrong definition of the network to be used for the communication between the replication sites.
## Context
System replication e... |
## 3.18.5 SAP HANA Inter-Node Communication Problems | ## 3.18.5 SAP HANA Inter-Node Communication Problems
This section contains analysis steps that can be performed to resolve SAP HANA inter-node communication issues.
## Procedure
1. If communication issues occur between different nodes within an SAP HANA scale-out environment, usually the SAP HANA tracefiles contain co... |
## 3.19 SAP HANA Dynamic Tiering (Deprecated) | ## 3.19 SAP HANA Dynamic Tiering (Deprecated)
Identify and resolve specific performance issues and enhance the performance of SAP HANA dynamic tiering.
## ξ Note Dynamic tiering is deprecated. SAP HANA Native Storage Extension replaces it. See SAP Note 3414255 .
Troubleshooting information for SAP HANA dynamic tiering ... |
## 3.19.1 Tools and Tracing | ## 3.19.1 Tools and Tracing
This section gives you an overview of the tools and tracing options available for SAP HANA dynamic tiering. |
## 3.19.1.1 Federation Trace | ## 3.19.1.1 Federation Trace
Federation trace can be turned ON to diagnose most issues with SAP HANA dynamic tiering.
Federation trace generates tracing information in the indexserver.ini trace file.
To enable federation trace:
```
ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini', 'SYSTEM') SET ('trace', 'fedtrace'... |
## 3.19.2 Query Plan Analysis | ## 3.19.2 Query Plan Analysis
The query plan shows the various operators involved in the query execution.
Queries referencing both SAP HANA tables and SAP HANA dynamic tiering tables are either:
- Executed in SAP HANA by pulling data from SAP HANA dynamic tiering
- Relocated to SAP HANA dynamic tiering, where the data... |
## 3.19.2.1 Statistics | ## 3.19.2.1 Statistics
Statistics help the query optimizer in choosing the right query plan. Missing statistics may prevent the query optimizer from selecting the optimal query plan.
When no statistics for an extended table are present, the query optimizer assumes the table size to be 1 million rows. If the actual tab... |
## 3.19.3 Data Loading Performance | ## 3.19.3 Data Loading Performance
SAP HANA dynamic tiering supports all data loading methods for extended tables. This section explores the various mechanisms for inserting data into extended tables, and recommends the optimal loading mechanisms.
In general, SAP HANA dynamic tiering is optimized for batch writes, lik... |
## 3.19.3.1 IMPORT FROM Statement | ## 3.19.3.1 IMPORT FROM Statement
If you have a CSV file for the data to be loaded, the IMPORT FROM statement is by far the best method for loading data into an SAP HANA dynamic tiering table.
The IMPORT FROM statement is sent directly to the SAP HANA dynamic tiering node for the data load. Currently, IMPORT FROM does... |
## 3.19.3.2 INSERT Statement with SELECT Statement | ## 3.19.3.2 INSERT Statement with SELECT Statement
If the data is present in another SAP HANA table, then INSERT-SELECT is a better loading method than the IMPORT FROM statement.
The query optimizer tries to relocate the INSERT-SELECT on an extended table to the SAP HANA dynamic tiering node. The SAP HANA dynamic tier... |
## 3.19.3.3 Parameterized Array Inserts | ## 3.19.3.3 Parameterized Array Inserts
Array insert is by far the most optimal mechanism to load data into an extended table.
SAP HANA dynamic tiering converts an array-insert into a LOAD statement on the SAP HANA dynamic tiering node.
Bulk load is controlled by the bulk_inserts_as_load and bulk_load_as_binary parame... |
## 4 Tools and Tracing | ## 4 Tools and Tracing
This section gives you an overview of the available tools and tracing options that are available. |
## 4.1 System Performance Analysis | ## 4.1 System Performance Analysis
As a first step to resolving SAP HANA performance issues, you can analyze detailed aspects of system performance in the SAP HANA studio on the Performance tab of the Administration editor.
When analyzing system performance issues, the information provided on the Performance tab enable... |
## 4.2 SQL Statement Analysis | ## 4.2 SQL Statement Analysis
A key step in identifying the source of poor performance is understanding how much time SAP HANA spends on query execution. By analyzing SQL statements and calculating their response times, you can better understand how the statements affect application and system performance.
You can anal... |
## 4.2.1 Analyzing SQL Traces | ## 4.2.1 Analyzing SQL Traces
The SQL trace allows you to analyze the response time of SQL statements within an object.
## Procedure
1. In the Administration editor, choose the Trace Configuration trace and edit the SQL trace.
2. In the Trace Configuration dialog box, specify a name for the trace file, set the trace s... |
## 4.2.1.1 SQL Trace | ## 4.2.1.1 SQL Trace
The SQL trace collects information about all SQL statements executed on the index server (tenant database) or name sever (system database) and saves it in a trace file for further analysis. The SQL trace is inactive by default.
Information collected by the SQL trace includes overall execution time ... |
## 4.2.2 Analyzing Expensive Statements Traces | ## 4.2.2 Analyzing Expensive Statements Traces
The expensive statements trace allows you to identify which SQL statements require a significant amount of time and resources.
## Procedure
1. In the Administration editor, choose the Trace Configuration trace and edit the expensive statements trace.
2. In the Trace Confi... |
## 4.2.2.1 Expensive Statements Trace | ## 4.2.2.1 Expensive Statements Trace
Expensive statements are individual SQL statements whose execution time exceeds a configured threshold. The expensive statements trace records information about these statements for further analysis and is inactive by default.
If, in addition to activating the expensive statements ... |
## 4.2.3 Analyzing SQL Execution with the SQL Plan Cache | ## 4.2.3 Analyzing SQL Execution with the SQL Plan Cache
The SQL plan cache is a valuable tool for understanding and analyzing SQL processing.
Before it is executed, every SQL statement is compiled to a plan. Once a plan has been compiled it is better to reuse it the next time the same statement is executed rather tha... |
## 4.3 Query Plan Analysis | ## 4.3 Query Plan Analysis
In SAP HANA, to identify queries that are inefficiently processed, you can both technically and logically analyze the steps SAP HANA took to process those queries.
From a technical perspective, analyzing query plans allows you to identify long running steps, understand how much data is proces... |
## 4.3.1 Analyzing SQL Execution with the Plan Explanation | ## 4.3.1 Analyzing SQL Execution with the Plan Explanation
You can generate a plan explanation for any SQL statement and use this to evaluate the execution plan; you may be able to use this information to optimize the query by reducing the run time or the memory consumption.
The Explain Plan can be collected in severa... |
## 4.3.2 Analyzing SQL Execution with the Plan Visualizer | ## 4.3.2 Analyzing SQL Execution with the Plan Visualizer
To help you understand and analyze the execution plan of an SQL statement, you can generate a graphical view of the plan.
## Procedure
1. Visualize the plan of the SQL statement in one of the following ways:
- a. Enter the statement in the SQL console and choos... |
## 4.3.2.1 Overview Page | ## 4.3.2.1 Overview Page
Visualization of execution plans automatically displays an Overview page.
Some important KPIs required to begin a performance analysis are shown on the Overview page so that you can see a big picture of what is going on before going into the complex details.
## Overview Page
The following table... |
## 4.3.2.2 Statement Statistics | ## 4.3.2.2 Statement Statistics
Visualization of execution plans for procedures displays a set of statistics for each SQL statement involved in a procedure.
## Context
This set of statistics is automatically visualized when a procedure is executed and it provides a good starting point for analyzing performance of proce... |
## 4.3.2.3 Timeline View | ## 4.3.2.3 Timeline View
The Timeline view provides a complete overview of the execution plan based on visualization of sequential time-stamps.
## Context
The following pieces of information are available in the view:
- X-axis: time elapsed since query execution,
- Y-axis: list of operators
- Duration of each operator ... |
## 4.3.2.4 Operator List for Plan Visualizer | ## 4.3.2.4 Operator List for Plan Visualizer
The Operator List view is used within the context of the Plan Visualizer perspective. It lists detailed characteristics of all operators within a current plan, both visualized and executed.
The Operator List can be used to dynamically explore the operator set along user defi... |
## 4.3.2.5 Network View | ## 4.3.2.5 Network View
The Network View can visualize sequential network data transfers between different servers based on their given timestamps when an execution plan is based on a distributed query.
## Context
The following pieces of information are available in the view:
- X-axis: servers involved,
- Y-axis: time ... |
## 4.3.2.6 Tables Used | ## 4.3.2.6 Tables Used
The table usage view provides an overview on which tables have been used during the processing of a statement.
## Context
The Tables Used view can be used to cross-check your business understanding about which tables are needed to fulfill a given SQL statement.
The view displays 3 metrics per tab... |
## 4.3.2.7 Performance Trace | ## 4.3.2.7 Performance Trace
The Performance Trace view displays the list of operators that have performance trace data. The data can be viewed by selecting any of the operator shown in the list.
## Context
The view consists of two main sections:
- The left panel shows list of operators you can select to view performan... |
## 4.3.2.8 Plan Trace | ## 4.3.2.8 Plan Trace
Use the plan trace to collect SQL queries and their execution plans, executed in a given time frame for a particular application session.
## Context
The plan trace enables you to capture details of selected SQL queries and their execution plans. For each SQL query traced, you can visualize the exe... |
## 4.3.2.9 Calculation Scenario Visualization | ## 4.3.2.9 Calculation Scenario Visualization
By navigating to a particular calculation view in the Systems view, you can access the Visualize View context menu, which will visualize the calculation scenario associated with the view.
The calculation scenario visualizer consists of following three main sections:
- left:... |
## 4.4 Result Cache | ## 4.4 Result Cache
The static result cache and the dynamic result cache are configurable applications of caching query results to gain performance benefits.
Caching is used widely in SAP HANA as a strategy to improve performance by re-using queried data rather than re-reading and processing the data every time it is r... |
## 4.4.1 Static Result Cache | ## 4.4.1 Static Result Cache
Complex SQL views and calculation views place a heavy load on the system. You may be able to use the static result cache to reduce CPU consumption (and thus to increase overall system throughput) or to reduce the response time of queries.
Frequently accessed views may consume an excessive ... |
## 4.4.1.1 Creating and Using the Static Result Cache | ## 4.4.1.1 Creating and Using the Static Result Cache
This topic gives a number of examples to illustrate how you can use the result cache.
To save memory cached SQL views are based on aggregated results (SUM, MIN, MAX and COUNT are supported); only the aggregated values are stored. The SQL optimizer uses the aggregati... |
## 4.4.1.2 Resources for Testing the Result Cache | ## 4.4.1.2 Resources for Testing the Result Cache
This topic uses an example calculation view to illustrate how you can work with tools to test the result cache.
After caching a view it is important to verify that the view has been successfully cached, that correct results are returned, that the cached views is actuall... |
## 4.4.2 Dynamic Result Cache | ## 4.4.2 Dynamic Result Cache
The dynamic result cache may be used to improve the performance of queries which are frequently executed.
In comparison to the static result cache, running queries against a dynamic result cache may be a better option for increasing the performance of queries. The dynamic result cache off... |
## 4.4.2.1 Working With The Dynamic Result Cache | ## 4.4.2.1 Working With The Dynamic Result Cache
This section includes examples of creating the cache and the configuration parameters available to modify the operation of caches and monitoring usage.
## SQL Syntax
The OPTIMIZER ADMIN privilege is required to execute commands to configure the dynamic result cache.
You ... |
## 4.4.2.2 Testing the Dynamic Result Cache | ## 4.4.2.2 Testing the Dynamic Result Cache
You will need to test queries using a dynamic result cache to verify the performance benefit. Some general guidance to support testing is given here.
## Testing and Verification
Important resources for testing include Explain Plan and Plan Visualization, and the monitoring vi... |
## 4.5 Advanced Analysis | ## 4.5 Advanced Analysis
If have you an advanced knowledge of SAP HANA and SQL databases and you suspect that automated processes are making poor decisions that have negative impacts on query performance, you can perform advanced analyses to better understand how those decisions were made.
In SAP HANA cockpit you can u... |
## 4.5.1 Analyzing Column Searches (qo trace) | ## 4.5.1 Analyzing Column Searches (qo trace)
In SAP HANA, if a column search takes a long time, you can analyze how the query-optimizer performed the column search. A query-optimizer (qo) trace of a single SAP HANA table search provides the details you need for such an analysis.
## Context
The qo trace provides a lot... |
## 4.5.2 Analyzing Table Joins | ## 4.5.2 Analyzing Table Joins
In SAP HANA, if a query on joined tables takes a long time, you can analyze how the tables are joined and in what order. A join evaluation (je) trace of joined SAP HANA tables provides the details you need for such an analysis.
## Context
The je trace provides a lot of detailed informati... |
## 4.5.3 SQL Plan Stability | ## 4.5.3 SQL Plan Stability
SQL Plan Stability can be used to guarantee the consistent optimal performance of select statements by capturing query execution plans so that exactly the same plan can be reused when the query is executed again.
In SAP HANA, the SQL query processor parses SQL statements and generates SQL q... |
## 4.6 Additional Analysis Tools for Support | ## 4.6 Additional Analysis Tools for Support
To complement the standard tools for performance analysis, SAP HANA provides additional analysis tools that SAP Support can use to help determine the cause of performance issues.
The following analysis tools are available in SAP HANA; however, these tools are intended only f... |
## 4.6.1 Performance Trace | ## 4.6.1 Performance Trace
The performance trace is a performance tracing tool built into the SAP HANA database. It records performance indicators for individual query processing steps in the database kernel. You may be requested by SAP Support to provide a performance trace.
Information collected includes the process... |
## 4.6.2 Kernel Profiler | ## 4.6.2 Kernel Profiler
The kernel profiler is a sampling profiler built into the SAP HANA database. It can be used to analyze performance issues with systems on which third-party software cannot be installed, or parts of the database that are not accessible by the performance trace. It is inactive by default.
The ke... |
## 4.6.3 Diagnosis Information | ## 4.6.3 Diagnosis Information
You can collect diagnosis information (a full system info dump) in the SAP HANA studio, in SAP HANA cockpit or using command line scripts.
To collect this information in SAP HANA studio open the Administration Editor and navigate to Diagnosis Files Diagnosis Information . Use the Collect... |
## 4.6.4 Analysis Tools in SAP HANA Web-based Developer Workbench | ## 4.6.4 Analysis Tools in SAP HANA Web-based Developer Workbench
There are a number of tools available for application performance analysis in the SAP HANA Web-based Developer Workbench.
## SQL Console
The extended SQL Console (part of the Catalog perspective) supports implicit and explicit performance measurement wh... |
## 5 SAP HANA Database monitoring with Solution Manager | ## 5 SAP HANA Database monitoring with Solution Manager
This topic gives information about SAP HANA database monitoring with Solution Manager.
## Setting up Solution Manager
SAP Solution Manager can be used to monitor one or more SAP HANA databases. A starting point to find all the information you require for the setup... |
## 6 Alerts and the Statistics Service | ## 6 Alerts and the Statistics Service
Alert checkers are part of the statistics service which is a central element of SAP HANA's internal monitoring infrastructure.
The statistics service is a key administration resource which notifies you when potentially critical situations arise in your systems. The statistics serv... |
## 6.1 Alerts Reference | ## 6.1 Alerts Reference
Details of alerts in HANA 2.0 SPS07.
| ID: | 0 |
|------------------------|-----------------------------------------... |
## 7 SAP HANA SQLDBC Error Codes | ## 7 SAP HANA SQLDBC Error Codes
Error code reference for SQLDBC.
When using Netweaver to connect different SQLDBC libraries to databases such as SAP HANA it can be helpful to have a short description for the various error codes. The following table is a list of SAP HANA SQLDBC Error Codes which may be reported by the ... |
## 8 Important Disclaimer for Features in SAP HANA | ## 8 Important Disclaimer for Features in SAP HANA
For information about the capabilities available for your license and installation scenario, refer to the Feature Scope Description for SAP HANA.
## Important Disclaimers and Legal Information
## Hyperlinks
Some links are classified by an icon and/or a mouseover text. ... |
## 1 Introduction | ## 1 Introduction
## Target Audience
- Technology consultants
- Security consultants
- System administrators
This document is not included as part of the Installation Guides, Configuration Guides, Technical Operation Manuals, or Migration Guides. Such guides are only relevant for a certain phase of the software life cy... |
## 2 Before You Start | ## 2 Before You Start
## Fundamental Security Guides
SAP S/4HANA is based on ABAP Platform and the SAP HANA Platform. With respect to SAP Fiori apps, SAP Gateway plays a fundamental role as well. This means that the corresponding Security Guides are also applicable for SAP S/4HANA.
Whenever other guides are relevant, a... |
## 3 User Administration and Authentication | ## 3 User Administration and Authentication
## Overview
SAP S/4HANA generally relies on the user management and authentication mechanisms provided with ABAP Platform, in particular the Application Server ABAP and the SAP HANA Platform. Therefore, the security recommendations and guidelines for user administration and a... |
## 3.1 User Management | ## 3.1 User Management |
## 3.1.1 Non-SAP Fiori Technology | ## 3.1.1 Non-SAP Fiori Technology
User management for SAP S/4HANA uses the mechanisms provided with the Application Server ABAP, such as tools, user types, and password concept. For an overview of how these mechanisms apply for SAP S/4HANA, see the sections below. In addition, we provide a list of the standard users r... |
## 3.1.2 SAP Fiori Technology | ## 3.1.2 SAP Fiori Technology
For details on the user management and authorization concepts used in SAP Fiori apps, go to https:/ / help.sap.com/s4hana\_op\_2021, enter SAP Fiori Overview into the search bar, press Enter , and open the search result with that title. |
## 3.2 User Data Synchronization | ## 3.2 User Data Synchronization
By synchronizing user data, you can reduce effort and expense in the user management of your system landscape. Since SAP S/4HANA is based on ABAP Platform, you can use all of the mechanisms for user synchronization in ABAP Platform here.
For more information, go to https:/ /help.sap.com... |
## 3.3 Role Administration | ## 3.3 Role Administration
Business roles in SAP S/4HANA represent the central object used to structure users' access on the frontend server.
For more information, go to https:/ /help.sap.com/s4hana\_op\_2021 and proceed as follows:
- General information on role maintenance in systems based on Application Server ABAP: ... |
## 3.4 Integration into Single Sign-On Environments | ## 3.4 Integration into Single Sign-On Environments
## Non-Fiori Technology
SAP S/4HANA supports the single sign-on (SSO) mechanisms provided by Application Server ABAP technology. Therefore, the security recommendations and guidelines for user management and authentication that are described in the ABAP Platform Secur... |
## 4 System Hardening with SAP Security Notes | ## 4 System Hardening with SAP Security Notes
## Backlog of Existing Security Notes
There is also a backlog of security notes that require your attention during early phases of your SAP S/4HANA system setup. The following is a list of important security notes which include manual configuration steps and which you need ... |
## 5 SAP S/4HANA System Landscape Information | ## 5 SAP S/4HANA System Landscape Information
There are various ways of deploying SAP S/4HANA in your new or already existing system landscape. This section describes some examples.
## Example: SAP S/4HANA New Installation
A new installation of SAP S/4HANA needs to run on the SAP HANA database. It is recommended to use... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.