If you are going to upgrade to from 10g to 11g soon, you should consider the following issue :
Why Does The OBIEE 11g Consistency Check Show Errors And Warnings After An Upgrade That Did Not Occur In 10g?
The goal is to understand why an OBIEE repository (RPD) that completed an error and warning free consistency check in 10g, results in many warnings or errors when the RPD is upgraded to 11g and a consistency check is executed.
A wide range of errors and warnings have been seen. A few examples have been copied below; however, many other errors or warnings could show after the upgrade.
Error: The content filter of a source for logical table: Fact response details references multiple dimensions. [nQSError:15001] Could not load navigation space for subject area Test_Area
Error 38126 Object Type: Logical Level
Logical Level “XyZ”.”123″ .. has name with leading or trailing spaces
Error 15004 Object Type: Business Model
Internal Error: Missing functional dependency association for colum 5: X_TABLE.ROW_ID
[nQSError: 15001] Could not load navigation space for subject area Test_Area.
Error 38079 Object Type: Physical Foreign Key
Foreign Key “ABC.123″….
FKey#2 A comparison is being carried out between non-compatible types
Warning: Fact table is not joined to logical dimension table. This will cause the problems when extracting project(s).
Warning: Missing Functional dependency association for column:
Oracle’s reply was:
In general with each release, the consistency checker is enhanced to improve the consistency rules and to correct consistency checks that may not have been occurring in a previous release, but should have been. Therefore, it is common and expected for each major release upgrade that you will see additional consistency check errors or warnings that you did not see in a previous release.
The majority of consistency check errors and warnings that show in 11g but did not show in 10g are legitimate and represent a RPD design issue. The goal of these warnings and errors is to enforce RPD design rules and each one should be investigated and addressed as these could cause additional issues.
It is also advisable if you are in ‘online’ mode to check the nqserver.log from the BI Server to ensure you are correcting all the errors associated with a particular Subject Area and/or consistency check issue.
The default location will be here (assuming default instance name).
My advice is to make a good contingency plan, including roll-back possibility along with full regression testing (which can be tricky in OBIEE).