Categories
- All Categories
- 4 Oracle Analytics Sharing Center
- 12 Oracle Analytics Lounge
- 189 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.4K Oracle Analytics Forums
- 5.9K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 65 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Adding Additional Sources to Logical Table - Can't See Additional Source Data in Subject Area

Hi.
I am creating a Semantic Model in OAC & I want to add an additional Source (Table B) to an existing logical table (Logitcal Table A). Table A & Table B are the exact same table structure. However, after I add table B as an additional Source in the Logical Layer to Logical Table A, check for errors & deploy, the subject area only shows data for table A BUT not B. Mapping is correct. I've read through the Oracle Doc.Building Semantic Models in Oracle Analytics Cloud
. Table B certainly has data. Both tables are enabled in the Sources tab. Both have Priority 0. Both Table A & B are joined to a Calendar table at the Physical Layer & those are the only 3 tables used so far.
New to this. We don't have the option for an ETL to union both tables. Any suggestions on what I could check?
Best Answer
-
Hi @Erik AE ,
This is the expected behavior. By default, different logical table sources for the same logical table are not combined together.
You have 2 options to do the union:
- If you are using the Model Administration tool to create and manage the RPD, you have to tick the "This source should be combined with other sources at this level" option in the Content tab of each logical table source that you want to combine. There should be something similar in the Semantic Modeler as well.
- Otherwise, you could combine the tables directly in the physical layer by defining an opaque view, or in the database by defining a view and importing it in your Semantic Model.
1
Answers
-
In addition to what Federico said, if your 2 tables do not contains exactly the same data, you don't want to always query both tables. If you have a known rule defining what is in table A and what is in table B, you can define the fragmentation rule. In this way, if a filter is set in the front-end for that same criteria, the physical query will not go to both tables but only to the one with the data. It can help improve your performance. But as said, it only work if you have a known rule defining the data contained in A vs B.
0