AWS HANA Instance failing to Activate documents

[Former Member]

For over 24 hours now, I have been unable to Activate anything using HANA Studio in my AWS Instance. I can use the web server for activated documents, and I can open the Repository and System views and I can open and edit and save documents, BUT I cannot Activate anything, or even Cancel an Activation that is trying to run.

What could be the trouble? I tried also to update the Studio but was unable to reach the server from the internal update site.

How can I get this working again?

My Instance is

This is what I see effectively forever. It never goes above 0%.

Bob

[Former Member · Accepted solution]

Of course, just after I submitted the "complaint" above, everything is working once again.

Still - who do I contact about these types of failure on an Amazon Instance?

[Former Member · Accepted solution]

HANA on AWS doesn't have support - check the terms. If you gave HANA One Premium then you get Enterprise Support.

If you have a HANA dev/test/prod license then you get support from OSS.

Otherwise there is a peer support community here: SAP HANA One Support | SAP HANA

John

[Former Member · Accepted solution]

What is OSS?

[Former Member · Accepted solution]

You can't run HANA with 4gb ram! Increase it to 16gb and you will be fine.

[Former Member · Accepted solution]

John - ok. But how do I get my existing AWS Instance to increase to 16gb? Would I have to start clean and bring in the whole set of namespaces?

[Former Member · Accepted solution]

You can change the machine type once you shut down the EC2 instance down.

[Former Member · Accepted solution]

I do not know how to do that. My instance is suspended. I can edit properties (of vistual machine) but I see no way to modify the size.

I see only this. Dropdowns have no other choices.

Do I need to come in some other way besides the url which I have? https://opensap.hana.ondemand.com/console/?mode=details

https://opensap.hana.ondemand.com/console/?mode=details

[Former Member · Accepted solution]

Right - you showed us you Studio instance. Your HANA instance is m2.2xlarge which is 34GB. That's not your problem then.

Double click on your system and see how much RAM is used and available - let's just double check that first.

Then let's dig into the index server log. Click Diagnosis Files, sort by modified date. There will be a file like indexserver_alert_saphana1.trc. Run an activation and see if something is logged in that file. Paste it here.

John