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

Similar Messages

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

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

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

[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

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

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

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

Logical fact table with fragmented data sources with different dimensions

Hello.
I have a logical fact table with four logical table sources. Three of the LTS's share the same dimensions, but the fourth LTS has one dimension (called Dim_A) less. In the physical layer the dimension Dim_A is joined to the first three physical fact tables, but not to the fourth fact table (since it doesn't have that dimensionality). In the BMM layer the logical fact table is joines to the logical dimansion Dim_A.
When I run an analysis on this RPD the measures from the logical fact is aggregated correctly (union of all four table sources) as long as I doesn't include Dim_A, but as soon as I include dimension Dim_A I get the error message:
+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: 14052] Internal Error: Logical column Dim_A.Column_X has no physical sources that can be joined to the physical fact table source [Logical table sources (Priority=0): Fact_B.Fact_Y]. (HY000)+
I would like a solution where the analysis returns correctly aggregated measures also for the LTS with the "missing" dimension, but with a dimension value NULL for this LTS. Or something like this.
Is there a way to set this up in the RPD.
Thanks,
Henning Eriksen

The SQL could look something like this.
SELECT dim_a.col_1, fact_a.measure_1
FROM db.dim_a
JOIN
db.fact_a
ON fact_a.col_2 = dim_a.col_2
WHERE fact_a.date = '28-nov-2012'
UNION ALL
SELECT dim_a.col_1, SUM (fact_b.measure_1)
FROM db.dim_a
JOIN
db.fact_b
ON fact_b.col_2 = dim_a.col_2
WHERE fact_b.date = '28-nov-2012'
UNION ALL
SELECT dim_a.col_1, SUM (fact_c.measure_1)
FROM db.dim_a
JOIN
db.fact_c
ON fact_c.col_2 = dim_a.col_2
WHERE fact_c.date = '28-nov-2012'
UNION ALL
SELECT NULL, SUM (fact_d.measure_1)
FROM db.fact_d
WHERE fact_d.date = '28-nov-2012'
I would appreciate if you could give me some hints for the RPD.
Thanks,
Henning

Implementing Logical FACT & Logical dimension from 2 different data sources

Hi Gurus,
Here is my situation. We have 2 Different Data sources. One is SRMW and the other one is a different source. What we are trying to implement here is we wanted to create logical dimensions and logical facts as well in the BMM layer. For ex: w_day_d from SRMW and other time dimension from another source makes a logical table. And similarly a fact from SRMW and and another similar fact (Same data types though) will make a logical fact in the BMM.
I have done the POC of it, but the only problem is that i was able to fetch the data from only one data source not the other source.
Any suggestions ??
Thanks in Advance.

What I already mentioned is that you have to create multiple logical table sources and set the fragmentation content on each logical table source.
When you have two physical tables for the product dimension, for example DIM_PRODUCT_A and DIM_PRODUCT_B, you must add them to your logical table Products as two separate logical table sources and map all columns to the corresponding logical table columns on the Column Mapping tab.
Hereafter you should go to the Content tab of each logical table source and describe what content is in the logical table source.
For example for the logical table source of DIM_PRODUCT_A:
"BM"."Product"."Product Name" <= 'Product 2'
and for the logical table source of DIM_PRODUCT_B.
"BM"."Product"."Product Name" >= 'Product 3'
Then you must also check "This source should be combined with other sources at this level"
When you run a query in Answers only on the product table, two queries will be generated to get values from both tables.
Regards,
Stijn

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

Similar Messages

Maybe you are looking for