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

Similar Questions

• 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.

• 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

• 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!

• 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.

• 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

• related fact table column reference the same table dim

  In my analytical field, my fact table related reference column the same dim table, but in a physical schema, between two tables can have a join, so I create a copy of the Sun table, then finish the join in physics. This method can solve this issue, but not very good, someone at - it a perfect solution?

  You must create aliases for table dim, not just a copy. Why does it resolve the issue?

• Unable to limit the amount of characters using {tag_name} under webapps

  Nice day

  We have a WEB APP for and must limit the amount of characters that are displayed on the Web page under the view of LIST of WEB applications. and we tried the following:

  {tag_name, 10}

  {tag_name, 50}

  {tag_name, 400}

  {tag_name, 400}

  It does not matter what I try, it shows all the characters on the name of this WEB APP.

  for example web app name:

  Test event 1 Test event 2 Test event 3 Test Event 4 Test event 1Test event 1Test event 1 Test event 2 Test event 3 Test Event 4 Test event 1Test event 1Test event 1 Test event 2 Test 3 Test 4 Test 1Test 1 event event event event

  Is there a way to limit these, im I something wrong? @

  Hello

  {tag_name} at the point in the webapp doesn't have this feature, so you have mixed two things here, the tag name and

  {tag_description, number of characters}: Description of the element (content editor). On the 'Layout (Backup) list', you can use {tag_description, 10} to display the first 10 characters of description of the element of the webapp.

  Hope this helps

• Look for the partition for the fact table

  Oracle version: Oracle 10.2
  
  I have a table of facts with daily partitions.
  I'm insertion of test data in this table for the old date 20100101.
  
  I am able to insert that record into this table as below
  insert into fact_table values (20100101,123,456);
  
  However I noticed that the partition for this date does not exist in the table (all_tab_partitions) more I'm not able to select the data using
  
  Select * from facT_table partition (d_20100101)
  
  but I am able to extract the data using
  
  Select * from facT_table where date_id = 20100101
  
  could you get it some please let me know how to find the partition in which these data could be inserted
  and if the partition date 20100101 is not present so why put so that the date doesn't work?

  user507531 wrote:
  However I noticed that the partition for this date does not exist in the table (all_tab_partitions) more I'm not able to select the data using

  Select * from facT_table partition (d_20100101)

  Wrong approach.

  but I am able to extract the data using

  Select * from facT_table where date_id = 20100101

  Correct approach.

  could you get it some please let me know how to find the partition in which these data could be inserted
  and if the partition date 20100101 is not present so why put so that the date doesn't work?

  Who says that the date is invalid. ? It is a partition of the range - which means that each partition covers a range. And if you bothered to read in the SQL Reference Guide on how the definition of a partition of the range, you will notice that each partition is defined with the value end of the range it covers. There is no starting value - as the end of the previous partition is the "+ border +" between this and the previous partition.

  I suggest that before you use a database feature first become familiar you with it. Another evil to use and making assumptions wrong about it, more than likely outcomes.

• Adding indexes to the fact table large

  Hello
  
  Using oracle 11.20.3
  
  If made big table several billion lines and wants to add index disadvantages to only expliciltly gathering stats on the new index.
  
  Reason I just want to make the new index will be much faster.
  
  Thoughts?
  
  Thank you

  11.2 or later, his Stats are collected at the time of the creation of the index and you don't need to do it explicitly. Oracle optimizer will be bale to see this index immediately after creating indexes.

• Slow down execution SQL - extracting data from the FACT Table

  taHi,

  We have a SQL that runs slowly.

  Select / * + ALL_ROWS PARALLEL (F 8) * /.

  IA_OASIS_GRP_CAPTR_D.GRP_CAPTR_GRP_ID,

  IA_OASIS_GRP_CAPTR_D.GRP_CAPTR_BIL_UNT_ID,

  IA_OASIS_GRP_CAPTR_D.GRP_CAPTR_BNF_PKG_CD,

  IA_OASIS_GRP_CAPTR_D.GRP_CAPTR_UNDWR_CD,

  IA_OASIS_GRP_CAPTR_D.GRP_CAPTR_CAC_CD,

  IA_OASIS_GRP_CAPTR_D.GRP_CAPTR_RTMS_HLTH_COV_CD,

  IA_OASIS_GRP_CAPTR_D.GRP_CAPTR_ACTUR_RSRV_CATEG_CD,

  IA_OASIS_GRP_CAPTR_D.GRP_CAPTR_BNF_TYP_CD,

  IA_OASIS_GRP_CAPTR_D.GRP_CAPTR_GRP_BGIN_DT,

  IA_OASIS_GRP_CAPTR_D.GRP_CAPTR_GRP_END_DT,

  IA_OASIS_GRP_CAPTR_D.GRP_CAPTR_PLN_SEL_CD,

  IA_OASIS_GRP_CAPTR_D.GRP_CAPTR_SBGRP_NM,

  IA_OASIS_GRP_CAPTR_D.GRP_CAPTR_SBGRP_TYP_CD,

  IA_OASIS_GRP_CAPTR_D.GRP_CAPTR_SBGRP_TYP_DESC,

  IA_OASIS_GRP_CAPTR_D.GRP_CAPTR_COBRA_IND,

  IA_OASIS_GRP_CAPTR_D.GRP_CAPTR_SBGRP_POL_NBR,

  IA_OASIS_GRP_CAPTR_D.GRP_POL_CD,

  IA_OASIS_MBR_CAPTR_D.MBR_CAPTR_SBSCR_ALTN_ID,

  IA_OASIS_MBR_CAPTR_D.MBR_CAPTR_RLNSP_CD,

  IA_OASIS_MBR_CAPTR_D.MBR_CAPTR_GNDR_CD,

  IA_OASIS_MBR_CAPTR_D.MBR_CAPTR_BTH_DT,

  IA_OASIS_MBR_CAPTR_D.MBR_CAPTR_MBR_ID,

  IA_OASIS_MBR_CAPTR_D.MBR_CAPTR_SBSCR_SCTR_CD,

  IA_OASIS_MBR_CAPTR_D.MBR_CAPTR_SBSCR_RGN_CD,

  IA_OASIS_MBR_CAPTR_D.MBR_CAPTR_SBSCR_ZIP_CD,

  IA_OASIS_MBR_CAPTR_D.MBR_CAPTR_BDGT_RPT_CLS_CD,

  IA_OASIS_MBR_CAPTR_D.MBR_CAPTR_WORK_DEPT_CD,

  IA_OASIS_MBR_CAPTR_D.BSC_DUAL_IN_HOUSE_IND,

  IA_OASIS_MBR_CAPTR_D.MEDCR_HICN_NUM,

  IA_OASIS_CLM_SPEC_D.CLM_PRI_DIAG_CD,

  IA_OASIS_CLM_SPEC_D.CLM_PRI_DIAG_BCKWD_MAP_IND,

  IA_OASIS_CLM_SPEC_D.CLM_PRI_ICD10_DIAG_CD,

  IA_OASIS_CLM_SPEC_D.ICD_CD_SET_TYP_CD,

  IA_OASIS_CLM_SPEC_D.CLM_APG_CD,

  IA_OASIS_CLM_SPEC_D.CLM_PTNT_DRG_CD,

  IA_OASIS_CLM_SPEC_D.CLM_PROC_CD,

  IA_OASIS_CLM_SPEC_D.CLM_PROC_MOD_1_CD,

  IA_OASIS_CLM_SPEC_D.CLM_PROC_MOD_2_CD,

  IA_OASIS_CLM_SPEC_D.CLM_POS_CD,

  IA_OASIS_CLM_SPEC_D.CLM_TOS_CD,

  IA_OASIS_CLM_SPEC_D.CLM_PGM_CD,

  IA_OASIS_CLM_SPEC_D.CLM_CLS_CD,

  IA_OASIS_CLM_SPEC_D.CLM_ADMIT_TYP_CD,

  IA_OASIS_CLM_SPEC_D.CLM_BIL_PROV_PREF_STS_CD,

  IA_OASIS_CLM_SPEC_D.CLM_BIL_PROV_PRTCP_STS_CD,

  IA_OASIS_CLM_SPEC_D.CLM_ATTND_PROV_PRTCP_STS_CD,

  IA_OASIS_CLM_SPEC_D.CLM_BIL_PROV_PLN_STS_CD,

  IA_OASIS_CLM_SPEC_D.CLM_NDC,

  IA_OASIS_CLM_SPEC_D.CLM_BRND_GNRC_CD,

  IA_OASIS_CLM_SPEC_D.CLM_ACSS_PLS_OOP_IND,

  IA_OASIS_CLM_SPEC_D.CLM_BNF_COV_CD,

  IA_OASIS_CLM_SPEC_D.CLM_TYP_OF_BIL_CD,

  IA_OASIS_CLM_SPEC_D.CLM_OOA_CD,

  IA_OASIS_CLM_SPEC_D.CLM_SANCT_LAT_CALL_IND,

  IA_OASIS_CLM_SPEC_D.CLM_SANCT_DED_PNLTY_IND,

  IA_OASIS_CLM_SPEC_D.CLM_SANCT_COPAY_IND,

  IA_OASIS_CLM_SPEC_D.CLM_SANCT_PCT_COPAY_IND,

  IA_OASIS_CLM_SPEC_D.CLM_SANCT_FLAT_DLR_COPAY_IND,

  IA_OASIS_CLM_SPEC_D.CLM_SANCT_HMO_ACCUM_COPAY_IND,

  IA_OASIS_CLM_SPEC_D.CLM_BIL_ALLOW_APPL_CD,

  IA_OASIS_CLM_SPEC_D.CLM_TMLY_FIL_APPL_CD,

  IA_OASIS_CLM_SPEC_D.CLM_TPLNT_APPL_CD,

  IA_OASIS_CLM_SPEC_D.CLM_ADJ_CD,

  IA_OASIS_CLM_SPEC_D.GRP_PRVDR_TIER_CD,

  IA_OASIS_CAPITN_CLM_D.CAPITN_CLM_SS_CD_CD,

  IA_OASIS_CAPITN_CLM_D.CAPITN_CLM_HMO_COV_LVL_CD,

  IA_OASIS_CAPITN_CLM_D.CAPITN_CLM_FUND_POOL_CD,

  IA_OASIS_CAPITN_CLM_D.CAPITN_CLM_HMO_PRDCT_CD,

  IA_OASIS_CAPITN_CLM_D.CAPITN_CLM_BNF_CATEG_CD,

  IA_OASIS_CAPITN_CLM_D.CAPITN_CLM_ADJ_TYP_CD,

  IA_OASIS_CAPITN_CLM_D.CAPITN_CLM_IPA_ACSS_PLS_IND,

  IA_OASIS_CAPITN_CLM_D.CAPITN_CLM_FUND_ID,

  IA_OASIS_CAPITN_CLM_D.CAPITN_CLM_FUND_DESC,

  CLM_CLS_PLN_CAPTR_D.CLM_CLS_PLN_GRP_ID,

  CLM_CLS_PLN_CAPTR_D.CLM_CLS_PLN_CLS_ID,

  CLM_CLS_PLN_CAPTR_D.CLM_CLS_PLN_CLS_DESC,

  CLM_CLS_PLN_CAPTR_D.CLM_CLS_PLN_PLN_ID,

  CLM_CLS_PLN_CAPTR_D.CLM_CLS_PLN_PLN_DESC,

  CLM_CLS_PLN_CAPTR_D.CLM_CLS_PLN_PRDCT_CATEG_CD,

  CLM_CLS_PLN_CAPTR_D.CLM_CLS_PLN_PRDCT_CATEG_DESC,

  CLM_CLS_PLN_CAPTR_D.CLM_CLS_PLN_PRDCT_ID,

  CLM_CLS_PLN_CAPTR_D.CLM_CLS_PLN_PRDCT_DESC,

  CLM_CLS_PLN_CAPTR_D.CLM_CLS_PLN_MTL_LVL_CD,

  CLM_CLS_PLN_CAPTR_D.HIOS_PLN_ID,

  CLM_CLS_PLN_CAPTR_D.HIX_GRP_ID,

  OASIS_CLM_MBR_XREF. LGCY_SBSCR_ID,

  OASIS_CLM_MBR_XREF. LGCY_MBR_SFX_ID,

  OASIS_CLM_MBR_XREF. FACETS_SBSCR_ID,

  OASIS_CLM_MBR_XREF. FACETS_MBR_SFX_ID,

  OASIS_CLM_MBR_XREF. LGCY_CUST_ID,

  OASIS_CLM_MBR_XREF. LGCY_GRP_ID,

  OASIS_CLM_MBR_XREF. LGCY_BIL_UNT_ID,

  OASIS_CLM_MBR_XREF. FACETS_PRNT_GRP_ID,

  OASIS_CLM_MBR_XREF. FACETS_GRP_ID,

  OASIS_CLM_MBR_XREF. FACETS_CLS_ID,

  OASIS_CLM_MBR_XREF. FACETS_CONVER_MBR_EFF_DT,

  IA_OASIS_TOT_PROV_CUR_D.PROV_ID AS BEN_BILLING_PROV,

  IA_OASIS_TOT_PROV_CUR_D.PROV_ID AS BEN_ATTENDING_PROV,

  IA_OASIS_TOT_PROV_CUR_D.PROV_ID AS BEN_PCP_NUMBER,

  IA_OASIS_TOT_PROV_CUR_D.PROV_ID AS BEN_IPA_NUMBER,

  EDW. CLM_CAPITN_F.CLM_CAPITN_FRST_SVC_DT_SK,-CAL_DT Dimension is associated and had CAL_DT_SK column

  EDW. CLM_CAPITN_F.CLM_CAPITN_LST_PRCS_DT_SK,-CAL_DT Dimension is associated and had CAL_DT_SK column

  EDW. CLM_CAPITN_F.CLM_CAPITN_FRST_LOC_DT_SK,-CAL_DT Dimension is associated and had CAL_DT_SK column

  EDW. CLM_CAPITN_F.CLM_CAPITN_CHK_DT_SK,-CAL_DT Dimension is associated and had CAL_DT_SK column

  EDW. CLM_CAPITN_F.CLM_CAPITN_ADMIT_DT_SK,-CAL_DT Dimension is associated and had CAL_DT_SK column

  EDW. CLM_CAPITN_F.CLM_CAPITN_ICN,

  EDW. CLM_CAPITN_F.CLM_CAPITN_LN_NBR,

  EDW. CLM_CAPITN_F.CLM_CAPITN_PD_AMT,

  EDW. CLM_CAPITN_F.CLM_CAPITN_BIL_AMT,

  EDW. CLM_CAPITN_F.CLM_CAPITN_ALLOW_AMT,

  EDW. CLM_CAPITN_F.CLM_CAPITN_ALLOW_DY_NBR,

  EDW. CLM_CAPITN_F.CLM_CAPITN_UNT_OF_SVC_QTY,

  EDW. CLM_CAPITN_F.CLM_CAPITN_COB_SAV_AMT,

  EDW. CLM_CAPITN_F.CLM_CAPITN_COINS_AMT,

  EDW. CLM_CAPITN_F.CLM_CAPITN_RSN_CHRG_AMT,

  EDW. CLM_CAPITN_F.CLM_CAPITN_WTHLD_AMT,

  EDW. CLM_CAPITN_F.CLM_CAPITN_DED_AMT,

  EDW. CLM_CAPITN_F.CLM_CAPITN_SANCT_LAT_CALL_AMT,

  EDW. CLM_CAPITN_F.CLM_CAPITN_SANCT_DED_PNLTY_AMT,

  EDW. CLM_CAPITN_F.CLM_CAPITN_SANCT_COPAY_AMT,

  EDW. CLM_CAPITN_F.CLM_CAPITN_SANCT_PCT_COPAY_AMT,

  EDW. CLM_CAPITN_F.SANCT_FLAT_DLR_COPAY_AMT,

  EDW. CLM_CAPITN_F.SANCT_HMO_ACCUM_COPAY_AMT,

  EDW. CLM_CAPITN_F.CLM_CAPITN_TOT_NEGOT_RT_AMT,

  EDW. CLM_CAPITN_F.CLM_CAPITN_LN_NEGOT_RT_AMT,

  EDW. CLM_CAPITN_F.CLM_CAPITN_SEC_ALLOW_AMT,

  EDW. CLM_CAPITN_F.CLM_CAPITN_GATWY_ID,

  EDW. CLM_CAPITN_F.CLM_CAPITN_PROV_AGR_ID,

  EDW. CLM_CAPITN_F.CLM_CAPITN_F_SNPSHOT_MO_SK

  OF EDW. Partition CLM_CAPITN_F (JAN2012),

  EDW. IA_OASIS_GRP_CAPTR_D IA_OASIS_GRP_CAPTR_D,

  EDW. IA_OASIS_MBR_CAPTR_D IA_OASIS_MBR_CAPTR_D,

  EDW. IA_OASIS_CLM_SPEC_D IA_OASIS_CLM_SPEC_D,

  EDW. IA_OASIS_CAPITN_CLM_D IA_OASIS_CAPITN_CLM_D,

  EDW. CLM_CLS_PLN_CAPTR_D CLM_CLS_PLN_CAPTR_D,

  EDW. OASIS_CLM_MBR_XREF OASIS_CLM_MBR_XREF,

  EDW. IA_OASIS_TOT_PROV_CUR_D IA_OASIS_TOT_PROV_CUR_D

  WHERE

  EDW. CLM_CAPITN_F.CLM_CAPITN_IA_GRP_CAPTR_EDW_SK = IA_OASIS_GRP_CAPTR_D.GRP_CAPTR_EDW_SK (+) and

  EDW. CLM_CAPITN_F.CLM_CAPITN_IA_MBR_CAPTR_EDW_SK = IA_OASIS_MBR_CAPTR_D.MBR_CAPTR_EDW_SK and

  EDW. CLM_CAPITN_F.CLM_CAPITN_IA_CLM_SPEC_EDW_SK = IA_OASIS_CLM_SPEC_D.CLM_SPEC_EDW_SK and

  EDW. CLM_CAPITN_F.CLM_CAPITN_IA_CLM_EDW_SK = IA_OASIS_CAPITN_CLM_D.CLM_EDW_SK and

  EDW. CLM_CAPITN_F.CLM_CLS_PLN_CAPTR_EDW_SK = CLM_CLS_PLN_CAPTR_D.CLM_CLS_PLN_CAPTR_EDW_SK and

  EDW. CLM_CAPITN_F.MBR_XREF_SK = OASIS_CLM_MBR_XREF. MBR_XREF_SK (+) and

  EDW. CLM_CAPITN_F.CLM_CAPITN_IA_BIL_PROV_EDW_SK = IA_OASIS_TOT_PROV_CUR_D.PROV_EDW_SK and

  EDW. CLM_CAPITN_F.CLM_CAPITN_ATTND_PROV_EDW_SK = IA_OASIS_TOT_PROV_CUR_D.PROV_EDW_SK and

  EDW. CLM_CAPITN_F.CLM_CAPITN_IA_PCP_EDW_SK = IA_OASIS_TOT_PROV_CUR_D.PROV_EDW_SK and

  EDW. CLM_CAPITN_F.CLM_CAPITN_IA_IPA_PROV_EDW_SK = IA_OASIS_TOT_PROV_CUR_D.PROV_EDW_SK (+);

  --------------------------------------------------------------------------------

  Oracle Database 11 g Enterprise Edition Release 11.2.0.4.0 - 64 bit Production

  PL/SQL Release 11.2.0.4.0 - Production

  CORE Production 11.2.0.4.0

  AMT for Solaris: 11.2.0.4.0 - Production Version

  NLSRTL Version 11.2.0.4.0 - Production

  VALUE OF TYPE NAME

  ------------------------------------ ----------- ------------------------------

  OPTIMIZER_CAPTURE_SQL_PLAN_BASELINES boolean FALSE

  optimizer_dynamic_sampling integer 2

  optimizer_features_enable string 11.2.0.4

  optimizer_index_caching integer 0

  OPTIMIZER_INDEX_COST_ADJ integer 100

  the string ALL_ROWS optimizer_mode

  optimizer_secure_view_merging Boolean TRUE

  optimizer_use_invisible_indexes boolean FALSE

  optimizer_use_pending_statistics boolean FALSE

  optimizer_use_sql_plan_baselines Boolean TRUE

  Please suggest how this can be optimized.

  VALUE OF TYPE NAME

  ------------------------------------ ----------- ------------------------------

  db_file_multiblock_read_count integer 32

  VALUE OF TYPE NAME

  ------------------------------------ ----------- ------------------------------

  DB_BLOCK_SIZE integer 32768

  CURSOR_SHARING EXACT string

• Where can I get the concept of the fact Table and the Dimension table of

  Please answer me as soon as possible

  You can create the Essbase cube by creating hierarchies/models OLAP using Essbase Integration services or Essbase Studio.

  Hope this will help you to get the clear idea: All Oracle

  Kind regards

  Santy