Home » Posts tagged '#SAP' (Page 2)

Tag Archives: #SAP

Start Stop SAP HANA DB using sapcontrol

To start and stop an SAP HANA database using the sapcontrol tool, you can execute the following commands:

  1. Start HANA database:
    • sapcontrol -nr <instance_number> -function StartSystem HDB
    • Replace <instance_number> with the number of the HANA instance you want to start. For example, if you want to start instance 00, the command would be:
    • sapcontrol -nr 00 -function StartSystem HDB
  2. Stop HANA database:
    • sapcontrol -nr <instance_number> -function StopSystem HDB
    • Replace <instance_number> with the number of the HANA instance you want to stop. For example, to stop instance 00:
    • sapcontrol -nr 00 -function StopSystem HDB

Note: The sapcontrol command requires administrative privileges, so you might need to execute it as a superuser or with appropriate administrative permissions. Also, ensure that the sapcontrol tool is in your system’s PATH or provide the full path to the sapcontrol executable in the command.

Start stop of HANA Database with HDB

To start and stop an SAP HANA database, you can use the following commands:

  1. Start HANA Database:
    • On Linux: sudo -u <SID> HDB start
    • On Windows: HDB start
    Replace <SID> with the System ID of your HANA database.
  2. Stop HANA Database:
    • On Linux: sudo -u <SID> HDB stop
    • On Windows: HDB stop
    Again, replace <SID> with the System ID of your HANA database.

Tools used to check slowness in an SAP System.

In SAP systems, there are several transaction codes (Tcodes) and tools available to check and analyze system slowness. Here are some commonly used ones:

  1. ST03/ST03N: These Tcodes provide workload and performance statistics for SAP systems. You can analyze system performance, identify top transactions, and check response times.
  2. STAD: This Tcode allows you to analyze the workload of the SAP system and provides detailed statistics on user activities, executed transactions, and response times.
  3. SM50/SM66: These Tcodes display the process overview and can help identify any long-running or stuck processes that might be causing system slowness.
  4. ST05: This Tcode is used for SQL trace and can help analyze the performance of database calls made by SAP transactions. It allows you to identify slow-performing database queries.
  5. SE30: This Tcode is used for runtime analysis and can help identify performance bottlenecks in ABAP programs. It provides detailed information about the execution time of each statement and subroutine.
  6. SM21: This Tcode displays the system log and can help identify any system-related errors or issues that might be causing performance problems.
  7. SAP Solution Manager: It provides a range of tools for monitoring and analyzing system performance, including End-to-End Root Cause Analysis (RCA) and Performance Monitoring Dashboards.
  8. SAP EarlyWatch Alert: It is a proactive monitoring service provided by SAP that analyzes system performance, identifies potential issues, and provides recommendations for performance improvements.
  9. SAP Performance Optimization Workload Analyzer (PWA): It is a powerful tool for analyzing workload and performance data. It helps identify performance bottlenecks, provides optimization recommendations, and supports capacity planning.

How to do mass RFC connection test in SAP?

Follow below steps to do mass rfc connection test

Goto SE38 -> RSRFCCHK,

Enter RFC destinations names (use wildchars)

RSRFCCHK

Description of Fields in above reports:

  • RFC destinations: Either provide RFC names or use a wildchar.
  • Connection Type: Choose from below available connection types.
    • I Connection to Application Server with Same Database
    • 3 Connection to ABAP System
    • 2 Connection to R/2 System
    • T Start External Program Using TCP/IP
    • L Reference Entry (Refers to Other Destination)
    • S Start External Program Using SNA or APPC
    • X RFC Using Special ABAP Driver Routines
    • M CMC Connection
    • H HTTP Connection to ABAP System
    • G HTTP Connection to External Server