Documente Academic
Documente Profesional
Documente Cultură
Link
http://scn.sap.com/community/hana-in-memory/blog/2013/05/27/andy-silvey--sap-
hana-command-line-tools-and-sql-reference-examples-for-netweaver-basis-
administrators
The SAP HANA Reference for SAP Basis Administrators was started because during studies for
HANATec Certification it was noticed that anybody interested in HANA Administration was
missing a one stop shop location and reference for the HANA Commands and Command Line
Tools and Administrator's SQL queries respective to the Basis Administrator's HANA
requirements.
The SAP HANA Reference for SAP Basis Administrators is a live SCN Community project, this
means it is continuously updated and extended to include the latest valuable knowledge on SAP HANA from the
Basis Administrator's perspective.
Everybody who has gems of knowledge anything from tips tricks to howto's on SAP HANA
from the Basis Administration perspective is positively welcomed and encouraged to join this
open source sharing SCN Community collaborative initiative to make this resource the most
powerful SAP HANA Basis Administration
resource available.
Let's together exploit the power of the SCN Community and unlock the value of the knowledge
and experience in the community to the benefit of all.
To contribute either add a comment at the bottom or email or private message me.
p.s.
if you click the View as PDF button on the right, then you can save this as a pdf onto your
phone or pc for offline access and reading - of course this work is live so come back from time to time and get
the latest version.
Contribution History
Interactive Contents
Used Memory
o 8e) FAQ: DB Users for the DBA Cockpit for SAP HANA
o 9d) Reactivating the SYSTEM user when no User with USER ADMIN is
Available
The story
o 17) HDBSQL
o 23) To check the state of the data backup, use the following command
o 26) hdbbackupdiag
o 33) hdbrename
o 34) hdbnsutil
o 43) The time stamps for the "Start Time" in Data Provisioning of HANA Studio
are UTC time
o 44) How to Check SUSE Linux Distribution Version and Patch Level
o 45) Remove the SAP HANA Extended Application Service (SAP HANA
scriptserver) from the topology of your SAP HANA database
o 46) HANA Alerts related to File System Utilization
o 47) Log Volume is Full and the Database Doesn't Accept any new Requests
o 47b) Move HANA Data and Log Files to a different Mount Point
o 48) Using the REGI Tool to Deploy Content for Delivery Units for example
Translated Texts
o 49) Homogenous System Copy on SAP HANA
o 58b) How to Handle Empty Column Store Tables have large size on disk
o 60) Optimal Settings for Suse Linux SLES 11 SP2 and SLES 11 for SAP SP2
o 60a) Hardware Configuration Guide and Software Installation Guide for SUSE
Linux Enterprise Server with SAP HANA and SAP Business One
o 60b) RedHat Linux Support For SAP HANA Since SPS08
o 64) Network Ports Used By SAP HANA Database For Internal And External
Communication
o 65) Troubleshooting Guide For SAP Business One 9.0 Running On SAP HANA
1) Stop HANA
1. ./HDB stop
2. /usr/sap/hostctrl/exe/sapcontrol -nr &-function StopSystem HDB
1. ./HDB start
2. /usr/sap/hostctrl/exe/sapcontrol -nr &-function StartSystem HDB
1. cdexe
2. ./sapcontrol -nr &-function &
1. /usr/sap/HDB/SYS/exe/hdb
which is linked to
1. /usr/sap/HDB/exe/linuxx86_64/hdb
2. imdbhdb:~ # su - hdbadm
3. imdbhdb:/usr/sap/HDB/HDB00> cdexe
4. imdbhdb:/usr/sap/HDB/SYS/exe/hdb> pwd
5. /usr/sap/HDB/SYS/exe/hdb
6. imdbhdb:/usr/sap/HDB/SYS/exe/hdb> cd ..
7. imdbhdb:/usr/sap/HDB/SYS/exe> ls -la
8. total 8 drwxr-x- 2 hdbadm sapsys 4096 2013-01-25 14:17 .
9. drwxr-x- 3 hdbadm sapsys 4096 2013-01-25 14:17 ..
10. lrwxrwxrwx 1 hdbadm sapsys 25 2013-01-25 14:17 hdb -> ../../exe/linuxx86_64/hdb
11. imdbhdb:/usr/sap/HDB/SYS/exe>
of an application the SAP HANA database provides several techniques to process such
accesses within the database. By doing so application logic is processed within the SAP
HANA
database procedures. The use of database procedures reduces the data volume to be
transferred
between the database and application server. In addition, compared to code running on the
application server level, a database procedure can more efficiently access data stored in the
database.
The disadvantage of database procedures, in general, is that they might somehow affect the
stability
of the database itself. In order to minimize the risk of destabilizing the SAP HANA database,
procedures can be performed on the script server. The script server is one of the SAP HANA
database servers, which has its own memory management and is therefore separated from the
main server. Its usage is optional. The script server does not store application data.
Full details of how to start and stop the Hana Script Server including setting automatic start of
the
1. /usr/sap/hdbenv.sh
2. /usr/sap/exe/hdbnameserver
1. /usr/sap/hdbenv.sh
2. /usr/sap/exe/hdbindexserver -console
6) hdbuserstore
Create a user key in the user store and store the password under this user key:
For example:
For example:
1. hdbuserstore LIST millerj
1. hdbsql -U &
For example:
1. hdbsql -U millerj
hdbuserstore Example of User Creation while solving saphostagent/sapdbctrl for HANA issue
The saphostagent functions for querying the database status and for
starting and stopping the database are now also available for the HANA.
a. To query information from the database, you require a database user with
the monitoring role.
You can create a database user with the HANA studio. Connect as the SYSTEM
user and execute the following SQL commands:
Then logon to the HANA studio under the username &and execute
the following command:
b. As the OS user &adm, you must provide the user key &SAPDBCTRL in
hdbuserstore on the database server. You can check the existence of the
user key with the following command:
If the user key does not exist, you can create it as follows:
/usr/sap/hdbclient
or
/usr/sap/&hdbclient
&-dbtype hdb
You can delete all installed license keys by executing the following SQL command
UNSET SYSTEM LICENSE ALL
[ +this Knowledge Base Article contains a fantastic overview including screenshots of the
actions in
HANA Studio and on the command line with SQL for checking all kinds of memory
consumption:
Show the Total Read Size and the the Total Write Size for each Volume since the Service
M_VOLUME_IO_STATISTICS_RESET
You can use the M_SERVICE_MEMORY view to explore the amount of SAP HANA
Used Memory as follows:
FROM SYS.M_SERVICE_MEMORY;
FROM SYS.M_SERVICE_MEMORY;
FROM M_CS_TABLES;
SELECT round(sum(USED_FIXED_PART_SIZE +
FROM M_RS_TABLES;
FROM
M_CS_TABLES
GROUP BY SCHEMA_NAME
round(MEMORY_SIZE_IN_TOTAL/1024/1024, 2) as "MB"
FROM M_CS_TABLES
from PUBLIC.M_HOST_RESOURCE_UTILIZATION;
from PUBLIC.M_HOST_RESOURCE_UTILIZATION;
( This content is published and shared with very kind thanks to Vinod Nair originally
published in this blog)
Used Memory
The total amount of memory in use by SAP HANA is referred to as its Used Memory.
This is the most precise indicator of the amount of memory that the SAP HANA database
When used: To understand the current used memory in HANA when HANA alerts shows usage greater
than licensed memory. Understanding memory usage by components will help in troubleshooting and perform
necessary memory clean up actions.
Display the current size of the Used Memory; you can use the following SQL statement
FROM SYS.M_SERVICE_MEMORY;
FROM M_CS_TABLES;
FROM M_CS_TABLES
GROUP BY SCHEMA_NAME
sum(used_memory_size) used_mem_size
FROM PUBLIC.M_SERVICE_COMPONENT_MEMORY
Database resident
FROM M_SERVICE_MEMORY;
Find the total resident on each node and physical memory size
SELECT HOST,
ROUND((USED_PHYSICAL_MEMORY + FREE_PHYSICAL_MEMORY)/1024/1024/1024,
2) AS "Physical Memory GB"
FROM PUBLIC.M_HOST_RESOURCE_UTILIZATION;
SELECT T1.HOST,
(T1.USED_PHYSICAL_MEMORY +
T2.SHARED_MEMORY_ALLOCATED_SIZE)/1024/1024/1024 "Total Resident"
FROM M_HOST_RESOURCE_UTILIZATION AS T1
JOIN
(SELECT M_SERVICE_MEMORY.HOST,
SUM(M_SERVICE_MEMORY.SHARED_MEMORY_ALLOCATED_SIZE)
AS SHARED_MEMORY_ALLOCATED_SIZE
FROM SYS.M_SERVICE_MEMORY
GROUP BY M_SERVICE_MEMORY.HOST) AS T2
ON T2.HOST = T1.HOST;
SAP HANA database tracks the highest-ever value of Used Memory reached since the database
was started. In fact, this is probably the single most significant memory indicator that you should monitor as an
overall indicator of the total amount of memory required to operate the SAP HANA database
over a long period of time.
SELECT
FROM
(SELECT
SUM(CODE_SIZE+SHARED_MEMORY_ALLOCATED_SIZE) AS "M"
FROM SYS.M_SERVICE_MEMORY
UNION
SELECT
SUM(INCLUSIVE_PEAK_ALLOCATION_SIZE) AS "M"
FROM M_HEAP_MEMORY
SAP HANA maintains a special Used Memory indicator, called the Peak Used Memory.
This is useful to keep track of the peak value (the maximum, or high water mark) of Used Memory over time.
Here is how to read the Peak Used Memory:
FROM
FROM SYS.M_SERVICE_MEMORY
UNION
FROM M_HEAP_MEMORY_RESET
free g | awk '/Mem:/ {print "Physical Memory: " $2 " GB."} /cache:/ {print "Resident: " $3 "
GB."}'
Memory Cleanup:
Login to HANA server -> open HDBAdmin.sh and navigate to Services -> Console
Select the node where the garbage collection to be triggered. Execute the below command
mm gc f
The garbage collector will be triggered, and free up the memory. This will not unload the tables.
When Used:
when testing a report or need to monitor the peak of memory usage by a SQL, monitor IO, memory objects
throughput and statistics about garbage collection jobs.
M_HEAP_MEMORY view contains information about memory consumption of various components in the system.
M_MEMORY_OBJECTS_RESET view provides information about the number and size of resources currently in
the resource container and about the throughput of the resource container.
ALTER SYSTEM RESET MONITORING VIEW SYS.M_MEMORY_OBJECTS_RESET;
Schema/Tables Monitoring
When used:
To see what tables are loaded to memory at any given time; If a report is running slow see if the table is loaded to
memory though the tables goes on lazy loading it is a best practice to have the table loaded to memory.
SELECTLOADED,
TABLE_NAME,
RECORD_COUNT,
RAW_RECORD_COUNT_IN_DELTA ,
MEMORY_SIZE_IN_TOTAL,
MEMORY_SIZE_IN_MAIN,
MEMORY_SIZE_IN_DELTA
from M_CS_TABLES
HOST,
TABLE_NAME,
COLUMN_NAME,
MEMORY_SIZE_IN_TOTAL
from PUBLIC.M_CS_COLUMNS
MERGE DELTA
SELECT LOADED,
TABLE_NAME,
RECORD_COUNT,
RAW_RECORD_COUNT_IN_DELTA ,
MEMORY_SIZE_IN_TOTAL,
MEMORY_SIZE_IN_MAIN,
MEMORY_SIZE_IN_DELTA
from M_CS_TABLES
Smart merge
Find Compression
When used:
To see the uncompressed size and the compression ratio in HANA for the loaded tables.
sum("DISTINCT_COUNT") RECORD_COUNT,
sum("MEMORY_SIZE_IN_TOTAL") COMPRESSED_SIZE,
sum("UNCOMPRESSED_SIZE") UNCOMPRESSED_SIZE,
(sum("UNCOMPRESSED_SIZE")/sum("MEMORY_SIZE_IN_TOTAL")) as
COMPRESSION_RATIO,
100*(sum("UNCOMPRESSED_SIZE")/sum("MEMORY_SIZE_IN_TOTAL")) as
COMPRESSION_PERCENTAGE
FROM "SYS"."M_CS_ALL_COLUMNS"
GROUP BY "SCHEMA_NAME"
To go on a detail level and identify what type of compression is applied on each column and the
ratio please use below
select
COLUMN_NAME,
LOADED,
COMPRESSION_TYPE,
MEMORY_SIZE_IN_TOTAL,
UNCOMPRESSED_SIZE,
COMPRESSION_RATIO_IN_PERCENTAGE as COMPRESSION_FACTOR
from M_CS_COLUMNS
SELECT
HOST,
PORT,
CONNECTION_ID
FROM M_CONNECTIONS
Expensive Statements
When used:
Also to monitor the expensive sqls executed in HANA. Identify the ways for performance
optimization.
SELECT
"HOST",
"PORT",
"CONNECTION_ID",
"TRANSACTION_ID",
"STATEMENT_ID",
"DB_USER",
"APP_USER",
"START_TIME",
"DURATION_MICROSEC",
"OBJECT_NAME",
"OPERATION",
"RECORDS",
"STATEMENT_STRING",
"PARAMETERS",
"ERROR_CODE",
"ERROR_TEXT",
"LOCK_WAIT_COUNT",
"LOCK_WAIT_DURATION",
"ALLOC_MEM_SIZE_ROWSTORE",
"ALLOC_MEM_SIZE_COLSTORE",
"MEMORY_SIZE",
"REUSED_MEMORY_SIZE",
"CPU_TIME"
FROM "PUBLIC"."M_EXPENSIVE_STATEMENTS"
SELECT
"HOST",
"PORT",
"CONNECTION_ID",
"TRANSACTION_ID",
"STATEMENT_ID",
"DB_USER",
"APP_USER",
"START_TIME",
"DURATION_MICROSEC",
"OBJECT_NAME",
"OPERATION",
"RECORDS",
"STATEMENT_STRING",
"PARAMETERS",
"ERROR_CODE",
"ERROR_TEXT",
"LOCK_WAIT_COUNT",
"LOCK_WAIT_DURATION",
"ALLOC_MEM_SIZE_ROWSTORE",
"ALLOC_MEM_SIZE_COLSTORE",
"MEMORY_SIZE",
"REUSED_MEMORY_SIZE",
"CPU_TIME"
FROM "PUBLIC"."M_EXPENSIVE_STATEMENTS"
CONNECTIONS
FROM "PUBLIC"."M_CONNECTIONS"
WHERE CONNECTION_STATUS = 'RUNNING'
Resetting Connections
FROM M_CONNECTIONS
Disconnect Session
PASSWORD Policy
Disable password policy on a user, this is used when you dont want the policy to be applied on a
user. This will set to lifetime.
Audit Policy
Configure
'SYSTEM')
set ('auditingconfiguration',
set ('auditingconfiguration'
,'default_audit_trail_type' ) = 'CSVTEXTFILE'
with reconfigure;
set ('auditingconfiguration'
,'default_audit_trail_path' ) = 'path'
with reconfigure;
'SYSTEM')
set ('auditingconfiguration',
Policy enable/disable
With thanks to Vinay Singh, the original author of this blog for allowing it to be shared in the
HANA Reference.
2.Run Unique checker (you can schedule it in you crontab also ,so as to get updates
automatically in your mail box.
This program helps you to find duplicate entries in tables . Reach out to SAP to get the program
or refer to https://help.sap.com/HANA/SAP_HANA_Administration_Guide_en.pdf if you
do not have it.
check it on admin console -->Performance -->to see the dumps (OOM dumps as well) give the
serach text as "dump"
if you find any crash dump -->analyze if its because of any query -->notify the query owner to
optimize it in case if its causing dumps.
frequency could be everyday or once in 3 days you can decide after seeing the pattern :
execute mm gc -f
It triggers the garbage collector and without unloading the tables it free up memory .
There is a very useful SAP Note containing Technical Consistency Checks for SAP HANA
Database:
8e) FAQ: DB Users for the DBA Cockpit for SAP HANA
SAP have published a wonderful SAP Note explaining all about how the DBA Cockpit works
with SAP HANA,
how to set it up, configure the integration, setup the Users with the correct authorisations etc.
1640741 - FAQ: "DB users for the DBA Cockpit for SAP HANA"
Replication Server Monitoring - Transaction LTRO gives all details of all configuration at one
glance.
The full detailed guidance including screenshots is delivered in the very useful Knowledge
Base Article:
In the following OSS Note you can find the usual steps that are required to analyze an OOM
dump file.
The OOM dump file contains information about allocated memory and limitations that can be
evaluated
to understand the root causes of high memory consumption and OOM dumps.
The following OSS Note based How-to-Procedure guides you through steps required to
monitor replication process,
to check replication configuration, to assess trigger status of different tables and to have a
look at the statistics of
the replication.
1993756 - System Check for SAP Landscape Transformation
The IBM Systems Solution for SAP HANA appliance Health Checker allows the execution of
health checks for
administrators and system operators based on the Linux Health Checker framework (lnxhc).
Checkout the following OSS Note for all details and especially the zip file attached to the
OSS Note:
If the SYSTEM users password is lost, you can use the SAP system user
to reset the password.
To recover an SAP HANA instance where the SYSTEM users password is lost,
you need to have &adm access to the instance where SAP HANA's master
/usr/sap/HDB/hdbenv.sh
/usr/sap//HDB/exe/hdbnameserver
/usr/sap/hdbenv.sh
/usr/sap/exe/hdbindexserver -console
When the service has started, you have a console to the SAP HANA
Reset the SYSTEM user's password and store the new password in a
secure location with the following SQL command:
Ref this blog from Jake Echanove which also contains the screenshots.
UPDATE: Section 7.3 in the admin guide for SP6 discusses how to do this:
[http://help.sap.com/HANA/SAP_HANA_Administration_Guide_en.pdf ]
? su anaadm
? ./HDB stop
Start the name server service this may not get back to a prompt
? hdbnameserver &;
Start index server. Run command even though may not be at a prompt.
? hdbindexserver console
killall -9 hdbnameserver
Start HANA
./HDB start
with thanks to Richard Bremer for allowing this to be shared from his blog
The story
The question was this: "SAP recommends that the SYSTEM user be deactivated [personal note:
yes, absolutely and beyond any doubt - SYSTEM should not be used in regular database
operations]. What options do you have if you need to reactivate the SYSTEM user, but for
whatever reason all other database users with privilege USER ADMIN are unavailable?"
Now the question first sounds pretty hypothetical - there is no good reason why all your regular
administrative users which have the USER ADMIN privilege should be unavailable. Still, you
can construct such situations. I have recently managed to get all regular users deactivated by
simply deactivating the "force_first_password_change" setting, but leaving the initial password
lifetime at a finite value, and also not disabling the password life time of users. All users that I
had created in this situation were deactivated after the initial password life time had passed.
There are at least two ways to resolve this situation. The first one requires a database restart but
does not have any further prerequisites. The second one does not need the restart, but requires
that you still have some database users available that have development capabilities.
1. Start the database in console mode as described in the database administration guide
2. User SYSTEM is not allowed to unlock itself. You therefore have the following options:
o If there are other database users with privilege USER ADMIN, but these users are
locked/deactivated, you can activate/unlock one of them. The procedure to
unlock/activate depends on the reason for the user being deactivated. It's either a
password reset, or an "alter user <name> activate user now"
o Alternatively, you may create a dummy user and grant USER ADMIN to this
user:CREATE USER emergency_user_admin PASSWORD WhySoComplicated?;GRANT
USER ADMIN TO emergency_user_admin;Shut down the system that you have started
in emergency mode:
o Stop the indexserver process by entering "quit" in the SQL console
o Stop the nameserver and compileserver that you have started by hitting Ctrl+C in
their respective linux terminals.
3. Now start the instance again in the regular way:
"/usr/sap/<SID>/HDB<instance>/exe/sapcontrol -nr <instance> -function StartSystem
HDB"
4. Once the system is started, log on with either the unlocked regular user administrator, or
with the emergency_user_admin, depending on what you did in step 2.
5. Activate the SYSTEM user: "ALTER USER SYSTEM ACTIVATE USER NOW"
6. Verify that the SYSTEM user is in fact working again.
7. If you created an emergency user admin: delete that emergency user, get a regular user
administrator working again.
8. With that regular user admin, deactivate the SYSTEM user, and activate any other
locked/deactivated user admin.
It does, however, require that you can create and activate a SQLscript procedure in the SAP
HANA repository - either in the modeler or using the developer workbench, whatever you prefer.
And you must be able to execute that procedure.
If you are having this trouble in your production system, and if you have deactivated SYSTEM,
I'm pretty certain your HANA is als "read only" - i.e. you do not have development accounts in
this database. So the requirements are that you need to be able to import (including activation) a
stored procedure into your system, and that at least one active user has the execute privilege on
the database schema in which the runtime object of the procedure will reside (e.g. execute on
schema _SYS_BIC).
If you do have development users in the troubled system, then you are probably good to go, as
any database user with minimal development privileges can create and activate stored
procedures, and in most cases they will also have permission to test, i.e. execute, these activated
procedures.
One more prerequisite is that the system parameter sqlscript_mode must be set to UNSECURE -
the reason is that we need to use dynamic SQL in the procedure, which needs a read/write
procedure. Read/write procedures are only possible if SQLSCRIPT_MODE = UNSECURE.
4. Finally you want to clean up. This means: perform steps 7/8/9 from the first procedure.
And you also want to remove the sqlscript procedure from the repository, making sure
that also the runtime object gets deleted.
You have a SAP HANA database system and you would like to only allow certain
administration users to
connect and work on the database for some time. Regular user sessions should be
disconnected and no
new user sessions for non-administration users should be allowed. After your administrative
actions you
would like all regular users to be able to connect to your SAP HANA database system again.
The OSS Note explains the whole process and SQL statements and steps:
Note: If you specify the host name, make sure that it is fully qualified, such as
myhost.sap.com (i.e., not just myhost).
Connect to the system with an X server client to enable GUI system access.
Open a root shell and go to the directory where you mounted the SAP HANA DVD,
by entering a command such as the following:
cd /mnt/&DATA_UNITS/HANA_IM_LINUX__X86_64
./HANAconfig.sh --gui
Select Next
HANAconfig.sh gui can also be used for other tasks including installing and de-installing
SMD Agents
The configuration files (.ini files) are located by default in the following directories
$DIR_INSTANCE/../SYS/global/hdb
custom/config global.ini
indexserver.ini
nameserver.ini
$SAP_RETRIEVAL_PATH
sapprofile.ini
daemon.ini
/usr/sap/&trace
Instead of Client-Side JDBC or ODBC tracing an administrator would like to enable serverwide
SQL traces.
3. Click the Configure Trace ... icon in the top right corner
sqltrace_&_&_000.py
Note: Make sure you are connected to the correct HANA instance :-)
The steps below are for Windows. Adjust them accordingly for UNIX and Linux.
6. Confirm the settings took by running hdbodbc_cons show all. You should see something
similar to the following:
Configuration:
see SAP Note 1998549 - How to collect HANA - NetWeaver SQL Communication trace
You need to get and capture the SQL queries that are being sent to Hana.
Checkout this wonderful OSS Knowledge Base Article which includes screenshots
SAP Support asked you to provide a collection of the relevant diagnosis files
All details of how to do this, are described in the excellent Knowledge Base Article
During a SAP HANA database analysis it can often be required to collect special information.
You can test the installation of the ODBC driver and your ability to connect
by using the odbcreg tool, which is part of the ODBC installation.
or
If the driver is installed properly, you should get the ODBC login screen.
As of HANA SPS5, the SAP HANA Automated Update Guide only mentions
SUM (SUM4HANA) for updating the SAP HANA appliance software
and related components.
You are not sure if SUM is mandatory and using hdbupd is obsolete by now.
+The use of SUM is mandatory and the highly recommended way for updating
the SAP HANA appliance. SUM takes care of:
o Migrating the old SAP HANA file system structure to the new
shared layout during the selfupdate process
Other tools such as the On Site configuration tool rely on this landscape
to be correct in order to work properly.
It is technically possible to use hdbupd but you should consider this option
only in special/extreme situations and after consulting a SAP representative.
So how do you recognize if your SAP HANA instance was installed with hdbinst or
Unified Installer?
exist then the Unified Installer was used and you should apply Support Package Stacks
and Revisions with SUM for HANA. If you do not have these directories, the recommendation
is to bring your instance up-to-date and install SUM for HANA and lm_structure using
SAP Note 1793303. After following this note you can use SUM for HANA to apply revisions
and SP Stacks.
The SAP Software Update Manager is a separate software component that must
be started on the SAP HANA server. A good practice is to install this component
as a service.
The SAP Software Update Manager does not have a user interface.
export JAVA_HOME=/usr/sap/&SUM/jvm/jre
/usr/sap/&SUM/daemon.sh install
The service can be started using the following command:
/etc/init.d/sum_daemon start
After the release of an SPS of the SAP HANA Appliance Software new revisions of the SAP
HANA
database are released.
To update your SAP HANA database to these new revisions, use the commands
hdbupd or hdbsetup which are provided with the SAP HANA database installation.
this section is in progress and will be based upon Nicolas Chang's excellent blog here
Install the SAP HANA ODBO driver on the host where MS EXCEL has been installed and is
running.
For more information, see SAP HANA Client Installation and Update Guide.
a. Open a command prompt and call the SAP HANA client installation program by entering
the following command:
hdbinst -a client
There is a Python script that allows you to collect information from your systems
even when no access to the system via SQL is possible.
fullSystemInfoDump.py
and is part of a server installation. It runs from a command line and is located
in the directory
$DIR_INSTANCE/exe/python_support
(Linux).
python fullSystemInfoDump.py
By default the script creates a zip file with all of the collected support information
to the directory
This output directory is shown as console output when the script is running, but it can
be looked up by entering:
To change the default directory, an explicit absolute path can be given to the script,
for example:
python fullSystemInfoDump.py h
To collect support information you need an SQL user with rights to select the system tables and
views listed in System Tables/Views.
For security reasons the user name and password for this SQL user cannot be given as command
[ts1adm@luvm252058a:/usr/sap/TS1/HDB01/exe/python_support |
mailto:ts1adm@luvm252058a:/usr/sap/TS1/HDB01/exe/python_support]> python
fullSystemInfoDump.py
Password:
If the system can be reached via SQL and the user name and password information is valid, the
script
starts collecting support information.
If user name and/or password are invalid, the script aborts.
17) HDBSQL
SAP HANA HDBSQL is a command line tool for entering and executing SQL statements,
executing
database procedures, and querying information about SAP HANA databases.
You can use HDBSQL interactively or import commands from a file and execute them in the
background. You can access databases on your local computer and on remote computers.
hdbsql -h
Examples:
One step logon to the database on the PARMA computer with instance ID 01 as database
user MONA with the password RED.
Start HDBSQL:
hdbsql /
\s
host : wdfd00245293a:30015
database : ORG
user : SYSTEM
autocommit : ON
18) To run sql queries using hdbsql:
\q to quit
COUNT()*
14927
You can enter SQL commands either by using the SQL editor in SAP HANA studio,
or by using the hdbsql program on the command line.
/usr/sap/exe/
Note Backups using SQL commands are only recommended for batch mode
Currently, the main tool for batch mode backup is the command
line interface hdbsql.
This is the current recommended mode for executing backups from
operating system level.
You can use the program hdbbackupcheck to check a part of the backup for changes
The full usage of the command, all switches, use cases and including examples is fully
A data backup is then created in the default location. In the above example,
the prefix of all service-related backup files is MONDAY.
To cancel a running data backup, you can use either SAP HANA studio or an SQL command.
Prerequisites
A user needs the system privileges CATALOG READ and BACKUP ADMIN.
You can use SAP HANA studio to cancel running data backups that you
started using the backup wizard. To cancel a running data backup, choose Cancel.
When a data backup is started, the system assigns a unique ID to the data backup.
To find the backup ID of the running data backup, use the monitoring view
M_BACKUP_CATALOG,
To find the backup ID of the running data backup, use the following SQL command:
select BACKUP_ID from "SYS"."M_BACKUP_CATALOG" where entry_type_name =
'complete data backup' and state_name = 'running' order by sys_start_time desc;
You can now use the backup ID to cancel the running data backup.
To cancel the running data backup use the following SQL command:
23) To check the state of the data backup, use the following
command
ref: SAP Note 1816483 - Restore when log backups are missing
A restore fails with the error "Recovery could not be completed Cannot open file ...".
One or more log backups of the SAP HANA database are missing or damaged.
All the available log backups exist in the file system of the database server.
If not all the required log backups are available, an SAP HANA database restore is subject to
restrictions.
In most cases, you will only be able to restore the SAP HANA database to a in time that lies
before the time when the oldest missing log backup was written.
A restore to any point in time (including redo of the log area) is possible only if the content of the
missing log backup still exists in the log area.
To determine if this is the case, proceed as follows:
Determine the volume IDs and the lowest log item of the missing log backup from the name of
the backup. If a previous restore has failed with the error message specified above, you can
determine the name of the missing log backup from the error message.
The log backups are named after the schema log_backup_&_0_&log item>_&, for example,
log_backup_2_0_12345_67890.
In this example, the volume ID would be 2 and the lowest log item 12345.
Use hdblogdiag to determine the lowest log item that still exists in the log segments of the log
area as follows:
Call
LogSegment[0/0:&-&(...
LogSegment[0/1:&-&(......
Take into account that the system outputs the log items in hexadecimal format and that you have
to convert them into decimal numbers.
Example:
Assuming the parameter basepath_logvolumes has the value /HANA/log/HAN and the parameter
use_mountpoints has the value yes, so that the log egments lie in the subdirectory mnt0001.
The log segments for the volume with the volume ID 2 then lie there in the subdirectory
LogSegment[0/0:0x129540-0x131c00(...
LogSegment[0/1:0x131c00-0x139540(...
Log segment 0 has the lowest log item 1217856 (hexadecimal 0x129540), log segment 1 has the
lowest log item 1252352 (hexadecimal 0x131c00).
This means that the lowest log item that exists in the log segments is 1217856.
If the lowest log item of the missing log backup is bigger than the lowest log item that still exists
in a log segment of the log area, a restore to the latest available point in time is possible.
You can restore the SAP HANA database only with the log backups that were written before the
missing log backup.
You cannot use the log backups that were written after the missing log backup.
Start the restore for the point in time that you selected. For this, you must select "Initialize Log
Area".
26) hdbbackupdiag
The program hdbbackupdiag provides support for determining the data backup files and log
backup files that are required to restore an SAP HANA database, with "Recover the database to
its most recent state" as the aim.
Depending on the availability of the file BackupCatalog.xml that is saved under the path
$DIR_INSTANCE/../SYS/global/hdb/metadata and that is used to determine the restoration
strategy, two application scenarios arise; they are both described in the following section.
Scenario a: BackupCatalog.xml is available
hdbbackupdiag
determines the most suitable data backup and creates a list of the required log backup files.
To do this, you must call the program with the option -c &. Use the option -c &to specify the
name of the BackupCatalog file.
If the program is not started from the directory in which the file
BackupCatalog.xml
is located, you can use the option -d & to adjust the access path.
hdbbackupdiag -d $DIR_INSTANCE/../SYS/global/hdb/metadata -c
BackupCatalog.xml
Output:
Data backup file: thursday_databackup_0_1
RedoLogPosition: 0
A recovery of SAP HANA database fails. The file "backup.log" contains the error messages:
The backup catalog that the database created is not available or defective.
All data backups and log backups that are required for the recovery are available in the file
system of the database server.
You can use the program "hdbbackupdiag" to create a new backup catalog.
For this, you provide all the data backups and log backups in the file system of the database
server. If you cannot use the standard paths for data backups and log backups due to space
restrictions, you can also save the files in different directories. Note that all files of the data
backup must be saved to one directory. However, log backups can be distributed across multiple
directories.
dataDir
--logDirs
-d
If you have distributed the log backup across multiple directories, you can specify them behind
the option --logDirs separated by commas.
For example:
When you call "hdbbackupdiag", the content of the specified directories is analyzed and a new
backup catalog is generated.
This backup catalog is created with a directory for the log back up that is specified with -d.
Then new backup catalog has the file name "log_backup_0_0_0_0.n" whereby n is the newly
generated backup ID of the database.
To be able to verify the content of the backup catalog, you can output the recovery strategy that
is based on the latest data backup in the generated backup catalog. For this, use the command
"hdbbackupdiag -d "
After you generate the backup catalog, a recovery of the database may carried out.
In case the backup catalog is not created in the standard directory $DIR_INSTANCE/backup/log,
you must specify the directory in which the backup catalog is located in the Recovery Wizard in
the step "Locate Log Backups".
hdbcons is a tool to provide information about the actual used memory, the peak memory, the
throughput of the different allocators, etc.
SAP HANA Development Support requires information about a suspected memory issue.
Write output:
This will show us how much memory is located by which code line.
This will show which allocator allocates how much memory at the moment and its peak memory
allocation.
The memory consumption stays at a high level / the database seems to hang because of high
memory consumption
Please provide a runtime dump as described in SAP Note 1813020 and the content of the
monitoring view M_HEAP_MEMORY.
or
Total RAM is
or
Disk Sizing
https://websmp209.sap-
ag.de/~sapidb/012006153200000051552013E/SAP_BW_on_HANA_Sizing_Report_V1_4.pdf
You intend to migrate an SAP NetWeaver BW system from any database platform to the SAP
HANA In-Memory Database and need information on hardware sizing of the HANA platform.
Starting with version 7.30 SP5 you can run SAP Business Information Warehouse (SAP BW) on
SAP HANA as database platform.
This enables you to leverage the In-Memory capabilities of HANA and the SAP-HANA-
optimized BW objects.
To simplify sizing of an SAP BW system that is supposed to be migrated, SAP now provide the
database independent ABAP report
/SDF/HANA_BW_SIZING
For a detailed description of the report, its input parameters, and how to interpret its output,
please refer to the document:
ref: SAP Note 1736976 - Sizing Report for BW on HANA and the pdf attached to the Note
The following contribution is with thanks to John Appleby for allowing his excellent blog to be
I've had more than a few questions on BW on HANA Licensing and Sizing, and it seems that
there
isn't anything authoritative in the public domain. So here we go, but before we start...
Caveats
Architecting BW on HANA systems requires some care. First, database usage, number of
indexes
and aggregates, use of database compression, reorgs and non-Unicode systems all cause a
variance
in compression in the HANA DB. The best way to size a HANA DB is to do a migration.
In addition, you may choose to use the cold data concept, to archive/delete prior to migration
or to use
Sybase IQ for NLS. All of these will vary the amount that you need. And don't forget growth -
you need
to plan for data volume growth, and M&A activities or projects which may increase data
volumes.
If you get this wrong with SAP HANA, then you may buy the wrong hardware. I've worked
with customers
who bought 3-4x too much, and customers who bought 3-4x too little, so please get expert
advice.
In addition be careful when architecting HANA systems, whether you need Dev/Test/UAT, if
you have a
big system, will it be scale-out, will there be a standby node, and is there HA/DR? Where will
you store
So whilst this blog is intended to help and inform, the responsibility lies with you for getting it
right. If in
doubt, get the services of an expert. Now we've got that out the way!
What are the license models for BW on HANA?
1) By the 64GB unit. As noted in this slide deck, this is EUR 60k per unit for up to 10 units,
and then the
price decreases with every additional 10 units you buy, and future licensing purchases are
accretive and
retroactive.
2) By Software Application Value. You pay 8% of your total SAP purchase price and SAP
provide an
unlimited runtime license for BW. This is also available at 20% including ERP on HANA.
As has been described before, BW on HANA is non-discountable, but you should always have
a frank
discussion about your overall license package with your Account Exec.
Note that this purchase covers you for all usage: Dev, Test, Training, HA and Disaster
Recovery. The only
time when you need anything else is if you want to build HANA Enterprise models, and in
this case you
Generally, the SAV licensing is much cheaper unless you are a large organization who has a lot
of SAP
software and a small BW. If you are a mid-size organization with a big BW, the SAV licensing
can be
There is an attachment to SAP Note 1736976 - Sizing Report for BW on HANA. This note
contains some
manual corrections, and then needs to be installed via SAP Transaction SNOTE. Ensure you
run the latest
version, because it is constantly updated. You can then run ABAP Report
/SDF/HANA_BW_SIZING.
When you run this report, run it with and without future growth, and keep both sets of
numbers. It will produce
is a 120GB MSSQL database, which it suggests will be a 127GB HANA DB. The sizing tool
tends to be
In newer versions of this tool it will tell you how many Medium (512GB) nodes you would
need, or how
many Large (1TB) nodes. This is a rule of thumb, use it with care.
Now ensure that you think about what you are sizing for. For instance, you may feel that you
can archive
or delete data. Now is a good time to do this, and if you look at the PSA and DSO Change Log
sizes in
this system below, a cleanup is definitely in order. Also, you can set some data to be "cold" in
HANA
and purge it from memory after the migration. You can remove this from the sizing if you like.
If you have a very large system (greater than 3-4TB of HANA required) then it may be cost-
effective to use
the IQ Near Line Storage (NLS). You can subtract any data that you can archive from NLS
from your sizing,
but be careful: the NLS software is only good for cold data that is not updated frequently.
First, start by sizing your productive environment. Once you have this, you can decide the
production architecture.
In my case here I only need 160GB RAM, so I would buy a 256GB HANA system.
Once you require more than 1TB RAM then you will need to move to a scale-out HANA
system. This is where
customers often go wrong. Let's assume we use Medium (512GB) nodes and the sizing tool
says we need
100GB for the row store and 1.5TB for the column store. The row store requires one master
node, and the
column store fits on the remaining nodes. This means that we need 4 active nodes, plus one
standby node
Now we need to architect for disaster recovery, and we can take the same as production.
Now we can architect our test system. If our disaster recovery can be warm (i.e. take some
time to start up
in case of a failure) then we can share this with our test system. This may make sense if you
want a
production sized copy in test. Note that if you do not have a DR system you will need a
dedicated test
system. If you have a scale-out production environment, always ensure you have a scale-out
test system
And now you need a development system. Normally I recommend copying the existing
system, and one
512GB node should be sufficient unless development is a copy of production. Use common
sense.
From here you can work with a hardware vendor for the best approach, but be careful - the
hardware vendors
often cut some items out to cut cost (or indeed add extra hardware to get a larger sale), and I've
dealt with a
number of customers who have been bitten by this and have had to buy substantial amounts
of extra hardware.
Ensure that your hardware partner has an upgrade policy for the amount of hardware you
expect to need in the
Final Words
My final word would be to make sure that you get good advice throughout this process, and
sanity check it
yourselves. With a regular database, if you size it wrong then you can add more RAM or disk
at relatively
low cost, and you will just sacrifice performance. With HANA, you will have overspent, or
will have to spend
a significant amount to change your HANA architecture. Depending on your design, this can
be very inconvenient.
Your first HANA deployment is critical, because it will set the tone of sentiment in the
business for HANA as
a technology stack. Take the time to get this part right, and you will help your BW on HANA
deployment on
Thanks to HANA Distinguished Engineer Lloyd Palfrey for his input on the original blog!
28b) Sizing the SAP Business Suite on HANA
Initial Sizing observations for Suite on HANA (SAP enhancement package 6 for SAP ERP 6.0,
version for SAP HANA, SAP enhancement package 2 for SAP CRM 7.0, version for SAP
HANA, SAP enhancement package 2 for SAP SCM 7.0, version for SAP HANA, SAP
enhancement package 3 for SAP Supplier Relationship Management 7.0, version for SAP
HANA)
Initial sizing observations are based on lab measurements, load tests and measurements
performed in customer test systems.
This information is only valid, if the system usage is not changed after the move; intense
additional reporting and OLAP processing is not taken into account.
Application Server
Based on the measurements SAP doesn't expect any changes concerning CPU, memory and
network requirements for the ABAP application server. This means that the existing hardware
and network infrastructure can still be used. Please check the PAM (www.service.sap.com/pam)
for further details.
As far as sizing of the HANA appliance is concerned, main memory is the most important
resource.
The current recommendation from SAP is that you should take half of the size of an
uncompressed but "well-maintained" disk-based database and include a safety buffer of 20%.
This means, if the database is currently approximately 1,8 TB in size (tables plus indexes), SAP
recommends a HANA appliance of 1 TB.
You should not forget to consider your future data growth into your planning.
SAP doesn't expect changes in memory requirements for applications using liveCache.
The appliance is configured in such a way that the CPU power and the I/O capacity is sufficient.
To fully support the parallel processing capabilities of HANA for optimal response times for
analytical applications SAP prefers a factor of 3 to 4 more CPU power for HANA than for disk
based databases without parallelization of single statements.
This also provides a buffer for running OLTP and OLAP load simultaneously.
If other software is running on the database server, please be careful to identify the CPU
consumption of the database.
You can for example look at the CPU consumption of the database process(es) using SAP's
monitoring tools.
Regarding the disk space of Suite on HANA, SAP recommends to use half of the required
disk space that is needed for the Business Suite for disk-based databases.
Please note that this does not mean that each table just needs half of the disk space as compared
to a disk based database.
For initial sizings you should use the Quick Sizer (www.service.sap.com/quicksizer) results for
database size (DB Disk) and CPU requirements (DB SAPS) as input for HANA main memory,
disk space and CPU sizing.
contains a fantastic pdf document containing a step by step procedure for setting up Kerberos with HANA+
Main reasons are the cross OS nature of the setup (Linux/ Windows), often resulting in problems
with case (Windows: case insensitive, Linux: case sensitive) and the tight integration into the network
configuration (/etc/hosts, DNS).
In particular, there are various sources of error when creating the keytab and exporting it from
Active Directory.
The process is highly manual and consists of several steps across different operating systems and
hosts.
A python script is provided in SAP Note 1813724 which automates the creation of the keytab.
$ python hdbkrbconf.py -h
for help.
There are two main options, "-k" for creating the keytab and "-v" for validating the configuration
including the keytab.
Option "-V" will provide verbose output, together with an analysis file for SAP support.
More info, check: SAP Note 1813724 - HANA SSO/Kerberos: create keytab and validate conf
DevendraKumar Saxena has published an excellent article on the steps and troubleshooting
for implementing
If you have a bigger RowStore you will need to customise this value relative to the size of the
RowStore, which can be two or four times higher than default
[row_engine]
page_compaction_max_pages =
Row store memory size is a lot bigger than the actual data size in row store and shows high
fragmentation ratio.
Row store grows by allocating a 64MB memory segment and shrinks by freeing empty
segments.
A segment is internally divided into fixed-size pages. When a row store table requires more
memory to store records, the table takes a free page from existing segments. If no segment has a
free page, a new segment is allocated.
In such a case, row store reorganization can be performed for memory compaction.
The pages in sparse segments are moved to other segments and the resultant empty segments are freed.
If the prerequisites are not satisfied, row store reorganization should not be executed.
The prerequisites, queries, and monitoring views used for the queries are applicable to Rev 50
and to change in future releases.
- The following procedure call should run successfully and returns empty result set.
CALL CHECK_CATALOG
('CHECK_OBJECT_REFERENTIAL_INTEGRITY','','','');
o Row store reorganization is recommended, when allocated row store size is over 10GB and
free page ratio is over 30%.
If the result of "Reorganization Recommended" is "TRUE", then row store memory can be
reclaimed after row store reorganization.
6. Restart the database. Startup will take longer than normal startup when row store
reorganization runs
When there are errors during reorganization, row store reorganization is stopped in that phase
and all the changes are rolled back and database starts up to return to its original state
Ref: SAP Note 1813245 - SAP HANA DB: Row store reorganization before reorganization is
run.
SAP Support asks you to generate a runtime dump during a high CPU/Memory consumption
Or alternatively
All three methods are described in great detail and with screenshots in the
You can use this hint for a FOR_ALL_ENTRIES in order to inform the
DBSL that an EQUI join can be created from this FAE statement; this
EQUI join can then be resolved for an IN data set.
You must then specify this hint together with the hint of the DBI interface
(&prefer_join 1&) in the statement (see Note 48230).
ABAP
From this, the system generates the following statement for the
database
o dbsl_add_stmt
Use: dbsl_add_stmt
This hint provides you with the option of adding an additional SQL
enhancement to the SQL statement in the DBSL. This hint is resolved
in the DBSL and the system appends the following text to the end of
the statement that was generated (after the keyword
dbsl_add_stmt).
ABAP
803 DBSL
Note
In Release 7.20, you cannot use the keyword %_HINTS HDB to define the
hints for SAP HANA; instead, you must use the keyword %_HINTS ADABAS.
The database interfinterface ensures that this hint is also generated for an SAP
HANA Connection.
Ref: Useful OSS SAP Note 1622681 - DBSL Hints for HANA
33) hdbrename
http://help.sap.com/businessobject/product_guides/HAN01SP4/en/HANA_sps4_HDB_server_in
st_en.pdf
You can rename an SAP HANA database system as described in this section.
Caution:
Renaming a SAP HANA database system that is running with a permanent SAP license
invalidates the license so that the instance is locked down.
You need to request a new license key with the new system ID and the new hardware key
(generated by renaming) in order to unlock the renamed system.
This especially impacts renaming in batch mode: since the renamed instance is locked down, no
other activities except license installation are then possible.
You identify an existing SAP HANA database system, created by an installation or a file system
copy, that is to be renamed.
If a mountpoint contains the system ID, you must first rename it manually before performing
the rename of the SAP HANA database.
To rename the instances of a distributed system, you perform the rename for all hosts with a
single call of hdbrename.
In interactive mode, the program queries all essential parameters that are not defined using
command line options as well as parameters that have invalid values.
b. Via the local mount point, change to the following directory on the shared file system:
///global/hdb/install/bin
./hdbrename
34) hdbnsutil
Example Usage:
SAP Note 1738390 - How to update SAP HANA Linux server hardware key
When you have installed SAP HANA, you want to update the Linux server hardware key.
Prerequisite: You have logged on to Linux as SAP HANA instance administrator.
in /usr/sap//SYS/global/hdb/custom/config/nameserver.ini
NOTE: Reinstallation of SAP HANA will generate a different hardware key, but upgrade of SAP
HANA will not change the hardware key.
The name of the Python script is fullSystemInfoDump.py and is part of a server installation.
To execute the script adm rights of the customer system are required.
To start the script out of its location directory, enter: python fullSystemInfoDump.py
By default the script creates a zip file with all of the collected support information to the
directory DIR_TEMP/system_dump where DIR_TEMP is the content of the variable with the same name in
sapprofile.ini
This output directory is shown as console output when the script is running, but it can be looked
up by entering:
To change the default directory, an explicit absolute path can be given to the script, for example:
python fullSystemInfoDump.py
python fullSystemInfoDump.py h
To collect support information you need an SQL user with rights to select the system tables and
views listed in System Tables/Views.
For security reasons the user name and password for this SQL user cannot be given as command
line parameters to the script.
If the customer system can be reached via SQL and the user name and password information is
valid, the script starts collecting support information. If user name and/or password are invalid,
the script aborts.
If the customer system cannot be reached via SQL the script only collects information which can
be read without SQL access.
fullsysteminfodump________.zip
HDB proc
HDB info
eg /usr/sap/HDB/HDB00/HDB info
http://help.sap.com/HANA/HANA_dev_sqlscript_en.pdf
SAP on the 28th May 2014 published a wonderful SAP HANA Technical Operations Manual, which is here:
The following OSS Note encapsulates everything important to do with operations of the the
IBM SAP Hana
Appliance.
The OSS Note contains excellent attachments, make sure to download them.
1650046 - IBM SAP HANA Appliance Operations Guide
[[http://help.sap.com/HANA/HANA_admin_en.pdf |
A great blog by Balaji Rajendran explaining some of the most important HANA tables/views required for
administration
To be continued
The time stamps are supposed to be displayed as UTC time in Data Provisioning of HANA
Studio.
It was a design decision to use UTC time to allow the replication schema to accommodate
systems from differing time zones. Using UTC time simplifies this task as then it is not necessary
to consider the time zone for each of the connected SLT and their respective source systems.
The time stamps you see in Data Provisioning match the internal time stamps which are used in
the replication process on each connected SLT system.
If you are not sure which SUSE distribution you are using, execute the following command to
identify the release version and patchlevel.
cat /etc/SuSE-release
If you are running on SLES 11 SP2 the following values should be shown:
VERSION = 11
PATCHLEVEL = 2
To view which revision of SAP HANA you are using go to /usr/sap//lm_structure and view the
landscapeDescription.xml file
45) Remove the SAP HANA Extended Application Service
(SAP HANA scriptserver) from the topology of your SAP
HANA database
You want to remove the SAP HANA Extended Application Service (SAP HANA scriptserver)
from the topology of your SAP HANA database (DB) because you do not use any applications
that require SAP HANA scriptserver.
Or you would like to restore the backup created when the SAP HANA script server was not
activated.
You must not simply stop the SAP HANA script server service. Since it has its own persistency,
it is relevant for backups. A data backup fails if the SAP HANA scriptserver volumes are still
entered in the topology but the service is not running.
Carry out the following steps to stop SAP HANA script server and remove SAP HANA
scriptserver from the topology:
o Stop all the applications that use the database.This is required because a new data backup
has to be created after you remove SAP
HANA scriptserver. A log replay over the time of the service removal is not supported.
o Determine all the hosts on which SAP HANA scriptserver services are active:
o Stop the SAP HANA scriptserver services. To do this, carry out the following command for
every with an SAP HANA scriptserver service:
ALTER SYSTEM ALTER CONFIGURATION ('daemon.ini', 'host', '<name>')
o Remove the SAP HANA scriptserver service entry from the topology.
To do this, carry out the following command for every with an SAP HANA scriptserver service:
o Remove the volumes from the topology. To do this, carry out the following command for
every of an SAP HANA scriptserver service:
In general, two types of storage space utilization have to be distinguished: Disk (file system)
usage and space consumed (internally) in the volumes attached to the HANA database.
Total Disk Usage represents the file system point of view and is identical to what
df -h
Volume size refers to the size of the HANA volumes on file system level
If there is a huge difference between Volume Size and Disk Usage, this would
indicate that a lot of space on files system level is consumed by files not related
to data volumes, log volumes or trace files. In this example, this is true for the
trace volume. All trace files together just consume around 100 MB, but consumed
from m_tracefiles
SIZE_MB
117,222
In cases like this, the 'du' command, executed against the file system in question,
259M/HANAmnt/HDB/hdbstudio_update/repository/plugins
620M/HANAmnt/HDB/hdbclient
797M/HANAmnt/HDB/global/hdb/custom/config/lexicon/lang
7.4G/HANAmnt/HDB/exe/linuxx86_64/HDB_1.00.51.374135_1005022
7.9G/HANAmnt/HDB/exe/linuxx86_64/HDB_1.00.55.376513_1078043
The file system containing the trace files also contains the executables of HANA software
(present and previous version), hence the difference in volume and disk usage.
Data Volumes
If the percentage of unused space is high, shrinking the volume can be considered.
In order to find out which column store tables are occupying most of the space inside the
volumes
from M_TABLE_VIRTUAL_FILES
group by table_name
order by 2 desc
Log Volumes
The number of log segments that consume space can either be determined using HANA Studio
SAP note 1679938 explains how to free space in case that the log volume is full.
Trace Files
If the trace files are contributing to the disk usage of the file system where they are located
(see section Volume Size vs. Disk usage), then 2 cases have to be distinguished:
Space consumed by a large number of files that are not exceptionally large or
Individual files that are significantly larger than expected.
The number and size of existing trace files is influenced by the following factors:
(1) Activated trace components. This can be verified by using the following SQL statement:
where (("SECTION"='trace')
or ("SECTION"='sqltrace' and "KEY"='trace' and "VALUE" = 'on')
or ("SECTION" like 'traceprofile_%')
or ("SECTION" = 'expensive_statement' and "KEY"='enable' and "VALUE" = 'true'))
and "LAYER_NAME" = 'SYSTEM'
47) Log Volume is Full and the Database Doesn't Accept any
new Requests
If the log_mode is set to legacy the logvolume keeps all log segments since the last full backup
in the logvolume.
Solution
HDB stop
cd /usr/sap//global/hdb/log/mnt00001
3. You have to move one of the logvolumes temporarily to another volume where enough space
is available.
You should free at least 2 GB of space to ensure that the database has enough space to start.
du -sh
mv hdb00003 /usr/sap//global/hdb/data
ln -s /usr/sap//global/hdb/data/hdb00003 /usr/sap//global/hdb/log/mnt00001/hdb00003
mv /usr/sap//global/hdb/data/hdb00003 /usr/sap//global/hdb/log/mnt00001
At the moment (HANA SP5/revision 45), those cannot be imported using the SAP HANA
Studio.
To deploy translated texts, the command line tool "Regi" can be used.
"Regi" is bundled with the HANA client installation (it is also bundled with the HANA server installation).
Note that Regi is only included in the 64bit Windows and Linux versions of the HANA client.
1) Start a command line window and navigate to the folder of your HANA client installation.
C:\Program Files\sap\hdbclient
/usr/sap/hdbclient
2) Set the user, password, host and port of the connection to the HANA system using
environment variables.
where "" is a two-digit number identifying the instance number of the HANA system.
export REGI_HOST=:315
export REGI_USER=
export REGI_PASSWD=
Note that further help for the REGI command can be accessed as follows:
This is the procedure of the homogeneous system copy of SAP HANA using backup and
recovery.
The prerequisites are that you have installed an SAP system with SAP HANA as the primary
database
and you have installed SAP HANA Studio in which the database that is to be copied is set up as a
system.
The version of the SAP HANA database server must be at least Version 1.00 Revision 28.
For carrying out the system copy, you must use SWPM 1.0 Support Package 1 or higher.
The scenario for this reference example is: You want to copy the BW system PRD connected to
the database
PR1 to the BW system DEV connected to the database DV1. The name of the ABAP schema in
PR1 is SAPPRD.
Therefore, PRD is the source system (the system that is to be copied), PR1 is the source database
(the database system that is to be copied), DEV is the target system (the copied system), and
DV1 is the target database (the target database system).
SAPPRD is the (database) schema (the schema name) or the database user of the system.
Procedure
For a full description of the procedure and the SAP HANA backup options, refer to
SAP HANA Database - Backup and Recovery Guide on SAP Help Portal.
a) In SAP HANA Studio, right-click the database system that is to be copied and choose
"Backup...".
b) If possible, select "Complete Data Backup" as the Backup Type and "FILE" as the Device
Type.
Under Location, enter a directory in which the backup files are to be stored and enter a prefix for
the backup files under Backup File Prefix.
Ensure that the backup directory contains sufficient free space for the backup and that no backup
that has the same prefix already exists there.
c) Check your entries and choose "Finish" to start the backup or choose "Back" to correct your
entries.
d) Wait until the backup has been created and then close the dialog box.
a) Copy all backup files to the standard backup directory of the target database system.
The backup files are saved in the standard backup directory of the source database system and
begin with the prefix entered in step 1.
a) Start SWPM.
b) Choose -> -> System Copy -> Target System -> ->
e) In the Database Schema dialogs, enter the schema names and the passwords that match the
data in the backup.
For example, if you install a system DEV and use a backup of the system PRD for the
installation, you must specify SAPPRD as the schema in the dialogs but not SAPDEV.
f) In the dialog Database Recovery, enter the name (prefix) of the backup.
In addition, you can specify whether you want the system to check whether the backup exists.
If this check is deactivated and the backup does not exist, the installation will terminate with an
error at a later time.
You also have to specify the password of the adm user of the database and the SAPControl URL.
The system prefills the SAPControl URL; it usually does not have to be changed.
4. Installation
a) After you complete the following dialogs, you can start the installation.
b) During the installation, the system may issue an error message such as:
com.sap.hdb.core.main.cmd.HdbCmdMain
Error during execution of SQL command:
DBTech JDBC: http://scn.sap.com/437 : only commands for license handling are allowed in
current state.
This license must be implemented manually using the SAP HANA Studio.
To do this, right-click the target database system in the SAP HANA Studio and choose
"Properties".
In the subsequent dialog, choose "License" and then choose "Install License Key".
Select a valid license for the target database and confirm your selection with "OK".
As soon as the license has been installed successfully, you can proceed with the installation in
After you copy the database, the target system has the same database connections (for example,
for the DBA Cockpit) as the source system; this may cause problems.
Therefore, you must check the database connections in transaction DBCO and adjust them if
required.
After you copy the database, the target system has the same RFC connections as the source
system; this may cause problems.
Therefore, you must check the RFC connections in transaction SM59 and adjust them if required.
After you copy the database, the target system has the same spool configuration as the source
system.
Therefore, you must check the spool configuration in transaction SPAD and adjust it if required.
The incoming requests are processed automatically within a few hours (maximum processing
time: three working days).
This information is displayed in the SAP HANA Studio on the attributes page of the system.
In the SAP HANA Studio, select your system in the Navigator and choose the option to display
the attributes in the context menu of the system.
Note that you require the system authorization LICENSE ADMIN to access this page.
On the "Request license keys" tab page, choose either "Search an installation" or "select it from a
list" and search for an ERP or an SAP NetWeaver installation.
In the installation list, you can enter the installation number directly in the blank field in the
column for the installation.
Alternatively, you can also use the installation search. Here, the system displays all of the
installation numbers for which you have to request the license key authorization.
Enter your hardware key, the amount of main memory (in GB), and the validity date.
You can also split your acquired SAP HANA license (total amount) over several instances (also
over several installation numbers).
If the required amount of main memory exceeds the licensed amount, the license key is reduced
by the difference accordingly so that, at the most, the licensed amount can be called.
If the entire amount has already been called, only temporary keys are issued.
Therefore, always check how much main memory you have currently licensed by contract.
For test and development systems, you can request license keys as required.
These license keys are permanent and contain the licensed memory amount number for each
request at the most.
In this system overview, click the required system ID under an installation number.
You can then choose "Open - File - Save as" to save the license key file directly to your host.
You can install a permanent license key, which you received by e-mail or download, in your SAP
HANA database only by using SAP HANA Studio.
The prerequisite for this is a database user with the system authorization LICENSE ADMIN.
On the properties page, choose the button for installing the license key.
After a successful confirmation, the properties page of the system is updated with the new
license information if this is valid for the database.
Another option of installing a license key is to use the SQL command line of SAP HANA Studio.
In this case, you also require a database user with the system authorization LICENSE ADMIN,
who can install a license key with the following SQL command:
Note that you must use the complete content of the license file, including the line breaks, for this
command.
If the specified license data is correct and corresponds to the database (hardware key, system ID),
the license is updated in the database, and you can verify it in the system view M_LICENSE.
Emergencies
If a production standstill occurs, you can create a message with priority 1 under component XX-
SER-LIKEY to request a temporary license key that is valid for one week.
The key is issued immediately. Request a permanent license key within this week.
ref: Note 1644792 - License key req./installation SAP HANA databases (HANA SPS3)
With SAP NetWeaver 7.4 SP04 the components of the following instances based on Application
Server Java are released for use with SAP HANA Database 1.00:
NW Product Description
PDF Export
Demo Applications
BPM
Enterprise Portal
BI Java
Advanced Adapter Engine
Composition Platform
Guided Procedures
AS Java Extensions
Development Infrastructure
Make sure to check SAP Note:: 1849151 - SAP NetWeaver 7.4 Java On HANA Release
Information
Definition: "SAP HANA appliance": "SAP HANA appliance" means a single SAP HANA node
server or a scale-out cluster of multiple server nodes within one logical SAP HANA system.
This described scenario has also been called Multiple Components One System (MCOS) in
regards to other SAP applications. The term "SAP HANA system" is used interchangeably with
the term "SAP HANA appliance".
In this context, some new terms are introduced: "Multiple DBs One HANA" (MDOH), and
"Multi-SID".
Important: When considering the support status, bear in mind that the items in the "special
considerations" section which follows must be taken into account.
SAP does not support running multiple SAP HANA databases on a single production SAP
HANA appliance
SAP does support running multiple SAP HANA databases on a single non-production
(DEV, QA, test, etc) single-node SAP HANA appliance.
While SAP HANA is delivered by the hardware partners with one DB installed, additional DBs
can be installed by an SAP consultant who has access to SAP internal documentation for this
purpose.
SAP does support multiple DBs on a distributed (multi-node) non-production SAP HANA
system as an SAP-managed project solution.
Additionally., SAP plans to offer generally available support for this in the near future; this note
will be updated when this status changes.
Special Considerations:
Please ensure that your system is sized appropriately for any additional DBs that you wish to
deploy. SAP recommends working closely with your hardware partner to ensure adequate
capacity planning.
Please be aware that running multiple DBs on one SAP HANA system may impact performance
of various types of operations, as contention for memory resources may occur.
This performance impact may appear despite adequate sizing.
Note this multiple DB one SAP HANA configuration is only available for non-production
SAP HANA systems, where consistently fast performance is generally not as critically
important as with production systems.
If performance issues arise when running multiple DBs on one SAP HANA system, stop all but
one of the DBs and see if the performance issue persists.
SAP support have stated they will only address the performance issue only if it exists when
only one DB is running on the SAP HANA system.
ref: SAP Note 1681092 - Support for multiple SAP HANA databases one HANA
While there are some important exceptions, in general, SAP generally does not currently
support the deployment of multiple applications (or scenarios) within a single SAP HANA
system in a Production environment.
Also note this means that SAP generally does not support a packaged application from SAP
residing together in the same SAP HANA system as the scenario "Custom Data Marts".
The following applications can run together with other applications on one Production SAP
HANA system
SAP Finance and Controlling Accelerator: Production Cost Planning (aka"CO-PC Accelerator")
"SAP NetWeaver BW powered by SAP HANA (BW on HANA). For more information,refer to
SAP note 1666670.
Things to take into consideration when running multiple components on one HANA system
- Applying SAP HANA support packages and revisions will affect all applications residing
within the SAP HANA database or utilizing other SAP
HANA components.
- Applications deployed on a single SAP HANA may have to be patched and/or upgraded at the
same time due to direct dependencies on SAP HANA patch levels.
- Packaged Applications releases, support packages or patches may have direct dependencies on
SAP HANA revisions, patches and support packages.
- Packaged applications may have independent release cycles to SAP HANA and may have
independent timeline for support of SAP HANA release levels and support packages.
Resource allocation and capacity planning:
If you are running multiple applications on one SAP HANA system, there is a risk that one
application's processing operations could consume a
significant amount of available CPU and memory resources, thereby reducing the amount of
such resources available for the processing operations of the other applications at a given point in
time.
Such contention for system resources may negatively impact performance of any one
application's processing operations.
An additive sizing approach is required for all applications running on a single SAP HANA
system.
This means that when performing capacity planning, you must determine the resource allocation
needs for each application, then add them together to estimate the required sizing for your SAP
HANA system.
It is important to avoid underestimating sizing, as this will help mitigate the risk of performance
issues due to contention for system resources.
SAP HANA monitoring, debugging and support tools are not individual application or schema-
specific, they are supported at the SAP HANA database level.
SAP HANA scale out distribution options (including node fail over) is offered at the database
level, not at an individual application or component level.
- Backup and Recovery is currently supported only at the SAP HANA database and component
level (e.g. SLT, Data Services) and not at a specific
application level in an MCOD scenario.
This means that a point-in-time recovery for the SAP HANA system will impact all applications
residing on that SAP HANA system.
Please note that various point-in-time recovery scenarios (recovering SAP HANA or recovering
a connected SAP Business Suite system) will likely entail re-initializing and re-loading
replicated data into SAP HANA.
Lifecycle management:
- All applications should be isolated from each other in separate database schemas.
- HA and Disaster Recovery is currently supported only at the SAP HANA database and
component level (e.g. SLT, Data Services) and not at a specific application level.
Security:
- Customers are responsible for implementing security models to protect and/or isolate
application artifacts (e.g. users, data, metadata, database
objects)
Production support systems ("Break fix systems") and Quality assurance system:
- It is recommended that "break fix" and QA systems have the same configuration as the
production system so that customers can replicate
issues and test corrections in systems that are representative of the production environment.
More information: SAP HANA Backup and Recovery Guide, available on SAP Help Portal
2. Check that there is sufficient disk and main memory capacity on the target database host.
The available main memory should be able to hold at least twice the size of your row store data.
To find out how much this is, execute the following SQL statement:
1. select sum(allocated_page_size)
2. from M_CONVERTER_STATISTICS
3. where type = 'RowStoreConverter';
Multiply this value by 2 to obtain the absolute minimum size of main memory required.
The total number of index servers on the target database must be the same as on the source
database.
(The number of index servers is normally the same as the number of hosts.)
To configure additional index servers, you need to change the daemon.ini file.
To change the daemon.ini file, execute the following statement (for example, with instanceids 40
and 42):
[indexserver.c]
instanceids = &,&,...
For example, for a triple host source system, you would need two additional instanceids and you
can use 40, 42, ...
4. Check that the additional index servers are configured in your target
instance.
The description indicates which are the added index servers ("HDB Tenant Index Server on Port
300&", where & corresponds to the instanceids you elected earlier).
6. Move or delete available data and log backup files from the target database.
BackupCatalog.xml
$(DIR_INSTANCE)/../SYS/global/hdb/metadata/
BackupCatalog_Recover.xml
8. Copy the data backup files and, optionally, the log backup files from the source database to the
corresponding directories in the target database.
Note:
The directories for data and log backup are defined by the parameters basepath_databackup and
basepath_logbackup in the global.ini file.
In SAP HANA studio, select the target database system and choose Recovery... from the context
menu.
13. Select the option Initialize log area and confirm the warning.
14. Select the option Install new license and specify the license file.
ref: SAP Note 1749467 - Copying SAP HANA From a Multiple- to a Single-Host System
SAP EHP 6 for SAP ERP 6.0, version for SAP HANA
SAP EHP 2 for SAP CRM 7.0, version for SAP HANA
SAP EHP 2 for SAP SCM 7.0, version for SAP HANA
apply:
a) High availability scenarios in a multi-node cluster with a standby-node are released for the Suite
on HANA, but are restricted to the simplest case of two servers (one worker, one standby) only, since
scale-out in general is not yet supported for Suite on HANA.
b) Scale-out scenarios with multiple worker nodes to scale memory are not yet released for Suite on
HANA.
ref: SAP Note 1825774 - SAP Business Suite Powered by SAP HANA - Multi-Node Support
And a warning that the hardware vendor must get the architecture approved by SAP
All of this information is specified in the SAP Note 1950470 which is kept up to date
ref: SAP Note 1950470 - Hardware Prerequisites for Business Suite on SAP HANA Scale Out
Attention has been drawn to this document by +HANA Distinguished Engineer and SAP Mentor
Tomas Krojzl .
The document is a must read for all HANA Basis Architects involved in HANA
implementations.
this section is under construction and and will be based upon Jochen Becker 's excellent blog
When connecting BI applications to HANA how do you provide failover when HANA is
distributed across
When using SSO connections to HANA (kerberos SAML) how to setup connections to
provide failover.
1990413 - How to connect BI applications to SAP HANA when there are multiple
HANA servers
55) How to Overcome the HANA Hardware Check or
Hardware not recognised errors during Installation
You have received new hardware from your Hardware-Partner for your SAP HANA appliance or
recently bought a new SAP HANA on top of new hardware.
When installing the newest SAP HANA Revision the hardware check fails for your hardware
configuration.
Beginning with SAP HANA Revision 18 a new Hardware check is mandatory when executing
the SAP HANA Installer.
The reason for this check is the elimination of problems due to wrong or unsupported Hardware configurations in
combination with the SAP HANA appliance.
Since hardware validation is a continuing process as new hardware becomes available on the
market, the check for allowed configurations will change over time to include newly certified
hardware.
When installing any SAP HANA Revision your new hardware may not be recognized by the
check, because it was not yet included at the corresponding release date.
Attached to that note you will find the most recent version of the Hardware Check including all
validated hardware.
in the
'server\linuxx86_64\SAP_HANA_DATABASE\server'
subdirectory of your SAP SMP download with the version attached to this note.
ref: OSS 1658845 - Recently certified SAP HANA hardware not recognized
For the receiving SLD to display the HANA database as the CIM instance "HANA Database
System" (SAP_HDBSystem), the SLD must meet the prerequisites specified in Note 1649323.
If the SLD does not meet the pre-requisites then it is necessary to apply the Java patches to the
SLD according to SAP Note 1649323.
To successfully register the SAP HANA Database in the SLD use either:
- sldreg, following the HANA Installation Guide with SAP HANA unified installer, page 46,
chapter 2.3.7.5 Configuring a SAP HANA System to Connect to System Landscape Directory
(SLD)
For more related information, see SAP notes 1673424 and also 1649323.
Make sure you meet these prerequisites:
You identify the existing system, created by an installation or a file system copy, that is to be
configured with SLD.
You mount the DVD with the HANA configuration tool, which you can find at the following
location on the SAP HANA DVD:
&\DATA_UNITS\HANA_IM_LINUX__X86_64
If you specify the host name, make sure that it is fully qualified, such as:
1. Connect to the system with an X server client to enable GUI system access.
2. Open a root shell and go to the directory where you mounted the SAP HANA DVD, by
entering a command like the following:
cd /mnt/ &DATA_UNITS/HANA_IM_LINUX__X86_64
3. Call the script in GUI mode:
./HANAconfig.sh gui
4. Choose Configure SLD Connection, then Next . Follow the instructions of the wizard.
Before you continue, make sure that you meet these prerequisites:
You are logged on to the host where the server software is installed.
In interactive mode, the program queries all essential parameters that are not defined using
command line options and if invalid parameters are entered the program interrupts the process.
./hanconfig.sh sldconfig
Before you continue, make sure that you meet these prerequisites:
You are logged on to the host where the server software is installed.
In batch mode, you specify all required values using command line options.
If you omit required values or specify invalid values the program interrupts the process.
cd /mnt/&DATA_UNITS/HANA_IM_LINUX__X86_64
3. Run the HANAconfig program in batch mode using the sldconfig task:
For the list of all available options, you can call the tool help, by entering ./HANAconfig --help
- RZ70
ref: 1871902 - Cannot find registered HANA DB system in the Technical Systems view of the
SLD
SAP HANA On-site Configuration does not support multiple systems installed on appliance.
In SPS05 the On-site Configuratio supports multiple systems on single SAP HANA appliance.
If you need to configure SLD connectivity for multiple systems in SPS04 the best approach is to
update the systems and the On-site Configuration tool
to SPS05. In this way you will have system and tools with the correct and integrated behaviour.
If this is not possible you can configure the SLD connection manually by using the sldreg tool.
Example:
"/usr/sap/&SYS/global/slddest.cfg"'
For addtional SLD configurations you can take a look in the SAP HANA
ref: SAP Note 1787755 - SLD configuration for multiple SAP HANA databases in SPS04
. OSS 1897236 - #SAP #HANA : Error "insufficient privilege: Not authorized" in SM21
. OSS 1898460 - #SAP #HANA : How to handle alert "Check internal disk full event"
. OSS 1898505 - #SAP #HANA : How to handle alert "Check last save point time"
. OSS 1899511 - #SAP #HANA : How to handle alert 'Check currently utilized percentage
of main memory'
. OSS 1899528 - #SAP #HANA : How to handle alert 'Check for new rte dump file'
. OSS 1899480 - #SAP #HANA : How to handle alert 'Check license expiration'
. OSS 1900261 - #SAP #HANA : How to handle alert 'Check a long lived cursor'
. OSS 1900296 - #SAP #HANA : How to handle alert 'Check database supports point-in-
time recovery'
. OSS 1900267 - #SAP #HANA : How to handle alert 'Check whether the database is
running in log mode overwrite'
. OSS 1900257 - #SAP #HANA : How to handle alert 'Check used memory against
allocation limit'
. OSS 1900788 - #SAP #HANA : How to handle alert 'Check last log backups'
. OSS 1900730 - #SAP #HANA : How to handle alert 'Check the age of last data backup'
. OSS 1900795 - #SAP #HANA : How to handle alert 'Check last data backup'
. OSS 1900728 - #SAP #HANA : How to handle alert 'Check whether a data backup
exists'
. OSS 1900682 - #SAP #HANA : How to handle alert 'Check availability of volumes for
backup'
. OSS 1898317 - #SAP #HANA : How to Handle Alert Check host free physical
memory
. OSS 1910188 - #SAP #HANA : How to Handle Alert Check record count of column
table partitioned
. OSS 1910159 - #SAP #HANA : How to Handle Alert Check number of connections
. OSS 1910169 - #SAP #HANA : How to Handle Alert Check for not assigned volumes
. OSS 1909641 - #SAP #HANA : How to Handle Alert Check param mergedog delta
merge
. OSS 1909707 - #SAP #HANA : How to Handle Alert Check lock waittimeout
. OSS 1909763 - #SAP #HANA : How to Handle Alert Check record count of not
partitioned column table
. OSS 1909742 - #SAP #HANA : How to Handle Alert Check delta memory record
counttable column count
. OSS 1909670 - #SAP #HANA : How to Handle Alert Check host CPU utilization
. OSS 1902033 - #SAP #HANA: How to Handle Alert Check Inactive Service
After deletion of all entries, a column-store table can still have a large size on disk. In seldom
cases,
Checkout the manual steps and useful SQL statements in the OSS Note:
2000792 - SAP HANA: High Memory Consumption and constantly growing on
Pool/RowEngine/QueryExecution
One Master Job (Monitoring Job) exists for each configuration that calls the initial load jobs
and the data transfer
Every day at midnight, the monitoring job and related data load jobs - but not the migration
object definition or
access plan calculation jobs are automatically stopped and restarted immediately.
This action has no negative impact on the ongoing data load and replication, it will simple
resume immediately.
One or several load (data transfer) jobs are used for the data transfer process in the SAP LT
Replication Server.
They are controlled by the corresponding master job.
If the master job is stopped then all data transfer jobs are stopped too.
How to test the HANA connector after, creating the HANA connector from tcode DBCO
Note:
The setup and configuration for Diagnostics Agent on SAP HANA Systems is described in the
SAP Note:
The optimal settings for Suse Linux are described in SAP Note:
1824819 - SAP HANA DB: Recommended OS settings for SLES 11 / SLES for SAP
Applications 11 SP2
1944415 - Hardware Configuration Guide and Software Installation Guide for SUSE Linux
Enterprise Server with SAP HANA and SAP
The SAP HANA database for SAP Business One runs on SuSE Linux Enterprise Server 11
(SLES 11).
The following OSS Note intends to provide instructions on how to configure the certified
hardware platforms
1944415 - Hardware Configuration Guide and Software Installation Guide for SUSE
Linux Enterprise Server with SAP HANA and SAP Business One
60b) RedHat Linux Support For SAP HANA Since SPS08
Since SAP HANA Platform SPS08, RedHat Linux is now aa supported Operating System.
2009879 - SAP HANA Guidelines for RedHat Enterprise Linux (RHEL) Operating System
Pay particular close attention to this SAP Note because it contains a very nice pdf attachment entitled:
Red Hat Enterprise Linux RHEL 6.5 configuration guide for SAP HANA
This is helpful if you would like your web app to be available on the default/standard HTTP port
Enable the developer mode which provides details on execution/runtime errors when helps
during development (rather than getting generic 500 errors).
-> Configuration
-> xsengine.ini
-> httpserver
SAP Note 1984858 - Network ports used by SAP HANA database for internal/external
communication
SAP Note 1969397 - Troubleshooting Guide for SAP Business One 9.0, version for SAP
HANA
2031547 - Overview of SAP-certified 3rd party backup tools and associated support process
SAP Notes:
1913500 - SAP HANA Backup Support Process for IBM Tivoli Storage Manager
1986958 - Common issues / Configuration recommendations for Symantec NetBackup for SAP
HANA
This is a very nice document from HP explaining a reference architecture for SAP Hana
Backup and Recovery.
Internet of Things IoT represents a strategic direction for SAP with HANA.
Published on Friday 8th May, is the SAP Note for the SAP HANA Internet of Things IoT
Edition:
2008304 - SAP HANA platform, Internet of Things (IoT) edition 1.0 Central Note
2010194 - SAP HANA platform, Internet of Things (IoT) edition 1.0 SP01 Release Information
Note
SAP have published a fantastic SAP Note full of SAP HANA Frequently Asked Questions, it is here:
2000003 - FAQ: SAP HANA
SAP have now published the FAQ for SAP Hana Memory
For SAP HANA developer, SAP HANA Studio is a common client tool to develop or manage
on SAP HANA.
At the same time, SAP HANA XS engine also provides a web-based development
environment. Only using a web
browser, you can perform some simple development. When you either cannot install and use
SAP HANA studio
locally or you need to develop from a remote location, you can use this IDE.
This web-based IDE is called SAP HANA Web-based Development Workbench, which
contains four modules:
The whole blog is here, The Configuration and Usage of SAP HANA Web-based IDE
There is an excellent blog written by Xing Jin where all of the steps to preparing a SAP Hana
system for SAP Lumira installation are explained and with screenshots.
Amazon Web Services is a popular Cloud based hosting option for SAP Hana.
The main url for information on SAP Hana on AWS Amazon Web Services is:
SAP HANA
SAP Hana on AWS Amazon Web Services Implementation and Operations Guide
72) SAP Hana on VMWare vSphere
https://www.vmware.com/business-critical-apps/sap-virtualization/sap-hana.html
There is a fantastic SAP Note from SAP explaining all of the most important information
regarding
Visit the SAP Note regularly, because it is the most up to date source of information in this are:
to build decision logic based on the organization's data. This rule engine applies rules and
actions as defined
Using the SAP HANA rules framework, you can plan your decision support application
development by:
SAP MarketPlace contains all of the implementation guides and security information.
The SAP Basis Administrator's Toolbox contains the longest list of SAP HANA Basis
related SAP Notes available in one place on the Internet
Vivek Singh Bhoj's SAP HANA Reference for Developers Part I Part II and other blogs
Tom Cenen's How to Achieve SAP HANA Certified Technology Associate Certificati