Oracle Communities

Oracle Analytics and AI

Child Item

OBIEE 12c : Analysis showing an error while adding column.

#Mayur

Hello All,

> OBIEE 12 C

-I am getting this error while adding dimension column in the existing report.

-How we can deal with this kind of issues??

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

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

Please have your service administrator review this error. (HY000)

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

Please have your service administrator review this error. (HY000)

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

Please have your service administrator review this error. (HY000)

State: HY000. Code: 14025. [nQSError: 14025] No fact table exists at the requested level of detail: [,,,,,,,,,,,,,,,,,,,

Thank you in advance.

#Mayur

Find more posts tagged with

Accepted answers

Gianni Ceresa

Hi,

It isn't because you see all the columns of a subject area on your screen that they can be designed together.

The tool is telling you that it doesn't know how to handle what you are requesting: the columns you selected can't work together.

You should go back in your RPD and check if all these pieces are modeled together logically and the tool should be able to use all the selected columns together. Most probably they can't be used together because you don't have joins or some other configuration.

But the RPD is the one driving all that, look into it.

Or is this something that always worked in the past and now stopped working?

What exact version is your "OBIEE 12c" ? Have you installed all the available bundle patches?

All comments

Gianni Ceresa

Hi,

It isn't because you see all the columns of a subject area on your screen that they can be designed together.

The tool is telling you that it doesn't know how to handle what you are requesting: the columns you selected can't work together.

But the RPD is the one driving all that, look into it.

Or is this something that always worked in the past and now stopped working?

What exact version is your "OBIEE 12c" ? Have you installed all the available bundle patches?

#Mayur

Thank you Gianni for your response.

OBIEE 12c Version 12.2.5.9.0.

This is the new column I am adding in the Analysis. Earlier Analysis is working fine.

Not sure about Bundle patches.

Gianni Ceresa

12.2.5.9.0 is OAS already, so I assume you are using Oracle Analytics Server 5.9.

As said, it's your model (the RPD) deciding what can be used together in an analysis or not.

If you aren't in charge of modelling/developing the RPD, ask the people who are doing that task about your issues. They can either tell you an alternative column that will work, or look at how to model things to make your analysis work.

Shantaram-Oracle

In addition to what was suggested, Normally, the error [nQSError: 14025] No fact table exists at the requested level of detail: ...points to the missing join relation to the Fact source.

You may need to recreate the joins in BMM layer and make sure that the many side of the join points to the Fact source.

[Deleted User]

https://community.oracle.com/products/oracleanalytics/discussion/comment/50276#Comment_50276

A word of caution: While "you may need to recreate joins" is not technically wrong it must never be read as "create dim/fact relationships" in the BMM for all entities.

The error message is tied to the engine not being able to resolve dimensional conformity between the facts and dimensions taking part in the logical query.

Dimensional modelling especially where multi-star queries are concerned is a bit more involved and you have to first comprehend which fact should be analyzable by what dimension and which dimensions that aren't actually related to a fact should still be usable together with said facts. Non-conformed-dimension modelling without understanding this first can lead to unwanted results. "creating joins" as in establishing BMM layer relationships is only a small part of the picture and will not correctly solve the issue unless all other facets like content levels are also in place correctly.