This blog will describe how you can tweak the Enqueue Replication 2 High Availability setup, and how you can benefit from of the new feature of Enqueue Replication 2 technology. When all application instances have been restarted, the dormant ERS should be restarted, the SCS cluster failed over and the remaining dormant ERS restarted.How to tweak your SAP S/4 HANA – Enqueue Replication 2 HA Setup When the instance has started successfully, it can be made active by reversing the isolation activities. Once isolated, the instance can be restarted to introduce the new kernel as space will detect the new version in /sapmnt and initiate a copy of the new version into the instance-specific executable directory. direct logon, transport system communication etc. Isolating the instance means preventing all access to the instance – e.g. In the preparation of the instance for RKS, we need to isolate the chosen instance. These steps should be performed for all instances of the SAP system being patched. The Rolling Kernel Switch for the SAP instances comprises the following steps: Once the SCS is prepared, physically switch in the new kernel by copying the newly prepared kernel into the /sapmnt/ file system. sapcontrol -nr 00 -function Parameter Value DIR_HOME | tail -1.The home directory of the SCS will generally be the working directory beneath the instance directory but can be checked using sap control on the SCS node as follows: Source and target versions kernels must be RKS compatible.Īfter downloading and preparing the new kernel and before starting the RKS, you need to prepare the central services (SCS). Copy the file “StoC.xml” located in the newly prepared kernel location to the directory of the SCS instance denoted by system parameter $DIR_HOME.Download relevant SAPEXE.SAR and SAPEXE.SAR archives and extract them in DIR_CT_RUN (central executable directory) using SAPCAR.Backup DIR_CT_RUN in we want to import new kernel patch.RFC’s must be configured with load balancing, if a single host is used, chances are to get they failed.VMC must be active in at least two AS ABAP instances or in none.We can verify this by checking if the UPD work process exists for all/ at least 2 application servers in the group.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |