Why is the application not working when we create the aggregate table starting with VW?
This problem can occur if you have not selected 'Re-cache changes' after doing modifications in warehouse, admin databases and datamodel. So select 'Apply/ Re-cache changes' to solve the issue.
Related Articles
Why is the automatic restart for application not working?
If you had problems with the windows scheduler during the specified time (at 7:30 PM), please check the Windows event log for any major exception/failure at that point of time. If there are persisting problems with the event then, delete and ...
Which aggregate table will the KPI refer to fetch results when there are multiple aggregate tables?
For the combination of measures and filters chosen in the KPI, if there are multiple aggregate tables then, you can define sequence for tables in the data model For Example, 1. 2. 5. 6.
The KPI refers to the incorrect aggregate table although the correct aggregate table that is to be referred is defined in the 'dbmodel.xml'
If the aggregate sequence of two different aggregate tables is either same or defined incorrectly then, the KPI refers to an incorrect aggregate table. Hence, ensure that the aggregate sequence is unique and properly defined
Why is the KPI not referring the correct aggregate table that is expected to refer?
This problem can occur if the force aggregate is chosen as part of the KPI definition during publishing. So each time, the KPI is analyzed, it refers the particular aggregate table.
Why can't I view the login page? Is the application not working?
Verify the application log for any exceptions. Ensure that the tomcat service is active. If not, restart it by verifying if the services is up and running