Last updated on MAY 12, 2011
Applies to:Oracle OLAP - Version: 126.96.36.199
Information in this document applies to any platform.
If an attribute of a dimension is mapped to a literal and other attributes of it are mapped to a source table, and later the source table is replaced by an other source table, then the previous old source table is still used in the SQLs generated for loading the dimension, what's more the old and new source tables appear in loading queries without join condition for which the optimizer generates Cartesian product in the execution plan, which can be suboptimal.
Note the dimension is no longer intended to be mapped to the old source table.
The issue only occurs if attribute is mapped to literal, if all the attributes are mapped to columns of tables/views, then all the load SQLs generated are based on the new source table only after remapping the dimension to the new source table.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms