This troubleshooting guide addresses 9 common consistency check warnings encountered when upgrading OBIEE RPDs from 10.1.3.4.1 to 11.1.1.7 using the Upgrade Assistant. It covers specific warning codes — including 39003 (missing functional dependency), 38028 (invalid data type), 39057 (unused physical table mappings), 39009 (aggregate source join errors), and more — explaining their root causes, typically tied to disabled Logical Table Sources or misaligned aggregation levels, and provides step-by-step solutions for each.
Key Takeaways
- Disabled Logical Table Sources cause cascading warnings — unused LTS from the 10g RPD get disabled during upgrade, directly triggering warnings 39003 and 38028; cleaning these up beforehand can prevent both.
- Aggregation level mismatches drive multiple errors — warnings 39009 and 39074 stem from fact and dimension tables having misaligned aggregation content levels (e.g., “Detail” vs. a higher level), requiring content tab updates to align grains.
- Missing physical joins are a recurring root cause — warnings 39008 and 39009 both point to missing or incorrect joins between Logical Table Sources and fact tables in the physical layer.
- Some warnings need manual reconfiguration, not just cleanup — issues like 39062 (wrong connection pool in init blocks) and 39076 (disabled “Use for Display” property) require explicit manual fixes rather than pre-upgrade prevention.
Common OBIEE RPD Upgrade Consistency Check Warnings
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.
- 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.
- 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.
- 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:
- Delete the unused logical tables. Delete the aggregations set for that dimension in the content tab of the fact.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
Conclusion
Most of the consistency check warnings that surface during an OBIEE 10g-to-11g RPD upgrade trace back to just two root causes: disabled Logical Table Sources left over from unused 10g objects, and mismatched aggregation content levels between fact and dimension tables. Cleaning up unused LTS objects and aligning aggregation grains before running the Upgrade Assistant can prevent several of these warnings — 39003, 38028, and 39057 — from appearing in the first place. The remaining warnings, like 39062’s connection pool misconfiguration or 39076’s disabled “Use for Display” property, require manual reconfiguration after the upgrade rather than pre-upgrade prevention. Working through these systematically, rather than fixing them one at a time as they surface in production, is what keeps an RPD upgrade from turning into a longer troubleshooting cycle than it needs to be.
FAQs: OBIEE RPD Upgrade Warnings
1) What causes warning 39003 (“could not compute a functional dependency”) during OBIEE RPD upgrade?
This warning typically occurs when a Logical Table Source (LTS) is disabled during the upgrade because it was unused in the original 10g RPD. Removing or cleaning up these disabled LTS objects before upgrading usually resolves the issue.
2) How do you fix warning 38028 (“invalid data type”) in the Business Model layer?
Warning 38028 is commonly caused by the same disabled Logical Table Source (LTS) issue that triggers warning 39003. Reviewing and removing unused or disabled LTS mappings typically resolves both warnings together.
3) Why does warning 39009 (“no fact source contains all mapped dimensions”) appear?
This warning usually indicates a mismatch in aggregation content levels between fact and dimension tables or a missing physical join between the Logical Table Source (LTS) and the fact table. Correcting the content levels and physical joins resolves the warning.
4) What causes warning 39062 during an RPD upgrade?
Warning 39062 occurs when an initialization block references an incorrect connection pool. Unlike some upgrade warnings, it requires a manual update to the initialization block’s connection pool configuration after the upgrade.
5) How do you resolve warning 39076 related to the “Use for Display” property?
This warning appears when the Use for Display property is disabled for a column that requires it. Re-enabling this property for the affected column resolves the warning.
Rajesh Kumar A
Digital Marketing Manager, Datagaps
Digital Marketing Manager at Datagaps. Drives data-driven growth through content, performance campaigns, and marketing technology.
Subrahmanya Narayana Chirravuri
Senior Director, Technology, Datagaps
Senior Director of Technology at Datagaps. Leads engineering for the ETL, BI, and data-quality validation platforms.
