Siebel Anywhere Upgrade Components Skipped During Synchronization

(Doc ID 2238738.1)

Last updated on MARCH 03, 2017

Applies to:

Siebel Anywhere - Version 8.1.1.14 [IP2014] and later
Information in this document applies to any platform.

Symptoms

Upgrade kits that are required and dependent are skipped.

Scenario:

Siebel Client Customer Revisions kits 1-9 created, activated, applied and required with either 0 or null, a client with Current Version = 0 will pull all 9 upgrade kits.

For Kit 1:
1. click Autocreate
2. choose Siebel Client Customer Revisions
3. choose a file
4. set Minimum Old Version = 0, Maximum Old Version = 0, New Version = 1
5. click Activate
6. click Apply Versions
7. click Require Upgrade Kit

For Kits 2 - 9:

1. click Autocreate
2. choose Siebel Client Customer Revisions
3. choose a file
4. set Minimum Old Version = 0, Maximum Old Version = 1, New Version = 2
5. click Activate
6. click Apply Versions
7. click Require Upgrade Kit

However, if you have any kit with version 10 and higher, the same set of kits, 2-9 are not pulled.

The business impact is that clients will not pull upgrade kits 2-9 as expected which could contain key files and updates needed. This could also occur unbeknownst to the Siebel Anywhere Administrator and causes data integrity for the clients in terms of what software is installed.

Cause

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