My Oracle Support Banner

Duplicated Objects After Rebase of Grand child Workspace (Doc ID 2977355.1)

Last updated on APRIL 04, 2024

Applies to:

Siebel Tools - Version 22.7 to 23.9 [Release V17]
Information in this document applies to any platform.


On : 22.7 version, Configuration - Dev Env

Duplicate objects created after rebase of grand child workspace, following is the workspace hierarchy:

The issue happened when integration workspace int_jun2023_01 was rebased (MAIN > int_project > int_jun2023_01), after changes from another integration int_mai2023_hotfix_01 was delivered to MAIN.


The issue can be reproduced at will with the following steps:

1. create 2 integration ws under MAIN
- int_1
- int_hotfix
2. create dev workspace under int_hotfix and make following changes:

Under a common BC, for example "A Portfolio Account" create BC User Property "All Mode Sort"
deliver to int_hotfix

3. create 2 dev workspace under int_1

for one dev workspace perform same change

Under a common BC, for example "A Portfolio Account" create BC User Property "All Mode Sort"

for the other dev workspace make any dummy changes, this is required to allow int_1 to be rebased.

4. deliver the dummy changes to int_1, status changed to checkpointed
5. deliver int_hotfix to MAIN
6. rebase int_1 with MAIN
7. rebase other dev_workspace under int_1
8. after rebase see 2 duplicate All Mode Sort UP under BC "A Portfolio Account"


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

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