Independently Apply RepositoryUpgrade Schema Changes

If your DBA would like to manage RepositoryUpgrade schema changes, you can instruct RepositoryUpgrade to generate a Data Definition File which the DBA can then use to apply the schema changes external to Siebel CRM utilities.

Note: Always run the RepositoryUpgrade utility from the Siebel Server home directory ($SIEBEL_HOME).

To independently apply RepositoryUpgrade schema changes

Run RepositoryUpgrade.exe with the -6 input argument set to Y, for example, as follows:
```
RepositoryUpgrade.exe -s C:\$SIEBEL_HOME\ses\siebsrvr -t CQ203003 -u QADMIN 
-p ******** -o Q203 -d DB2390 -y QADMIN -z ******** -e Q203 -g ENU -i N -c SSEROLE 
-j Y -6 Y
```
The purpose of setting the -6 input argument to Y is to export the database schema without applying the changes.
After execution, the DBA must execute generate_schema.ddl located in the following folder to apply the physical schema changes to the database:
```
ses\siebsrvr\log\RepositoryUpgrade_<time_stamp>\Common 
```
After the DBA has successfully applied the physical schema changes, rerun RepositoryUpgrade.exe with the same parameters but with the -6 input argument set to A, for example, as follows:
```
RepositoryUpgrade.exe -s C:\$SIEBEL_HOME\ses\siebsrvr -t CQ203003 -u QADMIN 
-p ******** -o Q203 -d DB2390 -y QADMIN -z ******** -e Q203 -g ENU -i N -c SSEROLE -j Y -6 A -9 MyIntegrationWS -n N 
```
After successfully executing RepositoryUpgrade, follow the instructions in Running RepositoryUpgrade Utility to deliver the Oracle-supplied repository changes to your customer repository.