QV server restarts with Internal Inconsistency Type A, T C and F in 12.0
Article Number: 000050816 | Last Modified: 2018/06/12
In QV 12.0 the Performance log shows multiple QV server restarts. At times during there are Internal Inconsistency server abort errors Type A, C, F and T in the QV Event logs where Critical Hi memory threshold is reached. This is a clustered environment.
QV-13265 "QV cluster restarts multiple times per day with Internal Inconsisteny Type A, F, T and C"
In QV 12, there may be times when a dashboard is opened which has , for example, a big demand of memory when expanding huge pivot tables, or exporting a large amount of data to Excel.
When reviewing the Event logs, search for MT_High or IncreaseMemoryQuota and you can see entries relating to pivot table box, straight table, etc.
IncreaseMemoryQuota: Request PivotTableBox::GetTableLayout going MT_HIGH
IncreaseMemoryQuota: RequestStraightTable::GetTableLayout going MT_HIGH
The entries are related to Memory Throttling (MT_High). QlikView server wants to temporarily increase the memory to handle the request e.g. exporting a large amount of data to excel, or a large demand of memory when expanding huge pivot tables. The memory is intended to be released once the request is complete.
In versions 12.0 - 12.20 SR2 , the memory may not get released.
Resolution: Upgrade to 12.20 SR 3 or later
Note -The dashboards responsible for the memory consumption need to be reviewed. You can help pinpoint what dashboards are responsible by reviewing the audit log and searching for customer actions occuring just prior to the MT_HIGH and Internal Inconsistency errors in the event log. Remember, Increase Memory Quota are information entries. You will not see those entries when searching for Warnings or Errors.