New Query/Report against new Data Source Connection failing

[screwdrive]

Dear Cognos users\Experts,

I am facing an issue while creating any new query or\and reports against the newly created (SQL Server 2014) Data source Connection which is using DQM and we had to create JDBC connection as we have a standalone environment with RHEL OS and ODBC is not supported (unless we go for DataDirect, which we didn't as of now).

So, status is Data Source connection has been established without any error and in Framework Manager Model has been created which is fetching only a single view. We tested in Framework manager it is successfully fetching data while testing through data viewer. Then, we published the package based on the single DB view based model.
And now if we create to run any ad-hoc query or report against that package to fetch a few2 particular data items in the report or query, it prompts an error.-
"XQE-PLN-0222
Columns of type BLOB are not permitted in a GROUP BY or ORDER BY clause."

Has anyone also faced it ever? It might be a silly mistake possibly from our end and so any guidance would be appreciated.

[MFGF]

Dear Cognos users\Experts,

I am facing an issue while creating any new query or\and reports against the newly created (SQL Server 2014) Data source Connection which is using DQM and we had to create JDBC connection as we have a standalone environment with RHEL OS and ODBC is not supported (unless we go for DataDirect, which we didn't as of now).

So, status is Data Source connection has been established without any error and in Framework Manager Model has been created which is fetching only a single view. We tested in Framework manager it is successfully fetching data while testing through data viewer. Then, we published the package based on the single DB view based model.
And now if we create to run any ad-hoc query or report against that package to fetch a few2 particular data items in the report or query, it prompts an error.-
"XQE-PLN-0222
Columns of type BLOB are not permitted in a GROUP BY or ORDER BY clause."

Has anyone also faced it ever? It might be a silly mistake possibly from our end and so any guidance would be appreciated.

Hi,

Looks like IBM have an open APAR for this. What version of Cognos BI are you using?

http://www-01.ibm.com/support/docview.wss?crawler=1&uid=swg1PI18313

MF.

[anth]

This is not a terribly scientific response, but every time I've had this error I've solved this by wrapping one of my returned data elements in to_char(), usually a wm_concat(). It's hackish and I feel a little dirty about it, but it's worked. I believe Cognos is being more paranoid than the underlying database (Oracle, in my case) regarding the types of returned elements.

[screwdrive]

That is exactly what we ended up doing to get pass this issue. Thanks both!
@MFGF- We were on 10.2.1 FP2 at that point of time and now on 10.2.2 FP4.