SAP HANA configuration files and location

 

 

About SAP HANA Configuration file.

SAP HANA Configuration files contains SAP HANA Database configuration settings.

There are two types of Configuration files in SAP HANA Database.

1. Global Configuration file
   
2. Local Configuration file 

Global Configuration files contains configuration of all hosts.

Local Configuration file contains configuration of specific hosts.

SAP HANA Configuration files location.

 The configuration files (.ini files) are located by default in the following directories

/usr/sap/<SID>/SYS/global/hdb/custom/config 

• global.ini
• indexserver.ini
• nameserver.ini

For host-specific configuration settings

$SAP_RETRIEVAL_PATH = /hana/shared/<SID>/HDB02/<hostname>

• sapprofile.ini
• daemon.ini

 

Easy way to do SAP HANA housekeeping trace files.

 

Easy way to do SAP HANA housekeeping trace files.

Now SAP HANA have automatically compresses and archives old trace files via SAP HANA Studio UI. but today we are going to See how to do manually via SQL Command.

Follow the below steps to remove the trace files in SAP HANA.

Step 1: Logon to the SAP HANA server as SID<ADM>.

Be aware that in a scale out scenario, you will have to logon to each and every host.

 Step 2: Navigate to the trace file folder
 

Just use the predefined shell command alias ‘cdtrace‘

techrelam:/usr/sap/TRM/HDB00> cdtrace

echrelam:/usr/sap/TRM/HDB00/techrelam/trace>

Step 3: Create the “traces_bck” folder
 

For example I simply create the “traces_bck” folder as a sub-folder of the actual trace folder.

You might and probably should create it at a different location, to release the storage space in the trace file folder.

techrelam:/usr/sap/TRM/HDB00/techrelam/trace> mkdir traces_bck

4. Move old trace files into the new folder:

This can take time…

techrelam:/usr/sap/TRM/HDB00/techrelam/trace>find . -type f -mtime +10 -print | xargs -I {} mv {} traces_bck/
 

you don’t actually need the trace files any more, you may delete this folder later on.

In general, it usually doesn’t make sense to keep the trace files generated by older revisions.

Exceptions to this general approach could be, that you faced bugs that you still wait to see fixed or to compare messages from normal/baseline system operations.  

Tcode: SP12 SAP TemSe Consistency Check

 

Tcode: SP12 SAP TemSe Consistency Check.

   SAP TemSe consistency check is to check whether entries in the TemSe data store are consistent. The TemSe consistency checks the header entry in table TST01 (TemSe objects) and object associated with the header entry; it can be stored in the file system or in the database table TST03 (TemSe data of the object). You can determine TemSe inconsistencies in dialog and delete them using the appropriate pushbuttons in transaction SP12.

Execute SP12 tcode.

Click  TemSe Data Storage ==> Consistency check. This will wait a moment.

Here no Consistency in this Spool.

Same Consistency check we can Check via report RSTS0020/RSTS0030 also.

This Report execute in background this list will show any inconsistency listed here. Execute the report at least once more after an interval of around 20 minutes. You must determine the exact interval based on the length of the running jobs.

To perform the deletion, start report RSTS0030 in dialog for the subareas of TemSe, in which the consistency check found inconsistent objects.

Select TST01 and TST03 for the check.

As soon as the report has generated the object list, you can delete either all or the selected inconsistencies.

Important note: 

Example, if a user is writing data to the TemSe during the consistency check. A check must be performed more than once to ensure that the inconsistency is not merely temporary. Inconsistencies that appear in multiple logs are actual inconsistencies and should be deleted. However, you cannot delete TemSe inconsistencies in the background.

Temporary inconsistencies are not actual inconsistencies and must not be deleted. Temporary inconsistencies may occur

reference : sap help doc.

How to Connect Remote Systems in SAP Web IDE

 How to Connect Remote Systems in SAP Web IDE.

Before Connect Remote System in SAP Web IDE we need to check some prerequisites.

Prerequisites

 
 If you want to connect to an ABAP system, make sure you have checked the requirements

• You have installed SAP_BASIS 7.31 SP 14 or 7.40 SP 8 or later.
• If you are using SAP_BASIS 7.31, make sure that the software components of the UI add-on for SAP NetWeaver (UI_700 and UI5_731) are installed.

Configuration 

1.Create some folders to explain.

 

 Yes, these all are folders, destinations is also a folder

2. Create for your on-premise SAP System a text file.
delete the extension, it should look similar to this screenshot  

 

3. Now open the text file with your preferred editor and copy paste the following lines.

Description=<mysystem> description
Type=HTTP
TrustAll=true
Authentication=NoAuthentication
Name=<mysystem>
ProxyType=Internet
URL=https\://<host>\:<port>
WebIDEUsage=<add a value according to the table below>
WebIDESystem=<mysystem>
WebIDEEnabled=true
sap-client=<SAP client number for ABAP systems only. Delete this line if you are not using an ABAP system.>

 
4. We need to fill the System details Should be look like this at the end.

The yellow highlighted part is in my example everything you can insert here.

You have to choose, what you want to do with your connection.

Also the Proxy Type could be On-premise, when your behind a firewall

5.When you have finished that, you have to configure in your SAP system you want to connect also.
 

Log on to your system and open transaction code SICF

Make sure you have activated the following nodes including all subnodes!!

• /sap/opu/odata

for the OData functionality of Gateway

• /sap/bc/ui5_ui5

for executing SAPUI5 applications from the SAPUI5 SAP ABAP Repository

• /sap/bc/adt

for extensibility scenarios and developing or deploying to SAPUI5 SAP ABAP Repository

• /sap/bc/bsp
• /sap/bc/ui2

for working with fact sheets

• /sap/hba

for SAP HANA XS OData services

When you have finished all of the above you can start your Orion-server again and try to consume a service. It should appear a logon dialog when trying that and everything is fine.

 

 

 

Installing SAPWebIDE Personal Edition

 

Installing SAPWebIDE Personal Edition Steps.

How to setup the SAP WebIDE personal edition?

Goto visit tools.hana.ondemand.com and browse to the SAPUI5-tab 

==> Download the preferred version given below.

 

Follow the guide section install SAP Official help document. Click here! 

 Kindly do not use the build in zip tool from Microsoft. Use the 7zip  software and it worked fine for me its true. Create the folder in C directory extract SAP WebIDE file on that folder based on Sap help document.

Extract the zipped files to C:\SAPWebIDE.

The folder-structure should look like this in the end:

 

Double click the Orion.exe setup file and wait for installation completed.

Start the SAP WebIDE and test, if you can reach the website

http://localhost:8080/webide/index.html
 

==> To start the WebIDE you have to go to the folder eclipse and start the orion.exe (marked yellow above)

This window Command prompt should show up  below screenshot.

 

When your at that point, the local parameters look all fine for the moment and you can proceed furture.

Now System is ready to connect On-Premise system .

Before that we need to create a logon user name only one userid will allow to create in SAPwebide.

 

 

Create a new account.

 

Now login to the SAP WebIDE.

 

 

Now SAP WebIDE is ready to connect the System.

How to add the System in SAP WEBIDE will see on upcoming Post.