BDA Crosstab created in 16.4 is not working in 16.7

RaviKumar_Rongali05
edited February 11, 2022 in Analytics #1
I have a crosstab which was created with BDA version 16.4 and now upgraded BDA to 16.7. when ever i try to open and the crosstab in BDA then i am getting "Incorrect version or crosstab cache type" error. below is the  electron.log

20200916 17:15:55.625  INFO com.actuate.ba.api.fastdb.internals.models.fastdb.request.GetColumnRequestFactory createFastDbRequest line 87 Engine operation: getColumns
20200916 17:15:55.662  INFO com.actuate.ba.api.fastdb.models.analysis.CalculateCrosstabRequestFactory createFastDbRequest line 99 Engine operation: calculatecrosstab
20200916 17:15:55.944 ERROR com.actuate.ba.api.fastdb.connection.Sender processRequest line 239 <exception><code>com.actuate.ba.api.common.exceptions.engine.CrosstabException</code><message>Incorrect version or crosstab cache type</message><enginecode>-1130</enginecode><enginemessage>Incorrect version or crosstab cache type</enginemessage></exception>
20200916 17:15:55.946 ERROR com.actuate.ba.electron.ws.RequestHandler invokeApplicationClass line 408 Error invoking method [calculateCrosstab] from class [application.analysis.Crosstab] - java.lang.reflect.InvocationTargetException - <exception><code>com.actuate.ba.api.common.exceptions.engine.CrosstabException</code><message>Incorrect version or crosstab cache type</message><enginecode>-1130</enginecode><enginemessage>Incorrect version or crosstab cache type</enginemessage></exception> - <exception><code>com.actuate.ba.api.common.exceptions.engine.CrosstabException</code><message>Incorrect version or crosstab cache type</message><enginecode>-1130</enginecode><enginemessage>Incorrect version or crosstab cache type</enginemessage></exception>
Stacktrace:
<exception><code>com.actuate.ba.api.common.exceptions.engine.CrosstabException</code><message>Incorrect version or crosstab cache type</message><enginecode>-1130</enginecode><enginemessage>Incorrect version or crosstab cache type</enginemessage></exception>
        at com.actuate.ba.api.common.exceptions.engine.CrosstabException.getInstance(CrosstabException.java:62)
        at com.actuate.ba.api.common.exceptions.engine.EngineException.parseException(EngineException.java:65)
        at com.actuate.ba.api.common.exceptions.GenericException.parseException(GenericException.java:80)
        at com.actuate.ba.api.common.exceptions.GenericException.parseException(GenericException.java:44)
        at com.actuate.ba.api.fastdb.connection.Sender.processRequest(Sender.java:234)
        at com.actuate.ba.api.fastdb.connection.Sender.processPoolRequest(Sender.java:121)
        at com.actuate.ba.api.fastdb.connection.Sender.processRequest(Sender.java:184)
        at com.actuate.ba.api.fastdb.internals.models.fastdb.request.RequestFactory.send(RequestFactory.java:96)
        at com.actuate.ba.api.fastdb.internals.models.fastdb.request.FactoryBase.plainExecute(FactoryBase.java:134)
        at com.actuate.ba.api.fastdb.analysis.Crosstab.calculateResults(Crosstab.java:113)
        at business.analysis.Crosstab.calculate(Crosstab.java:201)
        at business.analysis.Crosstab.calculate(Crosstab.java:174)
        at application.analysis.Crosstab.calculateCrosstab(Crosstab.java:180)
        at jdk.internal.reflect.GeneratedMethodAccessor199.invoke(Unknown Source)


Comments

  • This issue has been resolved after deletion of engine cache.

    this cache is in data/FastDB/databases/cache and requires having OTMDD_FastDB service down before proceeding to delete the content of that folder.