Saturday, 02 February 2013 19:40

OBIEE 11g upgrade : Fixing consistency check errors during RPD upgrade

Written by
Rate this item
(1 Vote)

This article walks you through the consistency check warnings found in the BI Apps RPD after running the 11.1.1.7 upgrade assistant on an 10.1.3.4.1 RPD.

1.Warning [39003] – Missing functional dependency association of a column.
Any Logical Table Source that has been unused in 10g is disabled during the upgrade. Cleaning up such tables before the upgrade might help avoid this warning.

Solution: Enable all the Logical Table Sources that are disabled during the upgrade.

 

2.Warning [38028] – column does not have valid data type.
I encountered this error because of the disabled Logical Table Sources (from warning 39003). The datatype for all the columns belonging to the disabled LTS were set to null.

Solution: Fixing the warning 39003 should fix this error, otherwise check to see if the column has a valid datatype.

 

3.Warning [39057] – There are physical tables mapped in Logical Table Sources that are not used in any column mappings or expressions.

Solution: The recommendations to workaround this issue:
   a. Delete the unused logical tables. Delete the aggregations set for that dimension in the content tab of the fact.
   b. Create dummy mapping columns from that table.

         Metalink note: Warning 39057 [ID 1386095.1]
         Cleaning up any unused logical tables pre upgrade, might help from running into this warnings.

 

4.Warning [39009] – Logical fact table FACTS have an aggregate source that does not join to a Dimension: source at the proper level of detail.

Solution: Make sure there is a physical join between the fact Logical Table Source and dimension’s Logical Table Source. Make sure the aggregation levels are set at the same grain for both dimension and fact on the content tab.

5.Warning [39076] – Logical level does not have any key with Use for Display property on. 
‘Use for Display’ option is turned off during the upgrade.

Solution: Turn on the ‘Use for Display’ option for all the keys specified.

 

6.Warning [39008] – Logical dimension table has a source that does not join to any fact source.
The Logical levels on the content tab for LTS and Fact table are not set properly.
The join between the LTS and Fact table is missing in the physical layer.

Solution: Fix the Logical levels on the content tab for Logical Table Sources and Fact table. Both should be set to the same Aggregation level.
Check for any missing foreign key joins between LTS and Fact table in physical layer.

 

7.Warning [39062] – Initialization block uses Connection Pool which is used for report queries.  This may impact query performance.

Solution: Update the initialization blocks to use the right connection pool. If a connection pool for the init block does not exist, create a new connection pool so that it does not use the connection pool specified for the queries.

 

8.Warning [39028] – The features in database does not match the defaults. This may cause query problems.

Solution: Make sure all the required database features are turned on.

 

9.Warning [39074] – Logical dimension table has a source with aggregation content set to level ‘Detail’. The same dimension has aggregation content set in fact source to a higher level.

Solution: The aggregation levels are set at different grain for fact dimension tables. Update the content tab for dimension and fact to be at the same level.
Read 8827 times Last modified on Tuesday, 02 February 2016 20:44