Logical joins differ from Physical layer joins

Can please answer to my Question?
1.How does Logical joins differ from Physical layer joins?
2.What is NQSConfig.INI file and what does it contain?
Thanks
Chi
[email protected]

2) The NQSConfig.INI file contains configuration and tuning parameters for the Oracle BI Server. There are parameters to configure disk space for temporary storage, set sort memory buffer sizes, set cache memory buffers, set virtual table page sizes, and a number of other configuration settings that allow you to take full advantage of your hardware's capabilities.
For more information about the NQSConfig.INI file parameters, refer to Oracle Business Intelligence Infrastructure Installation and Configuration Guide.
1) Logical joins are used in Business Model, Physical joins are used in physical layer. A key property of a logical join is cardinality. Cardinality expresses how rows in one table are related to rows in the table to which it is joined. Logical joins supports outer joins. so many else to mention... just go through RPD help file.
- Madan

Similar Messages

Physical Layer Joins

I am creating a data model from a database that is in 3rd Normal Form. My understanding in the physical layer I should make the joins based on the relation between tables. I have a CUSTOMER & ADDRESS table and I understand that my join will be 1:M here since 1 Customer can have many addresses. However I would like to get all my facts from the CUSTOMER table so since this is going to be the fact table should the Many end of the join be at the CUSTOMER table. I have been given much misinformation about this and have 2 scenarios but do not know which is correct.
Scenario #1: Model the joins in the physical layer as 1:M e.g 1 Customer has many Addresses and then reverse the joins in the BMM to make the CUSTOMER table a fact table.
Scenario #2: Model the joins in the physical layer making the M (Many) side of the join on the Customer table therefore choosing it as a fact table in the physical layer.
Thanks in advance for any answer.

So if I understand correctly then the join in the physical layer will look like this: CUSTOMER------------->ADDRESSES. Is this because the CUSTOMER table is going to be the fact table. I thought the relationship between Customer and Addresses is a 1:M i.e. 1 Customer has many addresses. Why do we not model this in the Physical Layer.

Additional join in rpd physical layer.

Hi,
I created a subject area joning all the tables in physical and BMM. Now I need to existing two tables with one more key. Can I just go the physical layer joins, double click on the join and add the new join there. Can we do like this or is there any process to follow. Please advice.

user4683504 wrote:
Hi,
I created a subject area joning all the tables in physical and BMM. Now I need to existing two tables with one more key. Can I just go the physical layer joins, double click on the join and add the new join there. Can we do like this or is there any process to follow. Please advice.Yes thats it, or edit the join from the UI (right click table -> Foreign Keys)

Joins in the physical layer

Hi,
I have a small doubt:
Is it possible to to give the Outer joins in the physical layer+ of the RPD.i.e.,left outer join,right outer join and full outer join.
If yes can you pls provide me any links related to that.
Thanks,
Chinna

Hi,
No we cannot have outer joins in Physicla layer.
We can outer joins in BMM layer.
In BMM layer - complex join can be full inner join or full outer join or whatever your criteria was,but in physical layer - physical join is always an inner join.
Check this....http://nerdsofobiee.wordpress.com/2010/07/06/obiee-interview-questions/
http://gerardnico.com/wiki/dat/obiee/physical_layer
Regards,
Srikanth
Edited by: Srikanth Mandadi on Oct 15, 2010 1:29 AM

Get Logical file name from Physical file name

Hi everybody,
Please how can i get Logical file name from Physical file name ?
Thanks & Regards
Hassan

Hi,
What i want is to get Logical file name from Physical file name, and not the opposite (get Physical file name from Logical file name).
Thanks & Regards,
Hassan

Error occurred when view the data from physical layer

Hi ,
I have created system DSN like "demo1" for excel file. After that i import the excel file into administration tool.
after that i want to view the data from physical layer. At that time ,I am getting following error .
Please resolve this issue.
Thanks in advance,

hi ashok,
u can push data from psa to ods, for this goto the psa in rsa1>psa>goto that request>rightclick>select " schedule update Immediately ", then data will moved from psa to ods.
or
In ods > delete the failed request>goto the processing tab-->select 3rd option " psa and then subsequentially to data targets ", --> schedule the infopackage.
bye
sunil

Multiple joins Problem in Physical Layer.

I have two tables Departments and Employees in the physical layer of admin tool. When i am trying
to create foreign keys at physical diagram its giving error.
Scenario:
Departments
===========
Department_id (PK)
Manager_id (FK)
Employees
========
Employee_id (PK)
Department_id (FK)
Manager_id (FK)
1. Manager_id of Departments table references Employee_id of Employees table
2. Department_id of Employees table references Department_id of Departments table.
3. Manager_id of Employees table references Employee_id of Employees table.
I have done 1st one. After 2nd one i have tested for consistency check, the following error is coming:
[38015] Physical tables "Oracle DB Connection".."HR"."EMPLOYEES" and "Oracle DB Connection".."HR"."DEPARTMENTS" have multiple joins.
Delete new foreign key object if it is a duplicate of existing foreign key.
How to solve this?
How to do 3rd one also?
Please clarify.
regards
chandra kanth
Edited by: Chandra kanth on 08-Dec-2011 01:47

Hi,
I have created two alias tables (E1 Employees, D1 Departments) for Employees, Departments tables.
I have created foreign key joins as follows:
D1 Departments:
EMPLOYEES.EMPLOYEE_ID = "D1 DEPARTMENTS".MANAGER_ID
E1 Employees:
EMPLOYEES.EMPLOYEE_ID = "E1 EMPLOYEES".MANAGER_ID
and it is consistent also. Please let me know whether the above approach is right or not.
regards
chandra kanth.

Defining Keys/Joins in the physical layer

When the keys and the join conditions are defined manually using a table's Properties dialog box in the Physical layer, do these keys or joins also get defined in the database automatically? My understanding is that it does not get created in the database. So what I am trying to understand is - once the joins are defined in the RPD physical layer, do I have to then define the indexes/constraints in the database as well?
Thanks,

803309 wrote:
When the keys and the join conditions are defined manually using a table's Properties dialog box in the Physical layer, do these keys or joins also get defined in the database automatically? No
My understanding is that it does not get created in the database. So what I am trying to understand is - once the joins are defined in the RPD physical layer, do I have to then define the indexes/constraints in the database as well?
Not required. Indexes can be created in DB on joining col for performance purpose only.
Hope this helps
Edited by: Deepak Gupta on Aug 15, 2011 10:07 AM

Keys and Join description at physical layer does not reflect in BI Answer?

Hi All ,
While creating a RPD , the description about keys and join information using
description and hint property which we define at physical layer, those informations do not reflect BI Answer when i query to metadata dictionary.
Any ideas in this regard?
-- Ashish

Hi All ,
Here i give little bit more description what i did.
(1) I created a RPD and gave some description about Foreign Keys and using hint a gave some description about Physical joins.
(2) After then using utilities I generated the Metadata Dictionary.
(3) Now after restarting of services when i query to Metadata Dictionary using BI Answer , i am not able to see those descriptions. Rest of the information like table level and column level descriptions i am able to see.
Is there any way to get these descriptions or metadata dictionary does not keep descriptions for keys and joins?
Any ideas in this regard??
--Ashish

How to add a stand alone table from Physical layer to Business Model

Hi,
I have tables from 2 different database sources in my Physical Layer.
My Business model currently uses only tables from one database. from my second database in teh physical layer I need only one table and that will be a stand alone table, to my Presentation layer.
1. Does it have to go through my Business layer or can it be directly added to the Presentation layer. What are the steps?
2. Can I restrict the permissions on that stand alone table only to the administrator?
Thank you.

1)create a view with single column using the sql (select 1 from dual) in physical layer and join it with the table using complex join in physical layer (1=1).
Move that to BMM, set the column as key in both physical and bmm layer.
2) You can restrict the access for the table presentation layer
Double click the presentation layer table -> Permission -> there you can restrict the access by user or group
Thanks,
Vino

Record Management: get logical document object from physical doc. object

Hello,
I'd like to get logical document from physical document (sdok object - stricture containing class and objid).
There is BAPI for "opposite direction": SDOK_LOIO_PHYSICAL_OBJECT_GET. By this FM I can get physical document's sdok object from logical document's sdok object.
Can anybody tell me BAPI's name for it?
I tried SDOK_PHIO_LOGICAL_OBJECT_GET, but this BAPI doesn't exist.
Best regards,
Josef Motl

Josef,
There are I don't believe there are any bapi's for this. You probably have to do this via ABAP OO. Create an object of the type CL_SRM_DOCUMENT. This is your logical (LOIO) object of your document. You have to enter the documentclass and the objectid of the document. This class has a method get_variant. This variant is your fysical (PHIO) object of the document. Use version and variant 0 so you will get the latest version object of your document.
If this isn't the answer, can you please explain where do you get the fysical object from if you haven't got the logical first?
Regards,
Tjalling-Jan

OBIEE 11g - complex join in physical layer

Hi, I need to create a complex join in the physical layer with join criteria like the following:
fact.fiscal_year = dim.fiscal_year and fact.accounting_period <= dim.accounting_period
Every time I try to do this, I get the nQSError: 37005 Transaction Update Failed message. Any ideas what is going on?
Thanks,
Scott

Actually, I (finally) got it to work - wow logical joins are a big pain in the butt in 11g. First off, I had to edit the RPD offline, couldn't get it to work (at all) online.
Next I had to delete the existing joins...there appears to be no way to change an existing FK join into a logical join.
Next created the logical joins as stated in my original post - but had to fiddle with it for about 15 minutes to get it to work. You can NOT click the two columns on the dim side, two columns on the fact side, and then just edit the default formula (which defaults to have = sign between the expressions) - because it creates a FK join, and then you start getting errors. Instead, I had to build the expression from scratch.
All in all, 11g has gotten much less flexible and easy to use in this regard.
Scott

Link Join Concept In Physical and Business Model Layer

Hi,
As we know that we could make join relationship in physical layer and also business model layer in obiee 10g. This is what makes me confuse.
First of all, I tried to follow the tutorial in the oracle learning library center with schema SH as an example.
In the beginning, it is stated that we must make join relationship first in physical layer for all imported tables which are consist of dimension tables and fact tables.
Then, in the business model layer, the tutorial said that we must also make join relationship for the logical dimension table and logical fact table.
So, what's the purpose actually we must make join relationship in business model layer ?
All objects in business model layer are actually mapped from physical layer. So automatically the relationship in business model layer should be available automatically as they are mapped from physical layer.
Maybe for you guys who know the concept well about this difference of relationship, could tell me so I could get the idea of what it is actually about.
Thanks

Physical layer does represent datamodel joins as is in almost all cases.
Federated queries are a best example why joins are implemented in both (Physical & BMM layer) places.
Business model mapping layer is modelled according to your business requirements.
This is where your model MUST be a simple star schema, also where you model your hierarchies based on logical tables in bmm layer, & do appropriate aggregate navigation.
Hope the view points presented will put you in right direction.
mark answers promptly.
-bifacts
http://www.obinotes.com
J
Edited by: bifacts on Dec 16, 2010 9:19 PM

Complex join in physical layer

Hi Experts,
In which scenarios we will use complex join in physical layer i saw in many blogs that when we are using expressions and other than equality.
For better under standing can any one post few scenarios on this.
Regards,
Rafi

Hi,
Always use “Foreign Key” joins, not “Complex Joins” on the Physical Layer
Refer-http://obiee101.blogspot.com/2011/10/obiee11g-golden-rules-rpd-physical.html
If your join looks like D_DATE = TRUNC(S_DATETIME) try add a extra column S_DATE in your DWH. Any matching processing done by the BI-server costs time and you often loose the advantage of an index in your DWH.
For all others relationships other than a Primary Key-Foreign Key Relationships (expression other than equal to perform an equi join), you have to use a complex join otherwise you have to use a foreign key

Joins in BI Administration layer

Hi,
I have created few dimension in Owb, along with a cube. now i imported them in BI administrations physical layer. is it necessary to join them both on physical and business model an mapping layer or its enough to join them on physical layer.
secondly, can we use complex join in place of logical foreign key joins.........??
regards,
imran

Thanks for ur response.......
I did the same but when i completed business model and mapping layer and then drage it to the presentation layer but consistancy check gives me error that shows there is some relationship error. i think some joins are still missing.... should i join on presentation layer as well .......... if not why ???? as i am joining tables in first two layers.....
Secondly tell me something about Chronological key in time dimension. what is its usage.......
thanks
imran
Edited by: user596732 on Feb 18, 2009 10:39 AM

Logical joins differ from Physical layer joins

Similar Messages

Maybe you are looking for