Last updated on JANUARY 31, 2017
Applies to:Business Intelligence Applications Consumer - Version 184.108.40.206.1 and later
Business Intelligence Suite Enterprise Edition - Version 220.127.116.11.151020 to 18.104.22.168.151020 [Release 11g]
Information in this document applies to any platform.
I have separate load plans for 'Student - Admissions and Recruitment' and 'Student - Records'. After a successful run of the Admission load plan, I executed the Records load plan. But later I observed that certain dimension tables which were common in both the load plans were re-loaded via full load instead of incremental.
Due to which, the surrogate keys got changed and join between fact tables (related to Admission) and common dimension (in both Admission and Records load plan) failed.
For example: Dimension table W_SIA_ACAD_CAR_D is part of both 'Admission' and 'Records' load plan. First, it got populated as a part of 'Admission' load plan and then later it got re-loaded by 'Records' load plan. Ideally, since W_ETL_LOAD_DATES had the entry for it, the Incremental load should have taken place.
Please suggest the changes (if required). Also, is it the expected behavior. In case this is the expected behavior how would I handle the different load plans for each sub-modules of Student analytics.
ETL: ODI 11g
Database: Oracle 11g
Source System: PeopleSoft 9.0
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