Time Dimension table

Similar Questions

• Hour/Min column in the Time Dimension

  Please can someone help me with the script to fill in the time Dimension Table that contains a column of hours/min. Here's my Time_D structure:
  
  Year
  Quarter
  Month
  Name of the month
  Week
  Day
  Hour
  Min
  
  Also is it a good practice to have the hour/Min column in the time Dimension?
  
  
  Thanks in advance.
  Concerning
  B

  B,
  Sorry if I confused things a bit...
  I wanted to say in the MDB layer, you can model a dimension table (time) with the path complete drill (year-> quarter-> month-> day-> hour-> Min)
  This a logical table would have two sources of logical table to map required fields of your two tables of phyiscal (Date_Dim and Time_Dim)
  You must define the levels of content accordingly for each logical table source, so the user in responses can perfectly break of the year all the way up to Min, their sound a single dimension, actually its two tables and the BI server switches according to the levels of content in the LTS.

  Sorted?
  Let us know if you get the probs.
  Alastair

• 2 dimension table size error

  Hello

  In file attached an example of my problem. I remove a 2-dimension table and the size of the screen. I can see in "size 2" (see the example) that the size is not 0. Is this a normal behavior?

  Thanks in advance, Daniel.

  Hi Daniel,.

  Since the delete array help page:

  "Delete From table details

  This function reduces the table in only one dimension... »

  Even if your table 'seem empty,' he is so really. I'm guessing that the memory for lines is still allocated.

  You can see by connecting the array to a loop and check how many times she iterates (i.e. twice).

  To really empty table, you can add a further dismantling of the Array function and delete lines (length = 2, index = 0). Now connect this to a for loop and you will see it does not iterate. Table sizes will now be 0,0.

  A little weird at first, but ultimately this is the expected behavior.

  Steve

• Time dimension

  I have the CSV file as a data source. I've created tables to CSV files and then them modeled in SPR and then created time on that dimension. But the time dimension does not work. Is it because the data source is a CSV file?

  Any help appreciated

  Where is their total content large?

  

  This one is from SampleApp, as you can see there is a "time Total" and it is reported as "grand total" (a box set).

  So maybe just remove your and build it yet keeping the grand total and rename the level of detail of the "year".

  Add your unique column it and set it as the key level (and also key chronological).

• Performance problem with SQL for recovering data in FACT and Dimension Table

  Hello

  We have a query that performs very slow when extracting data in FACT and the DIMENSION Table.

  SQL and Plan are in the attachment.

  Please suggest how this can be improved.

  The version of DB is 11.2.0.4

  Kind regards

  VN

  Slow is a very relative term, for about 1 hour is slow for some 1s is slow. So please always quantify your settings.

  The first thing caught my eye is done 4 times ia_oasis_tot_prov_cur_d access. Try to isolate which and change it like this and see if it returns the same result.

  select case when a.clm_capitn_ia_bil_prov_edw_sk = b.prov_edw_sk then b.prov_id end ben_billing_prov
       , case when a.clm_capitn_attnd_prov_edw_sk  = b.prov_edw_sk then b.prov_id end ben_attending_prov
       , case when a.clm_capitn_ia_pcp_edw_sk      = b.prov_edw_sk then b.prov_id end ben_pcp_number
       , case when a.clm_capitn_ia_ipa_prov_edw_sk = b.prov_edw_sk then b.prov_id end ben_ipa_number
    from edw.clm_capitn_f partition (jan2015) a
    left join
         edw.ia_oasis_tot_prov_cur_d b
      on (
             a.clm_capitn_ia_bil_prov_edw_sk = b.prov_edw_sk
          or a.clm_capitn_attnd_prov_edw_sk  = b.prov_edw_sk
          or a.clm_capitn_ia_pcp_edw_sk      = b.prov_edw_sk
          or a.clm_capitn_ia_ipa_prov_edw_sk = b.prov_edw_sk
         )
  

  If it works this means allows you to reduce certain I/O.

• Attributes of the update/load (nonkey elements) Dimension table

  Hello
  
  Is there a configuration change in DAC or Informatica where I choose to load all dimension during a load tables, regardless of a transaction in the fact table? I have observed that for all these accounts with no corresponding transactions are extracted, but fell to the time they reach the actual dimension table. So in the end goal of DWH, only these unique accounts are presented which have an associated transaction.
  
  I know that we can create a mapping to the in order to include some sort of a flag to DAC thing assuming that the corresponding made base table has also changed and then carry on the dimension data. But is there a simple alternative?
  
  For example, in the GL, we have an account dimension, which has a line details associated with the transaction for each account in the fact table. I just changed the name of the account from A to B. Any changes or updates to the entrance of the line in the FACT table. Now, I run an incremental load. Will be change (new account name) has recognized and more? OR it will bring only when associated with line changes too?
  
  Usually when the dollar amounts do not change, nobody cares, but in our case the customer wants. I googled widely understand incremental loading but cud not get a clear answer to this question. SCD2 plays a role any in this?
  
  Thank you
  Dan

  If you want to capture the story on a field that is NOT before now, you can activate the Type 2 SCD and then add that field to the ETL in TYPE2 COL DIFF indicator that is used to add the entries of SCD Type 2 during the ETL. If the dimension is activated in Type 2, most of the work is done, it is not too difficult. However, be aware that this can lead to many more recordings volume performance and data to keep in mind that do you this.

• How many heirachies can be created using a dimension table

  Hello
  
  I have a single dimension and a fact table, how heirachies can be created, he is alone?
  
  Thank you.

  Hello
  A dimension can have only a single hierrarchy for sure. But create dimension in such a way (columns to include in a single dimension, example: year and FYear in the time Dimension) that we can create two branches on the Total level.

  Check out this blog... Will resolve your doubts... http://gerardnico.com/wiki/dat/obiee/hierarchy#defining_multiple_hierarchies_for_the_same_dimension_logical_table

  Kind regards
  Srikanth
  http://bintelligencegroup.WordPress.com

• Time dimensions in double

  Hi all
  
  I think I have a simple requirement but I don't how it works:
  
  I have some dimensions and a fact table. In my table of facts, I have 2 foreign key on my dimension of time.
  When I import my tables and check the consistency, I get errors: "in double foreign key. Delete"(don't remember complete sentence)
  This is the first point that I do not understand. Why can I have not more than 1 foreign key?
  
  The second point is to know how to have 2 time dimensions. In the MDB, I duplicate my time dimension. But which to choose? I tested with a foreign key and complex join (and foreign keys 2 or 1 in Physics) and I still have the same result (bad).
  
  So can someone explain to me how configure both physical than MDB joins use a dimension greater than 1 hour (without creating a new physical dimension of course)
  
  Thank you

  Hello

  Create table aliases (as they play different roles) for the dimension of time in the physical layer and combining your done using physical joints.

  After importing to the physical layer, if duplicate keys exist, delete the duplicate keys.

  In this scenario, two keys will be exist on the fact for the time dimension, remove those and create the joins between aliases.

  Thank you
  Vino

• Add the quarter to the time dimension

  Hello
  
  We have created a time dimension using the owb wizzard, but did not include the quarter level. Is it possible to add it to the dimension later without deleting a re-creation of the entire dimension?
  A new time dimension would probably be corrupt all the cubes (data and metadata), so I would avoid that.
  Any ideas?
  
  See you soon,.
  
  Knut

  Hi Knut

  Yep, should be possible.

  Change the dimension and select the quarter level in the levels Panel, and then click quarter in hierarchies pane to add it to the hierarchy. You can then delete the link and autobind on details for the physical links to the underlying table. On the hierarchies pane, there is a button "Create map" that will regenerate the mapping to load the time dimension.

  See you soon
  David

• How does binds to the Dimension Tables.

  Hi all
  
  One explains how the ROW_WID of the table dimension and the related column in the fact table is filled with the same values in different mapping?
  
  Consider if we want to develop a new fact and dimension tables, how do I apply for the ROW_WID and the join between the fact and dimension.
  
  Thanks in advance.
  
  Concerning
  Vishwanath

  Hello

  Essentially in BI dims applications all are first populated and each dim table has a column of wid row outside the primary key (datasourceid + integration id) combination. If you open a seeded map and you will see this line wid column is filled using a reusable sequence generator transformation. Then every time u run this mapping the Feds line change...
  Now go to the facts... as a normal rule in ETL u run the facts after all the dimensions... If you open any map done planting you can observe all the facts has an associated wid the dims, he joined to... so if a fact joins 3 If stump so there will be 3 Feds associated with each dim. The Feds are again filled with a search on the dimension table and line extraction wid bad ID the Sun. If u get wid of the dimension row in the column of wid the fact... Please let me know if you hv questions

  Regarding
  VINET

• Coherence WARNING: logical dimension table [39008]... has a source...

  Hi well think for playback.
  
  I have a problem (which is quite common that I saw, but I could find a solution that solves my problem again) with coherence.
  
  My physical layer looks like this:
  
  Table_a
  Table_B
  Table_C
  Table_D
  Table_E
  
  In the business model, I have all of same tables and the following joints in the logical scheme of the Table:
  
  -> Table_B Table_a
  Table_C-> Table_A
  -> Table_A Table_D
  Table_E-> Table_A
  
  The consistency check is delivered two warnings:
  
  Warning
  Source of the logical table
  Table_a
  [39008] logical dimension table Table_A has a source Table_A who do not adhere to any source of fact.
  
  Warning
  Source of the logical table
  Table_B
  [39008] Table_B logical dimension table has a source Table_B who do not adhere to any source of fact.
  
  While working in BI answers, I managed to recover all the data tables C, D, E. But for tables A and B I can retrieve only the columns that are defined in the join Table_A-> Table_B. All other columns to deliver the following error message:
  
  Error codes: OPR4ONWY:U9IM8TAC:OI2DL65P
  State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error occurred. [nQSError: 14026] Unable to navigate the requested term: Table_A.Column_X. correct metadata consistency warnings. (HY000)
  
  If I get one column from Table_A and one from Table_E, I have the following error:
  Error codes: OPR4ONWY:U9IM8TAC:OI2DL65P
  State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error occurred. [nQSError: 15018] Incorrectly source the logical table set (for the fact Table_E table) does not contain a mapping for [Table_B.Column_X]. (HY000)
  (Yes its Table_B not one)
  
  I would like to correct this mistakes but do not know where the problem is hidden.
  
  Any help is appreciated with kindness.
  
  Evgeny

  Table_a >-Table_B
  Table_a >-Table_C
  Table_D >-Table_A
  Table_E >-Table_A

  It's seems that D and E are fact tables joined to a dimension. A has dimensions B and C, this is attached to itself.

  So the only facts are D and E, is that at the time? A is the size?

  D and E joined in A and A are the joints B and C, right?

  Concerning
  Goran
  http://108obiee.blogspot.com

• Time dimension wizard is not apear

  I'm just starting with OWB and have a few questions. I use OWB version 10.1.0.4.0.
  
  
  1. when I try to create a time dimension (right-click on the dimension) only 'create the dimension' will apear and not an opportunity to choose a wizard. What I am doing wrong?
  
  2. is it possible to display the content (data) in a table directly from the mapping Editor?
  
  THX in advance,
  
  Arjan

  Hi Arjan

  If you really must use OWB 10.1... This is true of OWB 10.1. OWB 10.1 has a standard dimension wizard, and there was a table function, condition to generate data, the card had to be built manually. See the 10.1 user guide, Chapter 22 - OLAP allowing with OWB. This article describes a time dimension prepackaged, that you can use if necessary.

  The version 10.2 OWB introduces wizards of dimension/time with on the support of the box and is wizard driven. Version 10.2 OWB has much richer support OLAP, OWB 10.1, it was made by a best practice/bridge technique.

  See you soon
  David

• several "logical joins" between a fact table and a dimension table

  It seems that cannot create multiple "logical joins" between a fact table and the table of a dimension in OBIEE with Administration Oracle BI tool. For example, whereas a business model with a dimension table TIMES and has made the table containing the value of START_TIME and END_TIME, we want to create separate logical joins BOTH done for the START_TIMEs and the END_TIMEs? Of course, underlying foreign keys can be created, but as far as I can tell the Administration Oracle BI tool does not support this. The solution would be to reproduce the table in TIME, but it's ugly.
  I'm looking for another approach.

  Try this. Create an alias of two for the TIME dimension (beginning & end) in the physical layer, then remove foreign key to the 'Parent' time dimension. Create the foreign key in the physical layer for new aliases, then create complex joins in the MDB layer for new aliases as well. This will allow you to present the two dates within the same table in the presentation layer. Not a more elegant solution, but it works.

• Approach for the removal of the physical dimension table

  Hello

  We have a situation to decommission a physical dimension table (table 1) and we will have new values.

  The table is a source for a consistent size with 2 facts in the business model.

  Can you please let me know steps to transform the existing for the future model and changes to these model reports.

  However, I do not have the documentation of data lineage of these reports, how do I know the reports that would be affected by this change in the repository?

  Receive your answer.

  Thank you

  Shravan

  Hello

  In tools > utilities you have a tool called 'Replace logical column or Table Source Table', use this tool to keep your business model and simply replace the existing physical sources with a new one.

  Once you're done to make sure your physical objects are not used more (right click > queries about objects) and then just delete.

  Always run the overall consistency checks after each important step to ensure that your SPR is always very good.

  This can be a way to do it, another way may be to add new items to the existing MDB and then gradually remove the old or even add a new dimension of MDB and map to the same objects of presentation layer.

  Ultimately it is to you to know if the new source for your dimension will correspond to each column, so you can just replace the physical source to the columns in the Sun or it will take further work (such as a snowflake and things like that).

• error in creating time dimension OLAP in ORDM

  HI Experts

  I am trying to update the data in olap time dimension that is based in ORDM of MV and I get the error message "path of aggregation for the hierarchies of a dimension 'TIME' is incompatible," Please suggest what is at stake / soln.

  Thank you

  Prateek

  Hi David,

  Please check your hierarchies for consistency.  Because it seems that the TIME dimension is selected for the updating of the MV, the hierarchies must be consistent star.

  This means that the hierarchies must be consistent with each other in regard to members and stars according to the subject at a level.

  Compatible with each other.

  "If a dimension member appears in several hierarchies, then his descendants playing to the level of detail are exactly the same in each hierarchy." For example, if Quarter_1 consists of January, February and March at the level of detail in the Calendar hierarchy, Quarter_1 cannot be July, August and September in the Fiscal hierarchy.

  However, the members of a hierarchy can have different parents in other hierarchies. For example, these customer hierarchies are compatible if the 'Total' Member all members at the SHIP_TO level in deliveries and market Segment. »

  -helps AWM on the Details of the implementation of the Panel properties of Dimension tab

  Consistent stars with each other = in addition to being consistent with each other, such as defined above,

  "If a parent has children at the same level in multiple hierarchies, these children must be identical. For example, suppose an a H1 and H2 hierarchies dimension and level L3 appears in both entities. If X parent has children, C1, C2 and C3 at the L3 level in hierarchy H1, X also children a C1, C2 and C3 to the L3 level in hierarchy H2.

  Following customer hierarchies are consistent star only if two hierarchies, REGION has the same members (for example, Americas, Europe, Pacific), rolling among the SHIP_TO members themselves.

  Hierarchy of shipments:

  TOTAL

  REGION

  WAREHOUSE

  SHIP_TO

  Hierarchy of the country:

  TOTAL

  REGION

  SUBREGION

  DEPARTMENT / PROVINCE

  SHIP_TO ".

  -helps AWM on the Details of the implementation of the Panel properties of Dimension tab

  -Ken Chin