Oracle Analytics Cloud and Server

Products Banner

OAC SUBJECT AREA ISSUE

Received Response
65
Views
5
Comments

Summary:

I have a subject area with one fact and 5 dimension and 1 dimension being from other database

Content (required):

I am able to view the data in subject area when I pull in 3 dimension and 1 being the cross join does works fine

but when I pull the 4 the dimension with cross join database doesn`t work

but when I pull the 4 dimension from same database works good

Have any faced this issue before?

Version (include the version you are using, if applicable):

OAC 6.5

Code Snippet (add any code snippets that support your topic, if applicable):

Answers

  • What is the error message you're receiving?

  • In Logical Table Source of Fact add other database Dimension with appropriate join condition. This may work.

  • ALOK SH-Oracle
    ALOK SH-Oracle ✭✭✭✭✭

    did you set the content level in BMM correctly ?

  • Dir_Pal
    Dir_Pal ✭✭✭✭✭

    @Joshua C. Stewart

    Error Recieved : Communication error connecting to remote end point.

    No Issue with the connection at all as it pulls by itself or with fewer dimensions not sure y did this error occured

    @Subhakara Netala-Oracle

    Not sure what you meant. But I did add other dimension table to fact with simple join id=id both physical and logical too

    @ALOK SH-Oracle

    Its a simple fact to dimension join do we need to set the content level. I don`t have any hierarchy too . Simple subject area one fact and fact joined to 5 dimensions.


    Still struggling where should I focus on for this issue.


    Physical Layer : All Joins are simple and looks good .

    Logical Layer : Simple joins too and inner joins nothing changes

    Not a connection issue as it reflect the data when pulling multiple dimensions and fact.

    As of now I stated other dimension in to fact residing database and its working perfectly

  • What type of databases are you using? I've ran into situations where I was pulling data from 2 different ADW's and was required to load the cwallet.sso file from a Regional Wallet to the OAC Connections Console. May be worth a try...