View are not opening for editing

Technical queries
,
#1

Hello Helical Insight,

I am using helical insight 4.1 GA. There are certain views which are not opening for editing in some cases. Why is this happening?

Thank You,
Jam.

#2

Hello Jam,

there could be few different issues because of which the view might not opening of the metadata. Every time a view is clicked also for opening or editing, the SQL of view gets executed. Hence in case if the table column has been removed from the db or renamed then this issue can happen.

Also another reason is some of the views might not open or might give timeout problem because of extensive joining clauses etc because of which they might become very slow to fetch the data. Execution of these views itself might be very slow andso when reports are created from this view wherein these entire SQL of view will go into the “from” clause. With a lot of concurrent users these reports can be very slow. So ideal is to have such precalculated tables for faster performance.
Also such view are many a times not running at the metadata level since at tomcat level query timeout has been defined.

Note: This is not advisable. But it can be a work around. Though with this workaround the view section of the metadata might not give error because of timeout but report performance can still be slow.
Aside for optimal performance do not make metadata very heavy. Try not to have a lot of tables and columns in the metadata as we have to parse through the entire metadata file in order to create the sqlquery for the report.
STEPS TO BE FOLLOWED:-

  1. Go to the HI:Login page -> Data Sources ->

  2. Click on the Database where the data related to your tables is present…Find the connection id of your Data Source name.

  3. Refer the below image (Ex: “DataSource name : DB Final and it’s connection Id is ‘4’ “)
    image

  4. Go to the globalConnections.xml ( Located at “… hi\hi-repository\System\Admin” )

  5. Find the Conn. Id (represented as id=” “) of your related data (Ex : In the below image Connection Id is “1”)

image

  1. Once you find your relevant Connection Id search for 180000 (Refer the above image).
  • You can replace 180000 to 300000. (or an even higher number if you think the sqlquery execution is slow). The time here is in milliseconds.
  • Save the file.
  1. Go to the default.properties file (Located at hi\hi-repository\System\Admin )
  2. In this file find “hikari.connectionTimeout=180000” and replace the value with 300000.You can refer to the below image. (or an even higher number if you think the sqlquery execution is slow). The time here is in milliseconds.

image

  1. In the same default.properties file find “tomcat.maxWait=180000” and replace the value with 300000.Refer to the below image. (or an even higher number if you think the sqlquery execution is slow). The time here is in milliseconds.

image

  1. Once the changes made – SAVE the file
  2. Now, go to the HI-Login page
  • Clear all the cached reports ,Cache and data sources created
  • Click on the three dots present at the top right of each cache as shown in below image- Select all and delete them
  • Refer to the below image.

image

ONCE THE ABOVE STEPS ARE DONE-----RESTART THE SERVER.

Also here we had to make changes in globalconnection.xml because that connection was already created and later we changed the tomcat hikari timeout properties. But all future connections will already have the new timeout which has just been specified in the default.properties file

Thak You,
Helical Insight.