Menu
SAP HANA on AWS
Quick Start Reference Deployment Guide

Troubleshooting and FAQ

If you run into any problems deploying this Quick Start, review the following FAQ for troubleshooting tips and guidance.

Where are the logs that monitor the Quick Start deployment progress?

You can find the deployment log in the /root/install/ folder of the SAP HANA instance. The name of the log file is install.log. You can log in to the SAP HANA instance as soon as you see that it’s in the running state, and the instance passes the status checks in the Amazon EC2 console.

I launched the SAP HANA Quick Start template for a new VPC, and I see two additional templates being launched in the AWS CloudFormation console. Why?

When you launch the SAP HANA Quick Start for a new VPC, it launches two templates: one template to set up your network infrastructure (VPC, subnets, managed NAT gateway, and so on), and a second template to deploy and configure your SAP HANA instance(s), once the network infrastructure is in place.

Can I enable Multitenant Database Containers (MDC) as part of this SAP HANA Quick Start?

If you’re deploying SAP HANA Platform Edition 2 SPS 1 or a later version, the Quick Start uses MDC by default. If you’re deploying an earlier version of SAP HANA, the Quick Start installs SAP HANA software with the single-tenant option. If you need MDC configured for an earlier version, we recommend that you skip the SAP HANA software installation during deployment (set the InstallHANA parameter to No). Once the deployment is complete, you can manually install your SAP HANA software with MDC or other advanced options.

Where is my SAP HANA software staged when downloaded from the S3 bucket?

The unextracted SAP HANA software is downloaded to the /media/compressed/ folder, and the extracted files are stored in the /media/extracted/ folder.

My deployment status says ROLLBACK_COMPLETE and my deployment failed with a CREATE_FAILED error. What should I do?

If you encounter a CREATE_FAILED error, refer to the following table for known issues and solutions.

Error message Possible cause What to do
n order to use this AWS Marketplace product you need to accept terms and subscribe. To do so please visit http://aws.amazon.com/marketplace/ You are trying to launch your stack with a RHEL or SLES AMI in AWS Marketplace without a subscription.

SLES for SAP and RHEL for SAP HANA require a subscription. Follow the instructions in step 2 and launch your stack again.

API: ec2: RunInstances Not authorized for images: ami-ID The template is referencing an AMI that has expired

We refresh AMIs on a regular basis, but our schedule isn’t always synchronized with AWS AMI updates. If you get this error message, notify us, and we’ll update the template with the new AMI ID.

If you’d like to fix the template yourself, you can download it and update the Mappings section with the latest AMI ID for your region.

The instance configuration for this AWS Marketplace product is not supported. Please see link for more information about supported instance types, regions, and operating systems. You are trying to launch a RHEL/SLES Marketplace AMI with an instance type that isn’t supported. Check your instance type and try to relaunch it with a supported instance type. If you want to extend the support for your desired instance type, contact the support team and open a support case.
X1 instance type requires a minimum Linux kernel version of 3.10. Choose the right operating system and try again. You are trying to launch the X1 instance type with an unsupported version of the Linux operating system. The X1 instance type requires SLES 12 and above, RHEL 6.7, or RHEL 7.2 and above for SAP HANA workloads. If you’re using R3 or R4 instances, you have two additional operating system choices: SLES 11 SP4 and RHEL 6.6.
Signal-failure function not implemented. Deployment failed for an unknown reason. Contact the support team and open a support case.
Your requested instance type (type) is not supported in your requested Availability Zone (zone). Please retry your request by not specifying an Availability Zone or choosing (zone). The instance type you selected is not available in the chosen Availability Zone. (Your subnet is associated with a single Availability Zone.) If you are trying to deploy SAP HANA into an existing VPC, create a new private subnet in the suggested Availability Zone and associate a route table with it. Retry the deployment by choosing the newly created private subnet.

If you are trying to deploy SAP HANA in a new VPC and you receive this message, choose the suggested Availability Zone when you launch the template.

Not able to access SUSE (or Red Hat) update repository, package installation may fail. The SAP HANA instance is unable to access the SUSE or RHEL update repository to download OS packages. The possible cause could be that Internet traffic for the SAP HANA instance is not routed through a NAT instance or NAT gateway. See if it is possible to temporarily route the Internet traffic by using a NAT instance or NAT gateway.

If your Internet traffic has to go through your internal proxy, contact your network team for access to the SUSE or RHEL update repository. For further assistance, open a support case in the AWS Support Center.

We currently do not have sufficient instance-type capacity in the AZ you requested. The Availability Zone you're deploying into doesn't have enough capacity or doesn't support the instance type. Retry the deployment with a different instance type, or choose a subnet in a different Availability Zone.
Instance ID did not stabilize. You have exceeded your IOPS for the region. Request a limit increase by completing the request form in the AWS Support Center.
WaitCondition timed out. Received 0 conditions when expecting 1. No or slow Internet access is causing delays when downloading SAP HANA software. The Quick Start requires Internet access to download the setup scripts from an S3 bucket. This process will hang and eventually time out if Internet access isn’t available. Make sure that you are deploying your SAP HANA instance in the private subnet and that you have access to the Internet either via a NAT gateway or a NAT instance. If you are routing your Internet traffic via your corporate proxy, check with your network team and ensure that firewall settings are set properly to allow such access.

You might also get this timeout error if you have an existing Amazon DynamoDB table from a previous Quick Start deployment. In this case, the table might contain duplicate entries with the same host name but different IP addresses, and the deployment script might fail to read it properly. Delete the table and retry the deployment.

The HANA installation did not succeed. Please check installation media. SAP HANA installation failed or SAP HANA services didn’t start up successfully. Verify that you have staged the SAP HANA software properly in the S3 bucket with correct permissions. (See step 3 for details.)

Another reason could be that SAP HANA services did not start up after the installation.

In either case, consider redeploying your instance with the SAP HANA installation parameter set to No. The Quick Start redeployment will skip the SAP HANA installation, and you can manually install the SAP HANA software to troubleshoot the issue.

System Administrator password must contain at least 8 characters. The SAP HANA master password contains $ or other special characters. Change the SAP HANA master password and then relaunch the Quick Start.

The password must be at least 8 characters, consisting of uppercase and lowercase letters and numbers. Avoid using special characters such as @ or $.

If the problem you encounter isn’t covered in the previous table, we recommend that you relaunch the template with Rollback on failure set to No (this setting is under Advanced in the AWS CloudFormation console, Options page) and open a support case in the AWS Support Center for further troubleshooting. When rollback is disabled, the stack’s state will be retained and the instance will be left running, so the support team can help troubleshoot the issue.

Important

When you set Rollback on failure to No, you'll continue to incur AWS charges for this stack. Please make sure to delete the stack when you've finished troubleshooting.