1. Search a parameter in profiles files
grep -wi "login/ticket_only_by_https\|login/create_virtual_user_sapstar" DS4_D00_vhcxfds4ci DS4_ASCS01_vhcxfds4cs DEFAULT.PFL
For BASIS Administration & HANA
1. Search a parameter in profiles files
grep -wi "login/ticket_only_by_https\|login/create_virtual_user_sapstar" DS4_D00_vhcxfds4ci DS4_ASCS01_vhcxfds4cs DEFAULT.PFL
1. sapcontrol -nr 00 -function GetProcessList ==> Check SAP Instance Status (shows for single instance)
2. sapcontrol -nr 00 -function J2EEGetProcessList ==> Check SAP Instance Status for Java instances
3. sapcontrol -nr 00 -function GetSystemInstanceList ==> Gives the status of all instances in the SAP system
------------------------------------------------------------------------------------------------------------------------
4. sapcontrol -nr 00 -function StartSystem ==> Starts all services controlled by the instance.
5. sapcontrol -nr 00 -function StopSystem ==> Gracefully stops the SAP system.
6. sapcontrol -nr 01 -function Start ==> Used when starting only one instance
7. sapcontrol -nr 00 -function Restart
--------------------------------------------------------------------------------------------------------------------------
8. sapcontrol -nr 00 -function StartService PRD ==> Used to Start sapstartsrv Service
9. sapcontrol -nr 00 -function StopService ==>Used to Start sapstartsrv Service
10. sapcontrol -nr 00 -function GetVersionInfo ==> It will give the kernel information
11. sapcontrol -nr 00 -function ABAPGetWPTable ==> displays the ABAP Work Process Table for a specific SAP instance from the OS level, similar to what you see in SM50
SAP Web-dispatcher acts as a reverse proxy and load balancer that sits in front of SAP systems and handles HTTP/HTTPS traffic.
Think of it as the gatekeeper for handling the requests from the below:
SAP Fiori
SAP GUI for HTML
Web Dynpro
OData / Gateway services
ICF services
It decides:
Which SAP server should handle a request
How traffic is balanced
Whether a request is allowed or blocked
| The user sends the requests through the browser (http/https). then the request go to the load balancer, then to the web dispatcher. | Browser → Internet/Corporate Network → Firewall → LB → LB→Webdispatcher→ICM→Abap dispatcher→workprocess. If any user reports any issue saying that they are not able to connect to SAP from a browser-based connection, we can check the ICM log from SMICM transaction. |
1. What is the location of Reginfo File in SAP?
/usr/sap/<SID>/SYS/global/reginfo
/usr/sap/<SID>/<INSTANCE>/data/reginfo
Statement 'SELECT * FROM SAPDGT.USR02 WHERE BNAME = 'DDIC' AND MANDT = '310''
Statement 'update USR02 set uflag=0 where mandt='310' and bname='DDIC''
update USR02 set PASSCODE = 'CELAzure1234#' where mandt='310' and bname='DDIC'
to Export and Import Certificates in SAP SYSTEM before and after Refresh:
Procedure: follow the steps specified in the blog:
https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-members/restore-pse-in-strust/ba-p/13274842
Process:
a). You need to log in to the application server through Putty and switch to the sidadm user.
Run the “R3trans -d” command. You will get the trans.log. Open that file, and you will get the version of the Hana database.
or
b). Another way is to check the work process log files from the work directory. Location—/usr/sap/SID/DVEBMGS00/work
Check the work process log file with the name dev_w[n].
General ways to check the HANA DB version
What are the ways to check the status of HANA Database
Hana DB status can be checked using
./saprouter -r -V 2 -K "p:CN=SAPRTRAPP, OU=0000036089, OU=SAProuter, O=SAP, C=DE" &
| Database | Port |
|---|---|
| SystemDB | 3<00>13 |
| Tenant DB | 3<o0>15 |
SAP HANA HSR provides High Availability and Disaster recovery
Fundamentals of HSR:
SAP HSR has two fundamental concepts
1. HSR Replication Mode: Synchronous, Synchronous to memory, Asynchronous
2. HSR Operation Modes: Delta shipping, Log replay or log replay with read access
The HSR replication mode determines the behavior of secondary system in acquiring the data from the primary system
The primary system waits for an acknowledgment from the secondary system before committing transactions.
Ensures no data loss.
Best for high-availability setups within low-latency environments.
Requires a reliable, high-speed network.
Ensures zero data loss but only guarantees that data is in the secondary system’s memory (not persisted to disk).
Faster than SYNC since it doesn’t wait for disk writes on the secondary system.
Suitable for systems with strict uptime requirements.
The primary system does not wait for the secondary system to acknowledge the transaction.
Some data loss is possible in case of failure before replication completes.
Best for disaster recovery setups over long distances.
Similar to SYNC but ensures the secondary system has fully committed the transaction before acknowledging.
Used in rare cases where absolute consistency is critical.
High availability within a data center? → SYNC or SYNCMEM
Disaster recovery across regions? → ASYNC
Extreme data consistency required? → FULLSYNC
HSR Operation mode determines how the data is sent and processed by the secondary system
SAP HANA INSTALLATION:
HANA Database supports the below 2 operating systems. (Check supported versions in SAP PAM)
/hana/data, /hana/log, /hana/shared/hana/backupsapadm (SAP Management User)sidadm (SAP Instance Admin User)