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

Similar Messages

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

External Table error: KUP-04043: table column not found in external source

I am trying to get the syntaxc correct for an external table.
I keep getting this error:
ORA-29913: error in executing ODCIEXTTABLEOPEN callout
ORA-29400: data cartridge error
KUP-04043: table column not found in external source: SITE
29913. 00000 - "error in executing %s callout"
*Cause: The execution of the specified callout caused an error.
*Action: Examine the error messages take appropriate action.
Data looks like: (some of one of many files, where the character field widths are variable)
ZZ,ANYOLDDATA,77777,25002000,201103,12,555.555,11.222
ZZ,ANYOLDDATA,77777,25002300,201103,34,602.162,8.777
ZZ,ANYOLDDATA,77777,25002400,201103,12,319.127,9.666
ZZ,OTHERDATA,77121,55069600,201103,34,25.544,1.332
ZZ,OTHERDATAS,77122,55069600,201103,22, 1.011,0.293
External table def I have:
CREATE TABLE MY_INPUT (
FIRST_CODE VARCHAR2(10),
SECOND_CODE VARCHAR2(20),
MY_NUMBER VARCHAR2(20),
THIRD_CODE VARCHAR2(20),
YEARMO VARCHAR2(6),
N NUMBER,
MEAN NUMBER,
SD NUMBER
ORGANIZATION EXTERNAL (
TYPE ORACLE_LOADER
DEFAULT DIRECTORY INPUT_DIR
ACCESS PARAMETERS (
RECORDS DELIMITED BY newline
BADFILE INPUT_LOGDIR:'bad.bad'
LOGFILE INPUT_LOGDIR:'log.log'
DISCARDFILE INPUT_LOGDIR:'discards.log'
fields terminated by ',' LRTRIM
MISSING FIELD VALUES ARE NULL
REJECT ROWS WITH ALL NULL FIELDS
( THIRD_CODE,N,MEAN,SD) )
LOCATION ( 'myfile.rpt')
NOPARALLEL
REJECT LIMIT UNLIMITED;
I have the directories INPUT_DIR and INPUT_LOGDIR defined, and read/write access granted to the user who creates the table and tried to query from it.
I have tried various combinations of VARCHAR2 lengths and NUMBER vs VARCHAR2 for some of the numeric fields.
I am not getting any Bad, Log or Discard files.
I can do a GET from the SQL prompt, and see the data:
SQL> GET 'C:\temp\input_dir'myfile.rpt'
and I see the data.
Windows 7
Oracle 11.2
I am not positive of the newline record delimiter - these files are generated by an automated system. Probably generated on a UNIX machine.
Any suggestions on what to try would be helpful.
KUP-04043 error message says to check the syntax .. .I am running out of thigns to check.
Thank you - Karen

And the get ( I created the sanitized file, so we have a real working, failing, santiized example):
SQL> get c:\Inputfiles\myfile.rpt
1 ZZ,ANYOLDDATA,77777,25002000,201103,12,555.555,11.222
2 ZZ,ANYOLDDATA,77777,25002300,201103,34,602.162,8.777
3 ZZ,ANYOLDDATA,77777,25002400,201103,12,319.127,9.666
4 ZZ,OTHERDATA,77121,55069600,201103,34,25.544,1.332
5* ZZ,OTHERDATAS,77122,55069600,201103,22, 1.011,0.293
So the full series is:
CREATE DIRECTORY INPUT_DIR AS 'C:\InputFiles';
-- grant READ and WRITE
GRANT READ ON DIRECTORY INPUT_DIR TO ILQC;
GRANT WRITE ON DIRECTORY INPUT_DIR TO ILQC;
-- As SYS, create the bad/log/discard directory:
CREATE DIRECTORY LOGDIR AS 'C:\InputFiles\Logs';
-- grant READ and WRITE
GRANT READ ON DIRECTORY LOGDIR TO ILQC;
GRANT WRITE ON DIRECTORY LOGDIR TO ILQC;
CREATE TABLE MY_INPUT (
FIRST_CODE VARCHAR2(10),
SECOND_CODE VARCHAR2(20),
MY_NUMBER VARCHAR2(20),
THIRD_CODE VARCHAR2(20),
YEARMO VARCHAR2(6),
N NUMBER,
MEAN NUMBER,
SD NUMBER
ORGANIZATION EXTERNAL (
TYPE ORACLE_LOADER
DEFAULT DIRECTORY INPUT_DIR
ACCESS PARAMETERS (
RECORDS DELIMITED BY newline
BADFILE INPUT_LOGDIR:'bad.bad'
LOGFILE INPUT_LOGDIR:'log.log'
DISCARDFILE INPUT_LOGDIR:'discards.log'
fields terminated by ',' LRTRIM
MISSING FIELD VALUES ARE NULL
REJECT ROWS WITH ALL NULL FIELDS
( THIRD_CODE,N,MEAN,SD) )
LOCATION ( 'myfile.rpt')
NOPARALLEL
REJECT LIMIT UNLIMITED;
SELECT * FROM my_input;
and GET is as above.

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

Consistency Warning - [39008] Dimension Table not joined to Fact Source

I have a schema in which I have the following tables:
A) Patient Transaction Fact Table (i.e. supplies used, procedures performed, etc.)
B) Demographic Dimension table (houses info like patient location code)
C) Location Dimension table (tells me what Hospital each unique Location maps to)
So table A is the fact, and table B is a dimension table joined to table A based on Patient ID, so I can get general info on the patient. This would allow me to apply logic to just see patient transactions where the patient was FEMALE, or was in the Emergency Room, by applying conditions to these fields in table B.
Table C is a simple lookup table joined to table B by Location Code, so I can identify which hospital's emergency room the patient was located in for instance.
So the schema is: A<---B<---C, where B and C are both dimension tables.
The query works as desired, but my consistency check gives me the following WARNING:
*[39008] Logical dimension table LOCATION MASTER D has a source LOCATION MASTER D that does not join to any fact source.*
How do I resolve this WARNING, or at least suppress it?

Hi,
What you need to do is to add the (physical) location dimension table to the logical table source of the demographic dimension, for example by dragging it from physical layer on top of logical table source of demographic logical dimension table in bmm layer
Regards,
Stijn

Table does not Exist in Unix OS after it has been created In HTML_DB

I created a table in HTML_DB and can see the table fine in my HTML_DB application. However, when I go to the Unix OS and try to look up the database using SQL*Plus, I am getting an error saying the table does not exist. Any help as to why this is happening would be appreciated.
Kelly

When I go to the Unix OS, I then try and search for the table in the exact schema that I used in >HTML_DB.I don't see what the Unix OS has to do with it here...do you mean you're connecting via SQLPlus?
If you're connecting via SQLPlus, which schema are you connecting to? (i.e. are you certain you're connecting to the same schema that the table was created under when you were connected to Application Express).

EXP-00011 table does not exist

Hi guru's,
My DB Version: 10.2.0.2.0
OS Version: Solaris 10
While trying to export a table from a schema i am getting error:
exp-00011 table does not exist
when i check the source database i found that table name as 'abc' exists there
but when i log on to schema and try to check the info about the abc table with below mentioned query i got below error:
SQL> select table_name from user_tables where table_name='rtx';
no rows selected
i also checked with table_name='RTX'
i am getting the same error.
Can anyone help me out

sorry the table name is rtx
C:\Documents and Settings\Administrator>exp userid=sysadm/rtxprod@rtxprod tables=sysadm.rtx file='E:\rtx.dmp' buffer=1000000 feedback=10000 statistics=none
Export: Release 10.2.0.1.0 - Production on Thu May 10 14:36:34 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options^C
C:\Documents and Settings\Administrator>exp userid=sysadm/rtxprod@rtxprod tables=sysadm.rtx file='E:\rtx.dmp' buffer=1000000 feedback=10000 statistics=none
Export: Release 10.2.0.1.0 - Production on Thu May 10 14:37:05 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
server uses WE8ISO8859P1 character set (possible charset conversion)
About to export specified tables via Conventional Path ...
EXP-00011: SYSADM.RTX does not exist
Export terminated successfully with warnings.

[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

[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

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

[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

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

Repository Consistency Check 39008 "does not join"?

I'm using Administration Tool 11.1.1.6.0 with a Repository version of 318.
I have imported my star schema metadata from the database using an OCI connection. All the joins were included, so I can go to Physical->Fact Table->Physical Diagram->Object(s) and Direct Joins and it shows my fact table linked to all my dimension tables. I then clicked-and-dragged my schema to the Business layer. I created my dimension by right-clicking on my logical tables in the Business layer and choosing Create Logical Dimension -> Dimension with Level-Based Hierarchy. This worked for all the dimensions that had only one level (a base level and a grand total level), but resulted in some odd errors when done for dimensions with more than one level. I got around these errors by manually creating these dimensions, clicking-and-dragging the logical columns in, and setting up the keys.
Only now when I do I consistency check, I get three of the following warnings, one for each dimension that has more than one level:
WARNINGS:
Business Model [Business Model]:
[39008] Logical dimension table [Logical Table] has a source [Physical Table?] that does not join to any fact source.At least, I think it is referring to the Physical Table, but changing the name of the Physical Table doesn't change the error message, though changing the Logical Table name does, so I'm not really sure what it is referring to. Here is what one looks like precisely:
[39008] Logical dimension table Time has a source TIME that does not join to any fact source.Now, each of the three multi-level dimensions have a base level with a key that is present in the Fact Table. I can even right-click on the Fact Table on the Business Layer and go to Business Model Diagram or Physical Model Diagram and get a diagram of my fact table linked to all of its dimensions, including the three in question. Analysis made in OBIEE work so long as I don't use those three dimensions.
Does anybody have any idea what I'm missing here?

Thanks, it looks like the field for those three logical dimensions was left blank for some reason. So it was because the Logical Dimensions weren't joining to the Fact Table, rather than the Logical Tables?

Error 39008: logical table does not join to fact source

Similar Messages

Maybe you are looking for