SAP HANA 2.0, express edition Troubleshooting
Prerequisites
- Setup: You are following the instructions to install SAP HANA 2.0, express edition in the Installing SAP HANA 2.0, express edition (Binary Installer Method) tutorial or Installing SAP HANA 2.0, express edition (Virtual Machine Method) tutorial.
How-To Details
Perform these steps to resolve issues when installing SAP HANA 2.0, express edition.
- Step 1
Issue: You are installing SAP HANA, express edition on a Linux server using
hdblcm
. You receive this error:Cannot start system.
Start instance 00 on host ‘hxehost.localdomain.com
’ failed.
FAIL: processhdbdaemon
HDB Daemon not running.Solution: Use
zypper
to check theutil-linux
,util-linux-systemd
anduuidd
packages to make sure they are at these versions:zypper info util-linux util-linux-systemd uuidd
The results need to show that you have at least the following versions installed:
util-linux
:util-linux-2.25-22.1
uuidd
:uuidd-2.25-22
util-linux-systemd
: 2.25-22.1If you are missing any of the packages, or if the versions are outdated, install them using the
zypper
install command.Check that socket activation is enabled and started. In a shell enter:
systemctl
statusuuidd.socket
If the status is inactive, start socket activation:
systemctl
startuuidd.socket
- Step 2
Issue: You are having memory issues on your VM and want to check resource usage.
Solution: If you have HANA studio, right-click on the system and select Configuration and Monitoring > Open Administration and check the Overview and Landscape tabs for anything in red.
If you don’t have HANA Studio, run the following queries in
hdbsql
to view SAP HANA resource usage:select service_name, round(effective_allocation_limit/1024/1024/1024, 1) as MemLimit, round(total_memory_used_size/1024/1024/1024,1) as MemUsed from m_service_memory;
If the
MemUsed
is close to theMemLimit
, you may encounter problems allocating memory.Alternatively, you can run the Linux
free
command at the command line to see free resources:free -g
The key number is in the second row (-/+ buffers/cache) in the free column. If this number is low, (e.g. 0 GB) you may have run out of memory when performing your recent operation.
You can also run the following command to see if you are running out of disk space on the VM’s
filesystem
:df -h
Look for the Use% for the
/dev/sda1 filesystem
. If it is down to just a few GB, you may have run out of disk space when performing your recent operation. - Step 3
Issue: You are trying to run a SAP HANA service on your SAP HANA 2.0, express edition installation and are receiving an error.
Solution: Log in to your SAP HANA 2.0, express edition installation as
hxeadm
.sudo su -l <sid>adm
Check which services are enabled on your machine:
xs apps
This operation may take 1-2 minutes to return the list of apps. You should see the following:
If the service you’re trying to use is shown as
STOPPED
, start it:xs start <app>
It may take a few minutes for the system to get started. Run
xs apps
again to see if the app has started and that underinstances
the app shows1/1
. - Step 4
Issue: You have received the following error:
Failed to concatenate downloaded files
You are downloading packages using the Download Manager. The Status area and Progress Detail area show the error
Failed to concatenate downloaded files
.Solution: Check the log file for details. The log file is in the Temp directory:
Linux:
/tmp/hxedm[yymmdd].log
Windows:
%TEMP%\hxedm_[yymmdd].log
If the log indicates a simple issue such as lack of disk space or file permissions, fix the problem and download again.
If the problem is less obvious, do the following:
Go to the Save directory. Delete all downloaded files, including incomplete download files. Download again.
or
Change the Save directory. Download again.
- Step 5
Issue: You are downloading packages using the Download Manager when you terminate Download Manager before download completes, or Download Manager quits unexpectedly.
Solution: Check the log file for details. The log file is in the Temp directory:
Linux:
/tmp/hxedm[yymmdd].log
Windows:
%TEMP%\hxedm_[yymmdd].log
- Step 6
Issue: You are unable to obtain an
IPv4
hxehost
IP address. You are using aVMware
hypervisor
.VMware
defaults tobridged
networking. You may need to adjustVMware's
network adapter settings in certain circumstances.If you are behind a proxy or a firewall, your institution’s network may prevent
VMware
from assigning anIPv4
address when you attempt to locate yourhxehost
IP
address.Solution:
-
In
VMware
, change your network adapter settings fromBridged
toNAT
. -
Wait a few minutes.
-
At the command prompt, enter
sudo ifconfig
to see if anIPv4
address is now assigned. You do not need to restart your VM.
-
- Step 7
Issue: You use
VMware
Fusion onMac OS X
. You import and starthxexsa.ova
. You receive an error message.This error displays: “
XSA
cockpit apps failed to start at this point of time. Please retry by runninghxe_cockpit.sh
script”Solution:
-
Shut down the instance.
-
Re-import
hxexsa.ova
. -
Start SAP HANA 2.0, express edition installation again, and this time choose to run
XSA
configuration in the background.
-
- Step 8
Issue: When you run
hxe_upgrade.sh
, you notice the upgrade hangs.Solution: The VM is low on memory. Run the
hxe_gc
memory management script.-
Open a new terminal to your VM.
-
Run the memory management script.
The
hxe_gc
memory management script frees up available VM memory.- In your VM, log in as
hxeadm
and enter:
cd /usr/sap/HXE/home/bin
- Execute:
hxe_gc.sh
- When prompted for System database user (SYSTEM) password, enter the New HANA database master password you specified during SAP HANA, express edition installation.
The cleanup process runs. The command prompt returns when the cleanup process is finished.
- In your VM, log in as
-
- Step 9
Issue: You have exceeded the 32GB memory limit of SAP HANA, express edition.
Solution: Consider migrating to SAP HANA Cloud. Visit the SAP HANA Cloud homepage to view more details about SAP HANA Cloud.
- Step 10
Issue: You have reached the memory limit on your local SAP HANA, express edition, but have not hit the 32GB memory limit
Solution: Run garbage cleanup or stop unnecessary or extraneous SAP HANA, express edition processes.
To run garbage collection, run:
bashCopycd /usr/sap/HXE/home/bin ./hxe_gc.sh
Log into XSA
bashCopyxs login
Follow the prompts to log in.
See which XS apps are running:
bashCopyxs apps
To stop any XS apps you do not wish to have running, run:
bashCopyxs stop <app>
This will stop the XS app and free any resources it may have been using.
- Step 11
Issue: Your local machine has run out of disk space.
Solution: You have a few options. You can physically install more disk space, make more disk available to your VM (for VM installations), or free up additional disk space by uninstalling and deleting unnecessary files and programs.
You can also move your SAP HANA, express edition installation to a cloud provider. Visit the SAP HANA, express edition homepage to view cloud offerings.
- Step 12
Issue: Your local machine has limited how much disk space your Virtual Machine can use for SAP HANA, express edition.
Solution: If your virtual machine is limiting how much disk space SAP HANA, express edition is allowed to use, and you have exceeded that amount, visit the virtual machine’s documentation to increase the virtual machine’s disk space threshold.
You can also move your SAP HANA, express edition installation to a cloud provider. Visit the SAP HANA, express edition homepage to view cloud offerings.
- HDB Daemon not Running
- Checking Resource Usage
- SAP HANA XS Applications Run Error
- Download Manager Shows Error
- Locate Download Manager Log File
- Unable to Obtain an IPv4 Address in VMware
- hxexsa.ova Installation Fails
- Upgrade Script Hangs While Upgrading VM Installation
- Memory Limit Exceeded - No Additional Local Capacity
- Local Memory Usage Exceeded
- Local Disk Space Full
- Local Disk Space Threshold Limited