Is there any particular reason why HANA views take longer time to activate?

[srujan_gannamaneni]

Hi Everyone,

Our HANA Calculation Views are taking longer time to activate. Even a simple view is taking more than 3 hours to activate. We started to see this behavior recently.

Are there any particular scenarios where Views take longer time to activate?
Will dependent objects cause this lag?

Thanks and Regards

Srujan Gannamaneni

[SergioG_TX]

this question is so vague - what version is your system? do you have other processes involved? memory size... etc... there are too many things you have not specified so no one will be able to give you guidance like this.

please specify other details

[former_member302041]

Hi,

The most simple calculation view (lets say aggregation node on small table) takes 3 hours?

BR,

[srujan_gannamaneni]

Hi Sergio,

Its HANA 2.0 SPS02
Memory size is 3TB distributed over 1 master and 2 slaves.

Please let me know in case any further details are required.

It used to work fine. But the issue started when we configured CTS+.

Also, When we initially change any column name in the base view, the dependent view used to get invalidated due to this change but now, the column name is getting automatically changed in the dependent view.

Thanks and Regards

Srujan Gannamaneni

[srujan_gannamaneni]

Hi Andrey,

Yes, Even for the simplest view as well. But the time will be only taken if there are dependent views on top of this view.

More the dependencies longer the time taken

Thanks and Regards

Srujan Gannamaneni

[shyam_uthaman · Accepted solution]

Hi,

We noticed this after the 2.0 upgrade. Also, there were red dots on a lot of views even though none of them are broken.

Not sure if you have the same issue but we noticed that a view that had a lot of dependencies took longer to activate.

We did the following:

1. Deleted all test objects in developer packages to minimize dependency checks.

2. Reactivated all views - top layer first (Query views), then reuse view and then private views - Helps clear the red dots (which were mostly due to forgotten broken objects in developer packages using private views which were also being used by the primary reuse views)

3. Upgraded to the latest service pack which seemed to help as well.

Again, if you see red dots on your view (not the error dots) even when its active, its most probably the dependency check.

Check your activation log - if you see a lot of rollback messages at the end, it confirms that you have the same problem.

Regards,

Shyam

[srujan_gannamaneni · Accepted solution]

Hi Shyam,

We are facing absolutely the same set of issues.
Let us follow the same steps and see if our issue gets resolved.

Thankyou Shyam 🙂

Best Regards

Srujan Gannamaneni

[shyam_uthaman · Accepted solution]

Nice to know I could help.

Hope this fixes your issue.

Shyam

[srujan_gannamaneni · Accepted solution]

Hi Shyam

It worked for us too.

Thanks and Regards

Srujan Gannamaneni

[shyam_uthaman · Accepted solution]

Good to know.

[p244500]

Hi,

Usually when you activate view all the dependent view will activate and relevant code generate If any of the dependent views have any errors / inconsistency then the system will try to validate those views which could take a longer time. IF you can check unused views available under the view and delete it if its not required. Then it will be fast.

Regards,

Nawa