My Oracle Support Banner

Business Service Corrupted After Incremental Repository Migration From Dev To Prod (Doc ID 2571506.1)

Last updated on JULY 30, 2019

Applies to:

Siebel CRM - Version 19.5 and later
Information in this document applies to any platform.

Symptoms

On : 19.5 version, System Admin

ACTUAL BEHAVIOR
---------------

Sometimes when a Business Service has been modified, delivered to the MAIN workspace, and then run the incremental repository to QA or prod, the BS doesn't work in those other environments as expected.

Testing the BS in Dev env it works fine, but it seems to be corrupted in QA and Prod environments as changes do not always reflect

EXPECTED BEHAVIOR
-----------------------
Business Service should work correctly with changes after incremental migration

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Modify business service in Development environment and test and deliver to MAIN
2. Perform incremental repository merge into QA
3. Business service does not work in QA as expected with the changes


Changes

 Changes made in Dev and delivered, but incremental migration to Prod does not carry the changes in the Business Service

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


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