1. Database Upgrade Guide
  2. Executing the Upgrade

Executing the Upgrade

This topic provides information about executing your upgrade.

Prepare the Payload

This table shows the accepted Siebel input versions and the corresponding supported Siebel versions:

Corresponding Siebel Version Accepted Siebel Input Version (current_ siebel_version)
7.8.2 v7.8.2sia
8 v8.0sia
8.1.1.10 v8.1.1.10sia
13 v8.1.1.11sia
14 v8.1.1.14sia
8.2.2 v8.2.2sia
8.2.3 v8.2.2.3sia
13 v8.2.2.4sia
14 v8.2.2.14sia
15 v15.0
15.5 v15.5
16 v16.0

This table shows the Siebel component groups:

Component Group Name
adm Application Deployment Manager
asgnmgmt Assignment Management
commmgmt Communications Management
contctr Content Center
dataqual Data Quality
mobilesync Disconnected Mobile Synchronization
mobilesyncsis Disconnected Mobile Synchronization SIA
dandb Dun and Bradstreet
eai Enterprise Application Integration
fieldsvc Field Service
fcstsvc Forecast Service Management
sync Handheld Synchronization
syncsis Handheld Synchronization SIA
icomp Incentive Compensation
mktgom Marketing Object Manager
mktgsrv Marketing Server
rtsremote MWC Real Time Sync
pimsi PIM Server Integration Management
creditasgn Sales Credit Assignment
saleshiersvc Sales Hierarchy Service
search Search Processing
siebanywhere Siebel Anywhere
callcenter Siebel Call Center
communications Siebel CME
cra Siebel Core Reference Application
eautomotive Siebel eAutomotive
echannel Siebel eChannel
econsumer Siebel eConsumerSector
edocuments Siebel eDocuments
hospitality Siebel eHospitality
erm Siebel Employee Relationship Management
fins Siebel Financial Services
htim Siebel High Tech Industrial Manufacturing
sisme Siebel Industry Marketing
iss Siebel ISS
lifesciences Siebel Life Sciences
loyalty Siebel Loyalty
loyaltyengine Siebel Loyalty Engine
publicsector Siebel Public Sector
remote Siebel Remote
rti Siebel RTI
sales Siebel Sales
ucm Siebel Universal Customer Master
siebel Web Tools Siebel Web Tools
taskui Task UI
workflow Workflow Management
xmlpreport XMLP Report

This table shows the input payload details:

Input JSON Sections Parameter Purpose Description
<root level> current_siebel_version Siebel version of the Customer Repository (Mandatory) The Siebel source version from a previous table.
requester_email Email Id of the requester (Mandatory) Array of user email ID
base_language Base language of the Customer Siebel Application (Mandatory) Single language entry (Example: enu)
other_languages Currently not supported This is a required entry but should be left blank until this is supported.
component_groups Component groups to be enabled on the upgrade application Comma separated values from the previous table.
degree_of_parallelism Degree of parallelism during the calendar upgrades (Mandatory) This should be a positive numeric value.
upt_file_url Obsolete (Mandatory) This is a obsolete entry and should be left blank, but must be included in the payload.
execution_preferences execution_type Indicates the process to be run (Mandatory) Values expected is one of these:
  • Assess
  • Dev
  • Prod
custom_files webtmpl_file_url OOS Bucket PAR URL for the zipped file containing custom webtemplates (<filename>.zip) Files to be zipped directly inside the zip file without any enclosing directory (zip <filename>.zip file1 file2 file3... )
js_file_url OOS Bucket PAR URL for the zipped file containing custom js files (<filename>.zip) Files to be zipped directly inside the zip file without any enclosing directory (zip <filename>.zip file1 file2 file3... )
css_file_url OOS Bucket PAR URL for the zipped file containing custom css files (<filename>.zip) Files to be zipped directly inside the zip file without any enclosing directory (zip <filename>.zip file1 file2 file3... )
prod_file_url OOS Bucket PAR URL for the zipped file containing custrep.dat and 10 schema_x.ddl files (Mandatory for Production upgrades) Files to be zipped directly inside the zip file without any enclosing directory (zip <filename>.zip file1 file2 file3... ). This zip file PAR URL is available on successful completion of dev upgrade.
db_dump dump_file_url OOS Bucket PAR URL for the Database Dump File (no zipping) (Mandatory for Database upgrade) dump_file_url or repo_file_url is mandatory (zipped/tar files not allowed)
schema_owner DBSchema owner for the database dump (Mandatory for Database upgrade) Source database schema owner
tablespace Tablespace name for the database dump (Mandatory for Database upgrade) Source database tablespace
index_tablespace Index tablespace name for the database dump (Mandatory for Database upgrade) Source database index tablespace
customer_repository repo_file_url OOS Bucket PAR URL for the CustomerRepository dat file (no zipping) (Mandatory for Repository upgrade) dump_file_url or repo_file_url is mandatory(zipped/tar files not allowed)

Payload Format and Sample Input Payload

Input Payload Format


{
  "current_siebel_version": "",
  "requester_email": [
    "email1","email2"
  ],
  "base_language": "",
  "other_languages": "",
  "component_groups": "",
  "upt_file_url": "",
  "execution_preferences": {
    "execution_type": "",
    "degree_of_parallelism": ""
  },
  "custom_files": {
    "webtmpl_file_url": "",
    "js_file_url": "",
    "css_file_url": "",
    "prod_file_url": ""
  },
  "db_dump": {
    "dump_file_url": "",
    "schema_owner": "",
    "tablespace": "",
    "index_tablespace": ""
  },
  "customer_repository": {
    "repo_file_url": ""
  }
}

Sample Input Payload: Development Upgrade

{
    "current_siebel_version": "v8.1.1.14sia",
    "requester_email": [
        "johnDoe1@example.com",
        "johnDoe2@example.com",
        "johnDoe3@example.com"
    ],
    "component_groups": "callcenter",
    "base_language": "enu",
    "other_languages": "",
    "upt_file_url": "",
    "execution_preferences": {
        "execution_type": "Prod",
         "degree_of_parallelism": "32"
    },
    "custom_files": {
        "webtmpl_file_url": "",
        "js_file_url": "",
        "css_file_url": "",
        "prod_file_url": "https://objectstorage.us-chicago-1.oraclecloud.com/p/abcdefghijklmnopqrstuvwzyz/o/output_files.zip"
    },
    "db_dump": {
        "dump_file_url":"https://objectstorage.us-ashburn-1.oraclecloud.com/p/abcdefghijklmnopqrstuvwxyz/o/SiebelDatabase.dmpdp",
        "schema_owner": "SIEBEL",
        "tablespace": "DATA",
        "index_tablespace": "DATA"
    },
    "customer_repository": {
        "repo_file_url": ""
    }
}

Sample Input Payload: Production Upgrade

{
    "current_siebel_version": "v8.1.1.14sia",
    "requester_email": [
        "johnDoe1@example.com",
        "johnDoe2@example.com",
        "johnDoe3@example.com"
    ],
    "component_groups": "callcenter",
    "base_language": "enu",
    "other_languages": "",
    "upt_file_url": "",
    "execution_preferences": {
        "execution_type": "Prod",
         "degree_of_parallelism": "32"
    },
    "custom_files": {
        "webtmpl_file_url": "",
        "js_file_url": "",
        "css_file_url": "",
        "prod_file_url": "https://objectstorage.us-chicago-1.oraclecloud.com/p/abcdefghijklmnopqrstuvwzyz/o/output_files.zip"
    },
    "db_dump": {
        "dump_file_url":"https://objectstorage.us-ashburn-1.oraclecloud.com/p/abcdefghijklmnopqrstuvwxyz/o/SiebelDatabase.dmpdp",
        "schema_owner": "SIEBEL",
        "tablespace": "DATA",
        "index_tablespace": "DATA"
    },
    "customer_repository": {
        "repo_file_url": ""
    }
}

To trigger the upgrade with the payload follow these steps:

  1. Prepare the payload as per the predefined payload format.
  2. Open any preferred REST API client.
  3. Paste the payload in the input area of the application and select POST method.
  4. Enter the REST API URI: http://<PUBLIC-IP>:<Port>/scm/api/v1.0/upgradefactory.
  5. Post the request by clicking Send (in case of Boomerang).
  6. You'll be prompted for authentication credentials.
  7. Enter these default credentials to proceed with the request;
    • USERNAME: admin
    • PASSWORD: Get a token from the SCM instance by signing in with an SSH key. Go to the folder /home/opc/cmapp/UPGRADEFACTORY/config and view the api_creds.ini file.

    Make a note of the basic_auth_password.

    Default Credentials

    USERNAME: admin

    PASSWORD: Token from the previous step.

  8. Wait for the response, which contains all the steps you need as part of the upgrade.
  9. You'll receive an email for subscription confirmation from Oracle Cloud Infrastructure Notifications Service.
  10. Click the Confirm subscription link to enable the email notifications for upgrade execution.

This table lists the steps that are executed as part of the Upgrade Factory process:

Step Details Action
01_env_provisioning Environment provisioning and Siebel setup using the Repository/dump file provided. Automated
02_assessment_report_generation Pre-upgrade Repository Analyzer execution and Assessment Report generation. Automated
03_upgrep_irm_process Trigger Siebel Upgrade Process - UPGREP followed by IRM Process. Automated
04_launch_webtool_for_conflict_resolution Prepares the environment to enable Web Tools launch for conflict resolution. Automated
05_conflict_resolution Waits for user to launch Web Tools and complete the conflict resolution. Launch Web Tools and complete conflict resolution
06_fullpublish Triggers fullpublish post conflict resolution Automated
07_upgphys_process Resumes Upgrade process with full publish followed by UPGPHYS process to complete the Siebel Upgrade. Automated

Status Check and Actions

Checking the Execution Status

After the upgrade factory process starts, it takes a couple of hours to set up the environment and execute the Repository Analyzer. If you subscribe to notification you'll receive an email on completion of every step. If you want to know the status of the execution, you can trigger a GET request on the same URI to know the current status (REST API URI Format: http://<PUBLIC_IP>:<Port>/scm/api/v1.0/upgradefactory).

Here's what you see:

  • The Status is marked as completed on successful execution with a start time and end time.
  • The current running status is marked as in-progress with a start time.
  • Important URLs are listed at the bottom of the payload.
  • If the upgrade status shows failed, it means there's an issue with the execution.

Sample Output Payload


{
  "data": {
    "stages": {
      "01_environment_setup": {
        "comment": "",
        "end_time": "03-03-2025 12:09:55 GMT",
        "start_time": "03-03-2025 11:33:51 GMT",
        "status": "Complete"
      },
      "02_upgrep_process": {
        "comment": "",
        "end_time": "03-03-2025 13:36:15 GMT",
        "start_time": "03-03-2025 12:09:55 GMT",
        "status": "Complete"
      },
      "03_irm_process": {
        "comment": "",
        "end_time": "03-03-2025 17:30:34 GMT",
        "start_time": "03-03-2025 13:41:17 GMT",
        "status": "Complete"
      },
      "04_webtool_preparation": {
        "comment": "",
        "end_time": "03-03-2025 17:44:36 GMT",
        "start_time": "03-03-2025 17:30:34 GMT",
        "status": "Complete"
      },
      "05_conflict_resolution": {
        "comment": "",
        "end_time": "04-03-2025 04:41:06 GMT",
        "start_time": "03-03-2025 17:44:36 GMT",
        "status": "Complete"
      },
      "06_fullpublish": {
        "comment": "",
        "end_time": "04-03-2025 05:46:07 GMT",
        "start_time": "04-03-2025 04:41:14 GMT",
        "status": "Complete"
      },
      "07_upgphys_process": {
        "comment": "",
        "end_time": "04-03-2025 07:17:27 GMT",
        "start_time": "04-03-2025 05:46:07 GMT",
        "status": "Complete"
      }
    },
    "upgrade_status": "successful",
    "urls": {
      "final_output_url": "https://objectstorage.us-chicago-1.oraclecloud.com/p/abcdefghkadflkajoeiwanlakfedlaj/b/UpgradeFactoryLogs-upgradefactory-siebel-cm/o/output_files.zip",
      "logs_url": "https://objectstorage.us-chicago-1.oraclecloud.com/p/ajflaoraenglajlrslegjljlerj/b/UpgradeFactoryLogs-upgradefactory-siebel-cm/o/UpgradeFactoryLogs_04032025071536.zip",
      "siebel_app_callcenter": "https://111.11.111.11:4430/siebel/app/callcenter/enu",
      "siebel_app_selfservice": "https://111.11.111.11:4430/siebel/app/selfservice/enu",
      "siebel_app_smc": "https://111.11.111.11:4430/siebel/smc",
      "siebel_app_webtools": "https://111.11.111.11:4430/siebel/app/webtools/enu"
    }
  },
  "message": "Upgrade is successful",
  "status": "success"
}

Pre-Upgrade Assessment Report (RepAnalyzer Reports)

Here's what you see in the pre-upgrade assessment report:

The assessment report and summary dashboard are uploaded to OCI bucket and the pre-assessment Report URL is shared in the status check response.

Here's what you can do next:

  1. Download the report from any browser.
  2. Unzip the ReportData.txtand RepAnalyzer Dashboard from the downloaded file.
  3. Open the UpgradeAssessementReport.htmlfile inside the RepAnalyzer Dashboard directory.
  4. The summary shows a count of conflicts that are critical, needs attention and informational for UI, business, and data entities, in the form of this table:
    Classification Definition
    Info No action required from the customer
    Attention Customer must verify and resolve, but not a show stopper
    Critical Need action from customer. It’s can be a show stopper
  5. Click Conflict Count to navigate to the detailed page.
  6. The tree structure on the left provides the categorization of UI, Business and Data layer.
  7. Only critical conflicts are displayed in the table.
  8. Schema page will have all the Schema level change details
  9. RepCrawler report (all unreferenced objects list) is added as part of the assessment report.
  10. Duplicate workflow and task list is captured as part of the assessment report.

Development Upgrade

  1. Execution type in the input payload is passed as “dev” for development upgrade execution.
  2. Development upgrade performs a series of activities on the database or Repository provided (upgrep and IRM), and then launches Web Tools for conflict resolution.
  3. Process is paused for conflict resolution by the user and resumes once the conflict resolution is completed on Web Tools.
  4. Process proceeds with fullpublish and upgphys to complete the upgrade activity.
  5. An output files downloadable URL which downloads dev output files zipped after development upgrade. There are 10 schema_x.ddl and one custrep.dat file which are required for test and production upgrades.

Production Upgrade

  1. Execution type in the input payload is passed as “prod” for production upgrade execution.

  2. Downloadable URL for Output files zip (output_files.zip) from the development upgrade is provided as input for the production upgrade.

  3. Production upgrade utilizes 11 files from the development upgrade and performs the production upgrep process to upgrade the schema and Repository in the production database.

Add Ingress Rules on OCI to Enable Access to Server

All the connections to the host server ports are secured using Ingress rules configuration on Oracle cloud infrastructure (OCI). If you're unable to access any of the required ports like 443 for the Siebel application and 1521 port for the database connect, it might be due to missing ingress configuration.

Here's how you can configure ingress rules:

  1. Identify your sub compartment name under the root compartment which you selected when you created the SCM stack.

    Compartment name format : <resource_prefix_name> -siebel-cm

    resource_prefix_name is the resource prefix to name the OCI resources. For example, if resource_prefix_name = UpgradeFactory then the compartment name is UpgradeFactory-siebel-cm.

  2. Go to OCI console > Compute > Instances and select the Compartment ID (resource prefix name + -siebel-cm) and click Instance Name.
  3. Drill down to the Name link for the instance having your Public IP, and then drill down further on the Subnet link.
  4. Select security-list-for-cm.
  5. Add ingress rules for required ports:
    • Source CIDR: This is the IP address of the source machine which would need access to the server. To get the IPv4 address of the machine, use this link: https://whatismyipaddress.com/. Source CIDR is <youripaddress>/32.
    • Destination port: 4430
      Note: Port 4430 for Siebel application access including Web Tools, 1521 port for Siebel DB access.
  6. Click Add Ingress Rules.

Resolve Conflicts Using Web Tools

You can find the upgrade conflict resolution screen in Siebel Web Tools. Once the upgrade factory process completes the 04_launch_webtool_for_conflict_resolution step, a status check response gives you a Web Tools URL, which is also sent to you by email. At this point, the upgrade factory process is paused for user action. Make sure the ingress rule is added for your system IPAddress and port 443. (The Web Tools URL is hosted with port 443).

Here's how you can resolve conflicts using Web Tools:

  1. Launch Web Tools using the URL available in the payload response.
  2. Enter the credentials shared on Web Tools.
  3. Navigate to Tools > Upgrade conflicts.
  4. You can override using the override flag or select options using the Resolution drop-down list.
  5. Select multiple records on the screen and then select Change records to update the records.
  6. Select Accept recommendations to update the recommendations on all records.
  7. Select Conflict Resolution Complete on the top applet and accept the confirmation message.
  8. On confirmation, Siebel Web Tools is signed out and the upgrade factory process will resume in sometime.

Complete the Upgrade

Here's what happens when the upgrade factory process resumes:

  • Once the conflict resolution is marked as completed, UPGPHYS is triggered.
  • Upgrade is complete once the UPGPHYS is completed.
  • The application URLs are available at the bottom of the response.
  • You can access the final output files using the URLs in the response.
  • The zipped file contains the Repository export and schema ddl.
  • Execution is now complete and the upgraded application is available.