One approach is to load the repository into the Server Db using "Repository Migration Configuration Utility" with a new name - such as "Siebel Repository - Vanilla". Then one can connect to the server db using tools and export sif files for comparisons. This works well for comparisons, but if one is wanting to check for that one "breaking change", then being able to make a quick local change to the repository to then do a compile, managing multiple local repositories is preferable.
Managing Multiple repositories: there are actually two ways of doing this:
- Maintain multiple local databases and multiple tools configurations
- Con: unable to use the Compare Objects --> Other repository command
- Pro: able to use the Compare Objects --> Other Repository command
- Pro: easy to switch between repositories in one window
Steps to extract a second repository into your local database (all steps take place within Siebel Tools):
1. Tools --> Check Out
|Check out dialog|
|Click on Get|
After clicking on get some warning dialogs appear:
These warnings can be dismissed without concern.
Finally after the Get has completed, this dialog appears that indicates you have multiple repositories including one that isn't active.
After I've retrieved the repository I'll lock it locally, make a change and cut a new SRF. If I put it on the server I'll be able to do a quick check to see if that one change was the "breaking change" and is invaluable for providing the feedback to Oracle Support.
I posted a link to this article on a LinkedIn Group and the group's created (an Oracle Support engineer) commented, pointing to the following link in Oracle support:
Multiple Repositories Causes Task Based UI (TBUI) Field To Not Show Any Values [ID 1297783.1]
Please keep that in mind when using multiple repositories - thanks Valter