Confused about source logical table

Similar Questions

• How multi Source logical Table would work?

  Hi all

  I am facing a problem with multi Source logical table. Can I build a business model with a Table of logical facts which have two Sources? Taking the low description for example:

  Name of the table	Columns	Description
  Fact	TIMECD (2013Q 101, that meet at Time.TIMECE), the DATA
  Fact_Aggr	TIMECD (2013Q 1, that meet at Time.PERQUARTER), the DATA	Overall table for the facts and the sum of the monthly data to quarterly
  Time	TIMECD, YEAR, SURPASSED, QUARTER, PERQUARTER, MONTH, PARMOIS

  I tried to create a MDB that contains two fact Table in the same logical fact Table. But POET shows the fact DATA, even if I drag PERQUARTER into the report.

  Here's my question:

  1. can I have a logical fact Table that contains facts and of the Fact_Aggr?

  2 How BIEE will determine what DATA should be used?

  Best regards

  Martin

  Hello

  Change the right content level, LTS are chosen according to the level of content.

  Level content for LTS Fact_Aggr should be PERQUARTER while LTS for fact should be at TIMECE.

  Kind regards

  Srikanth

  https://bintelligencegroup.WordPress.com/

• nQSError: 10058 incorrectly defined source logical table

  Hi all
  
  I'm trying to join two facts using a dimension. If I run the report with a dimension column & a fact it works. But when I run a report with 1 column in the first column done & 2nd of the second fact I get the below error.
  
  I don't know that this has something to do with the tab content in sources in MDB later.
  But can someone me what exactly I have to do.
  
  
  State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error occurred. [nQSError: 15018] Incorrectly defined logical table source (for the fact DWH_PA_MBR_PA_TMP_NEW table) contains no mapping for [DWH_PA_MBR_PA_TMPT_NEW. PERIOD_CODE]. (HY000)
  
  SQL issued: SELECT DWH_PA_MBR_PA_TMPT_NEW. PERIOD_CODE saw_0, DWH_PA_MBR_PA_TMP_NEW. CURRENCY_ID DWH ORDER BY saw_0 saw_1, saw_1
  
  Thank you
  Pankaj

  Create the hierarchy of the dimension.
  In LTS for two fact tables, set the lowest level of the dimension. (or other classes as the case may be).

• confused about source and external code path

  Hello

  I created a Jing video to describe my problem (I hope that is useful and is not annoying, make me know). In short, I don't know how external AS3 scripts are supposed to be referenced, but I do work in AS2 years.

  create a movieclip button in flash programming environment and have your current entending sprite class extend the movieclip class.

• Several Sources of Table unique logic vs logical Source of Table

  OBIEE 11 g. I'm totally confused. Can someone help me with the following for me.
  
  I saw sources of logical table used in 2 ways. I have a table of 2 sources: CUSTOMER & ADDRESS. In the physical layer these 2 tables are related by _ID CUSTOMER in a 1:M relationship.  for example, a customer can have many addresses.
  
  Scenario # 1: MDB two tables form a logical table called CUSTOMER with 2 different sources logical tables that are CUSTOMER and ADDRESS.
  
  Scenario # 2: MDB two tables form a logical table named CUSTOMER with 1 table logic source called CLIENT only.
  
  What is the difference between the above 2 scenarios and what is the best to use to create the logical table source.
  
  Kind regards.

  Scenario # 1: MDB two tables form a logical table called CUSTOMER with 2 different sources logical tables that are CLIENT & ADDRESS.
  --> In this case; based on the selection of source columns is defined in the physical request
  possible case would be customer, ADDRESS and ADDRESS of the SUBSCRIBER &
  --> Of standardized scenarios used in
  --> BI uses intelligence according to the settings on the content tab

  Scenario # 2: MDB two tables form a logical table named CUSTOMER with 1 table logic source called CLIENT only.
  --> In this case; CLIENT properties-> general tab used both ADDRESS CUSTOMER & in your physical query two tables regardless of column selection
  --> Standardized scenarios used in
  --> Forcing BI to follow our path, since we usually set the settings on the content tab

  Hope this helps

• Source of the logical table incorrectly defined

  Hello
  
  I have the following physical layer joins:
  
  Projects_dim is linked to Budget_Versions_dim
  Awards_dim is linked to Budget_Versions_dim
  Budget_Vesions_dim is linked to Budget_lines_fact
  
  Projects, grants have Budget Version are dimension tables while the budget lines is the fact table.
  Projects and scholarships are also linked to other tables of facts.
  
  I've implemented a fact table in my BBM with all my tables of facts, between them as sources, there is the table of budget lines, and I also did mapping suitable for each of them does.
  
  The problem is, let's say the user, no matter what, wants to have a report that has fields of Project_dim, Awards_dim and Budget_version_dim, without going through any column is in there. In this case, I get the error: incorrectly defined source logical table.
  
  How can I solve this problem and get the report to return the budget versions by project and by the price?
  
  Thanks adavance...

  Hi Patrick,

  I have not recived you send, but in the meantime I have another solution for you problem, I modified the SPR, there is a fictitious table doing the join with all that a TI is used as column made implicit.

  See if it can help you!

  Kind regards
  Gianluca

• Several Sources of the logical Table in MDB under 1 logic Table in OBIEE 11 g

  I have a question, and even after doing a lot of research on google I couldn't find any article by asking you: -.
  
  I want to create a logical Dimension table
  This logical dimension has columns from 2 different physical tables, TableA and TableB. The relationship between TableA to TableB is 1 to zero.
  
  There are 2 ways to create the logical dimension:--
  1) go to the properties of logical TableA table-> then source it + sign click and then add the right outer join TableB, tableA with.
  We see here a tableA table in the logical table source.
  (2) so that we have 2 logical table source, drag the column tableB.
  
  Please try to explain without using the concept of fragmentation and without taking into account the fact tables. I have a question for the simple logical dimension only tables.
  
  I wanted to know which is the right path and what requirement/factor decides what to do?

  See this post
  Business Model - Table logic Source

  Let me know for Qs.

  If brand as helping correct :)

• By dragging the columns in source existing logical table...

  Hello
  I'm learning just OBIEE 11 g and I use a turorial from oracle, it is
  "Creating a repository using the BI of Oracle 11 g Administration tool" for aim practice.
  In this tutorial, it's say that do drag the columns of phscial layer of Logica Table Source
  MDB layer to avoid creating a second source of logical table... But when I try to drag the columns to
  source of existing logic, it is disabling I mean that is not to allow... is there any other technical
  IT... or I'm wrong addresses.... The following are briefly in the
  Tutorial.
  
  
  "Drag all six columns of D50 Sales Rep in the physical layer to D5 Sales Rep in the MDB layer." This action
  creates logical columns and adds a logical table source D50 Sales Rep to D5 Sales Rep.
  The logical table D50 source Sales Rep and rename LTS1 Sales Rep.
  In the physical layer, expand D52 Sales Rep Position.
  Drag the POSTN_DESC and POSTN_LEVEL D52 Sales Rep posted to LTS1 Sales Rep that you are
  by dragging columns from the source to the logical table, not the logical table. Dragging to the logical table would create a
  second source of logical table.
  Drag the DISTANCE of D51 Sales Rep Parent child at LTS1 Sales Rep. Yet once, you drag the column to the logic
  the source of the table, not the logical table. »
  
  help would be appreciated.
  Thank you and best regards,
  Sri_Oracle.

  Hi Sri,

  When you drag a physical column on an existing source of the logic table and if it doesn't let you do, then it means that there is no physical join between the existing physical table (which the logical source already points to) and the new physical table (which you drag the column now). Then, please, make sure the joint in place.

  I hope this helps.

  Thank you
  Diakité

• Several Sources of data in a single logical table

  I'm new to OBIEE and I encountered a problem. I apologize if this information is in the forum somewhere, but I've searched and can't find it.
  
  My situation is that I would have a logical table that contains multiple sources of data, which all have the same columns. I already have the configuration of session variables to differentiate the security of the user through the variable for a specific column and a session variable to another column that determines the association of the user with the data source to which they belong to. This security works well when the data sources are separated in the business model and mapping party, but the question that arises is that the user cannot share reports when data sources are separated in the BM & M.
  
  I slipped and fell on a table in the physical model to the BM & M, I dragged then the second source of data (with the same meta data structure) on the "Sources" folder in the first data source table into the BM & M. on the content tab or each table data source, I've defined as WHERE clause where VALUEOF (NQ_SESSION. ("" SCHOOL session variable ") is my filter in the column and VALUE (NQ_SESSION. ("" GROUP filter ') is my critical data source:
  
  sandbox. ». SANDBOX. OBIEE_CROSS_ENROLLMENTS. HOME_SCHOOL = VALUEOF (NQ_SESSION. ("" SCHOOL ") AND sandbox. » ». SANDBOX. OBIEE_CROSS_ENROLLMENTS. DATA_SOURCE = VALUEOF (NQ_SESSION. "" GROUP")"
  
  Unfortunately that returns the values in the BI responses for the first drag and drop material table in the BM & M layer and not the second drug physical table in the folder 'Sources '. I also tried to create a new logical table and drag two tables in the "Sources" folder without success. I have experimented with the Fragmentation in the tab "Content" of the separate logical tables, checking the "this source must be combined with other sources at this level", which gives me an error in the responses of BI that there is no such thing as a column which has really.
  
  What might be missing? Thank you in advance to those who respond.
  
  Thank you
  
  Kyle

  Do not check the box "this source must be combined with other sources at this level", otherwise, it will always take the first logical table source. If you need to get rid of the error message. Are you sure that you have mapped all the columns on every logical table source?

  Maybe this article helps you to:
  http://www.rittmanmead.com/2007/06/19/OBIEE-data-modeling-tips-2-fragmentation/

  Kind regards
  Stijn

• FRAGMENTATION applied on several logical Tables does NOT WORK as expected

  Dear all,

  I have the below scenario implemented that does not work as expected.

  I have a logic Table LT1 (SUN) which is being implemented based on two physical Tables PT1 and PT2 (PT1 and PT2 are DIMS). LT1 has two of LTS, LTS1 and LTS2 implemented PT1 and PT2, respectively. Fragmentation is applied based on the ID of the system Source the PT1 and PT2 are loaded from different source systems. The granularity of the Tables physical is the same.

  Likewise, we have LT2 (DIM), which is implemented in two Tables of physics more and Fragmentation is applied in the Source systems function ID.

  We have an other TIMES DIM on which fragmentation is not applied.

  All of the above tables are linked to the fact (also physical and logical).

  I filter the data for TIME_DIM. Year = 2014 in all scenarios below.

  Scenario1: This solution works as expected when I shoot columns of LT1, SUN as well as the fact of TIME. (YEAR = 2014 is passed in the WHERE clause of queries UNION ALL 2, which is OK)

  Scenario2: This solution is also works very well when I shoot columns of LT2, SUN as well as the fact of TIME. (YEAR = 2014 is passed in the WHERE clause of queries UNION ALL 2, which is OK)

  Scenario 3: When I pull the LT1, LT2, SUN report, done TIME and filter the data for TIME_DIM. Year = 2014, the report does NOT WORK as expected. (Filter on YEAR = 2014 is not passed in UNION All queries in this scenario)

  When I build the model above (for scenario 3) report, it does not go as planned. Do not throw any error, it displays incorrect as results as physical demand generated by the BI server is not correct. Some of the filters is past the TIME SUN are not injected at the request of physics.

  Someone come in this scenario, no solution to the above is greatly appreciated. Thanks in advance

  Kind regards

  Madhav P.

  This is the bug in OBIEE 11 g of product. Oracle has provided the patch for the same and it is absolutely working fine now.

  Kind regards

  Madhav P.

• Confusion about the size of the array in Oracle 11 g

  There is confusion about the size of a table. When exporting schema 'CRESTELWOMPRD601', the log file shows:

  _____________________________________________________________________________________

  . . exported "CRESTELWOMPRD601." "' TBLRSUBSCRIBERFIELDWORK ' lines of 12.62 GB 35568

  ____________________________________________________________________________________

  which may involve the size of the TBLRSUBSCRIBERFIELDWORK table is 12.62 GB.

  But when I find the size of the table using the query:

  SELECT nom_segment, BYTES / 1024 / 1024 "SIZE (MB)" FROM dba_segments where owner = 'CRESTELWOMPRD601' and nom_segment = 'TBLRSUBSCRIBERFIELDWORK. '

  He said that the size is only 9 MB for the TBLRSUBSCRIBERFIELDWORK table.

  I hope that my request is clear that there is no clarity on the size of the TBLRSUBSCRIBERFIELDWORK table.

  Please get back with the answer to my query

  
  

  Concerning

  Dba_segments indicates the space allocated to the segment while expdp indicates the size of the exported data, so if you had a table with a measure of 1 MB, but no data, dba_segments would 1 MB and expdp would report 0 bytes.

  John

• Confused about trandata

  Hi all

  11.2.0.1

  I'm confused about additional logging.

  I have golden gate replication, but in primary db.

  Is this related to archive the recording? It works even if I'm not on the archive log?

  Installing Oracle: orcl

  Enable supplemental logging (required on primary database only)

  SQL > alter database adds additional log data;

  
  

  
  

  Hello

  One of the main reasons to enable additional logging is to generate logs for the update statement. As insert and remove implies the change to an entire line (addition or deletion of a complete line) and all the columns it while updating can occur on a column of a row.

  Additional logging on the side of database source to some of the columns are very well required to ensure that these changes to the columns that are supplemental logging enabled will be applied with success in the target database. With the help of these additional columns, oracle decides the lines that need to be updated on the destination side. This is so the extra logging is more imperative for replication.

  SUPPLEMENTAL LOGGING & laquo; ON CALL DBA SUPPORT

  Blog de Ajwat on Oracle: extra for Golden Gate

  Thank you

• Difference between a logical table duplication and creation of an alias

  Hello
  
  I have a question of basic theory.
  
  What is the difference between creating a duplicate in the MDB layer and creation of an alias physical and important in the MDB layer.
  
  I want to join the physical object to two facts and import that into MDB layer and duplicate the object logic and create an individual join for each of the entities in the MDB layer. This kind of structure will have any negative impact on the final result.
  
  Any suggestions on this will be greatly appreciated.
  
  Thank you
  
  This is for OBIEE10g

  FYI; Here it is my comments

  Assuming the column rename in MDB for the same physical object is supplied to this kind of approach ;)

  I suggest go by best practice or how consistency.
  A logical table should have a ref source of physical layer.
  Logic or presentation column should have at least one physical source directly or indirectly (buy from the other logical column)

  Would it help to have their own hiearchies dimension for each logical table, just in case you duplicate an existing logical table for which there is a dimension existing in the model you get consistency error.

  When you joined the MDB you may need to set the join by foreign key (which have a condition) in MDB instead of complex join logical layer.

• Logical tables with the same priority

  Hello
  
  Can someone please clarify on this.
  
  I have 2 sources of logic table in my MDB layer say Logical_Table_A and Logical_Table_B, which satisfies the columns requested in my presentation layer and the two have priority as 0.
  
  If during execution that would be considered for the application of these two tables?
  
  Thanks in advance,
  Pantxo

  Hello

  When you select only the fact tables then OBIEE server selects the table of optimal facts, but when you specify the dimensional hierarchies in the logical level, then it will look for the logical source dimension is referred to in the logic levels. Or alternatively, you can specify the conditions in the ' where clause' the content tab and according to the State meets the logical fact table will be recovered in the query

  Hope this has solved your problem.

  Concerning
  Young

• want to understand the logical tables in SPR

  Hello
  
  tableA-> PKA
  tableB-> FKA and FKC
  tableC-> PKC
  
  I have one thing to ask, I am using obiee 11g.
  The SPR that I dragged and droppped a table called tableA
  Now, I have 2 other tables tableB and tableC
  
  So should I do drag and drop other 2 tables in the same table logic table where I tableA so here the source will display 3 tables
  or do I have to create another logical table that the source will be tableB, tableC abd?
  How the decision should be taken that I want to say on what basis.
  
  Since I pk to tableA and tableb Drop Drag in the custom of logical table even would it be a problem?
  
  Thank you

  If PK and FK are foreign key, primary key, respectively in the post, then you have a star schema is already planning to tableB as does. So, in this case you just drag as a new table and do modeling in the business layer as a pattern in the star.

  The need to by dragging in the same table in order to have several sources in this, would come in a snowflake model. The snowflakes are few relatively more standardized, and to make it not standardized, a table with several sources is used in the business model. Thus, a star schema is reached in these scenarios.