[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

Similar Messages

[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

[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

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.

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

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

Source does not join to any fact source

I created a new dimension as follows:
1) Mapped Source from OLTP to Physical Layer
2) Created Alias for source
3) Create physical "Few Foreign Key" join between new source table and existing table (key to key)
4) Run consistency check with no issues.
5) Create new Logical table
6) Create new complex logical join between same two tables in Business Model
7) Join is a Right Outer Join
8) Run consistency check and receive the following warning message.
Can you please help me resolve? Thanks...
WARNINGS:
BUSINESS MODEL Marketing Contact List:
[39008] Logical dimension table OLTP Personal Communication has a source S_PER_COMM_ADDR that does not join to any fact source.

I'm still a bit confused:
Here are the steps that I understand:
1) Create Physical Alias Table (Personal Communication)
2) Create Physical Join between Personal Communication and Contact
3) Create Logical Table (Personal Communication) with physical source Personal Communication
4) Create Business Model Join between Personal Communication and Contact (right outer with Contact on right)
If i save now i get the warning message as described at the beginning.
The Business Model look like this:_
OLTP = Source of table is OLTP database
DW = Source of table is Data Warehouse
Personal Communication(OLTP Table)->Contacts(OLTP table)->Campaign Promotion(OLTP Table)->Contact Fact(DWTable)
In addition to the Contacts (OLTP) table that joins to Campaign Promotion the following other tables join to Campaign Promotion: Prospects (OLTP)
The Contact Fact table has 5 tables joined to it: Order, Service Request, Order Item Attr, Account, and Ordered Product
There are 5 Dimension Hierarchies (all created from the DW tables): Account, Contact, Order, Order Item Attr, and Ordered Product
I then try to recreate the steps indicated:
5) Right click on the new Logical Table (Personal Communication). which generates another Dimension Hierarchy: ContactDim
Since the other logical tables created from OLTP sources do not have hierarchy dimensions created I'm not sure why I'm doing this here. If someone could explain I would appreciate it?
If I select the properties for ContactDim:
a) The default root level = Contact Total
b) Tables listed are: Prospects (OLTP), Campaign Promotion (OLTP), Contact (DW), Contacts (OLTP), and Personal Communication (OLTP)
If I expand the ContactDim dimension I have a Contact Total:
Grand total level checked
Child Levels: Prospects (OLTP), Contacts (OLTP), Personal Communication (OLTP)
I then have sources for each of these below this with all fields listed and additional lists below that.
I'm stuck here and am not sure what to do. I really don't want any drill down capability but I want to elimenate the Warning message that I was getting before.
Thanks for any help that you can provide...

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

Oracle BI 11g
Hi,
I have this set of tables:
1) Table "Sales" with fields: ID, Billdate, ProductID, Amount
2) Table "Products" with fields: ID, ProductName, BrandID, TypeID
3) Table "Brands" with fields: ID, Name
4) Table "ProductTypes": ID, Name
In Physical layer I add these tables and create Physical Diagram with constraints like this:
[Brands] -------------------->[Products]
[ProductTypes] ---------->[Products]
[Products] -----------------> [Sales]
In Logical Layer I create logical table T1 Products with sources:
- LTS1 Brands,
- LTS2 ProductTypes,
- LTS3 Products
and fields:
- ProductID
- ProductName
- Brand
- ProductType
After that I create Dimention With Level-Based Hierarchy (H1 Products):
Total Products
- Brands
-- ProductTypes
--- Detail Products
When I try "Check Global Consistency" I get warning: "[39008] Logical dimension table T1 Products has a source LTS1 Brends that does not join to any fact source."
And after that when I try to make Analysis in Oracle BI, for example:
H1 Products | Amount
and then drill down item "Total Products" I receive error:
"State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14025] No fact table exists at the requested level of detail: [,Brand,,,,,,,,,]. (HY000)"
What's wrong? Where do I mistake? And why I don't get any messages about Logical Table Source LTS2 Product Type?

Hi,
you can create a single LTS for the product with the join for all 3 tables. Do you have a particular reason for the modelling that you have used?
Regards,
Gianluca

Consistency Warning: [39008] Logical dimension table ... has a source ...

Hi and many thinks for reading,
I have a problem (which is quite common as I saw, though I could'nt find a solution which resolves my issue yet) with the consistency.
My physical layer looks like this:
Table_A
Table_B
Table_C
Table_D
Table_E
In the Business Model I have just the same tables and the following joins in the Logical Table Diagram:
Table_A -> Table_B
Table_C -> Table_A
Table_D -> Table_A
Table_E -> Table_A
The consistency check is delivering the following two warnings:
Warning
Logical Table Source
Table_A
[39008] Logical dimension table Table_A has a source Table_A that does not join to any fact source.
Warning
Logical Table Source
Table_B
[39008] Logical dimension table Table_B has a source Table_B that does not join to any fact source.
While working in BI answers I manage to retrieve all data from Tables C, D, E. But for tables A and B I can retrieve just the columns which are defined in the join Table_A->Table_B. All other columns deliver the following error:
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_A.Column_X. Please fix the metadata consistency warnings. (HY000)
If i retrieve one Column from Table_A and one from Table_E, I have the following error:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Table_E) does not contain mapping for [Table_B.Column_X]. (HY000)
(yes its Table_B not a)
I would like to fix this errors but am not sure where the problem is hidden.
Any help is kindly appreciated.
Evgeny

Hi Goran,
thanks for you help.
I tried to create the BMM in the two way but, it doesn't work out neither way. The Administration tool is recognizing the repository as consistent, thought it has some warnings, but in BI Answers I cant retrieve even a single column from one table.
I am also not sure, how does it work, that you just add TableB to the logical TableA, who would the programm know which rows belong together? I assume one must establish a logical connection between TableA and TableB to make it compatible?
About my tables:
Actually TableA, TableB and TableC are recognized dimensions (white) and TableD and TableE are recognized as facts (yellow) in the Administration tool. Though I dont agree with this assignment. TableA is definitly a fact table (it is also the center of the star schema) while the other tables are the dimension tables. Not sure how the Administration tool is distinguishing between facts and dimensions...
Here are my warnings:
BUSINESS MODEL TAB: (with two logical tables)
[39008] Logical dimension table TableA has a source TableA that does not join to any fact source.
[39008] Logical dimension table TableA has a source TableB that does not join to any fact source.
BUSINESS MODEL TACDE: (with three logical table sources)
[39008] Logical dimension table LT2 has a source TableE that does not join to any fact source.
[39008] Logical dimension table LT2 has a source TableD that does not join to any fact source.
[39008] Logical dimension table LT2 has a source TableC that does not join to any fact source.
And the errors in Answers:
Retrieving ColumnX from TableA in the first model
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: TableA.ColumnX. Please fix the metadata consistency warnings. (HY000)
Retrieving ColumnX from TableA in the second model
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 17001] Oracle Error code: 12170, message: ORA-12170: TNS:Connect timeout occurred at OCI call OCIServerAttach. [nQSError: 17014] Could not connect to Oracle database. (HY000)
Thanks for further help!
Evgeny

WARNINGS: [39008] Logical dimension table D1_CALENDAR2 has a source D1_CA

WARNINGS:
[39008] Logical dimension table D1_CALENDAR2 has a source D1_CALENDAR2 that does not join to any fact source
even though it is joined to a fact , can any one tell me the reason y im gettin this warning?
Thanks in Advane.

Looks like you have not added all dimensions to Fact's Logical level.
Add D1_CALENDAR2's dimension to Fact's Content tab.
OR make sure all dimensions added to Fact's Content tab.
If helps Pls mark correct or helpful
Edited by: svee on Aug 3, 2012 1:26 PM

[39008] Logical dimension table X has a source

Hi
I have a Fact table with some dimensions. If I add a detail table to that Fact table I get:
[39008] Logical dimension table X has a source
Y that does not join to any fact
source.
For each dimension that I had.
Is this possible to model?. To have a fact that have details. I want to create pivot tables with the fact table, and some tables for the fact/detail relationship.
Regards,
Néstor Boscán

Hi..
Sorry to say this, i didn't understand your question properly..
But as per i understood,
your logical table is mixed of measures as well as dimension columns...
In this case, need to concentrate on rpd, business model development...
Need to divide the table into fact as well as dimension table in BMM...
All measures corresponding to table will located in fact table and remaining all dimensions will be in dimension table...
This is the best way of developing rpd..
Thanks & Regards
Kishore Guggilla

Warning [39008] : Logical dimension table...

Hi all,
in OBIEE we have a fact table linked in Physical Layer to 20 dimensions. I've created hierarchies for 15 dimensions but when I check consistency I receive the warning BUSINESS MODEL <bmname>:
+[39008] Logical dimension table <tname> has a source <tsource> that does not join to any fact source.+
The error refers to the 5 tables that don't have any hierarchy.
Have I to create hierarchies for these 5 tables too (even with a total and a detail view only)?
Thank you!
Gaetano.

Hi, thank you for your response. I have also found a doc showing that if I change the "Aggregation Content" in LTS from "Logical Level" to "Column" it works and you have no need to create dimensions for all objects. I don't know the impact of this.
http://download.oracle.com/docs/cd/E14847_01/bia.796/e14222/chapter.htm#BABJEAIH
Edited by: user615200 on 4-lug-2011 4.39

[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.

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

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

Similar Messages

Maybe you are looking for