Preupgrade Tasks for a Production Test Environment Upgrade

1. Review the information in Requirements for Upgrading the Production Environment.

2. Set up the Siebel database and Siebel Servers in the production test environment.

3. Stop the Siebel Servers.

4. Close all database connections. The only database connection must be the account performing the upgrade.

   Disconnect the Siebel Server from the development environment database and connect it to the production test environment database.

5. Copy application files to the environment:

   • Reports files

   • Custom Style sheets

     See the topic on copying UI files to a new Siebel environment in the chapter in Siebel Database Upgrade Guide that describes how to perform the Siebel Repository merge.

6. About Moving the Customized Repository and Schema Definition Files.

   If you revised repository objects or schema definitions after performing your development environment upgrade, regenerate the schema.ddl and custrep.dat files before transferring them to the production test environment. For information, see Regenerating the Siebel Repository Definition Files.

7. Preparing for a Siebel Upgrade Without a Development Environment.

   If you do not have a development environment, perform this task.

8. Verify the production test database is either a copy of the current production database or has the same topology and a similar amount of data. This is important for effective performance testing of the upgrade scripts.

9. Back up the production test environment database. To do upgrade tuning, you will restore this database and perform test upgrades on it.