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

Hi all!
I'm very new to Oracle BI EE. My need is to create my first report in BI. I've opened Oracle BI Administration Tool, created new repository, added physical tables, created new item named "reports" in "Business Model and Mapping" section, made "drug-n-drop" my physical tables into new item. Now when I run "check consistency" on "reports" item it returns errors:
Business Model reports:
[38133] The Logical Table '"reports"."table1"' is not joined to any other logical table.
[38133] The Logical Table '"reports"."table2"' is not joined to any other logical table.
[38133] The Logical Table '"reports"."table3"' is not joined to any other logical table.Could you please help me with these errors?
Oracle Business Intelligence 11.1.1.6.0

Looks like you drag-n-drop each table, try to all at once with that all physical layer joins are come and treated as logical joins. Other wise try to create them manually.
drag-n-drop always is not possible so we have to go for manually.
If this is not in your case let me know else pls mark as correct/helpful

Similar Messages

Error [38133] : does not join to any other logical table

Hi,
Is there a way to avoid this error. We dont have the requirement to join the table with any other table. The client wants to use
the OBI Answers functionality on a single table. No joins needed or wanted. Some hidden checkbox to avoid the OBI join-requirement?
Thanks

Hi,
Refer the below link.
Adding a single table without a logical join to another table (OBIEE 10g)
or,
To report on a single table: just drag/drop the table twice from the physical layer to the busines model layer. Then define a complex join (just drag/drop a line) between tablex and tablex#1. Define a key on the dimension table (the white colored folder).
You can then put one of the tables in a presentation folder and report.
Hope this help's
Thanks,
Satya ranki reddy
http://satyaobieesolutions.blogspot.in/

Logical table does not join to any logical table

HI,
I want to implement Business Unit hierarchy for drill down in OBIEE so I’ve created a custom table with the hierarchy information,
I’ve imported that table in the out-of the box physical schema & defined a relationship between the W_ORG_D table & my custom INVENTRY_ORG table as INVENTRY_ORG.BU_ID = W_ORG_D. VIS_PR_BU_ID* but when I try to check in my changes I’m getting the following error.*
Logical table INVENTRY_ORG does not join to any logical table.
Kindly let me know how to resolve this error.One more doubt i have is can we import custom tables in the out of the box OBIEE mappings for SIEBEL..that is the core subject area.
Thanks,

Hi user10340125 ,
1) I think you have joined tables in physical layer, but you have not created complex join in logical layer.
Check your consistency and see what warnings you are getting.
2) Yes you can import custom tables in whatever subject area. Once you imported tables in physical layer, then they all are just objects, so you can freely play around with them. Just for best practices, make sure you follow proper naming convention for custom tables and columns..
- Vinay

Logical Dim table does not join to any fact source

[39008]Logical Dimension table <table name> has a source < table name> that does not join to any fact source.
I am getting the above error when the "correct" joins have been made in both the physical and BMM diagrams. My fact tables are showing yellow as they should and my dimension tables are white like they should be. I am only getting this as a warning though when I run a request against the tables in Answers it is telling me to resolve the warnings in the admin tool.
I know this has already been posted before -- though I did not see any additional info to correct the issue. Any help is greatly appreciated.

Hi
Follow the following Step:
In BMM expend you fact table.
Expend your sources option that is present in fact table.
Now get the property of the fact table source.
In General tab Add button is present click on that
It will open new Browse window and in right bottom part it gives some table name.
select your fact table from that and click on select.
now your table will be selected nwo click on ok.
Now save this and click on Globle Chick in.
Now I think it will not give you any working msg.
If againg you have any proble then let me know.
Thanks
Siddhartha P

My ipod was stolen. Can i find with the GPS? If not is there any other way?

My ipod touch was stolen out of my locker. I have all things to prove its my ipod touch. (original box & serial number) I was hoping that it could be tracked by the GPS or some other method. I hope so because I do not have money to buy another one. Plus it was a gift from someone special so i would like to get this back. If you have any other methods please let me know. Thank you so much!
Mike Barreras
< Edited by Host >

You could find it, if you did install "Find my phone" before it was stolen. But you would have to own a ipod touch 4G, an iphone4 or an ipad to install it. See this article: http://support.apple.com/kb/HT4436

[15013] Logical table, BIDATA.W1_SYNONYM_EMPLOYEE1_D1, does not join to any

Hello all.
I have following situation.
I have a Employee table(w1_employee1_d1)
Salary table(w_salary_f) in Database.
every thing is fine when I import it in OBIEE Administration tool and use the answers.
Then I created a synonym as (w1_synonym_employee1_d1), believing that, synonyms can be used as tables/Views.
Now I imported into Physical layer and made a join in Start Schema in 'Physical Diagram'
and so far all is fine.
When I drag it in BMM layer and do a global consistency check, I get following error.
BUSINESS MODEL BIDATA:
[nQSError: 15001] Could not load navigation space for subject area BIDATA.
[15013] Logical table, BIDATA.W1_SYNONYM_EMPLOYEE1_D1, does not join to any other logical table
In BMM layer > right click the W1_SYNONYM_EMPLOYEE1_D1 > Bussiness Model Diagram > Whole Diagram
I can see the joins exists as how I made it in Physical layer.
what I am missing ? any help is appreciated.
Thanks

Ok Just for any body's information, My problem is partly resolved.
I added this in existing .RPD and it has caused the problems, which had Hirarchies and LTS and Alias tables.
However when I try a new and fresh .RPD and create a simple with synonym, that has not got this problem.
I will dig in the problems in old .RPD why there was error.
over all I must say the quest for this tests to find if I can use Synonym is been answered, using synonym in RPD is np at all.

[39008] Logical dimension table has a source that does not join to any fact

Dear reader,
After deleting a fact table from my physical layer and deleting it from my business model I'm getting an error: [39008] Logical dimension table TABLE X has a source TABLE X that does not join to any fact source. I do have an other fact table in the same physical model and in the same business model wich is joined to TABLE X both in the physical and business model.
I cannot figure out why I'm getting this error, even after deleting all joins and rebuilding the joins I'm getting this error. When I look into the "Joins Manager" these joins both in physical as well as logical model do exist, but with consistency check it warns me about [39008] blabla. When I ignore the warning and go to answers and try to show TABLE X (not fact, but dim) it gives me the following error.
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: TABLE X.column X Please fix the metadata consistency warnings. (HY000)
SQL Issued: SELECT TABLE X.column X saw_0 FROM subject area ORDER BY saw_0
There is one *"special"* thing about this join. It is a complex join in the physical layer, because I need to do a between on dates and a smaller or equal than current date like this example dim.date between fact.date_begin and fact.date_end and dim.date <= current_date. In the business model I've got another complex join
Any help is kindly appreciated!

Hi,
Have you specified the Content level of the Fact table and mapped it with the dimension in question? Ideally this should be done by default since one of the main features of the Oracle BI is its ability to determine which source to use and specifying content level is one of the main ways to achieve this.
Another quick thing that you might try is creating a dimension (hierarchy) in case it is not already present. I had a similar issue few days back and the warning was miraculously gone by doing this.
Regards

Error 39008: logical table does not join to fact source

About to lose my mind over this error!
I'm told logical table IT_WORK_ITEM_D (a dimension) does not join to any fact source, although it should show as joined to IT_WORK_ITEM_DSNPSHT_F
- I have verified the physical joins
- I have verified the business model joins
- I have created hierarchies for all logical tables joined to the fact (IT_WORK_ITEM_DSNPSHT_F)
- I have checked the Content tab for the fact table and ensured that the logical dimension is set to the lowset level.
Suggestions from here?
-John

This was helpful, although it did not solve the problem immediately.
After much consistency checking, I cleared out some of the content assignments and that seemed to work (after having not worked). I still don't feel like I identified the core problem, but it is working now.
-John

[39008] Logical dimension table X has a source that does not join to any...

Hi Gurus,
I have warning:
"[39008] Logical dimension table X has a source that does not join to any fact source"
WHERE X:
PROMOTIONS,PRODUCTS, CUSTOMERS, CHANNELS
but all logical table are mapped to fact.
Eveb I can create reports for them
(The metadata was derived from OWB 11gR2, SALES_EE)
Thanks
Laszlo
Thanks for Your earlier answer as well!

Hi,
Did you create hierrarchy on that dimension.?
Add contel level in fact source to hierarrchy detail for the fact that joins the dimension.
Look at this for best practice...http://gerardnico.com/wiki/dat/obiee/hierarchy?s
Please do close your previous thread assigning points by clicking helpful or correct to the replies
Import XML file into rpd file
Thanks,
Srikanth

[39008] Logical dimension table has a source that does not join to any fac

Hi
I have a problem in BMM layer:
*[*39008] Logical dimension table X has a source Y that does not join to any fact source.*
To start with I have three tables joining to Cust (customer) table in physical layer
Cust-Seg (Segments)-------------------------------->>Cust via segment key
Cust-Geo (customer Geographics)-------------->>Cust via address key
in the BMM layer under the CUST table when I pull in Cust- seg it works fine .
But it gives an warning [39008] -if iI create a single LTS for the product with the join for all 3 tables
The Same warning appears when i import th Cust -seg table as Logical table

Have you tried this?
http://obiee11gqna.blogspot.com/2011/02/obiee-error-39008.html

Please help me out with this error:Logical dimension table D_TARGET has a source D_TARGET that does not join to any fact source.

I get the folowing error when I run the global consistency check
WARNINGS:
Business Model DAC_Measures:
[39008] Logical dimension table D_TARGET has a source D_TARGET that does not join to any fact source.
Can someone help me out please?
Thank you!

It seems your dimension is not joined to any facts. Did you check your BMM/physical joins?

Logical Dimension tabel does not join to any fact source

I want to create a new “Dimension” table. This will be an Account Geographic dimension. My Business and Physical model are setup as follows:
1.     Account Address (WC_ADDR_F) is joined to Account (W_ORG_D) which is joined to multiple Fact tables (Ex: Order Item (W_ORDERITEM_F)
2.     When I perform “Global Consistency” check it comes back with no errors or warnings.
I create the Account Geographic dimension as follows:
1.     I right click on the subject area and select New Object->Dimension and name it “Account Geographic Dimension”. I do not select or change anything else.
2.     I right click on the new dimension and select New Object->Logical Level. I name the level “All” and check the “Grand total level” check box. Nothing else is changed.
3.     I right click on the “All” level and select New Object->Child Level. I name the level “Country”, set number of elements to 200.
4.     I right click on the “Country” level and select New Object->Child Level. I name the level “State”, set number of elements to 250.
5.     I drag the “Country” element from the Logical table (Account Address) to the “Country Level” on the new Dimension (Account Geographic Dimension)
6.     I drag the “State” element from the Logical table (Account Address) to the “State Level” on the new Dimension (Account Geographic Dimension)
7.     I then select the “Country” level properties and add a new key. For the key I select the “Country” column that I just dragged up there.
8.     I then select the “State” level properties and add a new key. For the key I select the “State” column that I just dragged up there.
My goal is that when an Analyst selects the “Country” column in Answers from the “Account Address” area that the user would be able to drill down from “Country” to “State”.
When I perform “Global Consistency” I now get the following warning:
WARNINGS:
BUSINESS MODEL CCCi Analytics:
[39008] Logical dimension table Account Address has a source CCCi_Dim_WC_ADDR_F_AccountAddress that does not join to any fact source.
Why do I now get an error no the Account Address table for not connecting to a Fact table? The error message references the “Account Address” dimension table which I believe is the source to the Account Geographic Dimension. If this is the source table, why did it not get a warning message before I created the new dimension?
Thanks…

Here is the solution that I was able to get to work:
1.     I did not have to reduce the business model to a star but was able to keep it a snowflake
Final design (which was same as the original) here is the Business Model (snowflake schema)
1.     Account Hierarchy (logical) -> Account (logical) -> Order Item Fact
2.     Account Address (logical) -> Account (logical) -> Order Item Fact
In this model the logical tables Account Hierarchy and Account Address snowflake off of the Account table which joins to the Fact table. I then:
1.     Created an “Account” dimension
2.     Created a child “Account Total” level
3.     Created two (2) children off of the “Account Total” level: (1) Account Address Country and (2) Account Hierarchy Top Level
a.     Key for “Account Address Country” was the Country column from Account Address (logical)
b.     Key for “Account Hierarchy Top Level” was the Top Level Account Name from Account Hierarchy (logical)
4.     Off of “Account Address Country”:
a.     Created a (1) child off of “Account Address Country” called “Account Address State” with the State field from the Account Address (logical) as the key
b.     Created a (1) child off of “Account Address State” called “Account Address Detail” with the ROW_WID from the Account Address (logical) as the key
c.     Created a (1) child off of “Account Address Detail” with the ROW_WID from the Account (logical) as the key
5.     Off o “Account Hierarchy Top Level”:
a.     Created a (1) child off of “Account Hierarchy Top Level” called “Account Hierarchy Level 1” with the Top Account ID from Account Hierarchy (logical) as the key
b.     Created (1) child off of “Account Hierarchy Level 1” called “Account Hierarchy Detail” with the ROW_WID from “Account Hierarchy” as the key
c.     Crated a (1) child off of “Account Hierarchy Detail” with the ROW_WID from the Account (logical) as the key
The global consistency check completed with no errors or warning with this design. It appears that perhaps you need to have all of the logical table keys in the dimension path that trace to the Fact table. One other note, cannot repeat use of other columns in the dimension except for the key of the first logical table.
Please let me know if I missed something.

Error in CodeFirst Seed with migrations : Modifying a column with the 'Identity' pattern is not supported. Column: 'CreatedAt'. Table: 'CodeFirstDatabaseSchema.Category'.

Hi,
I have activated migrations on my Azure Mobile Services project. I filled the new seed function Inside the Configuration.cs class of the migrations. If the tables are empty, the seed function is going without any problems. When my AddorUpdate tries to update
the first object I get the error in the inner exception : "Modifying a column with the 'Identity' pattern is not supported. Column: 'CreatedAt'. Table: 'CodeFirstDatabaseSchema.Category'."
Part of my code is as follows:
context.categories.AddOrUpdate(
new Category { Id="1", Code="GEN", Text="General"},
new Category { Id="2", Code="POL", Text="Politics"},
new Category { Id="3", Code="FAS", Text="Fashion"},
new Category { Id="4", Code="PEO", Text="People"},
new Category { Id="5", Code="TEC", Text="Technology"},
new Category { Id="6", Code="SPO", Text="Sport"},
new Category { Id="7", Code="LIV", Text="Living"}
Any help is welcomed. Thanks.
Faical SAID Highwave Creations

This occurred to me because I changed my POCO models to inherit from EntityData after I had already created my database without the extra Azure Mobile Service properties (UpdatedAt, CreatedAt, Deleted). The only way I fixed it was to drop the database and
start over with my classes inheriting from EntityData from the beginning. If you can't do that then I would create a new table with EntityData models and see how that database is created and manually update your tables to match those. Here's an image of one
of my tables from the management console on Azure. You can see that CreatedAt is an index.

Our service upgraded to 4g but now my Mac computer will not join the network, It sees the network but will not join

Our service just upgraded to 4g. Now my Mac computer will not join the network. It "sees" the network but will not "join"

Hi Hojo38,
That's not good! What happens when you attempt to make the connection? Do you receive an error message? What device is the computer making a connection to? Send details please.
Thanks,
PamelaF_VZW
Tweet us @vzwsupport

Does not join to any fact source issue in 10g

HI,
I am getting below issue while compiling rpd.
Logical Dimension Table Dim-XX has a source xx_aa that does not join to any fact source.
Let me describe situation here.
In physical layer , i have one xx_v table . there is no join condition physical layer. But in BMM layer we have created two logical tables for single xx_v table and providing join in bmm layer. When am compiling it i'm getting an error.
The one which i have using current rpd, same rpd in production with out any warnings(Logical Dimension Table Dim-XX has a source xx_aa that does not join to any fact source) and they don't have any logical level mapping in content tab. But i am using same rpd in dev instance getting warnings.
Thanks,
Mal
Edited by: user10675696 on Feb 11, 2013 3:08 AM

Hi Srini,
Please find the below warning here and we don't have an hierarchy for MTL_SYSTE_ITEMS_B
[39008] Logical dimension table Mtl System Items B has a source MTL_SYSTEM_ITEMS_B that does not join to any fact source.
I am getting this in Dev instance only but not in Production. But one rpd can be used in dev and production instances.
Thanks,
Mall

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

Similar Messages

Maybe you are looking for