Can one logical table had bothfragmented and non-fragmented table sources?

Hi,
I created one logical table with three logical table sources as explained below.
1. Inventory Item logical table source with fragmentation clause of ITEM_TYPE='INVENTORY', I checked source combination feature for this LTS.
1. Punch out logical table source with fragmentation clause of ITEM_TYPE='PUNCHOUT', I checked source combination feature for this LTS.
3. Category logical table source without any fragmentation.
The relation between category and item is one to many.
I am getting errors in answers if i try to query all attributes of item for a category in dimension only query.Could somebody validate whether i can create one Logical table with fragmeted as well as non-fragmented logical table sources or not?

Can you share the error messages you are getting?
regards
John
http://obiee101.blogspot.com

Similar Messages

Logical table having more than one Logical table sources

Hi ,
Is it possible a logical table has 2 logical table sources and there is no join between the underlying table of logical table sources?
What will happen if we create the request which contains one attribute from each source?
Will BI server return records with Cartesian join?
Is it mandatory if logical table is having more than one logical table sources(exp. Logical table sources are X,Y and underlying table is A,B respectively),
The underlying tables (A&B) must be joined ?
Can someone explain the logic behind the logical table sources? How does it work?
Any reference of document will be appreciable.
Thanks,Ashish

Hi Stijn,
Thanks for response.
You are saying that Oracle BI server will run a query against both tables and combine the results. But if there is no possibilty of any type of join, how BI server will combine the results from both tables.
I have a scenario like below -
Suppose i have 2 tables A and B at physical layer. Both table contains the information of any common subject area.
But there is no attribute is common between A and B so not any kind of join possible between two.
Now if i create a logical table with 2 logical table source A and B and create any request having one column from A and one from B ,
What will happen? How BI server will combine the result? Will BI server not result records after Cartesian join.
How can i model this scenario?

Question related to Logical table source

Hi All,
I have very basic questions -
(1) When do we create multiple logical table sources within a dimension?
(2) If a dimension has more than one logical table sources , when do we need to map the underlying table to other underlying table of logical table sources.
For exp consider these tables XLE_Entity_Profile, XLE_REgistration , AP_Invoice_ALL
AP_Invoice_All is a fact table. relationship between XLE_Entity_Profile & XLE_REgistration is (1:M).
Join info is as below -
(a) XLE_Entity_Profile.Legal_entity_id = AP_Invoice_ALL.Legal_entity_id
to get the registration of LE the where clause is as below-
(b) XLE_Entity_Profile..Legal_entity_id = XLE_REgistration.Source_id and XLE_REgistration.Source_table = 'XLE_Entity_Profile'
I have created the alias of XLE_REgistration as XLE_REgistration_LE.
With in a dimension , i have 2 logical table source - XLE_Entity_Profile & XLE_REgistration_LE.
logical table source 'XLE_REgistration_LE' has where clause 'XLE_REgistration.Source_table = 'XLE_Entity_Profile'
When i query , LE name , LE Registration Name, i get error like -
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14070] Cannot find logical table source coverage for logical columns: [LE_NAME]. Please check more detailed level keys are mapped correctly. (HY000)
Le Name is from XLE_Entity_Profile and LE Registration Name is from XLE_REgistration_LE.
But when using the properties of logical table source ' XLE_REgistration_LE' , i map it to 'XLE_Entity_Profile' ,i get the correct result.
I am not able to understand why am i getting error in first way of modeling.
Thanks , Ashish

Hi Ashish,
first about logical table sources (lts): you can create different lts for aggregation and/or fragmentation. Aggregation means that data is aggregated on another level among different physical tables. Fragmentation means that the content is different over different tables (other rows).
In your case, I think the problem is that your dimension is not denormalized, which results in a snowflake.
What I understand is that you have the following (physical diagram):
Invoice (fact table) >----- Entity (Dim) >----- Registration (Dim)
You have the following joins:
invoice.entity_id = entity.entity_id
and entity.entity_id = registration.source_id and registration.source = 'something'
First idea:
I would create the following join (in physical diagram):
Invoice (fact table) >---- Registration (Dim)
Where:
invoice.entity_id = registration.source_id and registration.source = 'something'.
Then in your Entity dimension you should create a hierarchy:
Grand Total Level
Entity
Registration.
In your dimension you should create the first lts: Entity
Set the aggregation content of this lts to Entity.
This lts contains only one physical table.
Map only the entity columns to the Entity physical table.
Then create the second lts:
Entity and Registration.
Set the aggregation content of this lts to Registration.
This lts must contain two physical tables, Entity and Registration.
Map the entity columns to the Entity physical table and the registration columns to the registration physical table.
Let me know if it works or not.
Regards,
Stijn

Business Model - Logical Table Source

Can someone give me clarification on exactly when you would follow scenario 1 when modelling a logical table and exactly when you would follow scenario 2, and what the key difference in behaviour between the two is. It would help if someone could illustrate with sql table joins equivalent.
Scenario 1
You drag a second physical table's column onto the logical table. This causes an additional field to appear in that logical tables list of columns sourced from a different table to the original and causes a second table to appear under the original table in the source folder.
Scenario 2
You drag a second physical table onto the existing logical table source of a logical table. The physical table source appears on the surface the same as before, but when you examine its properties you see that the second table has been joined to it.
Thanks for your input,
Robert.

Hi Robert,
This is quite an interesting question, I would say :). As per me, here is why
As you know already, BI Server generates intelligent queries based on our logical mappings in the BMM layer and there is only one primary goal for our BI Server Engine, generating an optimistic physical query.
Scenario 1 : Two logical sources created.
Two logical sources mean, there are two different ways the logical table(or same logical column) could be arrived at.
Ex 1:
You have a model, where you have Sales numbers and 4 levels of product hierarchy (lowest P4 -> P3-> P2-> P1) with sales at productlevel4.
And, You have created aggregated tables for sales numbers at level2 of product dimension also.
So, in this case the same product dimension would have two logical table sources, just because Level 1 Product can be derived from Aggregated product dimension source at level2 or detailed product dimension source at level4. And, it is the BI Server which would determine from where it has to pick (Of course there are some other criteria to control it).
Ex2:
Here even sales numbers are available at different granularities viz product level2, product level4. So for sales logical fact, we end up creating two sources just because there are two completely different sources with different granularity.
Scenario 2 : Two columns created, but only one logical source with a join in it.
Say, in the above example you have a snowflake product manager dimension to the product dimension. So, when you pull Product Manager into your product dimension (collapsing snowflakes), you end up creating just one logical table source with an inner join of ProductManager dimension and product dimension because product manager could be arrived only by going through products.
So, if you have report on sales by product manager, you would see query with an inner join of sales fact to product and inner join(this is based on the join type you set in this logical source) of product to product manager.
Hope I was clear enough and this helps.
Thank you,
Dhar

How can one read a Excel File and Upload into Table using Pl/SQL Code.

How can one read a Excel File and Upload into Table using Pl/SQL Code.
1. Excel File is on My PC.
2. And I want to write a Stored Procedure or Package to do that.
3. DataBase is on Other Server. Client-Server Environment.
4. I am Using Toad or PlSql developer tool.

If you would like to create a package/procedure in order to solve this problem consider using the UTL_FILE in built package, here are a few steps to get you going:
1. Get your DBA to create directory object in oracle using the following command:
create directory TEST_DIR as ‘directory_path’;
Note: This directory is on the server.
2. Grant read,write on directory directory_object_name to username;
You can find out the directory_object_name value from dba_directories view if you are using the system user account.
3. Logon as the user as mentioned above.
Sample code read plain text file code, you can modify this code to suit your need (i.e. read a csv file)
function getData(p_filename in varchar2,
p_filepath in varchar2
) RETURN VARCHAR2 is
input_file utl_file.file_type;
--declare a buffer to read text data
input_buffer varchar2(4000);
begin
--using the UTL_FILE in built package
input_file := utl_file.fopen(p_filepath, p_filename, 'R');
utl_file.get_line(input_file, input_buffer);
--debug
--dbms_output.put_line(input_buffer);
utl_file.fclose(input_file);
--return data
return input_buffer;
end;
Hope this helps.

Multiple Data Sources In One Logical Table

I am new to OBIEE and I have came accross an issue. I appologize if this information is in the forum somewhere but I have searched and cannot find it.
My situation is that I would like to have one logical table that contains multiple data sources which have all the same columns. I already have session variables setup to differentiate the user's security through a row-wise variable for a specific column and a session variable for another column which determines the user's association to the data source in which they belong to. This security works well when the data sources are seperated in the Business Model and Mapping portion but the issue that arises is that the user's cannot share reports when the data sources are seperated in the BM&M.
I have dragged and dropped a table from the Physical model to the BM&M, I then dragged the second data source (with same meta data structure) over to the "Sources" folder in the first data source table in the BM&M. On the Content tab or each data source table I have defined the WHERE clause as such, where VALUEOF(NQ_SESSION."SCHOOL") session variable is my row-wise column filter and the VALUEOF(NQ_SESSION."GROUP") filter is my data source determinative:
sandbox."".SANDBOX.OBIEE_CROSS_ENROLLMENTS.HOME_SCHOOL = VALUEOF(NQ_SESSION."SCHOOL") AND sandbox."".SANDBOX.OBIEE_CROSS_ENROLLMENTS.DATA_SOURCE = VALUEOF(NQ_SESSION."GROUP")
Unfortunatley this only returns values in the BI Answers for the first drag and drop Pysical table in the BM&M layer and not the second Physical table drug into the "Sources" folder. I have also tried to create a new logical table and drag both tables into the "Sources" folder to no avail. I have experimented with the Fragmentation content on the "Content" tab of the seperate logical tables, checking the "This source should be combined with other sources at this level", which gives me an error in BI Answers that a column does not exist which really does.
What could I be missing? Advanced thanks to those who reply.
Thank you,
Kyle

Stijn,
Thank you for the article link. That was very helpful! It seems that I had a few things off as you do need the "This source should be combined with other sources at this level." checked. In my two table source columns for DATA_SOURCE I defined a literal ('086496' and '085597' for the other) in the Column Mapping tab. I pasted the following in the Fragmentation content, checking the "This source..." box on the Content tab:
eSIS.SANDBOX4_SCHOOLS.DATA_SOURCE = '086496'
And pasted the following into the WHERE clause, checking "Select distinct values" on the Content tab:
sandbox4."".OBIEE.NWOCA_SCHOOLS.SCHOOL_CODE = VALUEOF(NQ_SESSION."SCHOOL") AND sandbox4."".OBIEE.NWOCA_SCHOOLS.DATA_SOURCE = VALUEOF(NQ_SESSION."GROUP")
This took care of my user's security, utilizing the session variables in the WHERE clause. I am now able to generate reports that only one user can access from one data source and share that same report with another user who can only see data from the other data source.
Many thanks!!!

Two Dimension Hierarchys based on one Logical Table

Is it possible to have two dimesion hierarchys based on one logical table? Suppose we have the following case:
Accounts Table
Code
Name
Category
Subcategory
Level 1
Level 2
Level 3
I would like to have one dimension Total > Category >Subcategory > Code and one Total > Level 1 > Level 2 > Level 3 > Code, so I can drill down on both paths. Is this possible?
Thanx

Yes, the trick is to have the same key on the lowest level in your hierarchy.
regards
John
http://obiee101.blogspot.com/

No Fact table Exists and [nQSError: 14070] Cannot find logical table source

Hi,
I have 3 tables A(fact),B(dim) and C(dim). there are some other dims. i am getting Errors here.
A is joined with B and B is joined with C .
1) In report if i pull columns from A and B its giving data. If i include C table Columns in the report i am getting Error like
No Fact table Exists.
2) If i pull the C table columns only in the Criteria i am getting error [nQSError: 14070] Cannot find logical table source
How can i resolve this.
Thanks

In Logical table B source properties general tab ->Click on Add button and add table C and pull required columns from Physical layer table C.
If helps mark for any issues let me know.
Edited by: Srini VEERAVALLI on Feb 13, 2013 6:42 AM

Why can one mac access the internet and not the other?

Hi I have just installed a 2nd generation Airport Express base station. I have setup a network and I can connect to it to access the web. Here's the rub, only my Macbook Pro can connect. My Macbook Air cannot connect? A weird error message says (translated from Swedish): Airport has the selfapplied/selfselected IP adress 169.254.67.130 and will not be able to connect to the internet.
Why can one mac access the internet and not the other? Is there something simple that I can do to get more macs to be able to use my Airport Express to access the internet?
Tech details:
Airport Express 2nd generation (just purchased) model 1392
Macbook Pro running 10.8.2
MacBook Air running 10.6.8

It seems the Airbook assigns a dummy IP address so somehow it doesn't reach and receive an IP from the Express. I deleted the previous Express setting restarted the Air connected again, restarted the modem, restarted the Express nothing....
I spoke to the internet provider and the cable modem does not require any username or pw. from the modem to the cable it's one public ip, pure internet is flowing from the modem to the Express but the express doesn't seem to assign any IP address apart from the one assigned to the Macbook Pro.
Do you need a screendump of the settings on the functioning Mac or the faulty one? What settings are you interested in i.e. which tab should it shot?

Incorrect Logical Table Source getting picked

Dear All,
Can you please help me with my query.
I have 2 logical table sources for my fact table
LTS1 -- L1 with some number of levels mappings
LTS2- L2 with same number of level mappings as L1 with one extra level mapped
now when i query on the columns w.r.t to LTS1, though my LTS 1 is in the higher level in the order of LTS's for fact table, the obiee query is hitting the LTS2 and hence we are getting wrong results.
Can you please suggest on my query.Appreciate your help.
Best Regards,
Achala

I have found the solution. The dimensional hierarchy associated with the Dimension of LTS2 of fact had wrong count set for "Number of elements at this level" in the hierarchy.
the below info from http://gerardnico.com/wiki/dat/obiee/level_number_element
helped me figure out this.
"Fact sources will be selected on a combination of:
the fields selected as well as
the levels in the dimensions to which they link.
For example, when aggregate navigation is used, multiple fact sources exist at different grains. The Oracle BI Server multiplies the number of elements at each level for each qualified source as a way to estimate the total number of rows for that source.
Then, the Oracle BI Server compares the result for each source and selects the source with the lowest number of total elements to answer the query. The source with the lowest number of total elements is assumed to be the fastest.
By adjusting these values, you can alter the fact source selected by Oracle Business Intelligence in some cases."
Thank you all,
Achala

Logical Table source source query

In OBIEE 10g we can have multiple logical table sources and we can also add multiple tables into a single logical table source(logical table source source). I wanted to know the difference between doing so and having multiple logical table sources for each logical source.
Hope I made myself clear.
Cheers
Rem

Hi Rem,
When data is duplicated across different physical tables add them as separate LTS with column mapping pointing to most economical sources. Specifying the most economical source is about the idea that a single column exists in more than one table, based on the column mappings BI server picks up those LTS's which could satisfy the request with minimal joins.
When the data is not duplicated add them in a single LTS source. When the physical sources are added in a single LTS, you have the flexibility of using outer joins. But specifying a join as outer join makes BI Server to include this source even if its not required otherwise when the join is inner, the sources will not be included if not required to satisfy the query.
Hope this helps.
Thanks!

Max number of logical table sources

Hi,
I have one logical table based (a fact table) on 8 logical table sources. This is done to simulate some partitioning as my customer does not have an partition set up on data base level.
Anyway my challenge is that a request fired in answers does not seem to take all logical table sources into account when building the physical SQL.
The missing logical table source (the one not being part of the physical SQL) does not differ from the other logical table sources.
Is there a limit of how many logical table sources BIEE can handle under one logical table?
BIEE version: 10.1.3.4

Alastair,
thanks for replying.
The logical tables sources partition the data by year. The aggregation level is the same for all LTS, the check for using this with other sources at this level is set and I've tried to force a result from every LTS (not combined but each LTS for itself). Forcing the results is done by using a dashboard prompt in answers filtering on year.
The whole 'LTS-setup' works in combination with Oracle Warehouse Builder. What I mean by this is the following: In OWB I split the data from one table into 8 different tables, each containing 3 years of data (except for the oldest data where the number of years and amount of data will grow over time).
This is done by comparing values of a year column with the actual year. E.g. the most actual table would contain data for the years 2010 - 2008, the next would contain data for 2007 - 2005, and so on.
Now as the years in the different tables will change, I decided to establish an equaly changing counterpart in BIEE. Basically I defined some repository variables: actaul_year, three_years_ago, six_years_ago, 9_years_ago, etc.
The fragmentation content of the different LTS is defined like this:
most actual data: MyModel.Year.Year >= VALUEOF("3_years_ago")d
next table: VALUEOF("3_years_ago") > MyModel.Year.Year AND MyModel.Year.Year >= VALUEOF("6_years_ago")
next table: VALUEOF("6_years_ago") > MyModel.Year.Year AND MyModel.Year.Year >= VALUEOF("9_years_ago")
etc.
The funny thing is that the missing table is the one containing years 13 - 15. All the other tables (e.g. 16 - 18 years and 19 - 21 years) are represented in the physical SQL. This particular table is not even represented in the physical SQL.
I haven't yet tried to take one of the 'working' tables out to see if this helps (getting an idea if there is a limit on number of LTS per logical table).
Any idea?
Thanks
regards
Andy

Multiple Logical Table Sources vs Single Logical Table Source

OBIEE 11g. I am totally confused. Can someone help me with the following for me.
I have seen logical table sources being used in 2 ways. I have a 2 sources tables: CUSTOMER & ADDRESS. In physical layer these 2 tables are linked by CUSTOMER _ID in a 1:M relationship. i.e. A customer can have many addresses.
Scenario # 1: In BMM the two tables form a logical table called CUSTOMER with 2 different logical table sources which are CUSTOMER & ADDRESS.
Scenario # 2: In BMM the two tables form a logical table called CUSTOMER with 1 logical table source called CUSTOMER only.
What is the difference between the above 2 scenarios and which one is better to use when creating the logical table source.
Regards.

Scenario # 1: In BMM the two tables form a logical table called CUSTOMER with 2 different logical table sources which are CUSTOMER & ADDRESS.
-->In this case; based on the columns select source is defined in the physical query
possible case would be CUSTOMER , ADDRESS, and CUSTOMER & ADDRESS
-->Used in DE-normalized scenarios
--> BI uses intelligence based on content tab settings
Scenario # 2: In BMM the two tables form a logical table called CUSTOMER with 1 logical table source called CUSTOMER only.
-->In this case; CUSTOMER properties->General tab used both CUSTOMER & ADDRESS, in your physical query both tables present irrespective of column selection
-->Used in normalized scenarios
-->Forcing BI to follow our way, since we wont set content tab settings
Hope this helps

Invalid data from serveral fact logical table sources after upgrade to 11g

Hi,
We have a situation after upgrade from 10g to 11g. Answers' querys works fine in 10g environment, but in 11g, generated SQL is not correct.
Our example is something like that: we have orders fact table, customers and time dimensions. Customer have an hierarchy like: Customer Total -> Customer Country -> Customer Region -> Customer Detail (each level in one different physical table).
Order's logical table source has two table sources. One sets to Customer Country level, second one Customer Region level, both with different WHERE clauses in Content tab inside LTS configuration. Both at same level of Time dimension.
The issue is that, at dimension level, SQL is getting correct table to resolve Customer data (Customer Region level), but then, is getting the WHERE clause sets in LTS set to Customer Country level, so we are getting error data. Priority is the same to both LTS at fact table, sets to 0 (default).
How to know the way Oracle BI Server takes one LTS instead of another one? It's supposed to take the LTS defined at the same granularity level... but is not correct this case.
Thanks.

Can you try one of these options:
Try to set the priority group of lowest granular dimension to 1
or disable the LTS that is getting the where clause and check if it works fine and then enable again.

Logical table source error

I am having a union report.
I have a strange problem. The report executes successfully normally but when I am ordering the columns as per the customer requirement its throwing an error "
A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Fact - tablename does not contain mapping for [case when Dim - Account. Number in (some values)]
none of the report is using any column from the fact table so I don't think that join should exist between fact-dim in this case.
Any other solution one can suggest?

Try to redo the same report with requested order. that would be the simplest way to handle it unless you have hidden hills in your development.
If helps mark
Thanks,
http://cool-bi.com

Can one logical table had bothfragmented and non-fragmented table sources?

Similar Messages

Maybe you are looking for