Step 6: Implement New and Enhanced 11g Functionality

Planning to Upgrade from Oracle BI 10g to BI 11g 1-11 information, see Section 1.2.3, BI Repository Metadata: Highlighted New 11g Functionality to Leverage.

1.2.1 Repository Metadata: Major Upgrade Considerations

This section describes upgrade considerations related to Oracle BI repository metadata. This section contains the following topics: ■ Section 1.2.1.1, Enhanced Repository Consistency Checking ■ Section 1.2.1.2, Oracle BI Server Query Changes

1.2.1.1 Enhanced Repository Consistency Checking

In 10g, there were several modeling constructs allowed by the consistency checker that resulted in unexpected query behavior at runtime, or inconsistencies at MUD checkout time. In 11g, the Consistency Check Manager addresses these issues by enforcing additional validation rules to help ensure that the repository is consistent. In addition, some rules that existed in previous releases might now be displayed during consistency checks. The following table summarizes these rules: Validation Rule Example Type Description [14031] The content filter of a source for logical table: FACT_TABLE_ NAME references multiple dimensions. Error The given logical table has a logical table source with a WHERE clause filter that references multiple dimensions. A WHERE clause with multiple dimensions is invalid. [38126] Logical Table Technology - WFA.Fact WFA WO has name with leading or trailing spaces. Error Identifies an object with leading or trailing spaces in the object name. Repository objects can no longer have leading or trailing spaces in their names. Leading and trailing spaces in object names can cause query and reporting issues. [38012] Logical column DIM_Start_ Date.YEAR_QUARTER_NBR does not have a physical data type mapping, nor is it a derived column. [38001] Logical column DIM_Start_ Date.YEAR_QUARTER_NBR has no physical data source mapping. Error Logical columns that are not mapped to any logical table source are reported as consistency errors, because the logical table source mappings are invalid and would cause queries to fail. Both of the given validation rules are related to the same issue. [39028] The features in Database MyDB do not match the defaults. This can cause query problems. Warning Some database feature defaults were changed in Oracle BI EE 11g. Unless you have specific customizations to your feature set, it is recommended that you reset the database features to the new defaults. [39003] Missing functional dependency association for column: DIM_Offer_End_Date.CREATE_DT. Warning This warning indicates that the given column is only mapped to logical table sources that are disabled. The warning brings this issue to the repository developers attention in case the default behavior is not desired. [39055] Fact table HR.FACT - HC Budget is not joined to tables in logical dimension HR.DIM - HR EmployeeDim. This will cause problems when extracting projects. Warning This warning indicates that there is a physical join between the given fact and dimension sources, but there is not a corresponding logical join between the fact table and the dimension table.