nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

OBIEE 12c RPD consistency warnings

986359

HI All,

Could you please tell me how do i resolve the below consistency warnings after the upgrade from obiee 11g to 12c?

38028 --> Logical column 'a' does not have a valid data type.

38100 --> The logical tables 'dimension' and 'Fact' connected by logical join '"Relationship_2004:40367111412380694"' have no corresponding physical connections.

38128 --> Presentation level '"a".."b Hierarchy"."c Hier"."d Detail"' has no display columns.

39028 --> The features in Database 'ABC' do not match the defaults. This can cause query problems.

39048 --> The variable 'ABC_XYZ' does not have a constant default initializer.

39062 --> Initialization Block 'XYZ' uses Connection Pool '"ABC"."Connection Pool"' which is used for report queries. This may impact query performance.

39074 --> Logical dimension table 'Dim - D ' has a source 'Dim_D' with aggregation content set to level 'Dim - D Detail'. The same dimension has aggregation content set in fact source to a higher level.

39090 --> Logical column "BM"."Timeframe"."Month" has invalid Sort Order column 'Row Wid'.

39092 --> Presentation level 'RTR' is first under presentation hierarchy, but logical level it is associated with is not grand total level.

39097 --> Logical lookup column "Usage Tracking" has no descriptor id column set. This will cause slower query performance.

39098 --> Level "Detail" has more than one level key selected as a display key.

39099 --> Level " Detail" has at least one display key that contains multiple columns. Only the first column of a display key is displayed when drilling.

39100 Logical column 'QUERY' has CLOB/BLOB data type but has no sort order column and/or description ID column assigned. This will cause slower query performance.

Any links pointing to these warnings will also help.

Thanks in advance!!!

Find more posts tagged with

Accepted answers

All comments

Gianni Ceresa

Hi,

Open the repository, take your warning and fix them one by one ....

Difficult to be more explicit when you have something as precise as "Logical column 'a' does not have a valid data type." or "The logical tables 'dimension' and 'Fact' connected by logical join '"Relationship_2004:40367111412380694"' have no corresponding physical connections.".

Is there one of these warnings you don't understand? Because it's all about your RPD ...

(Doesn't mean it wasn't working or wasn't set in 11g, it looks like in some cases few pieces disappear during the upgrade to 12c based on some other users posting on here, but not saw it by myself).

986359

I thought since those have specific error code we have a set of solution involved to solve them. Do we have something of that sort? If yes could you please help me on that??

AnkitR Gupta

I tried to provide initial thought to resolve warning/error, please go through inline comments

38028 --> Logical column 'a' does not have a valid data type. --> Look at Physical Column data type and match it with Database column data type

38100 --> The logical tables 'dimension' and 'Fact' connected by logical join '"Relationship_2004:40367111412380694"' have no corresponding physical connections. --> try recreating physical joins as well

38128 --> Presentation level '"a".."b Hierarchy"."c Hier"."d Detail"' has no display columns. --> this is just a warning, you could either remove dimension hierarchy from Presentation table or add those column to presentation table

39028 --> The features in Database 'ABC' do not match the defaults. This can cause query problems. --> you can either ignore it or change it to default

39048 --> The variable 'ABC_XYZ' does not have a constant default initializer. --> this variable need a default value

39062 --> Initialization Block 'XYZ' uses Connection Pool '"ABC"."Connection Pool"' which is used for report queries. This may impact query performance.

39090 --> Logical column "BM"."Timeframe"."Month" has invalid Sort Order column 'Row Wid'. --> check if the column is expressed/named correctly

39098 --> Level "Detail" has more than one level key selected as a display key. --> delete logical key

Gianni Ceresa

It's just the error code numbers related to the text you see. The set of solutions is to do things in the way OBIEE works. So if the error tell you that you have logical join between A and B but no physical relationship what do you do? Well ... OBIEE works in layers: you have physical joins and logical joins (in the BMM layer). For any logical join OBIEE must have a way to translate it into a physical join. So if no physical join supporting your logical one you get that error.

The set of solutions is to do things in the way OBIEE works, not more, not less ...

RobbertD

Hi,

Is there also a solution for this warning?

39092 --> Presentation level 'RTR' is first under presentation hierarchy, but logical level it is associated with is not grand total level.

Regards Robbert

Gianni Ceresa

Does that hierarchy have a grand total level?

RobbertD

Yes!

Kevin Tully-Oracle

I have answers/workarounds for some of these:

38028 --> Logical column 'a' does not have a valid data type. *** Apparently, when the RPD was converted to 12c, some of the Physical Layer data types were lost and are now set to UNKNOWN. We have aliases with this issue. Duplicate the source object/table of the alias. Edit the alias and change its source to be the duplicate, change it back to the original, then click OK. Check the alias data types to verify they are now correct. Delete the duplicate source table.

38100 --> The logical tables 'dimension' and 'Fact' connected by logical join '"Relationship_2004:40367111412380694"' have no corresponding physical connections. *** Check your physical joins between the tables referenced in the BMM. The physical joins either wern't there to begin with (so the BMM join is an artifact) or the physical join was lost and needs to be recreated.

38128 --> Presentation level '"a".."b Hierarchy"."c Hier"."d Detail"' has no display columns. *** The display column setting disappeared, redefine it.

39062 --> Initialization Block 'XYZ' uses Connection Pool '"ABC"."Connection Pool"' which is used for report queries. This may impact query performance. *** This occurs when you have two connection pools defined for the same database. At some point, their order changed so that the one used by the initialization block is listed first. Change the connection pool order so that the Initialization block connection pool is not listed first - the first connection pool is always the one used for most queries.

39090 --> Logical column "BM"."Timeframe"."Month" has invalid Sort Order column 'Row Wid'. The sort order column disappeared or is corrupted. *** Reset/redefine it.

39098 --> Level "Detail" has more than one level key selected as a display key. *** Uncheck all of the keys, leaving only one checked.

39099 --> Level " Detail" has at least one display key that contains multiple columns. Only the first column of a display key is displayed when drilling. *** Change the hierarchy key definition to only contain a single column or add another key with only one column and specify that key as the display column.

While I also have most of the other errors, I'm still trying to find solutions/workarounds for them.