Bookshelf Home | Contents | Index | PDF |
Siebel Database Upgrade Guide > Performing the Siebel Repository Merge > Preparing for the Repository MergeAll upgrades. This topic applies to all upgrades. Environments: Development environment only. This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade. 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 may 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 may go undetected. If the merge fails, you must restore the database environment to its pre-merge state and run the merge again. Additionally, it is recommended, as another precaution, that you export the New Customer Repository to preserve existing workflows. Recovering from a Failed MergeIt is recommended that you perform the following two tasks to preserve the pre-merge environment in the event of a failed merge.
|
Siebel Database Upgrade Guide | Copyright © 2008, Oracle. All rights reserved. | |