My Oracle Support Banner

Dimension Mapping When Non Literal Mapping Remapped Load Query Refers to Old Table (Doc ID 1321410.1)

Last updated on NOVEMBER 07, 2023

Applies to:

Oracle OLAP - Version and later
Information in this document applies to any platform.


NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

The issue occurs in Analytic Workspace Manager.
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.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.