OBIEE 12c: Modifying an RPD under Source Control Management Updates Many XML Files and Causes Missing Navigation Space Errors
Last updated on AUGUST 29, 2017
Applies to:Business Intelligence Suite Enterprise Edition - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
An OBIEE 188.8.131.52.x environment is being migrated to 184.108.40.206.0 (on Linux).
In 11g, modifications to the RPD were done under Source Control Management (SCM) as per: http://www.oracle.com/technetwork/articles/bi/screen-config-obi11g-1844060.html
After the 11g RPD was migrated to 12c, the (migrated) RPD is being modified under the same SCM process using the client-side Admin Tool 220.127.116.11.0 (on MS Windows).
Two issues are encountered when using SCM in OBIEE 12c:
1. The Commit step causes many XML files - for objects that are not related to the actual change - to be updated (content is removed).
For example: Add one new static repository variable to the SampleApp.rpd and see the Commit step will update 75+ XML files related to Logical Tables etc.
2. Reports fail when the modified Repository is deployed / uploaded to the server-side OBIS.
For example: Save the MDS XML Repository back to a binary Repository, perform a global Consistency Check (in the Admin Tool) and see no Errors are reported.
Upload the RPD to the Linux OBIEE server, and see reports now fail with the "[nQSError: 15002] Missing navigation space for subject area XXX" error.
Additionally, "[nQSError: 42004] Logical element XXX has no physical data link" errors are observed in the OBIS logs.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms