Prepare the Siebel Database for Upgrade

1. Stop the Siebel Servers and the Siebel Gateway.

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

3. Copy application files to the environment, including:

   • Reports files.

4. Copy the custrep.dat and schema.ddl files to the environment. See Moving the Siebel Repository Files.

   If you have made changes to the Siebel repository since performing the development upgphys, then you must regenerate the schema.ddl and custrep.dat files. See Regenerating the Siebel Repository Definition Files.

5. Verify the test database is either a copy of the current production database or has the same topology and amount of data.

   This is important for effective upgrade tuning before performing the production upgrade.

6. Back up the test environment database. (If you backed up the database as part of an RDBMS upgrade, then ignore this step.)

   To do upgrade tuning, you will restore this database and perform test-upgrades on it.