Kevin,
I hope you don't mind but I wanted to add your latest response here as this thread is becoming very fragmented - I see your issue very much related to what I experienced earlier this evening as an over-consumption/leaking/lockout of certain system resources.
Sorry to hear your are still having issues but THANKS for the support and contribution, I would go back to re-use of my earlier AMI but have no confidence the issue would not rear its head again. Note I had to double my instance size in order to perform base operations - I dont know if this is a test option for you with Cloudshare, the sizing is fixed?
I hope we can get concerted help from SAP, I wonder if the issues are known/reported within the Service Marketplace, surely other appliances on SPS6 revision 60 are seeing this?????
From Kevin Small 19-Aug-2013 23:58
"Hi Wolfgang,
I've executed the "count(*) from public.schemas" a few times and have had mixed results.
When I first restarted my instance after a few days without using it, everything seemed fine again. The Catalog opened fine, I could browse schemas and the "count(*)" returned quickly saying 18.
As soon as I started using the Studio for a while, maybe an hour, things started to go bad again. Even opening an SQL window was taking >5 minutes, and the "count(*)" statement did return but took >10 minutes to return a value of 18.
I've rebooted the VM, done a ./HDB start stop and it is back hanging again. Opening the Catalog just hangs completely, it does not complete within an hour. (And same as before, even when the Studio hangs opening the Catalog folder, I can call OData services ok, IDE lite runs and is usable, XSEngine is fine.)
Regards, Kevin."