Last updated on DECEMBER 01, 2016

Applies to:

Symptoms

On : 8.1.1.11 SIA [23030] version, System Admin

ACTUAL BEHAVIOR
---------------
If 2 repositories are loaded into the dev or test environment database then

a) site map-> administration - application -> Manifest Administration shows records for both repositories, making administration confusing.
b) if the repository is deleted from within Siebel Tools, the manifest data is not deleted and remains as orphan data in tables such as S_UI_EXPR, S_UI_FILE,S_UI_OBJECT,S_UI_OBJ_EXPR,S_UI_OBJ_EXP_FL

EXPECTED BEHAVIOR
-----------------------
a) site map-> administration - application -> Manifest Administration should offer a way to differentiate the records belonging to different repositories
b) delete repository should also delete manifest related data.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Start -> Siebel Enterprise -> Database Server Configuration and follow the
wizard to import a repository
2. site map-> administration - application -> Manifest Administration.
Sort by name and notice there are duplicates.
3. Get the row ids of a few records with apparently same data (e.g same name) and
log in to SQLPLus and run a query and notice they belong to different repositories
4. in tools , delete one of the repositories.
5. double check the records were NOT deleted in site map-> administration - application -> Manifest Administration. or re-run your SQL query to confirm data pointing to the deleted repository is still available in the manifest tables.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, administration of manifest related data gets confusing in the presence of multiple repositories.

Cause