Hi ,
Were you able to resolve this ? We are facing similar issues while modifying procedures that are referenced in other procedures.
In my case :
I am trying to modify the logic in Procedure A and this procedure is called from multiple procedures. When I try ro activate procedure A, I get the same cyclic dependency error.
Looks like this is a more generic error with activation and just limited to .HDBDD objects
Hi, I have had a few issues around cyclical dependency, the most recent yesterday which involved the inability to activate a script calculation view which called procedures which in turn referenced a table type in a .HDBDD. Selecting the calculation view, HDBDD and procedures and trying to activate them together didn't work, nor did forcing activation. I commented out the call to procedures to get the activation of the .HDBDD through.
In my earlier posted example I had to work back through related objects, deleting to see which prevented .HDBDD activation, then activate .HDBDD and then restore the deleted artifacts. Not nice.
I think the rules governing activation of .HDBDD are too strict, as activation can even fall foul of ODATA services consuming information model views which upset .HDBDD.
Did you product the graph as suggested in the indexserver trace? Have you commented out recent changes made to Procedure A to see if you can activate? Comment out all code? Comment out reference to Procedure A one by one? Any changes made to interface (in and out definitions) of Procedure A?
Far more developer friendly if a graphical representation of dependency was available within Studio itself.
Grateful if Thomas Jung can comment on any awareness of issue internally. I wonder if any changes to .HDBDD activation made an appearance in Rev.72?
I have the seem issue, takes a long time to log on..
Thanks wenjun,
I have deleted the Instance from cal.sap.com and re-installed SAP HANA developer edition , it is working great now.
Thanks you so much , I have assign points 4 you.
Regards.
Hari
That's just for security, internally it is saved.
Can you do command "cat /usr/sap/<SID>/HDB<SN>/.odbc.ini" in your HANA linux system and see the MY_IQ DSN?
Yes, I see the DSN when I run the specified command.
it might be a read authorization error.
Make sure the owner of the .odbc.ini file is the <sid>adm user (use chwon command with root user) and the group is sapsys (use chgrp command with root user).
I tried giving 777 to the file .odbc.ini but still not working 
This is an unsupported solution and assumes that everything you have done is in a Delivery Unit with defined project(s) and one or two schemas. I did not do an update to the existing server, I created a new instance and imported my rev 68 content to the new instance.
I created a new AWS instance using the new image on SPS7 (I actually used rev 70, but I saw that rev 72 is available now). While that instance was booting up, I exported my delivery unit with all my project development artifacts from the old system (using the File-Export-SAP HANA Content-Delivery Unit menu path), call this "du export".
After that completed, I also did a content export using File-Export-SAP HANA-Catalog Objects. Call this "data export".
When the new server came up and I had access, I reversed the process and did an import of the files created on the "du export" (File-Import-SAP HANA Content-Delivery Unit) and activated. Once I got through the activation phase, all my development objects were created but I had no data.
I then did an import (File-Import-SAP HANA-Catalog Objects) of the "data export" to bring in the catalog objects and data.
A few gotchas are still around -
1) if you enabled PAL, you will have to do that manually again using the correct scripts on the server. Not hard to do, but be sure to use the updated scripts on the new server to make sure that things are correct. There are also some naming conventions for the PAL algorithms that changed between 68 and 70 that I had to correct in my scripts
2) If you had a trust-store for a hdbhttpdest, you will have to recreate it manually
3) Check the roles/authorizations for your user(s).
You have to pay a few hours of double AWS time since you'll be running two instances, but it is one work-around that worked for me while I was waiting to get an upgrade to SPS7. You can even reassign the old EIP to the new instance, but i suggest doing a full new checkout of the objects that have loaded into a new workspace and project or you might run into development version issues (it seems that the change counter restarted once I imported the DU.)
Just remember to stop/terminate the "old" instance once you have verified everything on the "new" instance to avoid racking up extra costs.
Hope this helps.
Jim
I am facing the same issue as mentioned by you above. I am not able to save the user id and password in the HTTP Destination in the web portal. You are right it is very slow as well.
Please help if you are able to solve the save issue.
Its not 777, it's ownership. You gotta set <sid>adm as the owner with the chown command.
I think HANA Server restart is required after all the configuration steps. Its finally working now.. 
Thank you for your help.
Awesome. ;-)
Kulwinder,
Refactor option is to move views from one package to another package. But my problem is about schema.
Schema name used for creating views are different in test and production environments..
Hi Fernando,
Thanks for the suggestion. That seemed to work, though it is strange that it is not one of the *.xs.* application privileges. So, just to be clear, here are the application privileges I have now in order to use the web based IDE:
Thanks,
Kevin
Hi Kevin,
That was exactly my issue when I stopped to access ide after upgrade. Also found no information googling. So I've started the try and test till get the access.
Regards, Fernando Da Rós
Hi Prabhakar,
See also this thread SAP HANA Web-based Development Workbench Privileges
Regards, Fernando Da Rós
Hi Juergen,
can you please clarify one detail: the AMI Hana instance (ami-db546ab2) shows "Other Linux" as platform. First of all, why not SUSE Linux, and second, when purchasing a reserved instance, there is no "Other Linux" option, so can you confirm that selecting "SUSE Linux" there will purchase the matching reserved instance for Hana? I understand that you haven't tried it yourself, however someone at SAP should have the authoritative answer :-).
Cheers,
-- Micha
Sorry , i misunderstood your question. You have to do schema mapping for this. for e.g If in my test system schema name is ABC and production schema name is PRD, then in schema mapping you have to mention ABC in authorizing schema and PRD in physical schema.
Sorry once again...
Kulwinder
Unfortunately, commenting out the call to procedures is not an option for us as we will have to do this in more than 25 procedures.
We converted all our .HDBDD to .hdbstructure and that took care of the cyclic dependencies.
thanks for your help.