​Hello,

We have a report that randomly returns an error message:

RSV-SRV-0063 An error occurred while executing the 'asynchRunSpecification_Request' command. XQE-RSA-0021 An invalid attempt to cast a class occurred during data retrieval: com.cognos.xqe.runtree.relational.vectorization.DoubleColumnVector incompatible with com.cognos.xqe.runtree.relational.vectorization.DecimalColumnVector

But if you run it minutes later, it runs fine.

Any ideas?

Thanks,
Jen

------------------------------
Jenifer Broughton
------------------------------

#CognosAnalyticswithWatson

From Environment perspective, validate if all dispatchers are running and have same set up.
For Report perspective, check if any specific column is causing the issue.

------------------------------
Buddhi Gupta
------------------------------

Hi Jennifer,
This is a bug in the system. We suspect that the behavior fluctuates depending on cached vs. non-cached data and re-using result sets.
One thing to try is to set use-local cache to false for that report and see if the behavior becomes consistent.

In any case, you should log it as a bug.

//Henk

------------------------------
HENK CAZEMIER
------------------------------

Open a support call, it is a defect.  Given you did not mention which release you are on, possible that we have already addressed this case.

As an FYI, the more complete stack trace to the error would be in <cognos>\logs\XQE ...

------------------------------
NIGEL CAMPBELL
------------------------------

All,

Thank you so much for this information related to the known 'bug'.  It does appear to be a sporadic error spanning different reports.  I will get it logged.  We are running version 11.0.11.


Jenifer​

------------------------------
Jenifer Broughton
------------------------------

Original Message:
Sent: Sat February 15, 2020 10:15 AM
From: NIGEL CAMPBELL
Subject: Cognos 11.0.11 - Double Column Vector Error

Open a support call, it is a defect.  Given you did not mention which release you are on, possible that we have already addressed this case.

As an FYI, the more complete stack trace to the error would be in <cognos>\logs\XQE ...

------------------------------
NIGEL CAMPBELL
------------------------------