Use Of Save Point Mechanism In SAP HANA Database | Techrelam

Use Of Save Point Mechanism In SAP HANA Database  

SAP HANA database persists in-memory data by using savepoints. Each SAP HANA service has its own separate savepoints. During a savepoints operation, SAP HANA database flushes all changed data from memory to the data volumes. The data belonging to a savepoint represents a consistent state of the data on disk and remains so until the next savepoint operation has completed. Redo log entries are written to the log volumes for all changes to persistent data. In the event of a database restart the data from the last completed savepoint can be read from the data volumes, and the redo log entries written to the log volumes since the last savepoint can be replayed. The frequency at which savepoints are defined can be configured in the persistence section of the global.ini file (every 5 minutes by default). Savepoints are also triggered automatically by a number of other operations such as data backup, and database shutdown and restart. 

Open SAP HANA DB connection to SAP | Techrelam

 

How to Open SAP HANA Database Connection to SAP via SAP Router?

First of all we can Determining the Used Server Name and the Ports (JDBC/SQL and HTTP(S))

You determine the HTTP(S) and JDBC ports according to the following pattern:

1. SAPStartSrv/HTTP port: 5<instance>13
2. HTTPS is used: 5<instance>14
3. JDBC/SQL port: 3<instance>15

For Example: The system has the instance number 21, the ports are 52113 for HTTP, 52114 for HTTPS, and 32115 for JDBC/SQL.

Add entry on the SAProuter :

1. Check which saprouttab Route-Permission table the SAProuter uses.
2. Create an entry of the following form in the corresponding table :                                                   P <IP-Address SAP-SR> <host name Server or IP address> <Port Application> 
3.  For SNC coding (SAPserv2):                                                                                                         KP "p:CN=sapserv2, OU=SAP router, O=SAP, C=DE" <IP Server> <port application> 
4.   Save the changed file. 

Example: 

P 122.307.2.5 Techrelam/IP 32115 

P 122.307.2.5 Techrelam/IP 52113 

KP "p:CN=sapserv6, OU=SAP router, O=SAP, C=DE Techrelam/IP 32115 

KP "p:CN=sapserv6, OU=SAP router, O=SAP, C=DE" Techrelam/IP 52113 

Note: A generic entry of type P * * * is not sufficient, because the wildcard character '*' for the port only activates the ports with numbers 3200 to 3299.

      5.  To import the changed table in the SAProuter, use the saprouter -n command without restart the router update the entry  or else  restart the SAProuter.

   6.   Check whether the SAProuter can reach the target hostname and IP address on the given port and can resolve the host name in your DNS for each server. If not, set up the network accordingly.

After add the entry in saprouter now logon to the SAp support portal and Creating a Service, Maintaining the System Data, and Opening the Connection to access SAP HANA Database.

1. Log on to SAP Support Portal, using the service connection (URL: https://support.sap.com/remote-support/remote-connections.html)

2. Choose Maintain Connections.

3. Choose the SAP HANA Database system ID of the system to which you want to create a service connection.

Creating a Service

1. Choose Manage Services.

2. Go to the Set Up Connection Types section.

3. Choose the icon in front of the SAP HANA database service name.

4. In the new window, enter the following data:

P ort Assignment: 

In the first line, enter the SAPStartSrv (HTTP/HTTPS) port 5<instance>13 

In the second line, enter the JDBC/SQL port 3<instance>15

Now enter the required field like contact person.

5. Choose Transfer to copy the selection at the end of the list.

Choose Back to navigate to the system view for service connections.

Opening the Connection at SAP Support Portal:

1. Choose Maintain Connections to display all active services.

2. Choose Open/Close Connections.

3. Choose the icon in front of the service to open the service connection.

4. Select the opening time (default value: 8 hours). 

5. Save your entries.

6. To open a network connection, use the Service Connector. The Service Connector must be installed once on your computer. It calls your SAProuter and connects to the SAP Support Portal backend.

7. Choose Start Service Connector to create the stfk.oez configuration file.

8. In the new window, choose Open. 

The Service Connector starts and opens the network connection between your SAProuter and the SAP Support Portal backend. The Service Connector indicates whether the network connection is opened successfully. 

Now connection is open, SAP Support can log on to the system by using transaction code STFK. 

ADD SAP HANA Database connection to Solution manager 7.2 | Techrelam

 ADD SAP HANA Database connection to Solution manager.

Using SAP saphostagent / sapdbctrl for NewDB connection establish between solman7.2 and HANA DB.

 If you want to use the SAP HANA database connect without a password, the following below prerequisites:

1. We need to monitor the hana database you require a database user with the monitoring role.
You can create a database user with the NewDB studio. Connect as the SYSTEM user and execute the following SQL commands:

CREATE USER <username> PASSWORD x<password>x
GRANT MONITORING TO <SID>DBCTRL

 
Then logon to the NewDB studio under the username <username> and execute the following command:

ALTER USER <Username> PASSWORD <password>

2. As the OS user <sid>adm, you must provide the user key <SID>SAPDBCTRL in hdbuserstore on the database server. You can check the existence of the user key with the following command:

hdbuserstore LIST <SID>SAPDBCTRL

If the user key does not exist, you can create it as follows:

hdbuserstore SET <SID>SAPDBCTRL <dbhost>:<port> <Username> <password>

The tool hdbuserstore is installed under the following paths:

/usr/sap/hdbclient or
/usr/sap/<SID>/hdbclient

3. To check whether the sapdbctrl queries without passwords work, execute the following command as OS user <sid>:
 

/usr/sap/hostctrl/exe/saphostctrl -function GetDatabaseStatus -dbname <SID> -dbtype hdb


If sapdbctrl responds with the following error text:
ERROR: Database user authentication failed: SQLDriverConnect: Connect with userkey failed!
then you must check the connect data in hdbuserstore again.

 

Types Of Schema in SAP HANA Database

 

Types Of Schema in SAP HANA database.

There are three types of Schema available in SAP HANA database The database schema is a way to logically group objects such as tables, views, stored procedures etc. 

1. User Defined Schema
2. System Defined Schema
3. SLT Derived Schema

 User Defined Schema:
These are created by user (Database administrator or System Admin)

SLT Derived Schema:
When SLT is configured, it creates schema in HANA system. All the tables replicated into SAP HANA system are contained in this schema

System Defined Schema:
These schemas are delivered with the SAP HANA database and contains HANA system information. There are system schemas like _SYS_BIC, _SYS_BI, _SYS_REPO, _SYS_STATISTICS etc..., 

How to Keep Shared Memory Over Restart in SAP HANA Database

 

How to Keep Shared Memory Over Restart in SAP HANA Database

       Here we can see How use the parameter keep_shared_memory_over_restart and set he value as true , SAP HANA will keep the row store in memory.If set to false the row store is generally recreated from scratch during the SAP HANA database startup.

Parameter.

Parameter Name       - keep_shared_memory_over_restart
Default Value           - true
About Parameter      - Is set to true or false, if true the row store data will stay in shared memory.

Parameter Path  - indexserver.ini -> [row_engine] -> keep_shared_memory_over_restart 

 

 

SAP HANA Trace and error Log file location

 

 

SAP HANA Trace and error Log file location?

Here we are going to check Hana Errors & Logs & location of SAP Hana Trace file location :

Path ==>      /usr/sap/<SID>/HDB<int no>/<hostname>/trace

                                                       or 

                   /hana/shared/<SID>/HDB<instno>/hostname/trace

Here you’ll get trace files for all SAP Hana Process/Services: