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

Similar Messages

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

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

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

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 table

Hi All,
I am creating logical columns using two logical dimensions in a separate logical table. Do I need create complex joins for the new logical table, two source logical dimension tables have complex joins created already. Could you anyone provide some clarification on this.
Thanks in advance,
RK

As mma1709 mentioned,
you must be careful with the joins of this new logical table with your fact...
When you check for errors in the administrators,are there any??
if no,at any report with this column you have any problems??
hope i helped....
http://greekoraclebi.blogspot.com/
///////////////////////////////////////

Creating logical dimension table using common attributes of Facts

I need to create a common logical dimension based on an attribute present in both the fact tables. Example -
Expense fact has 3 columns expense_key, expense_amount and customer_name
Revenue fact has 3 columns revenue_key, revenue_amount and customer_name
I need to create a prompt for customer_name and have a report including expense_amount and revenue_amount.
How can I create the logical dimension table in the Repository and join it to both the fact tables?
Any Suggestions?
Thanks.

Will there be an exact match between the customer names in both the tables? Also, we do not have a common key between both the tables(Customer Name cannot be used as the common key since it is not the primary key. If we make a join on customer Name we would get wrong duplicated data). If all you want is to pass down the filter of customer name and get the revenue and expense, create 2 fact tables(for expense and revenue) with their own dimensions and then pull them into a common subject area. Then use the set operations to create the following report
Customer Name Revenue Expense_Null (just populate 0)
Union All
Customer Name Revenue_Null(just populate 0) Expense
Then use the dashboard prompt on this report.
Thanks,
Venkat
http://oraclebizint.wordpress.com

Having more LTSs in logical dimension table hit the query performance?

Hi,
We have a logical table having around 19 LTSs. Having more LTSs in logical dimension table hit the query performance?
Thanks,
Anilesh

Hi Anilesh,
Its kind of both YES and NO. Here is why...
NO:
LTS are supposed to give BI Server an optimistic and logical way to retrieve the data. So, having more Optimistic LTS might help the BI Server with some good options tailored to a variety of analysis requests.
YES:
Many times, we have to bring in multiple physical tables as a part of single LTS (Mostly when the physical model is a snowflake) which might cause performance issues. Say there is a LTS with two tables "A" and "B", but for a ad-hoc analysis just on columns in "A", the query would still include the join with table "B" if this LTS is being used. We might want to avoid this kind of situations with multiple LTS each for a table and one for both of them.
Hope this helps.
Thank you,
Dhar

Define logical Key on Logical Dimension Table

It's recommended to define a logical key for any logical dimension table - in 10g there was a function on the right mouse button, as far as I remember - but in 11g there is no such functionality ? the foreign key can be added by "green plus" button, but not the primary key ?? you have to type in the name of the key, then you can choose the column and then you select as primary key ... funny.
bug or undocumented feature?

Hi Srini,
Since my main logical fact table consists of two LTS and the dimension being created from this table will also have 2 LTS, the content level will be set to all levels on which the fact is joined.
So I would like to create a logical dimension based out of my dimension and then assign the content level at the detail level.
Please let me know if I am not clear.
Thanks

Getting Warning while adding Dimension table to FACT LTS

Hi,
While i am applying join betwwen fact and Dimension at BMM level, i am getting warning as there is no join with Fact Source, even though i provided join there.
Can any one help in this.
thanks
Manu

Hi
Make sure you have set the Content Level of all LTS of all Fact Tables...
Double click on LTS of fact, go to Content Level --> change to Logical Level to 'Column (or) Detail Level'
then u will not get warnings..
Please mark helpful or correct if this helped you out

Using multiple physical tables in a single logical dimension table

I have two physical tables that are related on a 1 to 1 basis based on a natural key. One of these tables is already part of my RPD file (actually, it is the W_EMPLOYEE_D from the Oracle BI Applications). The second table contains additional employee attributes from a custom table added to the data warehouse. Unfortunately, I don't seem to be able to display ANY data from this newly added custom table! I'm running on OBIEE 11.1.1.6.
Here's what I've tried to do. Lets call the original table E1 and the new one E2. E1 is part of the repository already, and has functioned perfectly for years.
- In my physical model, I have imported E2 and defined the join between E1 and E2.
- In my logical table for E1, I've mapped E2 to E1 (E2 appears as a source), set up an INNER JOIN in the joins section for E1 and added the attributes from E2 in the folder
- In the SOURCES for this logical table, I've set the logical level of the content for E2 appropriately (detail level, same as E1)
- In my presentation folder for E1, I've copied in the attributes from E2 that were included in my logical table
Consistency check runs smoothly, no warnings or errors. Note: E2 contains hundreds of rows, all of which have matching records in E1.
Now, when I create an analysis that includes only an attribute sourced from E2, I get a single row returned, with a NULL value. If I create an analysis that includes one attrribute from E1 and one from E2, I get all the valid E1 records with data showing, but with NULL for the E2 attributes. Remember, I have an inner join, which means that the query is "seeing" E2 data, it is just choosing not to show it to me! Additionally, I can grab the query from the NQQuery.log file - when I run this SQL in SQL*Developer, I get PERFECT results - both E1 and E2 attributes show up in the SQL - the query engine is generating valid SQL. The log file does not indicate there are any errors either; it does show the correct number of rows being added to cache. If I create a report that includes attributes from E1, E2 and associated fact metrics I get similar results. The reports seem to run fine, but all my E2 attributes are NULL in Answers. I've verified basics, like data types, etc. and when I "Query Related Objects" in the repository, everything looks consistent across all 3 layers and all objects. E2 is located in the same (Oracle) database and schema as E1, and there are no security constraints in effect.
I've experimented with a lot of different things without success, but I expected that the above configuration should have worked. Note that I cannot set up E2 as a new separate dimension, as it does not contain the key value used to join to the facts, nor do the facts contain the natural key that is in both E1 and E2.
Sorry for the long post - just trying to head off some of the questions you might have.
Any ideas welcomed! Many thanks!
Eric

Hi Eric,
I would like you to re-check on the content level settings here as they are the primary causes of this kind of behavior. You could notice that the same information might have written down in the logical plan of the query too.
Also, as per your description
"In the SOURCES for this logical table, I've set the logical level of the content for E2 appropriately (detail level, same as E1)"
I would like to check on this point again, as if you had mapped E2 to E1 in the same logical source with an inner join, you would get to set the content level at E1 levels themselves but not E2 (Now, that E2 would become a part of the E1 hierarchy too). This might be the reason, the BI Server is choosing to elimiate(null) the values from E2 too (even you could see them in the sql client)
Hope this helps.
Thank you,
Dhar

Warning [39008] : Logical dimension table...

Similar Messages

Maybe you are looking for