My Oracle Support Banner

RepositoryUpgrade Utility Without Automatically Applying Database Schema Changes Not Creating Int_siebel_update Workspace In MSSQL And Oracle Databases (Doc ID 2983090.1)

Last updated on OCTOBER 25, 2023

Applies to:

Siebel CRM - Version 23.3 and later
Information in this document applies to any platform.

Symptoms

Updated the Siebel version from 22.2 to 23.3. While running the RepositoryUpgrade utility without automatically applying database schema changes in the MSSQL database platform, it is completed without errors.

But it is not creating Siebel shipped int_siebel_update_X workspace under int_my_ws. Below is the command line output:

C:\Siebel\home\siebsrvr\BIN>RepositoryUpgrade.exe -s C:\Siebel\home\siebsrvr -t dbo -u SIEBEL -p XXXXX -o esia17_DSN -d MSSQL -y SADMIN -z SIEBEL -e SIEBEL -g ENU -i N -c SSE_ROLE -l Y -j Y -3 Y -6 A -9 int_my_ws -n N
------------------------------------------
Current Content Version    : 23.3
Current Schema Version     : 23.3
Current Repository Version : 22.9
------------------------------------------
------------------------------------------
Following build available in the installer
------------------------------------------
20.3
20.7
20.9
22.12
23.1
23.2
23.3
Starting for each build
         Skipping: No Manifest present for 22.10
         Skipping: No Manifest present for 22.11
        Running for 22.12
         Skipping: No Manifest present for 23.1
         Skipping: No Manifest present for 23.2
         Skipping: No Manifest present for 23.3
Completed for each build
------------------------------------------
Manifest Import Completed
------------------------------------------
RepositoryUpgrade Execution Report Location : C:\Siebel\home\siebsrvr/log/RepositoryUpgrade_20231019_120800.html


The issue can be reproduced at will with the following steps:

1. Open the command prompt and navigate to Siebel server root directory. For example:C:\Siebel\home\siebsrvr\bin
2. Run respositoryupgrade utility independently by following Independently Apply RepositoryUpgrade Schema Changes from the Upgrade Guide

Changes

 Applied 23.3 on top of 22.2 and running repositoryupgrade utility

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.