OAC ERROR: The data source does not support adding every dimension to the SELECT list.

GLarr00

Summary

After updated OACC to 105.3.0-93 No reports that connect to EPBCS will run.

Content

After updated OACC to 105.3.0-93 No reports that connect to EPBCS will run. Any ideas?

Error Codes: OPR4ONWY:U9IM8TAC:U9IM8TAC:U9IM8TAC:U9IM8TAC:OI2DL65P

State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. (HY000)

State: HY000. Code: 43113. [nQSError: 43113] Message returned from OBIS. (HY000)

State: HY000. Code: 43119. [nQSError: 43119] Query Failed: (HY000)

State: HY000. Code: 22079. [nQSError: 22079] The data source does not support adding every dimension to the SELECT list. Please exclude at least one dimension from the SELECT list. (HY000)

Version

105.3.0-93

johan pretorius

Hello Greg, Facing the exact same issue when pulling FCCS into OAC. OCI instance so can't check instance but EPM 19.10.

Did you resolve the issue or change the report layout?

Thanks

GLarr00

The only way around this for me was to leave out a dimension from both the grid and filter. For me this is not a viable solution since I report off of an Essbase cube and need to be able to filter on every dimension. I spoke to the Oracle Dev guys and they say that they are working on a patch fix which will become available soon. I'm not sure what "soon" means since I've had a ticket open with them for over 5 months now. 

Mazen Manasseh

Anyone has a fix for this issue?

[Deleted User]

https://community.oracle.com/products/oracleanalytics/discussion/comment/51460#Comment_51460

Not a fix but a workaround. If you add a "fake" (empty) dimension to the cube outline and just never include that in the analyses it will work.

Greg Holland

https://community.oracle.com/products/oracleanalytics/discussion/comment/51467#Comment_51467

@Christian Berg Would that fake dimension be setup within EPM or OAC? We've started seeing this issue on an EPM connection in OAC that had been working without issue up to now.

[Deleted User]

You need that fake dim in the EPM cube outline. If your cube has 12 dimensions, add a 13th one to the outlined that never gets included in the query. This way you can query your "real" dimensions from 1 to 12 without running into this issue.

A hack, granted, but for a solution you need an SR and a product defect.