Training - Administration SAP HANA
Troubleshooting and support
In this SAP Solution Manager training course, we teach you how SAP Solution Manager works. You will get the necessary know-how to implement SAP SolMan yourself.
In the default scenario, the support packages in the queue are fully loaded. In the event of an error, you will not be able to resume and complete the playback successfully unless the error(s) are resolved. Prerequisites The queue is already defined. Procedure To set the scenario you want, select Additions Settings. Select the desired scenario. Select Insert Support Package Queue. You can also use this function to restore an aborted commit procedure. The status bar provides information on the progress of the commit and the latest steps of the SAP Patch Manager. During the recording, you may get into the modification comparison (SPDD, SPAU). If you are playing with the default scenario, you must immediately perform the comparison of Dictionary objects (transaction SPDD), whereas when you compare Repository objects (transaction SPAU), you have the choice to skip it first and perform it later (modification comparison [page 22]). The mode is blocked while a Support Package is being introduced. To avoid repeated login, open a second mode before inserting the queue.
Storage Management Parameters in the SAP System
The application layer is the core of an R/3 SAP Basis system. This layer communicates in both directions, to the presentation layer and to the database layer. The application programs on the application servers request the required data from the database layer, process it, prepare it for the user and pass it on to the presentation layer. Data that the user enters in the SAP GUI is passed on to the database via the application servers.
You would like to know more about what is happening on your SAP systems - then I recommend that you take a closer look at the Solution Manager Usage Procedure Logging (UPL) functionality. What code is often executed? Which database tables are accessed regularly? What unused developments exist? - The UPL provides answers to these questions. You can implement the functionality into your existing SAP landscape without additional licence costs and with moderate effort. What information does the UPL provide? Usage Procedure Logging is used to log and record user behaviour data roughly comparable to the ST03N workload statistics. UPL is able to record the call and execution of the following ABAP objects: Reports Functional Blocks Classes Methods Subroutines SQL Calls In addition, UPL is able to detect dynamic programme calls and generate transparency about the modifications used. All usage data is recorded in detail and automated and, if desired, made available centrally in the SAP Solution Manager. Benefits 1) Hardly measurable Performance Impact 2) Central collection of data of all systems in the SAP Solution Manager's BW 3) No complex setup 4) Once activated, the collector and extractor jobs run regularly and without further manual activities Possible usage scenario If you have Solution Manager 7.2 in use, you can use UPL within the framework of "Custom Code Lifecycle Management" (in German: management of customer developments). After one activation of the BW content and some standard jobs, you select one or more systems for which you want to activate UPL. If you already have the SP05 installed, there is a separate "Guided Procedure" for configuring the UPL in SOLMAN_SETUP.
The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.
Based on a client/server architecture, SAP Basis includes configuration, a relational database management system, and a graphical user interface.
The role of the SME describes an expert in a particular field, such as SME databases or SME-SAP-HANA, in the context of SAP products and is gaining in importance due to new technologies and thematic areas.