Adding indexes to the fact table large

Similar Questions

• Limit the rows of the fact Table by using a table Dim - 10 g

  Hello
  
  I'm having some trouble trying to restrict the result to a fact table using a Dim picture (assume that the example below).
  
  -----DIM A-------------------------------FACT B--------------
  ID-Code - Id_Date - Id_Dim - value
  1---ABCD---01-01-2011---1---10
  2---XYZ---02-01-2011---2---20
  3---RST---03-01-2011---1---30
  ----------------------------------04-01-2011-------3------------40
  
  I want to show only the rows where Dim.Code = 'ABCD '. I know on the MDB, I choose the LTS of the fact table and on the content tab, on where clause insert: Dim.Id = 1, but I don't want to be limited by Dim.Id, I want to limit by Dim.Code and who cannot do this way.
  
  What I did on the LTS of the fact table, on the tab general got the fact Table on the mapped tables and I added the table Dim doing a join internal between the fact Table and the Table Dim. This way when I go to the content tab, I can do: Dim.Code = "ABCD" because the tables are attached now.
  
  Is it bad to do? Is there a better way to solve this problem?
  
  Before ask you I can't do it directly on the table of the Sun because this chart Dim is used in other Tables of facts. Creates an alias for the Table Dim and limit there the way forward?
  
  I hope that I was clear, thank you

  The way you do it is correct. If you have only one or two measures, then you could also do it using logical columns with the filter function.

  table of facts, for example:
  value = (unfiltered, do not show in the layer close)
  Value of ABCD = (filter (value using dim code = "ABCD"))

  Then you can expand this without having to create a table of facts for each variation:
  value = (unfiltered, do not show in the layer close)
  Value of ABCD = (filter (value using dim code = "ABCD"))
  Value of XYZ = (filter (value using dim code = "XYZ"))
  First value = (filter (value using dim code = "RST"))

  etc. Contrary to the statements of case, it pushes the return filter logic to the database (you get a where clause clause). Kind regards

  Robert

• Updating the fact table

  Hello
  
  I'm just starting with data warehousing. I need to design a warehouse that will record sales on a daily basis. This seems pretty much standard task. However, in my case an order may change several times before it is completed. I intend to handle similar to evolution slow type dimensions 2, adding the date effective date/expiration (Ref. for the dimension date) to the fact table. When an order is updated would be brand in the current record as having expired and I add a new. I can not just replace or delete the previous record, because it would make incorrect historical information. I also really like the idea of storing Let's say not historical orders and periodic snapshots separately - it seems too complicated.
  I thought about the partitioning of the fact table so that only the records in the most recent partition would be updated. In addition, I would create a view for users "where"Date of Expiration"=" N/a"" to work with the current information.
  I'm sure this is a common situation in the data warehouse, however, I couldn't find any useful information on the face. I'm on the right track? OWB does support this kind of functionality (find existing facts by a criterion-> update-> load records new) well?
  
  Thank you.

  Still a 'RESERVATION_TRANSACTION' which provides for a new record of fact related to the current three-dimensional image would be better than a fact of type 2. This way you have added facts (by type of operation - new/changed/cancelled/come/infiltrated etc., by time period, etc.) and the timestamps in place for their appearance takes place. But you do NOT want hunting through historic images in the table of facts at least quite inevitable - which I think is the case here.

  Just my opinion anyway.

  Good luck with that!

• Cannot create indexes on the flow table

  Hello

  I'm new to ODI.

  The problem is that during the execution of an interface, I get the error of the "IKM Oracle Dimension to slow variation"

  The command in step "Create unique index on the flow table:

  creating index < % = odiRef.getTable ("L", "INT_NAME", "A") % > idx

  on < % = odiRef.getTable ("L", "INT_NAME", "A") % > (< % = odiRef.getColList ("", "[column]", ",", "", "SCD_NK") % >)

  < % = odiRef.getUserExit ("FLOW_TABLE_OPTIONS") % >

  generate the following statement which lacks the name of the column between the (_)

  Create index I$ _MYTABLE_idx

  I have $_MYTABLE)

  NOLOGGING

  The result is that the interface fails with the error 936: 42000: java.sql.SQLException: ORA-00936: lack of expression caused by the previous command wrong.

  Please, can you help me?

  Thank you very much

  Angelo

  Hello

  I'm really really sorry! I just realized that you are working on the SCD. Basically, you are looking for all the column mapped as SCD_NK (key to slowly change natural Dimensions) insofar as shown here

  Substitution QAnywhere

  IF you need to read this

  SCD Type 2 - ODIExperts.com

  Let me know.

• Why do you say that the FACT table is off standard? I just don't understand.

  Why do you say that the FACT table is off standard? I just don't understand.
  
  According to my understanding, normalization is the process of getting rid of redundant. So, the fact table have redundant. So how is it that they say it is off standard.
  
  What dimension tables? They are also OF normailzed?
  
  Can you explain in words simple pls.

  Fact tables are generally standardized.

  Dimensions are usually denormalised because they often contain descriptive and rollup/hierarchical data repeated. Snow flake off a dimension will normalize the data.

  See you soon
  If

• Two filters in two dimensions without constraining the fact table

  Hi all
  
  does anyone know how to avoid the factual constraint when you create a report with two filters on different dimensions?
  
  I have a fact table big with more than 10 million lines. In the starmodel is the customer of the dimension and the products. I create a filter on the customer atrribute 'Status' and set to 'active '. Now I add the "Product Type" column of the dimension 'Product' in the filter section. When I want to choose a value OBIEE executes a select statement in the fact table. So I have to wait very long to select a value. Is it possible to say OBIEE only to select the dimension table without joining the fact table?
  
  Thank you much in advance.
  
  Kind regards
  Stefan

  Use is implied.

  Create a table of facts of the DUMMY and make also implied made for this dimension column. It will solve the problem.
  http://obiee11gqna.blogspot.com/2011/01/implicit-fact-column-in-OBIEE.html

  Published by: MK on January 17, 2012 07:08

  Published by: MK on January 17, 2012 07:08

• Dependence on the data cube on the fact tables?

  Hello
  
  We have a cube that is built based on a table of facts (with prior calculation of 35%)
  
  The fact table has approximately 400 000 records.
  
  Now I don't want to disturb my cubes but wants to move forward and still changing the data in the fact table, which could include the removal of thousands of records.
  
  SO my question here is how dependent are cube on the fact table data.
  
  The cube stores all the data? Can I go ahead and even to truncate (not drop) the fact table?

  The contents of the cube is not changed until it is built again. So, if you do the following

  (A) complete the table of facts
  (B) create the cube fact table
  (C) Truncate table facts

  Then your cube should always contain the data, and you can question him. The content will change only when you

  (D) create the cube again. At this point my previous answer comes into play.

• How to create indexes on the nested table.

  Hi all
  I held the syntax to create indexes on the nested table.
  
  I found below synta but when I try it with my table it gives me error
  
  CREATE UNIQUE INDEX indx_name
  ON nestedtablestore (NESTED_TABLE_ID, id);
  
  What is here NESTED_TABLE_ID & ID

  They are virtual your nested table

  Here is an example.

  create or replace type obj as object (no integer, address varchar2(100))
  /
  create or replace type tbl as table of obj
  /
  create table test_tbl (id integer, name varchar2(100), address tbl) nested table address store as address_nt
  /
  create unique index address_no_idx on address_nt (no, address)
  /
  

  Published by: Karthick_Arp on November 23, 2010 01:41

• Index on the primary table becomes UNUSABLE after Exchange of partition

  Hello!
  
  I am the scene changes to partition and somehow, I see that the partition that I Exchange eventually becomes "UNUSABLE".
  
  
  The steps that I'm following:
  
  1. creating the temporary table:
  
  CREATE TABLE TEMP_TKTHEADER
  AS SELECT * FROM T3TKTHEADER
  WHERE 1 = 2
  
  2. replacement of the partition
  
  ALTER TABLE T3TKTHEADER
  PART08Q1Q2 PARTITION EXCHANGE
  WITH TABLE TEMP_TKTHEADER
  
  
  After the Exchange is carried out and I ask the stats of the index on the primary table (T3TKTHEADER as in this case):
  
  INDEX_NAME NOM_PARTITION STATUS
  ----------------------------------------------------------------------------------------------
  XTKTHDR1 PART08Q1Q2 UNUSABLE
  XTKTHDR10 PART08Q1Q2 UNUSABLE
  XTKTHDR11 PART08Q1Q2 UNUSABLE
  XTKTHDR12 PART08Q1Q2 UNUSABLE
  XTKTHDR13 PART08Q1Q2 UNUSABLE
  XTKTHDR14 PART08Q1Q2 UNUSABLE
  XTKTHDR2 PART08Q1Q2 UNUSABLE
  XTKTHDR3 PART08Q1Q2 UNUSABLE
  XTKTHDR4 PART08Q1Q2 UNUSABLE
  XTKTHDR5 PART08Q1Q2 UNUSABLE
  XTKTHDR6 PART08Q1Q2 UNUSABLE
  XTKTHDR7 PART08Q1Q2 UNUSABLE
  XTKTHDR8 PART08Q1Q2 UNUSABLE
  XTKTHDR9 PART08Q1Q2 UNUSABLE
  
  
  This is normal behavior!
  Is not swap Partition just supposed to change the pointer to the partition of the temporary table data and leave the rest of the table intact!
  
  Thank you
  AB007

  Dear AB007,

  Please see subpart of swap partition. I assumed that the version of your database is GR 11, 2;

  http://download.Oracle.com/docs/CD/E11882_01/server.112/e10592/statements_3001.htm#BABHHAHF

  INCLUDING | EXCLUDING INDEXES Specify INCLUDING INDEXES  if you want local index partitions or subpartitions to be exchanged with the corresponding table index (for a nonpartitioned table) or local indexes (for a hash-partitioned table).
  Specify EXCLUDING INDEXES  if you want all index partitions or subpartitions corresponding to the partition and all the regular indexes and index partitions on the exchanged table to be marked UNUSABLE.
  

  Hope that helps.

  Ogan

• Understand the fact Tables

  Hello
  
  I'm new to OBIEE, I created several dimensions but am a bit confused with the measures, and the fact tables. I have a table of facts already populated in the database that contains the dimension by each dimension keys, 3 measures. There are a few additional columns (agreement_code, agreement_type, schedule_number). These additional columns do not bind to the dimensions. These columns must be included in the table of facts within the layer of OBIEE BM or could be deleted. My question is the fact table should contain only measures or can it be other columns not aggregated.
  
  Thank you

  Hello

  If you take certain columns actually that depends on the requirements of the company. If you think that these columns will be used in the reports, then you should take these columns in the data warehouse.

  Should not that only columns of measure should go in fact. You can take these columns not aggregated in your fact. But as a best practice, always try to move the columns not aggregated to your dimension. If you can't, as a last resort to it in fact.

  Thank you
  Sandeep

• Can date in the fact table as a measure?

  Dear all,
  
  I need to migrate a form of dimensional model database relational model. IT sort of a human resources database. I don't know WHAT should I keep in the fact table. Ago only dates, such as the date, the employee joined the institution and the date that he will leave. Most of the other fields are not digital. much is also not digital, but we can calculate the duration, the employee worked from these dates.
  
  What do you suggest me?

  Hello.

  I suspect that you can add as a column to a minimum as calculation:
  case that no employee.leave_date is zero then (employee.start_leave - employee.start_date) or null;

  which returns the work period.

  Alex.

  Published by: Alex B 07/29/2009 16:12

• How to remove the fact Table

  Hi all
  
  If I have to restart my fact table on the same day, more than once a day, and he had already stored in it, I want to remove these lines and reload the fact with the current date. I want to create a procedure and include it in the package, the process must check the current_timestamp and if the lines with the date and if there is then it should delete it. Please let me know how I can do this. I am running SQL Server - 2008.
  
  Thanks for your time and your help.

  You should have to date in your primary key (ex: in a varchar as YYYYMMDD format).

  Then you have 2 ways to implement:

  create an ODI procedure that will remove all data where this date = today. Perform this procedure before your interface.
  * or change your IKM: Add a step that will erase the data in the target table if date = today.

• Create ctxsys.ctxcat index in the object Table

  What I'm trying to do is to create an index of type ctxsys.ctxcat on 'col3 '. But this 'col3' is not a 'TABLE', but in an object, as follows:
  
  CREATE OR REPLACE TYPE TestObj AS OBJECT
  (
  col1 varchar2 (10),
  col2 varchar2 (10),
  COL3 varchar2 (10),
  COL4 varchar2 (10)
  );
  
  
  CREATE OR REPLACE TYPE AS THE TestObj TABLE TestTable;
  
  Now, how can I create an index of type ctxsys.ctxcat on 'col3 '?
  
  create index test_ind on TestTable (col3) indextype is ctxsys.ctxcat;?
  
  
  Thank you for helping.
  
  
  Scott

  You cannot index a user-defined data type. Indexes are used for persistent storage of persistent objects.

  What I suspect you really want is an associative array or an array indexed by integer binary. Demos here:

  http://www.morganslibrary.org/reference/arrays.html

• the fact table measures

  Hello
  
  Can I have measurements of the fact in the business layer table?
  I use obiee 11g.
  
  as if I had a fact table where I have a user I applied the rule of distinct count aggregation.
  Now, I would like to add a lower function as count (distinct (lower (username)).
  But he becomes as a measure with fx with the name and not the usual yellow color.
  
  Wanted to know if its good practices?
  
  Thank you

  Hello

  You have two columns of measure.

  with the lower function
  other no less function.

  For your information: separate are case-sensitive. It will show the difference between 'A' and 'a '.

  Kind regards
  Lacouture.

  Published by: Rey July 7, 2011 14:41

• Adding data to the existing Table

  Hello..
  
  IAM, try to import the oracle dump file. but the tables in dump files already exist in my database. How can I add data to existing tables... pls suggest me.
  
  Thank you.

  You don't say what you use the tool...

  If you use the traditional import utility (imp) then you can tell him to ignore the fact that there is already a table: IGNORE = Y.

  And I can't import datapump has similar features.