Bookshelf Home | Contents | Index | PDF |
Siebel Database Upgrade Guide > Performing the Siebel Repository Merge > Preparing for the Repository MergeEnvironments: Development environment only. The process of merging repositories to create a final customized repository used in the upgrade is time-intensive and resource-intensive. As a result, a merge might fail due to environmental factors, such as space constraints. When this happens, the merge process continues, even if there is a fatal database error, and the errors might go undetected. If the merge fails, then you must restore the database environment to its premerge state and run the repository merge again. Additionally, it is recommended, as another precaution, that you export the New Customer Repository to preserve any existing workflows. Recovering from a Failed MergeIt is recommended that you perform the following two tasks to preserve the premerge environment in the event of a failed merge.
|
Siebel Database Upgrade Guide | Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |