Unchanged LOV Rows In Target Environment Are Getting Invalidated Or Expired After Incremental Migration (Doc ID 2785493.1)

Last updated on OCTOBER 26, 2023

Applies to:

Symptoms

The Seed Migration Priority System Preference is set to Target (default) setting to preserve the changes made on the Target environment, Production or UAT for example, in case a change is made on the lower environment.
When performing changes on the Target environment on LOV rows, the row that is modified has WS_MAX_VER set to 1 (expiration indicator), and a new row is created to hold the modified version.

As an example, a non-modified row has WS_MIN_VER=0 and WS_MAX_VER=10000, see below:

The first row is the old row that is expired by having WS_MAX_VER=1, and the new row has the subsequent WS_MIN_VER as 1, this is expected behavior.

However, when doing incremental migration some LOV not recently modified rows are unexpectedly disappearing from the UI.
By inspecting the LOV versioning WS_MAX_VER column it was noticed that the missing LOV rows had WS_MAX_VER set to 1.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Run Full migration plan to export from source and import into target environment
2. Have old Siebel Repositories on the target environment
3. Modify some LOV on the source environment that was not modified on the target environment, and prepare an incremental migration
4. Perform an incremental migration
5. Verify the modified LOV row on the target environment
6. Verify whether others non-modified LOV rows got invalidated or expired by performing a record count on Administration Data - List of Values View

Changes

Incremental migration executed containing LOV data modification

Cause

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