Independently Apply RepositoryUpdate Schema Changes

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

To independently apply RepositoryUpdate schema changes

1. Run RepositoryUpdate with the -6 argument set to Y. This will generate the schema DDL file containing the required database changes, but will not apply them.

   Oracle example:

   RepositoryUpdate.exe -s C:\$SIEBEL_HOME -t SIEBEL -u SIEBEL -p ******** -o SIEBEL
   -d ORACLE -y SADMIN -z ******** -b SEBL_DATA -x SEBL_INDX -c SSE_ROLE -6 Y -9 int_future_release_X
   

   MSSQL example:

   RepositoryUpdate.exe -s C:\$SIEBEL_HOME -t dbo -u SIEBEL -p ******** -o Siebel_DSN
   -d MSSQL -y SADMIN -z ******** -c SSE_ROLE -6 Y -9 int_future_release_X
   

   DB2 UDB example:

   
   RepositoryUpdate.exe -s C:\$SIEBEL_HOME -t SIEBEL -u SIEBEL -p ******** -o DB2KLXXX
   -d DB2UDB -y SADMIN -z ******** -b TBS_4K -x TBS_4K -k TBS_16K -v TBS_32K -c SSE_ROLE -6 Y -9 int_future_release_X
   

   DB2390 example:

   RepositoryUpdate.exe -s C:\$SIEBEL_HOME -t CQ10D0XX -u QADMIN -p XXXXX -o Q10D
   -d DB2390 -y QADMIN -z XXXXX -c SSEROLE -b SIEBTS00 -2 BP1 -5 BP8K1 -f BP16K1 -7 BP32K1
   -8 D003 -a ASCII -j BP2 -e SYSDEFLT -h SYSDEFLT -6 Y -9 int_future_release_X
   

2. After execution, provide the generate_schema.ddl file to the database administrator, who can inspect the contents and make any required changes, such as specifying alternate Tablespaces or other storage options, and will then execute the file against the database to update the schema.

   ses\siebsrvr\log\RepositoryUpdate_<time_stamp>

3. After the DBA has successfully applied the physical schema changes, rerun RepositoryUpdate with the -6 flag set to A (indicating that the schema changes have already been applied), as shown in the following example:

   Oracle example:

   RepositoryUpdate.exe -s C:\$SIEBEL_HOME -t SIEBEL -u SIEBEL -p ******** -o SIEBEL
   -d ORACLE -y SADMIN -z ******** -b SEBL_DATA -x SEBL_INDX -c SSE_ROLE -6 A -9 int_future_release_X

   MSSQL example:

   RepositoryUpdate.exe -s C:\$SIEBEL_HOME -t dbo -u SIEBEL -p ******** -o Siebel_DSN
   -d MSSQL -y SADMIN -z ******** -c SSE_ROLE -6 A -9 int_future_release_X
   

   DB2 UDB example:

   RepositoryUpdate.exe -s C:\$SIEBEL_HOME -t SIEBEL -u SIEBEL -p ******** -o DB2KLXXX
   -d DB2UDB -y SADMIN -z ******** -b TBS_4K -x TBS_4K -k TBS_16K -v TBS_32K -c SSE_ROLE -6 A -9 int_future_release_X
   

   DB2390 example:

   RepositoryUpdate.exe -s C:\$SIEBEL_HOME -t CQ10D0XX -u QADMIN -p XXXXX -o Q10D
   -d DB2390 -y QADMIN -z XXXXX -c SSEROLE -b SIEBTS00 -2 BP1 -5 BP8K1 -f BP16K1 -7 BP32K1
   -8 D003 -a ASCII -j BP2 -e SYSDEFLT -h SYSDEFLT -6 A -9 int_future_release_X

4. After successfully executing RepositoryUpdate, follow the instructions in Running RepositoryUpdate Utility to deliver the new Workspace to the integration branch you chose in Step 1.