Siebel Database Upgrade Guide > Implementing Siebel High-Availability Upgrade Using Oracle GoldenGate to Upgrade to the Current Release >

Example of Implementing a Siebel High-Availability Upgrade

This topic provides an example of how to implement a Siebel high-availability upgrade, using Oracle GoldenGate software:

1. Install Oracle GoldenGate software on the source and target servers, and configure them.

   For more information on Oracle GoldenGate, see Oracle Technology Network (http://www.oracle.com/technetwork/indexes/documentation/index.html).

2. Install the current release of Siebel CRM, including the Siebel Server, Siebel Database Server, and Siebel Gateway Name Server.
3. From the installation of the current release of Siebel CRM, extract the Oracle GoldenGate files from the installed ZIP or tar file as described in Extracting Oracle GoldenGate Files, and copy the extracted files to the dirprm directory of the Oracle GoldenGate installation.
4. Make all the required changes to those files. Provide database login and password information, as well as table owner, target server name, and so on. Create the required directories under the dirrpt directory.
5. Customize the Oracle GoldenGate parameter files to include any custom tables that you have previously created (X_*), including any logic required for those tables.
6. Using the Oracle GoldenGate executable defgen and the modified parameter file d_782sia.prm, generate the schema definitions for Siebel 7.8.2 tables.

   This parameter file defines the output file as Siebel782.dat. This file is generated under the dirdat directory. Copy this file to the target server's dirdat directory.

7. Create a new database instance on the target server to host the Siebel 7.8.2 database that you will upgrade.
8. Ensure that all disconnected users synchronize their local database with the server database.
9. Bring the production database to an idle state by disconnecting all users and stopping all Siebel Server processes.
10. Take a full dump of the database. Using the dump file, create a new copy of the database in the target server.

    This database will be upgraded to the current release of Siebel CRM.

11. Start the Oracle GoldenGate Extract and pump process on the source server to capture all new transactions in the Siebel 7.8.2 database. Start the Siebel application and allow users to connect and continue to use the application.
12. Ensure that the Oracle GoldenGate processes are running and extract files are created on the source server and are created in the target server by the Oracle GoldenGate pump process.
13. Start the standard Siebel upgrade process on the target server to upgrade the Siebel 7.8.2 database and Siebel Business Applications to the current release of Siebel CRM.
14. Monitor the Oracle GoldenGate Extract process and pump process to ensure that they are capturing data from the source server. Move the data to the target server continuously.
15. After the upgrade to Siebel 8.1.1.x is complete and the upgrade is validated, start the Oracle GoldenGate Replicat process on the target server to apply the captured transactions in the extract files to the upgraded database for the current release of Siebel CRM.
16. After the Oracle GoldenGate Replicat process has retrieved all the transactions in the source Siebel 7.8.2 database, all disconnected users must synchronize their local database with the server database and stop using the Siebel application in disconnected mode.
17. Bring the production database to an idle state again, by disconnecting all users and stopping all Siebel Server processes.
18. Check that the last few identified transactions on the source database are reflected in the upgraded database for the current release of Siebel CRM. Start all the required Siebel server processes and start the Siebel application. The upgraded Siebel CRM database and Siebel applications are now ready for use.
19. Migrate all users so that they can start using the new upgraded database and Siebel applications for the current release of Siebel CRM. Shut down the Siebel 7.8.2 database, and stop the Oracle GoldenGate Extract, pump, and Replicat processes.
20. If some users are disconnected (Siebel Mobile Web Client users), then create a new version of the local database for these users, for the current release of Siebel CRM. After those users initialize their local database with the new local database extract, they can start using the application in disconnected mode.

    The upgrade of Siebel 7.8.2.x to the current release of Siebel CRM, using Oracle GoldenGate with minimum downtime of the Siebel application (version 7.8.2), is now complete.