My Oracle Support Banner

OBIA 12c: Migrating Customizations Between Environments Result in Mismatched Internal IDs in Target Environment (Doc ID 2891413.1)

Last updated on AUGUST 26, 2022

Applies to:

Business Intelligence Applications Consumer - Version 11.1.1.10.3 - Base Install - No OBIA Patch-Bundle or Patch-Set Applied and later
Information in this document applies to any platform.

Symptoms

Migrated the code from DEV to QA along with all the dependent objects by following (Doc ID 2688437.1).

On running the load plan on QA, realized that the steps where datastore's internal id is being used as input parameter, fails. On checking, noticed that the custom datastores' internal id is different to internal id of DEV.

In the Smart Import response file found that the original object import id and duplicated object import id has the same new value and not the original DEV one. 

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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