Bookshelf Home | Contents | Index | PDF |
Siebel Database Upgrade Guide for DB2 for z/OS > Performing the Siebel Repository Merge > About Backing Up the New Customer Repository or Database SchemaEnvironments: 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 the final customized repository used in the upgrade is time-intensive and resource-intensive. As a result, a merge might sometimes fail because of environmental factors, for example, space constraints. When this happens, the merge process continues, even if there is a fatal database error, and the errors might not be detected for some time. If the merge fails, you must restore the database environment to its premerge state and run the merge again. There are two methods you can use to preserve the premerge environment so that you can restart the merge again if necessary:
|
Siebel Database Upgrade Guide for DB2 for z/OS | Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |