11g to 12c Migration Error — Oracle Analytics

Oracle Analytics Cloud and Server

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

11g to 12c Migration Error

Received Response
12
Views
2
Comments
BenS
BenS Rank 3 - Community Apprentice
edited Aug 13, 2024 6:58PM in Oracle Analytics Cloud and Server

While migrating an RPD from 11g to 12c we are receiving the following error message in one of our subject areas:

ERRORS:

Business Model CCCi Google Analytics:

[nQSError: 15048] Logical table: Movement is referenced in a cross dimensional join or has an invalid primary key definition.

[nQSError: 15001] Could not load navigation space for subject area CCCi Google Analytics.

We do not get an error message or warning in 11g.  I looked at the Business Model and do not see an issue with the tables joins or with the primary key.  Has anyone else experienced this and/or do you have any suggestions?

At a high level we are joining the Movement (dimension which has one physical table) to Target (dimension - made up of 3 physical tables) joined to the another dimension and then the fact. 

Thanks...

Answers

  • 3032275
    3032275 Rank 1 - Community Starter

    Were you able to find a resolution to this problem? I'm experiencing the same issue with my RPD in 12c. When running consistency check, I get this error:

    [nQSError: 15048] Logical table: TableName is referenced in a cross dimensional join or has an invalid primary key definition.

    [nQSError: 15001] Could not load navigation space for subject area SubjectAreaName.

    Any insights would be greatly appreciated.

  • 1032872
    1032872 Rank 2 - Community Beginner

    Hi,

    It is just how optimized the 12c RPD is , as per Oracle please check below .this should be same for 12c as well 

    Please review the tables mentioned in the error message and check the following:

Set a proper column key which should ensure that the error on these tables go away.
Ensure that there are no measures or calculated columns in your logical tables
This RPD throws lots of "invalid cross dimensional join" errors.

The solution is to delete all logical joins between pairs of tables that belong to different dimensions in your rpd
    So, check your rpd for joins between the tables mentioned and other dimensions and delete them
    These should resolve the errors

    It should be noted:
Joining two dimension tables is not a recommended design practice.
    For logical schemas in the business model, snow flaking is not recommended even in previous OBIEE versions like 11.1.1.7.1
    Refer to page 10 of the document, attached to the following note, for details:

    Hope it helps