Oracle Forum - The Knowledge Center for Oracle Professionals - Looking Beyond the Possibilities

Full Version: Oracle Business Intelligence EE error
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Getting following error, help require ............
BUSINESS MODEL Core:
[39008] Logical dimension table Clients has a source Client Company(W_ORG_D) that does not join to any fact source.
[39008] Logical dimension table Need Last Discussion (W_LOV_D) has a source Need Last Discussion (W_LOV_D) that does not join to any fact source.
[39008] Logical dimension table Recovery Date (W_DAY_D) has a source Recovery Date (W_DAY_D) that does not join to any fact source.

BUSINESS MODEL Usage Tracking:
[39008] Logical dimension table Calendar has a source NQ_CALENDAR that does not join to any fact source.

BUSINESS MODEL Core New:
[39008] Logical dimension table Clients has a source Client Company(W_ORG_D) that does not join to any fact source.
[39008] Logical dimension table Need Last Discussion (W_LOV_D) has a source Need Last Discussion (W_LOV_D) that does not join to any fact source.
[39008] Logical dimension table Recovery Date (W_DAY_D) has a source Recovery Date (W_DAY_D) that does not join to any fact source.
Please review this MOS note:
Error: "[39008] Logical dimension table COMPONENT_CODE has a source 'XYZ' that does not join to any fact source." Importing Essbase Cube Into Repository (Doc ID 746919.1)
I got this business model error.
[39008] Logical dimension table MyDimension has a source MyDimensionSource that does not join to any fact source.

Is anyone helping me to get out this problem?
(01-09-2017, 05:03 PM)If you get the warning: OBIEE Error 39008: Logical dimension table XXX has a source that does not join to any fact sources. Check if there is physical and logical join exits and the granularity between dimension and fact tables are same. Wrote: [ -> ]The Content Level of DIM and FACT LTS should be same as the logical join occurs at the same grain.
Another trick to fix the above error, is to change the logical level to column in fact table LTS under content tab aggregation content, group by section.
[Image: 39008-1.jpg?w=438&h=134]
Change the logical level to Column in all the fact tables. Click ok and check the global consistency check.
[Image: 39008-2.jpg?w=432&h=111]
All the 39008 error will be gone. Again revert back the aggregation content, group by to Logical level, save the RPD and once again check the global consistency check, you should not see such warnings.