SAP HANA STUDIO Not Responding

[Former Member]

Hi All,

Good Day!!

Recently I have updated SAP HANA instance from SPS5 Revision 52 to SPS6 Revision 60.

I have updated SAP HANA Studio as well to SPS6 revision 60.

When I try to go to Modeler perspective and navigate to the content folder under my ID, the STUDIO gets hung.

After waiting, I could see in the task manager that "Modeler - - SAP HANA STUDIO Not Responding"

When I end it in task manager, I get the below error.

--XX: +HeapDumpOnOutOfMemoryError

I'm facing this issue only when I try to navigate to content folder and I don't see with rest of the navigations.

Later I updated SAP HANA Studio to revision 61, and this actually fixed the issue, I don't see this error in revision 61.

Please provide inputs or solution if anyone has come across the same issue.

Thanks & Regards,

Sampath Shankar

[pradeep_gupta]

Hello All,

I was facing this error since long.

Initially I started working with SAP HANA Studio 1.0 rev_60 & Client rev_60.

Suddenly in between the project,

When I used to open a Calculation View in HANA Studio, it started to hang. On closing the Studio, it would prompt a JAVA Heap memory issue as pointed out by Sankar.

I also tried to increase the memory in the .INI file as suggested by Christoph Pohl :

"max heap size in hdbstudio.ini from -Xmx1024m to, say, -Xmx1536m."

Dint work though.

Finally I uninstalled the Studio and Client, and reinstalled the latest versions

i.e. sap_hana_studio_win64_rev70

   & sap_hana_client_win32_rev70

https://hanadeveditionsapicl.hana.ondemand.com/hanadevedition/

And voila, It worked !!! Now I can open any CV without my system getting hanged.

I would like to thank SAP, all members involved in the post above for your valueable inputs, which has prompted SAP to get this resolved in the rev_70 version of SAP HANA. (atleast works for me).

Thank you all.

Its been a gr8 post.

[former_member184768]

Hi All,

We recently upgraded to Revision 66. So far (touch wood), there have been no issues related to the Studio hanging with "Fetching Children" issue. That doesn't mean everything is perfect as

• there are still some slow performance issues regarding the UNION nodes
• a couple of times the activation of view (which is used in multiple views above in layered architecture) has resulted in studio hanging
• sometimes the activation status shows "waiting" without any progress.

But in general it is not as painful as it used to be.

Regards,

Ravi

[former_member182500]

@SAP - A date for planned public release into community of latest Studio revision would be appreciated.

Two months ago we were asked for "a little more of your over-stretched patience", and still no communication of forthcoming release which might ease our pain.

Many thanks.

[Former Member]

- can you let me know where on SMP you downloaded just the Studio client ? Can't seem to find it. Thx !

[henrique_pinto]

Noob. 😉

[former_member184768]

Hi Clint,

Unfortunately my S-user id doesn't have access to the HANA Studio or Client install. I get it from our Basis team.

You can search for the HANA studio and may find the recent release on the Marketplace. To my knowledge, the past revisions are generally not available.

Regards,

Ravi

[former_member182500]

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 (in response to Wolfgang Auer)

"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."

[kevin_small]

In response to Uwe's earlier question about memory use, perhaps that is the issue.

I use a CloudShare instance which is fixed at 20 GB, non-upgradable they tell me.

I've searched on the service marketplace and there is no note relating to this issue.  Which makes sense since no live customer will be using a miniscule 20 GB instance.

I am getting about 30 minutes usage every 4 or 5 reboots of the VM, frustrating and not something sustainable.

Does this mean CloudShare is not a viable option anymore?

[former_member182500]

Perhaps through the course of your 30 minutes system practical availability you could take snapshots of the Administration overview, to see if usage grows abnormally until your system is no longer responsive?

I would be interested if you have seen this thread regarding "negative CPU index" and whether you also experience this error and significant growth of trace files, viewable via the Diagnosis Files tab, in your Cloudshare instance:

http://scn.sap.com/thread/3409932

I had hoped we would have had more SAP support and communication - disappointing and disheartening.  It remains to be seen whether this issue will become more commonplace as the upgrade process to SPS6 rev60 has recently been updated.

[Former Member]

Kevin and Jon-Paul,

it seems that is only so much we can do either on cloudshare or on aws, but i appreciate all the work you guys are doing as i thought i was alone with my studio reboots and refreshes (i've been quite lucky not to have to do any reinstalls recently). since we don't have the full control of the client/server cloud the questions always remain as to what is really going on the server.

SAP seems to want to help, but we can't really expect support at the level of a corporate paying account, so it's really great that this thread remains open but IMHO deserves more visibility if not here then on twitter, linkedin, etc.

thx,

greg

[Former Member]

Hi,

> open but IMHO deserves more visibility if not here then on twitter, linkedin, etc.

To be honest I don't want that my help and support is twittered to any body outside the SAP community.

Regards, Wolfgang

[Former Member]

Hi Kevin and Jon-Paul,

can your check the index server traces for entries like.

reading from channel 641 to 60788 <127.0.0.1:30005> failed with rc=14 (connection broken)

BufferedIO.cpp(01092) : channel 641 from <127.0.0.1:30005>: read from channel failed; resetting buffer

ERROR: reading from channel 3217 to 48415 <127.0.0.1:30005> failed with rc=14 (connection broken)

It seems that public.schemas is not responsive because it needs to collect schema names from other index server which reside in a different process.

Regards, Wolfgang

[former_member182500]

I do understand we cannot expect the same level of support afforded to a license paying corporate with Service Marketplace access and timely response.   We can only rely on the experiences, goodwill and time of the community, including best endeavours of the limited SAP resource expertise.

I also understand that given the contributions made to this thread, Kevin, myself and yourself must be in the very small minority - most SPS6 rev. 60 developers must have an adequate user experience otherwise they would be posting here (I hope!).  I would not expect limited SAP resources to be devoted to solution of an (intermittent) problem experienced by a handful.

Personally I don't think use of social media would be appropriate, constructive or deliver gains here.

I have myself effectively parked any further Hana development in the last week - disillusioned, frustrated and in the dark with regard to possible known issues or news of forthcoming revisions.  Recently greater time has been spent experiencing poor performance including non-response and posting about it here than enjoying a rewarding development experience I had with 56, especially during OpenSAP. 

In a week or so I'll pick it back up and battle on, possibly with a completely fresh SPS6 instance.  In the meantime I need to learn to write more concise posts

[former_member182500]

Hi Wolfgang,

As I have mentioned, for me the "public schema selection" problem is intermittent - some days I have not been able to work at all despite instance restarts, others the hanging issue goes away. 

Let's also not forget one of the original performance concerns - poor performance during normal development practices like copy/past of artefacts and repeated commitment of projects.  Any update?

Back on specific topic regarding index server traces.  Problem is intermittent, so having spun up my instance today schema selection is OK, but looking back through the index server trace files I find the following example.  There may have been more occurrences of this error , for example on the 15/08 when I first tried your suggestion, but I didn't back up my running system with another AMI when having a bad day with this - no point.

Perhaps these error messages are more prevalent on Cloudshare instances, Kevin?

[4691]{-1}[-1/-1] 2013-08-10 18:09:54.947391 e TrexNet          Channel.cpp(00345) : ERROR: reading from channel 360 to 30003 <127.0.0.1:45673> failed with rc=14 (connection broken)

[4691]{-1}[-1/-1] 2013-08-10 18:09:54.947411 e TrexNetBuffer    BufferedIO.cpp(01092) : channel 360 from <127.0.0.1:45673>: read from channel failed; resetting buffer

[4691]{-1}[-1/-1] 2013-08-10 18:09:54.947487 e indexserver      TREXIndexServer.cpp(03043) : TrexNet-Exception while dispatching to ims_search_api function: ReadChannel/127.0.0.1:45673/connection broken

FYI, every index server trace file contains a mass of the following:

[4693]{403189}[32/-1] 2013-08-10 18:10:17.868968 i TraceContext     TraceContext.cpp(00290) : UserName=SYSTEM, ApplicationUserName=JP, ApplicationName=HDBStudio

[4693]{403189}[32/-1] 2013-08-10 18:10:17.868964 e TransactionManag TransTokenManager.cpp(00497) : TransTokenManager::getPartitionID: a negative CPU socket index is returned - fallback: a dummy partition ID is assigned

[4693]{403189}[32/-1] 2013-08-10 18:10:17.869562 e TransactionManag TransTokenManager.cpp(00497) : TransTokenManager::getPartitionID: a negative CPU socket index is returned - fallback: a dummy partition ID is assigned

[4693]{403962}[36/-1] 2013-08-10 18:10:17.917140 i TraceContext     TraceContext.cpp(00290) : UserName=SYSTEM

[4693]{403962}[36/-1] 2013-08-10 18:10:17.917136 e TransactionManag TransTokenManager.cpp(00497) : TransTokenManager::getPartitionID: a negative CPU socket index is returned - fallback: a dummy partition ID is assigned

[4693]{403189}[32/-1] 2013-08-10 18:10:18.241213 e TransactionManag TransTokenManager.cpp(00497) : TransTokenManager::getPartitionID: a negative CPU socket index is returned - fallback: a dummy partition ID is assigned

[4693]{403189}[32/-1] 2013-08-10 18:10:18.365178 i TraceContext     TraceContext.cpp(00290) : UserName=SYSTEM, ApplicationUserName=JP, ApplicationName=HDBStudio

[4693]{403189}[32/-1] 2013-08-10 18:10:18.365175 e TransactionManag TransTokenManager.cpp(00497) : TransTokenManager::getPartitionID: a negative CPU socket index is returned - fallback: a dummy partition ID is assigned

[4693]{403189}[32/-1] 2013-08-10 18:10:18.365796 e TransactionManag TransTokenManager.cpp(00497) : TransTokenManager::getPartitionID: a negative CPU socket index is returned - fallback: a dummy partition ID is assigned

[4693]{403189}[32/-1] 2013-08-10 18:10:18.367154 e TransactionManag TransTokenManager.cpp(00497) : TransTokenManager::getPartitionID: a negative CPU socket index is returned - fallback: a dummy partition ID is assigned

[4693]{403962}[36/-1] 2013-08-10 18:10:18.577107 e TransactionManag TransTokenManager.cpp(00497) : TransTokenManager::getPartitionID: a negative CPU socket index is returned - fallback: a dummy partition ID is assigned

[4693]{403962}[36/-1] 2013-08-10 18:10:18.709191 i TraceContext     TraceContext.cpp(00290) : UserName=SYSTEM

[4693]{403962}[36/-1] 2013-08-10 18:10:18.709187 e TransactionManag TransTokenManager.cpp(00497) : TransTokenManager::getPartitionID: a negative CPU socket index is returned - fallback: a dummy partition ID is assigned

[4693]{403962}[36/-1] 2013-08-10 18:10:18.709868 e TransactionManag TransTokenManager.cpp(00497) : TransTokenManager::getPartitionID: a negative CPU socket index is returned - fallback: a dummy partition ID is assigned

[4693]{403189}[32/-1] 2013-08-10 18:10:18.745189 e TransactionManag TransTokenManager.cpp(00497) : TransTokenManager::getPartitionID: a negative CPU socket index is returned - fallback: a dummy partition ID is assigned

[4696]{400583}[28/-1] 2013-08-10 18:10:18.757953 e TransactionManag TransTokenManager.cpp(00497) : TransTokenManager::getPartitionID: a negative CPU socket index is returned - fallback: a dummy partition ID is assigned

[4696]{400583}[28/-1] 2013-08-10 18:10:18.758009 i TraceContext     TraceContext.cpp(00290) : UserName=DSOD

[4696]{400583}[28/-1] 2013-08-10 18:10:18.758007 e TransactionManag TransTokenManager.cpp(00497) : TransTokenManager::getPartitionID: a negative CPU socket index is returned - fallback: a dummy partition ID is assigned

[4696]{400583}[28/-1] 2013-08-10 18:10:18.758516 e TransactionManag TransTokenManager.cpp(00497) : TransTokenManager::getPartitionID: a negative CPU socket index is returned - fallback: a dummy partition ID is assigned

[4696]{400583}[28/-1] 2013-08-10 18:10:18.758765 i TraceContext     TraceContext.cpp(00290) : UserName=DSOD

[4696]{400583}[28/-1] 2013-08-10 18:10:18.758762 e TransactionManag TransTokenManager.cpp(00497) : TransTokenManager::getPartitionID: a negative CPU socket index is returned - fallback: a dummy partition ID is assigned

[4693]{403189}[32/-1] 2013-08-10 18:10:18.869364 i TraceContext     TraceContext.cpp(00290) : UserName=SYSTEM, ApplicationUserName=JP, ApplicationName=HDBStudio

Thanks for your time, appreciated.

[Former Member]

Jon-Paul,

all i can say hang in there and don't reduce your feedback as SAP certainly appreciates it. they do respond (even when this is a 'free' product). as to social media, it works for some, but not for everybody. this thread with all questions and responses is already part of it as it will show up in google searches whether you want it or not.

we all have a common interest here, ie to make hana work for us and and what's more important for our clients. social media is just another channel, if used properly, it delivers on its promise, at least it has for me.

i don't want his thread to be about social media and i will refrain from further posts about it. as to the problem we seem to all have experienced. i'm going to rebuild my project from scratch and try to delete the 'corrupt' one, but deletions have been very painful for me in the past, so at some point i may simply abandon it.

good luck with the fresh copy of SP6.

thx,

greg

[Former Member]

Hi Wolfgang,

i don't see anything wrong to let others know that SAP staff is trying to help others accept its flagship product. it so happens that most of my twitter followers/followees are already part of SAP community and if my posts were inappropriate i would simply get unfollowed. having said that i will not mention it any more, so i don't lose the support i'm getting here.

Best regards,

greg

[former_member182500]

Hi Greg,

Thanks for the support, as it's a cloudy Sunday where I am I think I will start with a fresh SPS6 instance and complete re-install of Studio and Client.  Of course I will post any further issues related to this thread.

Before you rebuild, which of the performance issues do you experience?  Is there anything you can document with a Youtube video that adds value to those I have created?  Did you execute the tests suggested by Wolfgang?

Many thanks.

[Former Member]

Jon-Paul,

i don't think you would enjoy me on youtube, but it may be a great medium for others. i have experienced

1. "fetching children",

2. very long activation times,

3. active icon staying grey after message saying "active",

4. web IDE not displaying an active file,

5. and many many studio crashes in the past.

my latest theory is that i may have kept too large data files that bogged down the synchronization between my machine and the server. i will report back after my 10th project re-build to see if this theory is true. Wolfgang's tests, while proving positive, didn't seem to diagnose my underlying problem.

my Sunday looks like lots of sunshine but the day is only beginning.

thx,

greg

[Former Member]

Hi Kevin and Jon-Paul,

can you give temporarily the statistics server more memory?

Value:

Admin Editor->Configuration->statistisccserver.ini->memorymanager->allocationlimit->5%

To

20%

Regards, Wolfgang

alter system alter configuration ('statisticsserver.ini','SYSTEM') set ('statisticsserver_general','editing')='yes' with reconfigure;

  ;

  alter system alter configuration ('statisticsserver.ini','SYSTEM') set ('memorymanager','allocationlimit')='20%';

  ;

  alter system alter configuration ('statisticsserver.ini','SYSTEM') unset ('statisticsserver_general','editing') with reconfigure;

  ;

  select * from m_inifile_Contents where section = 'memorymanager'

  ;

  alter system stop service('<your server>',3<instance
number>05) immediate

  ;

  select * from m_service_statistics

  ;

  select * from public.schemas

[kevin_small]

Hi Wolfgang,

I tried the statements above and all executed ok apart from the last statement.  Here is the output:

Statement 'alter system alter configuration ('statisticsserver.ini','SYSTEM') set ...'

successfully executed in 554 ms 937 µs  (server processing time: 323 ms 293 µs) - Rows Affected: 0

Statement 'alter system alter configuration ('statisticsserver.ini','SYSTEM') set ...'

successfully executed in 189 ms 449 µs  (server processing time: 16 ms 258 µs) - Rows Affected: 0

Statement 'alter system alter configuration ('statisticsserver.ini','SYSTEM') unset ...'

successfully executed in 256 ms 222 µs  (server processing time: 82 ms 873 µs) - Rows Affected: 0

Statement 'select * from m_inifile_Contents where section = 'memorymanager''

successfully executed in 617 ms 805 µs  (server processing time: 398 ms 647 µs)

Fetched 8 row(s) in 0 ms 139 µs (server processing time: 0 ms 0 µs)

Statement 'alter system stop service('hanacloud',30005) immediate'

successfully executed in 263 ms 943 µs  (server processing time: 2 ms 447 µs) - Rows Affected: 0

Statement 'select * from m_service_statistics'

successfully executed in 2.131 seconds  (server processing time: 1.885 seconds)

Fetched 6 row(s) in 0 ms 120 µs (server processing time: 0 ms 0 µs)

Could not execute 'select * from public.schemas' in 422 ms 682 µs .

SAP DBTech JDBC: [3587]: invalid protocol or indexserver (statisticsserver) shutdown during distributed query execution:  [2613] executor: communication problem

Duration of 7 statements: 4.436 seconds

Then I tried it again without the "stop service" statement and the system hung at the "select * from public.schemas" statement.  I repeated this again after a reboot of the server VM and the "select * from public.schemas" did complete ok that time (with the stop service commented out) but it took over 3 minutes to do so.

Unfortunately I won't be able to help diagnose further, I've restored my instance from a backup to try to workaround the issue.  If the issue returns I will post back here.  Thanks for your help.

[Former Member]

Hi,

I was to optimistic with the restart time of a service.

alter system stop service('<your server>',3<instancenumber>05) immediate

  ;

=>>>>>>>>>>>>>>> WAIT SOME TIME >>>>>>>>>>>>>>>>>>>>

  select * from m_service_statistics

Regards, Wolfgang

[kevin_small]

Hi Wolfgang,

I have restored from a backup now and cannot replicate the fault any more. From reading others' experiences it seems possible that the error will come back.  When it does I will post back results here.

Thanks for investigating.

Kevin.

[kevin_small]

Hi Wolfgang,

The issue came back again today, opening the Catalog folder started hanging again.  So I tried the SQL statements you provided.

Once I added in the wait part as you suggested, this seemed to fix the issue.  The final SELECT quickly returned all public schemas, and the Catalog folder now opens quickly.

Thanks for providing the workaround.

Kevin.

[former_member102219]

Hi Gentlemen, have you found the cause finally?

I've ran into this issue shortly after installing AFL on the rev60 HANA server. My Studio/Client are rev64.

No "Fetching children", no activation of SAPUI5 content, no "select count(*) from public.schemas" -- all hangs.

Happy to raise an OSS ticket, unless someone else already did it.

Cheers!
/RB

[former_member182500]

Hi,

Froze for me today (and the first day back logged on in weeks, so not a great start), executed the workaround, got as far as the "stop service" then system wouldn't respond, and AWS instance status had warnings about connection to system. 

Took a copy of the instance, terminated and restarted, all seems OK now, with successful and timely result sets from select of statistics and public schemas.

[former_member182500]

Hi Wolfgang,

I had to execute your workaround again today due to a hanging catalog folder expansion in the SAP Hana Systems tab .

Is there a more permanent solution in the offing?

Thanks.

[Former Member]

Hi Wolfgang,

when i am executing command

alter system stop service('54.251.162.124',30005) immediate;

it give me error

Could not execute 'alter system stop service('54.251.162.124',30005) immediate' in 87 ms 779 µs .

SAP DBTech JDBC: [2]: general error: host and port are not found .

I am using amazonaws server

Please help me..

Thanks..

Amit

[Former Member]

Hi,

the solution will be that we get rid of the statistic server as a separate process.

We are working on this.

Regards, Wolfgang

[Former Member]

Hi,

please select the m_services table and look what is the host of the stat server.

Regards, Wolfgang

[former_member182500]

Hi Amit,

You need to use your host name.  For example mine is imdbhdb.

[former_member182500]

Thanks for the update.  Despite trying your workaround I still have issues with Studio hanging on "Fetching children" when trying to expand the SAP Hana Systems catalog folder.

Still a flaky development environment for those with access only to Rev. 60. 

Still no recent Studio refresh for the community at large.

Still pretty much non-existent communication from SAP despite months of suffering with this poor revision.

With CEO's and technology directors espousing game changing features of Hana it will only ever be just hot air without continued grass roots support of the development community.  How can it be that revisions such as 66 are unavailable to the entire community - after all SAP did court a whole community with OpenSAP HANA,  madness.

Rant over - (yet) another day wasted with Studio 60.

Oh Golden Age of rev 56, my world has grown grey since your passing.

[former_member182500]

Hi Wolfgang,

With regard to "the solution will be that we get rid of the statistic server as a separate process" was there any analysis or hypothesis done "in-house" to suggest why this statistics server issue may arise for some but not majority of other Hana Developer rev. 60 users, bearing in mind there is a commonality in support pack level and feature set, instance sizing, default statistics server configuration (e.g. memory allocation) etc?

Can you confirm if this issue is definitely identified as the main cause of the catalog hangup? 

If the product team are still working on a solution then it is not out in the wild yet.  Thomas indicates no experience of these issues in use of several build flavours.  Many other AWS and Cloudshare rev 60 developers do not post here.  Ravindra Channe does not yet report persisting catalog hangup issues, and that is with rev 66 without the "fix in progress".   How can that be?

Is there a proactive workaround as opposed to your suggested reactive workaround? 

Do you have a timeline for delivery of this permanent solution, can we expect this in the next AWS revision?

Just looking for some light.  Much appreciated, many thanks.

[Former Member]

aws was fine this morning and it may have been bounced but now it's hanging with "Operation in progress..."

[Former Member]

Hi,

the root cause is that with the stat server as a seperate process the query on schemas is getting distributed. With SP7 we move the catalog of stat service into the main index server.

Like this the current situation can not occur any more.

For the moment the only workaround will be to give the stat server enough memory so the distributed query can be processed.

If you don't need the stat server at all you can remove it from the topology.

BUT this will break you back up history!

You have to handle this decision with care and immediately do a full data back up.

http://scn.sap.com/thread/3257759

SAP Note 1697613

https://websmp230.sap-ag.de/sap(bD16aCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1037575

Kind Regards, Wolfgang

[former_member182500]

Thanks Wolfgang for the added info.

"stat server as a seperate process the query on schemas is getting distributed." is the default for everyone, right? 

If this is indeed the core issue of the catalog querying then all appliances with this stat server process distribution configuration would inherit this problem and subsequently more users would experience the "hanging" as has been reported here.

Most users, including Thomas, have not reported any such hanging - it doesn't add up.

Any timeline for SP7 release to AWS and other cloud platforms?

Thanks.

[thomas_jung]

I think it does add up.  Note Wolfgang's remark:
For the moment the only workaround will be to give the stat server enough memory so the distributed query can be processed.

So if your system has enough available memory, there won't be a problem with this distributed query. In my mind this would primarily be an issue on systems like the AWS Developer Center where memory is very tight. Perhaps Wolfgang will clarify this point, but this was my impression of his answer.

[former_member182500]

Thomas, I don't know the figures but there must be minimal hundreds of AWS Hana Developer instances based on the recommended m2.2xlarge sizing - if the problem is as fundamental, core and generic as Wolfgang alludes to then you would agree that all these hundreds of instances, where "where memory is very tight", are affected, yes?

If yes, then where are the hundreds of SP6 developers screaming about this?  That's why it doesn't add up for me at least, yet happy to be enlightened.

Earlier in this thread I highlighted sluggish performance with an m2.4xlarge instance - that's double the memory capacity of recommended standard, with 68Gb.  I will continue to develop for the next week with an m2.4xlarge instance, adjusted with higher memory allocation to the statistics process, as per Wolfgang's workaround, and see how it goes. 

Perhaps a general consideration for now to "up" the default sizing to m2.4xlarge along with Wolfgang's workaround?

Thanks.

[Former Member]

is there any particular reason why we should not be able to go to 117GiB other than SAP and Amazon not having this written up somewhere? #lowmemory

[former_member182500]

16 cores and 117Gb on hs1.8xlarge, extravagant Gregory, I like it. 

I don't see why that should be a problem as long as your pockets are deep enough - I imagine the appliance will dynamically allocate/consume available resources no matter whether that memory bucket is big or bigger, of course would need an expert to confirm.

[PavanKrishna]

Hi Jon-Paul Boyd and others,

I have executed all the SQL statements mentioned by Wolfgang but am getting errors while executing the statement

'alter system stop service('54.83.17.204',imdbhdb) immediate';

The errors are mentioned below:

Could not execute 'alter system stop service('54.83.17.204',30015) immediate' in 302 ms 46 µs .

SAP DBTech JDBC: [2]: general error: host and port are not found

Could not execute 'alter system stop service('54.83.17.204',imdbhdb) immediate' in 301 ms 657 µs .

SAP DBTech JDBC: [257] (at 42): sql syntax error: incorrect syntax near "imdbhdb": line 1 col 42 (at pos 42)

Could not execute ''alter system stop service('54.83.17.204',imdbhdb) immediate'' in 301 ms 199 µs .

SAP DBTech JDBC: [257]: sql syntax error: incorrect syntax near "alter system stop service(": line 1 col 1 (at pos 1)

Can one of you please let me know what the error is and how to fix it. I am fed up with the message in my HANA studio "Fetching Children'.. I am using

Version: 1.0.7000

Build id:  386119

Thank you.

Regards,

Pavan.

[Former Member]

Hi,

the SQL is

ALTER SYSTEM STOP SERVICE 'host:port'

Regards, Wolfgang

[PavanKrishna]

Hi Wolfgang,

Thanks a lot. I tried the command

ALTER SYSTEM STOP SERVICE '54.83.17.204:30015'; but this is also giving the same error.

Then I tried

ALTER SYSTEM STOP SERVICE '54.83.17.204:imdbhdb'; This time I got an error saying

Database connection lost.

I restarted the studio and this time the Fetching Children message didn't appear. And the catalogs folder expanded within 10 seconds

Don't know why it was not working earlier but as of now there is no issue.

Thank you.

Regards,

Pavan.

[former_member182500]

In addition to resolution of the hanging hana system catalog issue both Kevin Small and I experience, is any update available on resolution of very slow user operations like copy/paste of artefacts. 

Have SAP seen these issues for themselves?

Do we have a timeline for publicly available new revision of Studio?

Many thanks, much appreciate an information update.

[uwe_kylau]

Hi Jon-Paul.

I did experience performance issues with a Rev.60 server on AWS today. Everything worked fine for two weeks. I stopped and started the instance a few times. Then I stop the instance on Saturday and after re-start today (Monday) it's just mayhem. Tried to make simple change in a HTML file using IDE Lite, but it just hangs on Save/Activate. Same thing in the big Web-IDE. HANA Studio looked fine at first, but after a while (and a few restarts of the server) everything just falls apart. In the end, I'm facing the "Fetching Children" hang, as well as not being able to load the admin view of the system (the one you get when double-clicking a system entry in the system explorer).

Now, here is what I think has happended, although I cannot say with 100% certainty.

I stop the server and change the instance type. Initially I just had launched it as a m2.xlarge (17GB RAM). I go one size up: m2.2xlarge (34 GB). Re-start the server. Voila, everything runs smooth like a clockwork.

I go into HANA studio to check the memory footprint. ... Just what I expected. The freshly started server consumes about 13.5 GB out of 30.7 GB that are available. Now, projecting that down, on a 17 GB instance you will have about 13.5-13.7 GB available. So, my guess is that I ran into a memory issue. The studio behaving badly is just a result of that, because it takes forever to get responses from the server.

Question back to you. What AWS instance type are you using? Can you check the memory footprint?

I guess you have done that before, but just in case here is a screenshot of what you are looking for after double-clicking your system in the system explorer. This system uses about 25.4 GB out of 485 GB.

Cheers,

Uwe

[former_member182500]

Hi Uwe,

I can imagine issues exacerbated with m2.xlarge.

However I have always used m2.2xlarge.  Maybe I should try the next instance size up 😉

Thanks.

[former_member182500]

Hi Uwe,

I spun up my m2.2xlarge instance I am having Catalog issues with, to take a look at used memory as you suggested, out of interest.

Upon trying to open the Administration Console Studio hangs on the Progress Information "Operation in Progress" popup dialog.  

Marvellous - but thanks for your suggestion, worth a shot.

[former_member182500]

Uwe,

Bashing away at this with a hammer, being stubborn,, I thought I would spin up an m2.4xlarge instance of my troublesome AMI:

Despite being a little sluggish, the administration overview appeared after a couple of seconds (it hung on m2.2xlarge), here's the screenshot:

So, considering my two AMIs I have at the moment in relation to m2.2xlarge sizing. 

• Upon fresh instance launch what is appearing to be consuming system resource to such effect that catalog/content and administration console requests hang, for one of the AMIs but not the other?   And.....

• where the troublesome AMI fails with m2.2xlarge, it (just about) functions with m2.4xlarge, with administration console/catalog and content drilldown/SQL console select from public.schemas works (slowly).

I hope this additional information helps.

[former_member182500]

Video of issue opening local workspace project.  Now this one surprised even me, as it was the first time I had experienced this in SPS6 rev.60.  All videos now a symptom of the same issue?

Studio seems to be getting progressively worse throughout the 3 or 4 full re-installs I have had to do.

Note that about 00:50 into the video Studio stops responding and dumps out - note the error "HeapDumpOnOutOfMemoryError" as was highlighted by the OP Shankar at the start of this thread and also noted by Stephen Kringas. 

Despite adjusting a .HDBSTUDIO.INI configuration parameter from -Xmx1024m to -Xmx1536m as advised by Christoph Pohl the heap dump is given.

Even after a fresh install of both client and studio after I recorded these videos  (having performed the hdbuninst for client and studio first) I get the "pending" hangs after expanding the System catalog folder and when creating a new Hana Repository workspace and trying to expand the packages.

@SAP - I offer access to my AWS instance, I'll even offer remote desktop to my PC if it will help diagnose and resolve these issues.

Don't know if this helps but a snippet from the /hdbstudio/metadata/.log file

!ENTRY com.sap.ndb.studio.backup 4 4 2013-08-15 19:14:53.696

!MESSAGE Could not open connection to 'HDB hanaaws 00'

!STACK 0

java.util.concurrent.TimeoutException

          at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)

          at java.util.concurrent.FutureTask.get(Unknown Source)

          at com.sap.ndb.studio.backup.BackupConnectionHandler.openConnection(BackupConnectionHandler.java:111)

          at com.sap.ndb.studio.backup.BackupConnectionHandler.getConnection(BackupConnectionHandler.java:84)

          at com.sap.ndb.studio.backup.BackupWorkbenchAdapter$2.call(BackupWorkbenchAdapter.java:151)

          at com.sap.ndb.studio.backup.BackupWorkbenchAdapter$2.call(BackupWorkbenchAdapter.java:1)

          at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)

          at java.util.concurrent.FutureTask.run(Unknown Source)

          at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

          at java.lang.Thread.run(Unknown Source)

!ENTRY org.eclipse.core.jobs 2 2 2013-08-15 19:15:41.743

!MESSAGE Job found still running after platform shutdown.  Jobs should be canceled by the plugin that scheduled them during shutdown: com.sap.ndb.studio.catalog.CatalogWorkbenchAdapter$1

!SESSION 2013-08-15 19:15:42.860 -----------------------------------------------

eclipse.buildId=unknown

java.version=1.7.0_21

java.vendor=Oracle Corporation

BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB

Command-line arguments:  -os win32 -ws win32 -arch x86_64

!ENTRY org.eclipse.emf.ecore 2 0 2013-08-15 19:15:44.034

!MESSAGE Both 'com.sap.ndb.studio.repository.model.resource' and 'com.sap.ndb.studio.rules.ecoremodel' register an extension parser for 'resource'

!ENTRY org.eclipse.emf.ecore 2 0 2013-08-15 19:15:44.035

!MESSAGE Both 'com.sap.ndb.studio.rules.ecoremodel' and 'com.sap.ndb.studio.search.model' register an extension parser for 'search'

!ENTRY org.eclipse.ui 2 0 2013-08-15 19:15:44.856

!MESSAGE Warnings while parsing the key bindings from the 'org.eclipse.ui.commands' extension point

!SUBENTRY 1 org.eclipse.ui 2 0 2013-08-15 19:15:44.856

!MESSAGE Could not parse key sequence: plug-in='com.sap.ndb.studio.planviz', id='pvcommand.prepare', keySequence='CTRL + SHIFT + V'

!ENTRY org.eclipse.osgi 2 1 2013-08-15 19:15:52.459

!MESSAGE NLS missing message: editor_catalog_header_message in: com.sap.ndb.studio.federation.catalog.i18n.messages

!SESSION 2013-08-15 20:51:55.937 -----------------------------------------------

eclipse.buildId=unknown

java.version=1.7.0_21

java.vendor=Oracle Corporation

BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB

Command-line arguments:  -os win32 -ws win32 -arch x86_64

!ENTRY org.eclipse.emf.ecore 2 0 2013-08-15 20:51:57.838

!MESSAGE Both 'com.sap.ndb.studio.repository.model.resource' and 'com.sap.ndb.studio.rules.ecoremodel' register an extension parser for 'resource'

!ENTRY org.eclipse.emf.ecore 2 0 2013-08-15 20:51:57.839

!MESSAGE Both 'com.sap.ndb.studio.rules.ecoremodel' and 'com.sap.ndb.studio.search.model' register an extension parser for 'search'

!ENTRY org.eclipse.ui 2 0 2013-08-15 20:51:58.764

!MESSAGE Warnings while parsing the key bindings from the 'org.eclipse.ui.commands' extension point

!SUBENTRY 1 org.eclipse.ui 2 0 2013-08-15 20:51:58.764

!MESSAGE Could not parse key sequence: plug-in='com.sap.ndb.studio.planviz', id='pvcommand.prepare', keySequence='CTRL + SHIFT + V'

!ENTRY org.eclipse.osgi 2 1 2013-08-15 20:52:07.674

!MESSAGE NLS missing message: editor_catalog_header_message in: com.sap.ndb.studio.federation.catalog.i18n.messages

!SESSION 2013-08-15 20:52:35.318 -----------------------------------------------

eclipse.buildId=unknown

java.version=1.7.0_21

java.vendor=Oracle Corporation

BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB

Command-line arguments:  -os win32 -ws win32 -arch x86_64

[former_member182500]

Video of issue opening catalog folder and Hana repository (remains in pending with "Fetching children").

[former_member182500]

Video of issue opening content folder in systems tab (after expanding packages, when I expect to see the child list of runtime artefacts it remains in pending with "Fetching children").

Audio commentary removed as unfit for public consumption.

[former_member182500]

Video of issue selecting from public schema using SQL console.

Shows hanging select from public schema yet meanwhile a successful select from another schema returns a result set.

[kevin_small]

I can confirm that Studio rev 62 does not fix the issue of opening the Catalog folder, as experienced by the original poster and several more people in this thread including myself.

I just got a colleague to try connecting their rev 62 Studio client to my Cloudshare SPS6 and behaviour is identical - opening Content folder, Security folder etc is fine, but when you try to open Catalog folder it hangs saying "fetching children".

Given this used to work fine under rev 60, it looks like something has happened on the database side that does not get resolved when the server is restarted.

Very, very frustrating.  Do I have any other recourse before I restore my server to an earlier image?  I have been able to export my developments as a Delivery Unit, so not all is lost, but all the data loaded I will have to do again.

My worry is it is only a matter of time before this happens again.

[former_member182500]

Kevin - that's unfortunate revision 62 did not resolve your catelog folder issue.  A good test with your colleague trying on a separate PC and Studio revision.

Interesting that you lean towards a possible server-side issue.  A few days ago I was getting this same issue despite several restarts of Studio and performing a clean install. 

A the end of that day I created an AMI (Amazon Machine Image) from my active instance (in order to back up) as I normally do, and today when creating the active spot instance (running instance) from my latest AMI all was OK with opening of the catalog folder.   I did however experience the usual sluggish performance, I'm pointing a finger at SPS6 rev.60 "enhanced" project tracking and repository synchronisation for this.

I'm unfamiliar with ways of managing instances on Cloudshare.  Correct me if I'm wrong but Cloudshare is always-on 24/7 right, so normally your instance is never terminated (whereas I always terminate to stop the "meter")?  Apologies if I'm way off but are you able to take a backup of your running instance, terminate the running instance and relaunch the instance using the backup image and then test the catalog folder?  

By "bouncing" the server and performing a restart you may clear some HDB connection, log or other issue that is causing the problem, it's certainly worth a shot if possible and I'd love to wake up to success on this!   I hope you can find a resolution with minimal pain.

If the "catalog folder" issue occurs again for me I shall report back. 

[Former Member]

Hello,

to narrow down the  Catalog issue I would like to ask you the following.

Open the Admin perspective.

Go to the view "SAP HANA systems"

Press the tirangle on the right.

Choose menu "Customize View"

Choose Content

Deslect everything except Navigator and Catalog.

Do the problems still occur?

1) Yes. Turn on JDBC trace. System-> Properties->JDBC Trace. Please send the last (hanging) SQL statement

2) No. Enable step by step the other navigator contributors. If the problems occurs goto 1)

Best Regards, Wolfgang

[kevin_small]

Ok thanks Wolfgang for investigating.

Yes the problem still occurs after carrying out the customizing of views as you described.

The JDBC trace is here:  https://www.dropbox.com/s/x2f07a81k7vt43w/HDB_jdbctrace_01.log

That is a trace of opening the studio and immediately opening the Catalog folder (with urls etc removed).  That is when it hung.  I left it running 20 minutes and the trace file was not getting any bigger, so anything the system was going to log should be in there.

[kevin_small]

Thanks Jon-Paul, a useful idea, but in my case I chose the "not-always-on-but-unmetered-usage" Cloudshare option, so the instance is restarted regularly.

[Former Member]

Hi,

please open a SQL console and execute.

SELECT * FROM PUBLIC.SCHEMAS

Does it return? How long does it take to fetch the data?

Regards, Wolfgang

[former_member182500]

Hi Wolfgang,

My issue with the catalog folder, same as experienced by Kevin, is back.

I spun up an AWS instance this morning but didnt launch Studio for about an hour.  First thing I did was navigate to Systems tab and try to expand the catalog folder.  It hangs with "pending".

I closed and re-opened Studio, and with the same AWS instance tried:

SELECT * FROM PUBLIC.SCHEMAS

This also "hangs", remaining in the progress tab view incomplete.  Cancelling the SQL request seems to hang too.

I terminated the AWS instance and spun up a new instance.  I directly repeated the same exercise, using the SELECT * FROM PUBLIC.SCHEMAS and trying to open the catalog folder.  Hangs.

When I execute a SELECT on one of my own schema tables IT DOES NOT HANG:

select * from  "MISSIONCONTROL"."hpl.missioncontrol.data::MC.Purchase.Header";

In the meantime, after the result set has been successfully returned from my own schema table, the select for the PUBLIC.SCHEMAS is still in progress.

Thanks.

[Former Member]

Hi,

just to confirm.

SELECT * FROM PUBLIC.SCHEMAS in the SQL console does not return.

You did not trigger any action in parallel in the Studio.

If yes it seems the instances have a problem with the database catalog.

Regards, Wolfgang

[former_member182500]

Hi Wolfgang,

To confirm, for my first test of executing SELECT * FROM PUBLIC.SCHEMAS I performed no other user operation in parallel, just sat for minutes awaiting the result set which did not happen.  The operation appeared to be stuck in progress, and will remain in progress for as long as Studio is open.

Thanks,

[Former Member]

Hi,

so it is an catalog engine issue.

Can you open some kind of ticket?

I am not familair with the support level you can access.

Regards, Wolfgang

[former_member182500]

Wolfgang,

Unfortunately I cannot open any kind of ticket as I do not have Service Marketplace access, therefore would very much appreciate you being able to raise and log this issue in some manner and:

• Keep the community informed of any progress.
• Suggest any temporary fix or workaround, when available, to enable onward development.

Many thanks.

[kevin_small]

Same behaviour here:

SELECT * FROM PUBLIC.SCHEMAS

does not return, it just hangs.

[Former Member]

Hi,

I will inform you as soon as I have more information from DEV support.

Might it be ok to get an HANA support user account to one of your instances if support needs some trace fies etc ...

W.

[former_member182500]

Absolutely, just let me know via a direct message.

If this can be arranged please ask support to also look at slow performance issues too, I would be happy for them to check out my Hana repository and have a play with committing and activating development artefacts.

Many thanks.

[kevin_small]

Happy to help also if you want to see another instance, just let me know.

[Former Member]

Hi,

can you please execute

select count(*) from public.schemas

Does it return, how many schemas exist?

Regards, Wolfgang

[Former Member]

Hi,

can you please execute

select count(*) from public.schemas

Does it return, how many schemas exist?

Regards, Wolfgang

[former_member182500]

Executing the following hangs, with no result tab with result set returned.

select count(*) from public.schemas;

[former_member182500]

Wolfgang,

As above I tried both the SELECT * and the SELECT COUNT against my latest AMI.  Both hung and returned nothing as indicated.

I then spun up an earlier (older) AMI instance of SPS6 (a day older than the one with SELECT failing).  I execute the same two SQL statements, and I get positive successful returns.

Note that for this older instance I CAN successfully drill down the system catalog and content folders AND the Hana repository folder.  From my other posts, where a SELECT from public schemas fails the drill down to these artefacts fails too.

Perhaps this information may be useful to compare/contrast instance state to determine root issue?

Happy to work with you to carry out more tests.

[kevin_small]

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.

[kevin_small]

I am experiencing the exact same problem, and want to add my voice to this thread so that it is clear is it not an isolated problem.

Opening the Content folder works fine, and functionally all seems well - OData services work, I can call SQLScript ok, the IDE lite works etc.

However, any time I try to look at schemas in the Catalog by simply opening the Catalog folder on the System tab I get a variety of faults.  Sometimes the request seems to time out and I am left with an empty folder.  Sometimes the request does complete and I see the schemas underneath after about 20 minutes waiting - but this is rare.  The most common fault is that the system just hangs saying "fetching children" and even after an hour or so nothing is returned.  Usually then Eclipse locks up and I have to use task manager to close.

This is using CloudShare SPS6 and rev 60 of Studio.  The fault is identical in the CloudShare Windows Client also, so it is not something related to my front end.  The system was fairly stable for a good few weeks since I upgraded to SPS6 - at least any faults were recoverable but not this one. I've done all the usual reboots and HDB start/stop and nothing helps.

I have done significant development on this box, and am loathe to just restore an earlier image over the top.  If Studio Rev 61 fixes this then great, but we do not know when that is coming out and for now I am stuck and cannot develop any more.

Jon-Paul Boyd summed up my sentiments perfectly above, worth repeating:

We all want to make Hana work, to learn and share, to promote the appliance, to sell it to peers, managers and technology groups as a solution.  With a (currently) flawed developer tool how are we as developers able to effectively access and utilise this amazing engine "under the hood"?  Without an effective and stable developer tool all these wonderful appliance-side features are irrelevant.  Developers and enterprises will stop or park their interest and walk away.

[Former Member]

Dear Mr. Shankar,

At my end, a similar kind of issue has been resolved by increasing Virtual memory.

Kind rgds,

Ashwin Mane

[uwe_kylau]

Dear HANA Developers.

I don't want to comment on what has been said here, but there are lots of valid points and we will discuss them in the SAP Developer Center team.

In the meantime, I want to point out some of the new development features introduced with HANA SPS06, namely browser-based IDEs. Yes, granted, they do not solve all the issues. However, for XS and UI5 development they are a real productivity improvement (at least from my experience). And that is not just because of the instant save+activate feature, or the support for keyboard shortcuts (e.g. Ctrl+S/C/X/V). I recommend you try and see for yourself.

You will find these two XS Apps on your HANA Server Rev. 60 (or above) under the following URLs (insert your host name or IP first):

http://yourhostname:8000/sap/hana/xs/editor

a lite IDE to edit files (as plain-text) and packages

http://yourhostname:8000/sap/hana/xs/ide

IDE with more traditional look&feel and more features (code completion, debugging, ...)

See also kindly compiled by , where he provides an introduction to these IDEs.

I hope this will help you make some progress on your projects, while we figure out the situation with the HANA Studio.

Best Regards,

Uwe

[former_member182500]

Thank-you Uwe for taking these points into consideration. I will explore the browser-based IDEs as alternatives whilst awaiting a revised Studio, thanks for posting the info.

Without question all the hard work your teams put into Studio is appreciated.

[mylesfenlon]

Revision 62 is available in the Service Marketplace/Software Download Center. Just select your preferred platform for HANA Studio (following the path in the screenshot below) and choose the required revision.

I cannot comment on the stability or otherwise of the various revisions, but I would always suggest that you upgrade to the newest revision where possible.

Regards,

Myles

[former_member182500]

And for a great many developers who don't have direct access to the Service Marketplace or don't want to abuse their work/team service centre logins for private training purposes?  This will account for many OpenSAP Hana graduates who wish to explore promoted SPS6 features in "Extra Knowledge" with a stable Studio environment.  This group are your keenest exponents.

With regard to "cannot comment on the stability or otherwise of the various revisions" there must be release notes for revision 62, can you arrange for these to be made available here please?

And with regard to "suggest that you upgrade to the newest revision where possible" can you confirm then that Studio revision 62 is compatible with Hana appliance SPS6 60? Many thanks.

With all respect Myles I feel you unfairly closed the thread regarding the "open letter" requesting a stable Studio environment - it was a more generic plea for a stable IDE.  This merited further honest and open discussion  It was also an invitation for news of forthcoming improvement or indeed a readily available revision to be made public that addresses the fundamental issues we face.  Do we contribute here provided we make no fair complaint? 

http://scn.sap.com/thread/3405709

We all want to make Hana work, to learn and share, to promote the appliance, to sell it to peers, managers and technology groups as a solution.  With a (currently) flawed developer tool how are we as developers able to effectively access and utilise this amazing engine "under the hood"?  Without an effective and stable developer tool all these wonderful appliance-side features are irrelevant.  Developers and enterprises will stop or park their interest and walk away.

Again I hope this is fair comment borne from frustration, which may have been alleviated with readily accessible revisions and supporting communication. Would much prefer utilising my time in learning and developing than seeing hours and days go by unproductively due to issues like these.

Many thanks.

[mylesfenlon]

I cannot comment on the stability of revision 62 as I am not personally familiar with it. I have included a list of the issues corrected in revision 62. I hope it will address the issues you have experienced.

At the moment, revision 60 is the most recent developer edition that is publically available. Higher revisions will be made available as soon as possible, as has always been the case. I hope it will be available by the end of this week, and I can check with my colleagues to confirm this.

I locked the other thread because a generic plea does not help us to fix specific issues. The comments and replies here regarding specific problems that users have experienced do help us to fix these issues. The fact that revision 62 itself exists demonstrates our commitment and intention to improve the software.

There was certainly no intention or attempt to censor you; users freely post their issues here and they are addressed by SAP HANA Product Management, and new revisions and features are highlighted here by Product Management and community members as soon as they are available.

I do understand your frustration, and we can certainly try to address the current situation regarding the availability of the new revisions, but clearly the fact that we continue to make new revisions available, as soon as is practical, shows that we take on board the concerns and criticisms of users who need greater stability and functionality.

I hope you feel that this has clarified the situation and addressed your concerns. We are most certainly listening.

Myles

Revision 62 release notes:

•Fixed high memory consumption of Pool/RowEngine/MonitorView

•If there is an insert/upsert trying to insert an already existing record into a columnstore table and a concurrent update on the same record which is rolled back, a duplicate record issue could arise.

•Removed internal length check for lob datatypes which could lead to SQL "inserted value too large for column" errors.

•Fixed a bug wich could crash the statisticsserver. Call stall contains "TrexThreads::ThreadManager::getStatistics" and "InternalHandler::getSimpleStat"

•Fixed wrong decimal value.

•Slow performance encountered during SPO access because filter transport for IN-lists were not supported.

•Due to a logical programming error, performance issue occurs when there are too many identical GROUP BYs being generated when perforing a select on an analytic view.

•Queries with CASE expressions return wrong result if the CASE expression produces a constant number.

•Fixed inconsitent data for column INDEX in the monitoring view HOST_SERVICE_COMPONENT_MEMORY.

•Fixed aborting upgrade during hdbmount.py --sudoers call when using a Storage Connector in a distributed enviroment.

•An indexserver crash might occur when the table is corrupted. The indexserver crash dump contains the following stack trace: "AttributeEngine::Parallel::MultiValueExpansionFilter::filter".

•Cache infrastructure will now distinguish between active and standby node and cache lookup requests are no longer sent to standby nodes.

•Some queries or DML statements with a correlated sub query having a TOP operator may return wrong results. For more details see SAP Note 1885029.

•Some user sessions could be hidden from the HANA DB Studio Session Monitor. This revision enables the Session Monitor to display all sessions created by users.

•Fixed a bug where accessing a temporary table within a stored procedure could result in incorrect data for preceeding selects to this temporary table when the stored procedure is called a second time.

•NOT BETWEEN queries triggered via DBSL (e.g. from BI) can show wrong results for data stored in delta. SQL based queries are not showing this behavior. For details see SAP Note 1893911.

•The Statistics Server is now dynamically obtaining memory needed for "SYS.M_STATISTICS_LASTVALUES" monitoring view. The overall memory consumption of the Statistics Server is reduced.

•Fixed a bug where 'alter system clear column result cache' command does not clear all remote result caches in a distributed system.

•Fixed indexserver crash when querying on an OLAP cube that contains a time dependent join and a pre-aggregation calculated keyfigure.

In the indexserver crash dump the following entry can be found:

"int AttributeEngine::Parallel::_merge<false, TrexTypes::FixedAttributeValue8,AttributeEngine::Parallel::sum<TrexTypes::FixedAttributeValue8> >(AttributeEngine::Parallel::ResultData<TrexTypes::FixedAttributeValue8>&, unsigned int, unsigned int, TRexUtils::CachedMemBlock<TRexUtils::Mapping>::iterator&, AttributeEngine::Parallel::ResultData<TrexTypes::FixedAttributeValue8> const&) + 0x100".

•Fixed indexserver crash at startup caused by an old deprecated procedure paramter (@PARAM@) definition.

In the indexserver crash dump the following entry can be found:

"RTSchema.cpp(01030) : _SYS_RT schema is marked as inconsistent in database. Refusing to change or upgrade content.repositorySetup.cpp(00413) : Permanently setting schema rt as in consistent in database.

RTSchema.cpp(00804) : Failed to update _SYS_RT schema on master host, RT will not be available."

•Fixed a bug where an 'ALTER TABLE ADD PRIMARY KEY' statement could fail with the following error:

"cannot CREATE UNIQUE INDEX; duplicate key found: [5]".

Several documents with the same ID exist in the index if the related table contains more than 2^31 rows (and therefore is partitioned)".

•In the scenario for SAP Business Objects Analysis, the extension to the 'BIMC_VARIABLE_VIEW' for 'VALUE_ENTITY' is added.

•When the ODBC driver of the SAP HANA client (Revision 52 to 61) is used to open a DB connnection, viewing reports on the SAP Business Intelligence platform may cause the Crystal Reports processing server to unexpectedly stop. Also, creating or viewing reports in SAP Crystal Reports based on a HANA ODBC connection established by the ODBC driver of the SAP HANA client (revision 52 to 61) may cause SAP Crystal Reports to freeze.

•Improved performance of queries that need to access "M_ACCESSIBLE_VIEWS" and "M_EFFECTIVE_STRUCTURED_PRIVILEGES".

•Fixed a bug where SQL queries could crash the indexserver. The stack trace contains the following function call sequence:

"TRexConfig::Table::getKeyAttributes", "TRexConfig::CachedMetaData::getKeyAttributeIndices", "TRexConfig::CachedMetaData::initAllKeyAttributeAccessors".

•Fixed a bug where sessions executing long running DML-SQL statements on large column tables like 'CREATE COLUMN TABLE A LIKE B WITH DATA' could not be terminated using either 'ALTER SYSTEM CANCEL [WORK IN] SESSION' or 'ALTER SYSTEM DISCONNECT SESSION' commands.

•Fixed the "Index syncpoint mismatch" error thrown from TRexAPI::DeltaIndexManager::jeReadValueIds4Values that can occur after a delta merge.

•Fixed a bug where executing an OLAP query could crash the indexserver (signal 11). The related call stack contains multiple entries related to: "AttributeEngine::Parallel::GroupByColumnInfoContainer".

•Fixed the issue when querying on OLAP cube and the following error occurs:

"failed with rc 6900; Attribute engine failed;calcEngine search on olapIndex failed."

•Fixed the issue in HDBSQL: /i does not allow file names with spaces properly.

When we are using /i to pass in a filename that contains spaces in HDBSQL, it is not possible to enclose the file name in double nor single quotes.

[former_member182500]

Hi Myles,

Thank-you for the response.

The generic plea was not intended to help SAP fix issues - it was to address a fundamental concern and highlight where communication from SAP to the community can be improved. 

This is not about individual, granular "my projection doesnt work" or "alll my entity columns are uppercase" - although important to the individual the bigger view is a stable IDE we can use to then create and discover these  wonderful things.

I hope SAP can look into how they can better log Studio issues experienced by the community, and how they can better communicate what has been addressed and when we can expect to have it, hopefully via faster release cycles.

From the release notes its hard to ascertain if the Studio performance and hanging issues are addressed in revision 62.  I look forward to 62 being available, with an indication of whether its compatible with appliance SPS6 60, and if not an update to Juergen's AWS thread with relevant 62 AMI's.

Thanks again for your time.

[former_member184768]

Hi Myles,

Thanks for the detailed message. But I agree with points mentioned by Jon-Paul above.

1) The release notes do not mention anything about the stability of the Studio.

2) I would be rather skeptical in requesting my Basis admin to plan for the upgrade because to use the Revision 62 Studio, I will have to request for HANA database revision upgrade and that becomes a much larger activity with database backup and upgrade. It has to be a planned activity as it results in database downtime.

3) The experience with Studio Revision 60 and then 61 has not been encouraging, so the chances that revision 62 would work out fine are not very high, UNLESS specifically mentioned by SAP that the studio issues are specifically addressed.

I understand that SAP development teams are totally committed to provide the best development environment and would help resolve all the issues, but right now the confidence is low considering the past experience with recent 2 revisions.

Hope somebody posts here saying that revision 62 is working fine and all the issues mentioned in the discussion thread are taken care of.

Regards,

Ravi

[thomas_jung]

I can offer a few comments from the HANA Product Management side.

>From the release notes its hard to ascertain if the Studio performance and hanging issues are addressed in revision 62

This is true.  Currently the Revision release notes only contain server changes.  It really doesn't contain any notes on changes/fixes in the Studio client side. We know this is a gap and we do have some steps to improve this; but these changes won't come immediately.  Please know that in just about every revision there are fixes in the Studio. Critical fixes are constantly being merged to the revision code branch. 

> with an indication of whether its compatible with appliance SPS6 60

The general rule of the HANA Studio/Client is that it always attempts to be backwards compatible.  Generally it should be safe to run a newer version of Studio than server (but not the opposite). I say general rule because there have been a few exceptions.  For example in SPS6 (Rev 60) we made major changes to the XSJS debugger on both client and server side.  Therefore the Rev60 and higher Studio can't debug against a server lower than Revision 60.  This break in backwards compatibility needed special exceptions and we only allowed it because of the major improvements it provided and that backwards compatibility would have been very difficult to maintain.  It was also allowed because this change came at a SP level. 

>although important to the individual the bigger view is a stable IDE we can use to then create and discover these  wonderful things

Please know that I have forwarded several of these thread to the various Studio development managers to review as well.  I can tell you that my personal experience doesn't match yours.  I use HANA Studio all-day every day and I've used Rev60-63(still in internal development); and I've not encountered many of the problems you describe.  I would say my experience has been quite stable. I've also taught several workshops on AWS (my own install; not the developer center image - but still it was Rev60) and they also have not encountered this situation. 

Perhaps some more information we could provide to development - Are you installing HANA Studio on your local machine or on an AWS instance?  What Java SDK (Version and flavor) are you running?  What OS - 64 or 32bit?  Just trying to see if there are any common patterns we are missing.

[former_member184871]

Hi Thomas,

Can you please provide any information when SAP HANA Studio and Client REV 62 will be available for download via https://hanadeveditionsapicl.hana.ondemand.com/hanadevedition/

My S-User ID don't have authorization to download the same from service marketplace.

Regards

Kumar. 

[thomas_jung]

I'm sorry but product management/development plays no part in the availability of software on the Developer Edition.  When development releases software it goes immediately to the service marketplace.  The distribution via the developer center is completely separate and controlled by the developer center team. I don't have visibility into their process or timeline.

[former_member182500]

Thanks for confirming backwards compatibility of Studio with Hana appliance server and for forwarding the threads to the Studio development team.  I hope there can be some consideration on how to better support the groundswell of Hana developers SAP helped grow with OpenSAP that do not have direct access to the Service Marketplace for messages, notes and downloads that may relate specifically to the Studio component.

I have been developing in Hana since January this year, where valuable knowledge content included your original Native Hana development workshop videos on YouTube.  Studio was stable.

Throughout a solid 8 weeks of daily Hana development following and practising the content of the OpenSAP Hana course Studio was stable (revision 56). 

In my experience over 7 months with several releases of Studio it was stable and responsive. Then I upgraded to revision 60.

Regarding Studio installation

Windows 7 Professional 64 Bit, Core i7, 16GB

Thanks.

[christoph_pohl]

Thomas Jung wrote:
(...) Currently the Revision release notes only contain server changes.  It really doesn't contain any notes on changes/fixes in the Studio client side. 

Sorry for the wiseacring but this is not the case: Revision release notes mention most fixes gone into a revision, no matter whether server, client, or studio.

[former_member184871]

Its very annoying - as with time HANA studio is not running as it is supposed to be.  Today I tried some UDF and studio, hanged. Moreover its having trouble in opening the catalog.

I tried this : - Un-installed client and studio rev 60 and Java, restarted the system re-installed everything and it worked fine, again after a system restart - HANA studio is giving the same problem as discussed above.  

please share if there is any temporary fix. 

Regards

Kumar.

[former_member182500]

After having many Studio revision 60 issues which culminated in a host of error log messages after installing the SAPUI5 plugins, and caused the artefact decorator to stop working (making it difficult/tedious to develop), I decided on an uninstall/clean install.

After the fresh install I do not get the host of errors upon launch of studio (I have yet to update with SAPUI5 prerequisites and plugins) , HOWEVER....

In the SAP Hana SYSTEMS tab the catalog will not expand - it hangs on "Fetching children" with pending - several relaunches of Studio result in same.

Dear SAP - please can we have a working, performing Studio, or at least an acknowledgement these issues are being dealt with along with a timeline for a publicly available revision.  For the moment I find it impossible to develop productively in Hana.

[former_member184768]

+ 1

Quite disappointed with Studio Revision 60 and Revision 61. . Not exactly sure what is wrong, but it is pretty much messed up.

We have taken up the Studio performance issue with SAP development team. Some of issues are as follows:

• Save and / or Activate operations on HANA models take longer time, at times resulting in Studio hanging.
• In the UNION node consisting of multiple projections with high number of fields, COLLAPSE button on Source result in Studio hanging. Basically nothing happens for 20 mins or more.
• Simple navigation steps like opening a model, mouse clicks etc take 10 - 15 seconds to respond.
• If you try to close the Studio, it hangs. You need to go to task manager and kill the process.

I have been using Studio since revision 20, but the experience with Revision 60 and 61 had been the worst so far.

I hope it gets fixed up soon. I think Revision 62 is already out, but we are yet to upgrade to 62.

Regards,

Ravi

[former_member182500]

Hi Ravi,

With even straightforward actions as renaming artefacts causing a recommit of the whole package and taking forever I wonder if Studio revision 62 is any better. 

I've tried searching for availability of this revision without success, have you seen it made publicly available anywhere?

Many thanks,

Jon-Paul.

[former_member182500]

And it goes from bad to worse - installed the SAPUI5 components following the guidelines (prerequisites first, as I have done for each studio release), and upon launch of Studio get error log messages, a snapshot of which is shown before - the most frustrating of which is now my development artefact status decorators do not show, so I cannot tell if an artefact is in error, commited, activated.  Arrrgh! 

Back to reinstall of revision 60 (unless anyone can point me to an improved release?).

So much for rapid development of high performing cutting edge enterprise software with a flunky clunky IDE.  Apologies for the frustration but with this current release I see days of my life flashing past before me.

[christoph_pohl]

Hi Jon-Paul,

at least the problem with the broken label decorations can be helped short-term:

Go to Window > Preferences > General > Appearance > Label Decorations ...and make sure that SAP HANA Team Decorator is switched on.

Apart from that it might be noteworthy that HANA Studio switched with Rev 60 from Eclipse 3.8.1 to 4.2.2 (the official Juno SR2 release) which was supposed to be more stable but turned out to be a memory hog. So if you keep getting OutOfMemory errors, it might be worth increasing the max heap size in hdbstudio.ini from -Xmx1024m to, say, -Xmx1536m.

Another source of errors may be a version inconsistency between HANA Studio and HANA Client. When installing a new revision of HANA Studio, make sure you install/update HANA Client to the same revision (because Development Perspective in Studio currently depends on the command line client for repository connectivity).

One last resort in case of diffuse error symptom might be to delete/rename your local Studio workspace (normally under c:\Users\<your_user_id>\hdbstudio). Studio will then start clean from scratch (no systems, no projects, etc.) but also no stale config data that might have caused strange errors.

Just my 2Cts...

HTH,

Christoph

[christoph_pohl]

Forgot one:

When you install additional software (like SAPUI5) into HANA Studio via update site, make sure to run HANA Studio as Administrator. See also Note 1828400.

[former_member182500]

Fortunate in that I'm developing on personal PC and thus always as Administrator.  Good point for others though.

Your intentions, like those of James Wong with his published top 10 KBA's for Hana per month are great, so thank-you.  However this of of no use to those WITHOUT Service MarketPlace access.  Juergen Schmerder comments on this point.

http://scn.sap.com/docs/DOC-36064

Knowing an approximate number of Hana developers with Service MarketPlace access and those without would be interesting.

[former_member182500]

Hi Christoph,

Thanks for sharing the appearance preferences screenshot, useful.

For each new revision as a matter of course I always:

• back up my local workspace then delete original folder.
• completely uninstall both client and studio (and then clean up the org.eclipse.ui metadata in my user folder that the uninstall does not remove)
• install client first followed by studio, followed by SAPUI5 prerequisites and then SAPUI5 plugins.
• Check out SAP repository to clean local workspace.

Is there any reason why SAP cannot bundle client/studio/SAPUI5 prerequisites/SAPUI5 plugins into one install?  This would make life easier for both developers and SAP in reducing the number of "points of failure", in this case less is more.

Thanks.

[christoph_pohl]

I was not aware that you need SMP access for reading SAP Notes.

Whatever, instead of installing everything as admin you can of course also install studio into a non-shared location (i.e., outside of c:\Program Files) to make it a user mode installation on top of which you can install other Eclipse features safely.

[christoph_pohl]

Delivering SAPUI5 and HANA Studio in one bundle is definitely a valid requirement. But without disclosing too many details I can just ask for a little more of your over-stretched patience 😉

[former_member182500]

Please let it be true

[former_member182500]

On several occasions I have experienced very slow performance in Hana Studio since upgrading to version 60 - the simple creation of a file based development artefact often triggers a "waiting for user operation" dialog and a recommit of my package, the saving of artefacts slow sometimes causing a momentary "Not Responding" of the Studio.

After pressing "Finish" to create the new file based development artefact the completion can take minutes.

Even performing a right-click copy of a development artefact (such as an .xsodata, and before I choose to paste) causes a recommit of the package.  When I do select paste it sometimes has to wait for completion of the background operation for the copy (because it triggered a commit of the package which takes quite some time).  The "Copying Resources" dialog for one single artefact can take minutes.

I have seen that file creation which causes a recommit of the package then blocks follow up user operations such as the paste of some code.  I have been forced to close and re-open Studio due to this "hanging".

For simple development tasks it seems more sluggish than earlier versions - I wonder if this is part symptom of the "enhanced" repository synchronisation?  There is certainly performance issues to be resolved here.

I'm developing remotely from home, connecting to AWS.  Does anyone else experience these kinds of performance issues, and if so, are you connecting to an on or off premises  server?  Grateful if you can share your experience and perhaps someone from SAP can elaborate on any known issues?

Fortunately I'm developing my own project in my own time - with current Studio performance I don't believe I could commit deliveries and support to onsite client deadlines, as development progress feels like running through mud.  After the "high" of completing the enjoyable, enriching and rewarding OpenSap Hana course my user experience of SPS6 60 is rather disappointing, especially as the issues are through normal typical ways of working, not anything obscure.

[Former Member]

Jon-Paul,

after reading this response, i can confirm the exact same issues on SP6 AWSHANA. i did some work on 56 and issues were similar, but i knew a lot less back then than i do now, but the recurring performance issues are quite disturbing, especially if one plans to present in front of a client.

this is simply not helping to spread the good news how revolutionary HANA really is.

plugging away...

greg

[stephen_kringas]

Hi Shankar,

I recently upgraded my Studio from SPS5 to SPS6 and experienced a similar problem. Previously the Studio was working fine but after the upgrade it began to respond very slowly and then it would eventually crash with the below error -

After un-installing the SPS6 version and doing a fresh install of SPS6 it began to work fine again.

Cheers,

Stephen

[Former Member]

Hi Shankar,

Whether you defined much more attribute view/analytic view/calculation view with SPS5?

Regards,

Jerry

[Former Member]

Hi Jerry,

True, we have much views present on the HANA instance but I'm not sure why this issue has started coming up for Revision 60.

After I updated to revision 61, I don't see this issue and was able to access the content folder in fraction of seconds...

Looking for any workaround if SAP has provided for revision 60.

Thanks,

Shankar

[Former Member]

Hi Shankar,

so far, I am not sure root reason, but I think that it should be sap hana studio issue, it maybe has merge issue for column views to up version, not your problem.

besides, upgrade maybe has trouble from revision 52 to 60, you can ask hana support member, if you are customer or you are partner.

I am using revision 60, I uninstall old version, and install new version, not use update way, so far, it works fine.

Regards,

Jerry