1. Database Upgrade Guide for DB2 for z/OS
  2. Running RepositoryUpgrade Utility

Running RepositoryUpgrade Utility

You can optionally run the RepositoryUpgrade 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.

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 22.x Update release.

The following procedure describes how to update the repository by running the RepositoryUpgrade utility, which is located in the siebsrvr\bin folder.

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

To run RepositoryUpgrade utility

  1. Run RepositoryUpgrade (RepositoryUpgrade.exe for Windows or RepositoryUpgrade.sh for other platforms) without any arguments to review the available command line arguments. The following tables describe the returned arguments and parameters, which you can use to run the RepositoryUpgrade utility.

    Parameter

    Description

    Example

    -s

    Siebsrvr installation path (Required)

    C:\$SIEBEL_HOME\ses\siebsrvr

    -t

    Siebel Table Owner (Required)

    SIEBEL

    -u

    TBLO Username (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 for the Migration Application (Default: Siebel Log Directory)

    Note: The RepositoryUpgrade utility will create a file named datamig.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)

    Valid options are:

    • 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 RepositoryUpgrade.
    • 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 RepositoryUpgrade 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 RepositoryUpgrade. For more information, see Independently Apply RepositoryUpgrade Schema Changes.

    N

    -9

    Parent Workspace Name

    Note: Best practice is to specify an Integration Workspace reflecting a planned future release (you will receive an error if you specify "MAIN"). This will allow you to merge the Oracle changes with your custom changes and test them before migrating them to Production.

    <Parent_IWS_Name>

    -b

    Default Tablespace

    Note: Mandatory argument for Oracle, DB2 UDB, and DB2390 databases.

    SEBL_DATA

    -x

    Default Indexspace

    Note: Mandatory argument for Oracle and DB2 UDB databases.

    SEBL_INDX

    -k

    16K Page Tablespace

    Note: Mandatory argument for DB2 UDB databases.

    TBLSPC16K

    -v

    32K Page Tablespace

    Note: Mandatory argument for DB2 UDB databases.

    TBLSPC32K

    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

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

    DB2390 example: 

    RepositoryUpgrade.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

  3. 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 ***

RepositoryUpgrade Execution Report Location : C:\$SIEBEL_HOME\ses\siebsrvr\log\RepositoryUpgrade_20210204_044026.html

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

    • At this point, RepositoryUpgrade will have created two new Workspaces in the repository, as follows:

      • An Integration Workspace named int_siebel_update directly underneath the Workspace specified by the -9 parameter (provided on the RepositoryUpgrade command line).

      • A Developer Workspace under this Integration Workspace named dev_sadmin_siebel_21_3.

        The Developer Workspace was used to import the repository changes and will have automatically been delivered to the Integration Workspace. The Integration Workspace cannot be delivered automatically due to the possibility of a customization conflict. The Integration Workspace must be delivered to its Parent Workspace manually, just like any Integration Workspace created by your development team.

        Note: You must perform the Delivery step to enable the new repository-dependent features.

  4. Deliver the Integration Workspace created by RepositoryUpgrade to its Parent Integration Workspace or MAIN.

    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 Using Siebel Tools.