SAP Basis Learnings

  Procedure:                                               SITE -A Enable system replication on the primary system(SITE A) as follows: In the Administration editor of SAP HANA studio, choose the  Configuration  tab and ensure that  log_mode  is set to "normal" in the  persistence  section of the  global.ini  file. Log mode  normal  means that log segments must be backed up. Log mode  overwrite  means log segments are freed by the savepoint (therefore only useful for test installations without backup and recovery). Do an initial data backup or create a storage snapshot. In multiple-container systems, the system database and all tenant databases must be backed up. As  <sid>adm  on the command line enable the primary for system replication and give it a logical name with the following command. The primary system must be online at this time: cd /usr/sap/<sid>/HDB<instancenr>/exe hdbnsutil -sr_enable --name=SITEA To check if the site has been successfully enable

  How much data wants to store in HANA DB? How much data is coming from Non-SAP System? How much data wants to use directly on top of HANA or NLS or Any Other ? Preparing Installation: 1.Main Memory sizing for static data 2.Main Memory sizing for Objects created during runtime (data load and query execution) 3.Disk Sizing 4.CPU Sizing Two Types of Sizing: User based Sizing (Small, Medium and High) Throughput based sizing (SAPS - no of hits on database)         1400 -- 1800 SAPS --- 1 CPU SAP HANA DB Sizing : will not follow none of the above but based on DATA

  Amazon EC2 M5 instances  are the latest generation of General Purpose Instances powered by Intel Xeon® Platinum 8175M processors. This family provides a balance of compute, memory, and network resources, and is a good choice for many applications. Amazon EC2 X1 instances  are optimized optimized for enterprise-class databases and in-memory applications. Amazon EC2 R4 instances are optimized for memory-intensive applications and offer better price per GiB of RAM than R3.

  Support Package Manager: Phases   The Support Package Manager informs you of the status of the phase currently being executed in the status bar. If you want to know which phases are executed for which scenario(test or standard scenario), run the program  RSSPAM10 .  The following list provides an overview of all the modules and phases and lists them in the order in which they are executed by the Support Package Manager: Preparation  Module        1.       PROLOGUE This phase checks whether you are authorized to import Support Packages.        2.       CHECK_REQUIREMENTS This phase checks various requirements for importing a Support Package, for example, whether the transport control program tp can log on to your system.        3.       DISASSEMBLE This phase unpacks files from the appropriate EPS parcels and saves them to the transport directory.        4.       ADD_TO_BUFFER This phase places the queue in the transport buffer of your system.        5.       MODIFY_BUFFER This phase

   Cleanup of backup catalog entries Cleanup of trace files Cleanup of SAP HANA alerts Cleanup of Dumps How to check the size of backup catalog? 1. Use below sql  SELECT T3.DESTINATION_PATH CATALOG_FILE_NAME,     T3.DESTINATION_TYPE_NAME FILE_TYPE,     TO_CHAR(TO_DECIMAL(T3.CATALOG_SIZE_MB,10,2))||' MB' CATALOG_SIZE,     TO_CHAR(T4.OLDEST_BACKUP_DATE,'YYYY/MM/DD HH24:MI:SS') OLDEST_BACKUP_DATE,     LPAD(T4.OLDEST_BACKUP_DAYS,18) BACKUP_RETENTION_DAYS,     TO_CHAR(CURRENT_TIMESTAMP,'YYYY/MM/DD HH24:MI:SS') ANALYSIS_TIME         FROM  (SELECT TOP 1 T2.DESTINATION_PATH,    T2.DESTINATION_TYPE_NAME,   T2.BACKUP_SIZE / 1024 / 1024  CATALOG_SIZE_MB      FROM  M_BACKUP_CATALOG T1,    M_BACKUP_CATALOG_FILES T2      WHERE T1.BACKUP_ID = T2.BACKUP_ID      AND T2.SOURCE_TYPE_NAME = 'catalog' AND T1.STATE_NAME = 'successful'      ORDER BY T1.SYS_START_TIME DESC ) T3,     (SELECT MIN(SYS_START_TIME) OLDEST_BACKUP_DATE,     DAYS_BET

   Note : we can't use SUM for migrating the sap releases 740 and below & Non - Hana DB 1.SUM 2.0 doesn’t support for release 740 2.SUM 1.0 doesn’t support for SAP ASE database   Hence we have to use SWPM  for migration and follow system copy method. SWPM - Migration Steps:- Preparations:                              1 . Export Preparation                             2.Table Splitting Export :                              1 . Database Instance Export Import :                              1 . Database creation                             2.Importing the Jobs (Tables)                             3.Table statistics update Post Processing  :                               1 .  Running SGEN                              2.Configuring DBACOCKPIT                              3.Configuring the Parameters                              4.Configuring & Triggering the Backup      1. Export Preparation :          Delete QCM Invalid Tables from SE14         Generate migration Key         Ke