Siebel Database Upgrade Guide > Upgrading the Siebel Database >
Regenerating SQL Files for a Siebel Upgrade
Upgrades from: All Supported Siebel releases.
Environments: Development and production test.
If you enter incorrect information in the Database Server Configuration Utilities, the SQL files they generate will be incorrect and must not be used. You must run the Utilities again, enter the correct information, and regenerate the SQL files.
For example, you are upgrading a non-Unicode database. You run the Database Server Configuration Utilities and enter that you are upgrading a Unicode database. The SQL that the utility generates will be incorrect and cannot be used. You must regenerate the SQL files.
When the Database Server Configuration Utilities generate SQL files, they create a lock file that prevents regenerating the SQL files. To regenerate the SQL files, you must delete the lock file.
Regenerating SQL files with the Database Server Configuration Utilities
- Verify that the SQL files must be regenerated.
Typically this is caused by entering incorrect information in the Database Server Configuration Utilities. If you are unsure if the files must be regenerated, create a service request (SR) on OracleMetalink 3, or contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application Expert Services.
- Navigate to
locate the file
This is the lock file that prevents the utility from regenerating the SQL files.
- Delete the
- Rerun the Database Server Configuration Utilities.