Siebel Upgrade Training

Demonstrated Training To Understand Upgrade Concepts

Jeya Singh
Principal Engineer
Global Customer Support, Siebel - CRM
September 2021

1 Confidential – © 2019 Oracle Internal

Siebel Upgrade Topics/Agenda:

• Upgrade Process

• Review steps involved in the upgrade

• Perform upgrade (DEMO)

2 Confidential – © 2019 Oracle Internal

 Overview
Dev Production
Test Env
Upgrade Upgrade
Upgrade

Goals in Dev Upgrade

• Upgrade current version Repository to latest Siebel
repository
• OOB repository changes merged with customer
changes
• Baseline for upgrading Test and Production
environments(custrep.dat and schema.ddl from
3
Copyright
dev env)
© 2021, Oracle and/or its affiliates | Confidential: Internal
 Development Environment: Upgrade Process

Prepare
Environment Install New
Version
Upgrade
(Binaries)
Repository
(Upgrep) Merge
Repository
Post Merge
Activities
(conflict Full
resolution) Publish
Upgrade
Schema
(UpgPhys)
Development Environment: Preparation
• Database BackUp
• Upgrade 3rd Party Components (DB, OS, etc.)
• Verify DB Sort Order (see Bookshelf for details)
• Verify other DB Params (see Bookshelf/Performance tuning Guidefor details)
• Inactivate all Workflows
• Clear the S_SRM_REQUEST table
• Check in all Repository changes
• Database-specific instructions in Bookshelf Upgrade Guide are critical
• Character sets
• Collation sequences
• Temporary space/Rollback segments/etc.
• Server/tools parameters (editing tools.cfg , siebel.cfg )
• Remember to change settings back after the upgrade
• Development environment should not be a copy of production.
• Production upgrades have significant amounts of data that may cause a development upgrade to run very slowly
5
• Delete all old repositories
 Development Environment
Upgrade Process

Prepare
Environment

Install New
Version

Upgrade
Repository
(Upgrep)
Merge
Repository

Post Merge
Activities

FullPublish

Upgrade
Schema
(Upgphys)

6
 Different scenarios for Environment set up:
Scenario 1:
1. Customer usually back up their current 16.19 DEV environment and Database as part of preparation step.
2. Then upgrade their OS and DB version and apply the siebel 17 and 20.12 binaries on same DEV env as migration installation
3. Then run the IRM in the same machine
Scenario 2:
4. Customer usually back up their current 16.19 DEV environment’s Database as part of preparation step
5. They take data pump (export) of 16.19 database on machine A
6. They install siebel 17 and 20.12 in different machine B (new environment) as new install.
7. Import the data pump from step 2 on machine B
8. Configure the Enterprise to point to the imported DB in machine B and run IRM
Scenario 3:
9. Customer usually back up their current 16.19 DEV environment’s Database on machine A as part of preparation step
10. They install siebel 17 and 20.12 in different machine B ( new env) as new install.
11. Configure the enterprise on machine B to use the 16.19 database in Machine A (dev env) and run IRM
Scenario 4: Internal testing of customer issue
12. Bring in the customer repository
13. Then import customer repository in to source Siebel version (in this case 16.19) and synchronize before applying the target version
17+20.12 binaries
14. Then run IRM
 Development Environment
Upgrade Process

Prepare
Environment

Install New
Version

Upgrade
Repository
(Upgrep) Merge
Repository

Post Merge
Activities

Upgrade

Schema Post-
Upgrade
Development
Tasks

8
Development Environment
Upgrade Repository: UpgRep Step
• What does it do?
• Modifies the Repository Tables structure to include any new Repository Tables and new attributes
• Loads baseline repositories for the previous Siebel version and current Siebel version
• Imports certain seed data needed by new version
• Preparation Steps
• Backup database
• Copy ancestor respository.dat file from the downloaded files to $SIEBELROOT\dbsrvr\common\sia directory or
follow the step in bookshelf “copying ancestor repository)
• For example: ancestor repository for upgrade from siebel 16 is r160.dat file

Execution Step:
• Run Database Configuration Wizard from a machine co-located with the database server
--choose upgrade Database--> development upgrade--> upgrep . Provide all values .
• Errors during execution? You can restart Upgrade after fixing the issue and marking the step as InComplete in
state.log.
9
 After Upgrep Step

1. Backup database after upgrep step

2. Run DB stats : instruction in upgrade bookshelf
sql>EXEC DBMS_STATS.gather_schema_stats (ownname =>
'SIEBEL', cascade=>true,estimate_percent =>
dbms_stats.auto_sample_size);
 Development Environment
Upgrade Process

Prepare
Environment

Install New
Version

Upgrade
Repository

Merge
Repository

Post Merge
Activities

FullPublish

Upgrade

Schema
Development Environment: Repository Merge Process
• What does it do?
• Combines your custom changes and OOB changes into a single repository

Customer Custom
Changes 16.x
Repository

Base 16.x
Repository
Merge
Process
Merged
Repository

OOB OOB 21.x

Changes Repository
 Development Environment: Repository Merge Process
Preparation Steps
• Backup database after Upgrep Step
• Run DB stats (command is available in bookshelf )
• Copy “irm_sav_file.ssf” from “siebsrvr\bin” to “Tools\Bin” location [Unix env ONLY] .make sure the state is 7
• Make sure the siebsrvr/bin/lang/siebel.cfg has following values
• DataSourceName = ServerDataSrc
• ClientRootDir = /refresh/siebel/ses/siebsrvr
• ServerDbODBCDataSource = esia209_DSN
• DockRepositoryName = New Customer Repository
• Make sure tools.cfg has following values:
• Change the SymStrPrefix value from the default value of X_ to SBL_.
• Make sure the EnableToolsConstrain value is set to the default value of False. If it is not, then set the
value to False.
• Set the DockRepositoryName value from the default value of Siebel Repository to New Customer
Repository.

Execution Step:
• Execute Incremental Repository merge: (use below command in case of Unix.
• <Unix> tools/bin >siebdev.exe /u <user name> /p <password> /d <Tools Data Source> /c <directory path to
tools.cfg> /l <primary language> /IRM UpgDeltaMerge /iPackmode
<windows> siebsrvr/bin> siebupg /m master_upgrep_dev_160.ucf
• Common problems: Errors in tools\log\IRM_MERGE*.txt
• Check the document for acceptable errors and workaround: How To Troubleshoot Messages Generated During the
Repository Merge in Siebel 7 and 8 (Doc ID 477269.1)
 Development Environment
Upgrade Process

Prepare
Environment

Install New
Version

Upgrade
Repository

Merge
Repository

Post Merge
Activities
(Conflict FullPublish
Resolution)
Upgrade

Schema
 Development Environment: Post Merge – Conflict Resolution
• What is a conflict?
• The same object has been changed in both the customer and OOB repositories.

• How are conflicts handled by merge process?

• Repository objects Type and Attribute determine the fate of conflicting attributes
• Generally, customer changes related to the UI (position of a control on an applet, captions, etc.) are preserved. Most other
conflicts are won by the OOB repository.
• What if the merge behavior is not what the customer wanted?
• After the merge, conflicts should be reviewed and resolved on a case by case basis

• To Review all conflicts and determine whether to override the default behavior
• Siebel Tools: Screens  Application Upgrader  Application Upgrade Attribute List

15

• Prior Customer, Prior Standard, and New Standard are all displayed
• Click the “Override” flag to change from Customer to Standard or vice versa
 Conflict resolution – mark completion
Mark the conflict resolution completed:

• Once the critical conflicts are resolved manually , need to Mark the conflict resolution completed
• Invoke the tools by running the below command
siebdev.exe /u username /p SIEBEL_TOOLS_ROOT /d "ServerDataSrc" /c Tools\bin\lang\tools.cfg" /l Siebel_Tools_Root /IRM
UpgDeltaMerge /iPackmode
• After Siebel Tools is started,
select the Conflict Resolution Completed check box.
• Click Finish.

• An entry is made in S_INST_UPG_HIST to indicate

that conflict resolution has been completed.
• When upgrade physical schema (upgphys) is executed
during Development upgrades, the first step validates
whether conflict resolution has been completed or not.
 Development Environment
Upgrade Process

Prepare
Environment

Install New
Version

Upgrade
Repository

Merge
Repository

Post Merge
Activities
(Conflict
Resolution) FullPublish

Upgrade

Schema
 Development Environment: Full Publish

• Before running upgphys, Full Publish must be executed. To generate the Siebel Runtime Repository data, you must
execute the Full Publish command in Siebel Tools.
• Full Publish must be executed against the New Customer Repository.
• Make sure to change the DockRepositoryName in tools.cfg to New Customer Repository and ensure Siebel tools
launches against the correct Repository.
• The Full Publish command :
• siebdev /c tools.cfg /TL ENU /d ServerDataSrc /u <username> /p <password> /FullPublish
• You can add multiple languages separated by a comma. For example:
/TL ENU,DEU,JPN

• Depending on the number of the languages specified, the Full Publish process spans the number of Siebdev
processes/Tools to compile objects in the specified language and write the data to the database. Siebdev silently
closes after completion of a Full Publish, which indicates there are no errors.
19
 Development Environment
Upgrade Process

Prepare
Environment

Install New
Version

Upgrade
Repository

Merge
Repository

Post Merge
Activities
(Conflict
FullPublish
Resolution)

Upgrade
Schema
(UpgPhys)
Development Environment: UpgPhys
• What does it do?
• Finalizes any database changes needed after the merge. Synchronizes logical and physical schema
Preparation Steps
• Backup database

Execution Step:
• Run Database Configuration Wizard from a machine co-located with the database server
• Errors during execution? You can restart Upgphys restoring the DB prior to running the upgphys
 <Insert Picture Here>

Test Environment
 Overview

Upgrade Upgrade
Upgrade Test
Development Production

Goals
• Determine upgrade timeframe (and determine if
tuning is necessary)
• Validate upgraded environment ready for use
• Ensure that production upgrade will run
smoothly
Test Environment
Preparation
• Test can be upgraded immediately after completing the development UpgPhys process
using a schema.ddl and custrep.dat file from Dev environment
• Regenerate schema.ddl and custrep.dat file from Development before each iteration

24
Test Environment: Upgrade Process

Prepare
Environment
Install New
Version
Upgrade
Repository
Merge
Repository
Prepare Post Merge
Database Activities
Upgrade

Schema
Test Environment: Upgrade Process

Prepare
Environment
Install New
Version
Prepare
Database
Upgrade
Repository
Upgrade

Schema
Test Environment
Prerequisites
• Development environment already upgraded

• Regenerate Schema.dll from development:

ddldict /u DatabaseOwner /p Password /c "ODBCDataSource" /d TableOwner /f DBSRVR_ROOT\DatabasePlatform\
schema.ddl /e y /a y /l SiebelLogDir\sch_dict.log /n "Siebel Repository" /t dcir

• Regenerate CustRep.dat from development:

repimexp /a e /u DatabaseOwner /p Password /c "ODBCDataSource" /d TableOwner /r "New Customer Repository"
/f DBSRVR_ROOT\DatabasePlatform\custrep.dat /l SiebelLogDir\exprep.log

• Copy Production database to Test environment

Test Environment
Upgrade Process

Prepare
Environment
Install New
Version
Prepare
Database
Upgrade
Repository
Upgrade

Schema
Test Environment
Upgrade Process

Prepare
Environment
Install New
Version
Prepare
Database
Upgrade
Repository
Upgrade

Schema
Test Environment
Upgrade Process

Prepare
Environment
Install New
Version
Prepare
Database
Upgrade
Repository
Upgrade

Schema
Test Environment : Upgrep

Upgrade Repository
• What does it do?
• Modifies the Repository Tables structure to include any new Repository Tables and new attributes
• Loads custom repository from development (CustRep.dat)
• Imports certain seed data needed by new version
• Take a DB backup before starting

31
Test Environment
Upgrade Process

Prepare
Environment
Install New
Version
Prepare
Database
Upgrade
Repository
Upgrade

Schema
Test Environment : UpgPhys

Upgrade Repository
• What does it do?
• Finalizes any database changes needed after the merge
• Take a DB backup before starting
 Demo

Copyright © 2021, Oracle and/or its affiliates | Confidential: Internal

34
 Click icon to add picture

Thank you

35 Confidential – © 2019 Oracle Internal