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 - Separate database with only one table and error in RPD

aPsikus

Oracle BI Admin tool 12.2.1.2.0

I have created new database, where only one table is attached.

I have created new business model with logical table, source and columns for this table from physical layer.

I have created Subject area in Presentaion layer and added few columns.

Global consistency check returns error:

ERRORS:

Business Model (name):

[38133] The Logical Table '"name"."name"' is not joined to any other logical table.

What I have missed in the setup?

There will be no any connection to other tables as it is not required and required table contains all data.

Find more posts tagged with

Accepted answers

All comments

[Deleted User]

A valid model can never ever have just one table. You need one logical dimension table and one logical fact table. And the logical dimension table must have a dimensional hierarchy.

Also, please update you other thread with the actual solution as not sharing the solution goes against the whole point of the forum - especially if you continue to ask questions and expect answers while not providing answers yourself.

Gianni Ceresa

To extended Christian's reply: a logical model is a start schema.

A fact table is only supposed to contains measures while everything not being a measure goes into a dimension.

Logical dimensions *can* have a dimensional hierarchy. If you don't do it you are missing a lot of what OBIEE can do, that's why it's easier to post that it must have it, so people invest 5 minutes to build it.

[Deleted User]

Gianni Ceresa wrote:Logical dimensions *can* have a dimensional hierarchy

Please stop saying this out loud. Most issues arise because people build those hierarchies wrong to begin with and fueling the "it's ok not to do the work correctly" faction will make things even worse.

aPsikus

Providing easy to implement solution:

in physical layer create dummy physical table with one column (can be named KEY), create a key on this column.

Create complex join between your table and dummy table with expression: 1=1

Move to BMM layer all required columns from standard table and as new logical table key column from dummy table.

Create a BMM diagram.

You can save your RPD without error.

Gianni Ceresa

aPsikus wrote:Providing easy to implement solution

Aka: how to spend $$$$ for nothing! Why to buy an analytical platform if you don't want to use it?

That kind of solution is like buying a desktop PC and sit on it instead of using it for doing some analysis on your data.

But fine ... easier to make a totally wrong model with garbage objects in your RPD instead than spending the same exact time it took you for the "workaround" and doing it right. A matter of personal choices I would say.

For those who care: that's not the "correct answer", that's a wrong workaround making OBIEE useless and acting just like SQL Developer, a free tool costing 0$!

Joel Acha

I have to agree with @Christian Berg & @Gianni Ceresa here. There doesn't seem to be any benefit (analytical or financial) of implementing OBIEE to work off a single database table. For the benefit of the wider OBIEE community, the solution you've provided as a workaround should be noted as a solution that doesn't take into account any OBIEE modelling best practices.

aPsikus

"Smart-ass" talk again...

But what can do if there is no any measures to create, and all data are loaded into single table?

Really worth to spend time spliting this into separate tables? Don't think so.

It's not best practice, it's problem solving.

Links describing similar approach:

https://gerardnico.com/dat/obiee/obis/single_table_model

OBIEE TRAINING: How do we Create report with Single table

OBIEE in IL: OBIEE - Model based on one table

[Deleted User]

Not smart-ass talk but actually someone who knows what he's talking about and why the chose "solution" - read: dirty hack - is absolutely wrong.

Cutting off a patients head to stop his headache also works. Sure.