Unlocking Digital Transformation with SAP RISE Private Cloud Edition (PCE)

Unlocking Digital Transformation with SAP RISE Private Cloud Edition (PCE) In a rapidly evolving digital economy, enterprises are under constant pressure to modernize their IT infrastructure while ensuring agility, security, and scalability. SAP RISE with SAP S/4HANA – Private Cloud Edition (PCE) is a game-changing offering that simplifies the path to cloud ERP transformation, empowering…

Set Up SAP HANA System Replication with the SAP HANA

HANA System Replication is one of the important topic in SAP HANA. Being used in the context of high availability and disaster recovery scenario, It is really important to learn how to setup HANA System Replication in multi-tier replication scenario.   In this scenario we are enabling HANA System Replication – In Multi-tier scenario.  …

|

Replication Modes between Sites : HANA Replication

Here i am explaining different replication Modes between Sites in the HANA Replication setup. Synchronous (SYNC) : The secondary system sends an acknowledgment back to the primary system as soon as the data is received and persisted to the log volumes on disk. Asynchronous (ASYNC): Asynchronous replication, the primary does not wait until the secondary sends…

statement_memory_limit

Parameter : statement_memory_limit Key Highlights :   statement_memory_limit parameter is used to control memory limit for single query execution. Sometime it happens if we don’t set any limit on query level then single execution of query takes complete HANA memory and result to the HANA crash . So it is really improvement to set proper value…

|

memorymanager –> Parameter : allocationlimit

Parameter : allocationlimit  Key Highlights : This parameter is very useful in the Multi-tenant database container (MDC) system to set memory limit on each tenant system. Example : If we have 4 tenant systems in the landscape then we can set on indexsever.ini file –> allocationlimit for each tenant system to the accepted memory limit for each tenant…

|

inifile_checker –> Parameter : interval

Parameter: interval   Description: Sets a time interval in seconds between two checks for differences of ini file parameters between primary and secondary systems in a system replication scenario. To disable/enable those checks, set the parameter [inifile_checker] enable. Value: Positive integer   Default: 3600 (seconds = 1 hour)   Restart required: No     Ref:…

|

inifile_checker–> exclusion_[|*][/]

Key Highlights: This parameter will help in the scenario where we don’t want to replicate few parameter from primary to secondary site. Scenario where we want to have different value of particular parameters in primary and secondary site. This parameter is helpful where replication on the primary site with [inifile_checker]/replicate = true is enables With parameter…

|

[inifile_checker]/enable=true & [inifile_checker]/replicate = true

  inifile_checker –> enable = True  &  [inifile_checker]/replicate = true Key Highlights : [inifile_checker]/replicate = true- This parameter is very useful in the scenario where we have muli -tier and multi-target replication setup in the landscape . If we are changing any parameter in the primary site and [inifile_checker]/replicate = true- parameter is enabled then automatically it will…

EHP8 Upgrade Error ‘SPDA_DISASSEMBLE_QUEUE’ EHP_INCLUSION Phase

Issue: During EHP8 upgrade ,we faced issue during SPDA_DISASSEMBLE_QUEUE step of  EHP_INCLUSION Phase. 4 ETQ399 … ERROR in patch queue handling 1 ETQ124 Scanned file ‘log/SPDA_EHP_INCLUSION.LOG’ from offset 548255 to 846628 for errors. 1EETQ399 Last error code set is: RFC system SID nr 00 function ‘SPDA_DISASSEMBLE_QUEUE’ 1EETQ399XRFC failed with code 1 key RFC_COMMUNICATION_FAILURE: 1EETQ399Xconnection closed without…

How to Fix “Start of UME Service Failed” in JAVA System

Issue: If your Java system server nodes are not coming up and in the server log files you see similar entries as below . Aug 2, 2019 12:22:39 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_125] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: “Name or password is incorrect (repeat logon)”. This message is critical if it appears during the…