Running RepositoryUpdate Utility

You can run the RepositoryUpdate utility on the development database to install new features since Siebel CRM 17.0 that require repository updates. This task does not apply if you do not require any of these new features, but we strongly recommend that it is done regularly to avoid firedrills when a new feature is needed and there is a big gap since the last execution of RepositoryUpdate.

For information about the new features that require repository updates, see Siebel CRM Update Guide and Release Notes on My Oracle Support for your Siebel CRM Monthly Update release.

Thefollowing procedure describes how to update the Repository by running the RepositoryUpdate utility, which is located in the siebsrvr\binfolder.

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

To Run RepositoryUpdate Utility

RunRepositoryUpdate without any arguments to review the available command line arguments. The following tables describe the returned arguments and parameters that you can use to run the RepositoryUpdate utility.

Parameter	Description	Example
-s	Siebsrvr installation path (Required)	`C:$SIEBEL_HOME\ses\siebsrvr`
-u	TBLO Username (Required)	`SIEBEL`
-t	Siebel Table Owner (Required)	`SIEBEL`
-p	TBLO Password (Required)	`********`
-o	ODBC Data Source (Required)	`Siebel_DSN`
-d	Database platform (one of: Oracle, MSSQL, DB2UDB, or DB2390)	`Oracle`
-y	Siebel Username (Required)	`SADMIN`
-z	Siebel User Password (Required)	`********`
-r	Repository Name (Default: "Siebel Repository") (Required)	`Siebel Repository`
-g	Primary Base Language	`ENU`
-w	Additional Languages (Default: None)	`ARA,CHS,FIN,ITA`
-c	SSE_ROLE (Required)	`SSE_ROLE`
-m	Seed inp (data input) creation path for the Migration Application (Default: Siebel Log Directory). Note: The RepositoryUpdate utility will create a file nameddatamig.inp, which is required for the Migration Application to migrate seed data related to the repository changes from the DR to RR environment.	`C:$SIEBEL_HOME\ses\siebsrvr\log`
-i	Unicode DB (Default: Y)	`Y`
-6	Generate Schema File Only (Default: N) Y (Yes, generate schema file only) – This option generates a file with the required schema changes without actually applying them. This allows your database administrator to apply the schema changes to the physical database outside of RepositoryUpdate. A (Already applied Schema changes) – This option means schema changes are already applied. Use this option after the database administrator has completed the schema changes in the physical database. N (No, don't only generate schema file) – This option means that you run RepositoryUpdate to perform schema changes and import all other changes in one execution. Note: Use this switch to generate the required schema changes without actually applying them, thereby allowing your DBA to apply the schema changes outside of RepositoryUpdate. For more information, see Independently Apply RepositoryUpdate Schema Changes.	`N`
-9	Parent Workspace: Note: Best practice is to specify an Integration Workspace reflecting a planned future release (using "MAIN" will cause an error). This allows you to merge Oracle changes with custom changes and test them before Production migration.	`<Parent_IWS_Name>`
-b	Default Table space. Note: Mandatory for Oracle, DB2 UDB, and DB2390 databases.	`SEBL_DATA`
-x	Default Index space. Note: Mandatory for Oracle and DB2 UDB databases.	`SEBL_INDX`
-k	16K Page Table space. Note: Mandatory for DB2 UDB databases.	`TBLSPC16K`
-v	32K Page Table space. Note: Mandatory for DB2 UDB databases.	`TBLSPC32K`
-4	Provide a suffix for log folder generated by RepositoryUpdate (Default: Null) Example: `-4 Ora_23_11` creates log folder as `RepositoryUpdate_Ora_23_11`.	`-4 Ora_23_11`

The following arguments are required only for DB2390 databases:

Parameter	Description	Example
`-2`	4K Buffer Pool (Required)	BP1
`-5`	8K Buffer Pool (Required)	BP8K1
`-f`	16K Buffer Pool (Required)	BP16K1
`-7`	32K Buffer Pool (Required)	BP32K1
`-8`	Database Name Prefix (Required)	D + Last 3 Characters of your schema qualifier
`-a`	Database Code Page (Required)	ASCII/EBCDIC/UNICODE
`-j`	Index Buffer Pool (Required)	BP2
`-e`	Storage Group for Indexes (Required)	SYSDEFLT
`-h`	Storage Group for Tables (Required)	SYSDEFLT

Note: Don't use parameters that are inappropriate for your database platform. For example, do not use the DB2390 -j argument with Oracle, MSSQL, or DB2UDB databases.

Execute the RepositoryUpdate utility using values appropriate to your database. Examples for each supported database platform follow.

Oracle example:

RepositoryUpdate.exe -s C:\$SIEBEL_HOME -t ORAXXXX -u ORAXXXX -p ******** -o Siebel _DSN 
-d ORACLE -y SADMIN -z ******** -b SEBL_DATA -x SEBL_INDX -c SSE_ROLE -9 int_1

MSSQL example:

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

DB2 UDB example:

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

DB2390 example:

RepositoryUpdate.exe -s C:\$SIEBEL_HOME -t CQ10D0XX -u QADMIN -p XXXXX -o Siebel_DSN
-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 -9 int_1

Review the returned output. Output similar to the following is expected:


------------------------------------------
Current Content Version : 21.3
Current DB Version : 19.12
------------------------------------------

------------------------------------------
Following builds available in the installer
------------------------------------------
20.3
20.7
...
21.3
------------------------------------------

------------------------------------------
Following builds need to be installed
------------------------------------------
20.3
...
...
21.3
------------------------------------------

------------------------------------------
Schema Installation Starts
------------------------------------------
Starting for each build
Running for 20.3
...
Running for 21.1
Skipping: No Schema present for 21.2
Running for 21.3
Completed for each build
Publishing Table Starts
Sync Logical and Physical Schema
Publishing Table Completed
------------------------------------------
Schema Installation Completed
------------------------------------------

------------------------------------------
Repository Import Starts
------------------------------------------
Starting for each build
Running for 20.3
...
Skipping: No Repository present for 21.2
Running for 21.3
Completed for each build
Deliver Workspace Starts
Deliver Workspace Completed
------------------------------------------
Repository Import Completed
------------------------------------------

------------------------------------------
Seed Import Starts
------------------------------------------
Starting for each build
Running for 20.3
...
Running for 21.2
Skipping: No Seed present for 21.3
Completed for each build
Running Seed Copy for LOV for each branch
------------------------------------------
Seed Import Completed
------------------------------------------

------------------------------------------
Manifest Import Starts
------------------------------------------
Starting for each build
Running for 20.3
Skipping: No Manifest present for 20.7
Running for 20.8
Running for 20.9
Skipping: No Manifest present for 20.10
Skipping: No Manifest present for 20.11
Running for 20.12
Running for 21.1
Skipping: No Manifest present for 21.2
Skipping: No Manifest present for 21.3
Completed for each build
------------------------------------------
Manifest Import Completed
------------------------------------------

*** Integration Branch : int_siebel_update ***
*** Workspace : dev_sadmin_siebel_21_3 ***
*** Please review Web Tools -> Archive -> SIF Attribute Differences and resolve any 
conflicts. Once done, click Apply Changes to apply your decisions. If you do not make any 
changes in the report, all incoming configuration will be used. Once you checkpoint or 
version the Workspace, the Apply Changes option will be disabled. ***

RepositoryUpdate Execution Report Location : C:\$SIEBEL_HOME\ses\siebsrvr\log\RepositoryUpdate_20210204_044026.html

Check the HTML file (RepositoryUpdate Execution Report) for more details, resolve any issues, and then rerun the process if required.

At this point, RepositoryUpdate will have created two new Workspace in the repository, as follows:

An Integration Workspace named int_siebel_update_X directly underneath the Workspace specified by the -9 parameter (provided on the RepositoryUpdate command line).
A Developer Workspace under this Integration Workspace named "dev_sadmin_siebel_mm_dd", where mm_dd represents the release you are importing, such as 23.10.

Review Web Tools > Archive > SIF Attribute Differences and resolve any conflicts. Once done, click Apply Changes to apply your decisions. If you do not make any changes in the report, all incoming configuration will be used. Once you checkpoint or version the Workspace, the Apply Changes option will be disabled.

The Developer Workspace was used to import the Repository changes. This Workspace can be used to inspect all the RepositoryUpdate-supplied changes and resolve any conflicts before delivery to the parent Integration Workspace. For more information on this, review the section Viewing and Resolving Conflicts after Siebel Archive File Imports in Web Tools in the Using Siebel Tools guide.

After completing the conflict resolution, deliver the Developer Workspace to its parent Integration Workspace.

Rebase the int_siebel_update_X branch to its parent Integration Workspace and test it in conjunction with your customer changes.
Once you are comfortable that your changes and the RepositoryUpdate-supplied changes work together, deliver the int_siebel_update_X branch to its parent Integration Workspace.
Depending on your specific implementation and any conflicts that may exist, this process may require a Rebase, Conflict Resolution, Submission for Delivery, approvals in Siebel Approval Manager, and so on. For more information on delivering changes from a Workspace, see the Using Siebel Tools guide.