Siebel Database Upgrade Guide > Implementing Siebel High-Availability Upgrade with Oracle GoldenGate to Upgrades to Siebel CRM Version 8.1.1.x >

Limitations When Performing a Siebel Upgrade with Oracle GoldenGate

The following limitations apply when performing a Siebel upgrade with Oracle GoldenGate software:

• You must not perform any of the following operations in the Siebel 7.8.2 database after the target database has been created when preparing to upgrade to Siebel 8.1.1.x:
  • Creating or modifying schemas, business components, applets, views, and so on in the Siebel Repository
  • Creating or modifying workflows, assignment rules, audit rules, and so on
• Siebel Enterprise Integration Manager tables are not replicated. This limitation is because all Siebel Enterprise Integration Manager operations on the source database result in changes to the application tables, and those transactions from the application tables are replicated.
• Transactions in the docking transactions log tables are not replicated. This limitation is because disconnected users are expected to get a newly installed local database from the upgraded Siebel database following the completed upgrade when all the Siebel CRM version 7.8.2 transactions have been applied to the 8.1.1.x database by Oracle GoldenGate.
• Log files and tables with data that are temporary are not replicated.
• For LOV-based column values that are used in the upgrade steps, the Oracle GoldenGate Replicat parameter file contains values in English (ENU) from the S_LST_OF_VAL table. For customers whose primary language is not English, some of these steps must be changed to use values in the customer's installed language.
• Using the OBEY files to define the Extract, pump, and Replicat processes and using the GGSCI command does not start those processes. You must run the start command from within GoldenGate secure command interface (GGSCI) when you are ready to start the processes.