1

Siebel Upgrade Consultant

Test client database connectivity using Oracle SQL PLUS and OBDC connectivity.

 

2

 

Install the following for version 7.5:

n Siebel Client

n Siebel Tools

n Siebel Sample Database

Test version 7.5 Siebel Client and Tools connectivity to the sample database to verify that Siebel 7 software is functioning correctly.

Make sure the sample section of the Siebel Client and Tools configuration files point to the correct path.

2 hours

3

 

Install the version 7.5 Siebel Gateway. See Siebel Server Installation Guide for Microsoft Windows for detailed instructions.

Make sure the service starts.

1 hour

4

 

Install the version 7.5 Siebel Enterprise Server and Siebel Server(s) to version 7.5. See Siebel Server Installation Guide for Microsoft Windows for detailed instructions.

Make sure the service starts.

1 hour for each server

5

 

Configure the Siebel Enterprise and Siebel Servers, and enable necessary components.

If Resonate is used or if Siebel Servers are clustered, this step requires considerably more time.

1 hour for each server

6

 

Apply a Siebel Maintenance Release, if applicable, to the Siebel Gateway, Siebel Server, Tools, and Client.

 

7

 

Install the version 7.5 Siebel Database Server software onto one Siebel Server that has already been upgraded to version 7.5.

30 min.

8

 

Install version 7.5 Siebel Web Server Extension.

1 hour

9

Siebel Upgrade Consultant

Upgrade the Siebel database schema, following the procedure in Upgrade Guide for Microsoft Windows.

7 hours

10

 

Print the list of acceptable errors, errors.rtf, located under SIEBEL_ROOT\dbsrvr\oracle.

 

11

 

Back up the database schema upgrade log files from SIEBEL_ROOT\siebsrvr\log:

n upgwiz.log

n upgwiz_01.log, and so on

Review all errors against the acceptable errors listed in errors.rtf. If you encounter an error that does not appear in errors.rtf, then it is an unacceptable error. Report the condition to Siebel Technical Support, do not rerun the Upgrade Wizard, and do not proceed with the upgrade. See Upgrade Guide for Microsoft Windows for more information.

 

12

Siebel Upgrade Consultant, DBA

Back up the premerge development environment database.

This backup will enable you to restore to your pre-merge database if you need to recover from a failed merge.

 

13

Siebel Upgrade Consultant

Verify that the database backup made in Step 12 was successful.

 

14

DBA

Optimize your Oracle 8.1.7 database to improve performance of a repository merge. See Upgrade Guide for Microsoft Windows for instructions.

 

15

Siebel Upgrade Consultant

Copy all files from the 6.3 file system to the \att subdirectory of the version 7.5 Siebel File System.

Update the file system for attachment records that are based on obsolete tables.

 

16

 

Add Siebel 7 license keys using Siebel Tools version 7.5.

 

17

Siebel Upgrade Consultant

Prepare the Prior Customer Repository for the merge in Siebel Tools 7.5.

n Migrate strings

n Merge labels and fields

n Merge Web templates

Locate the following files in Tools\TEMP\

n Labelmerge.txt

n Templatemerge.txt

30 min.

18

 

Review and back up the string migration log file: SIEBEL_ROOT\tools\objects\stringmigration.log.

 

19

 

Set ancestry objects for applets, business components, integration objects, and reports.

Setting ancestry objects must be performed after upgrading the repository (upgrep) and before the repository merge.

1-3 hours

20

 

Optimize the machine on which you are running the repository merge. See Upgrade Guide for Microsoft Windows for instructions.

 

21

 

Perform the repository merge using Siebel Tools version 7.5. See Upgrade Guide for Microsoft Windows for instructions.

6 hours;

10-16 hours for highly customized applications

22

 

Review merge status in Siebel Tools to make sure the status is Complete. See Upgrade Guide for Microsoft Windows for instructions.

 

23

 

Review object attribute differences for conflicts that may have occurred during repository merge.

n Review the Object Differences applet of the Application Upgrade Object list view.

n Review the Attribute Differences applet of the Application Upgrade Attributes list view.

See Upgrade Guide for Microsoft Windows for instructions to resolve conflicts.

8 hours

24

Siebel Upgrade Consultant

If the merge failed, restore the database from the backup made in Step 12, and restart from Step 15.

The merge is a critical step of upgrade. If the merge failed, it's safe to restart from where the upgrade of your Siebel database schema finished.

 

25

 

Review the repository merge log files.

n Review the merge.txt file under SIEBEL_ROOT\Tools\bin.

n Review and backup upgwiz*.log files.

 

26

Siebel Upgrade Consultant, DBA

Backup the database after a successful repository merge.

 

27

Siebel Upgrade Consultant

Verify that the database backup made in Step 26 was successful.

 

28

 

Generate EIM temporary columns for custom mappings. In Siebel 7.5 Tools, choose Tools > Upgrade > Generate EIM Processing Columns.

1 min.

29

 

Upgrade the custom database schema, following the procedure in Upgrade Guide for Microsoft Windows.

1 hour

30

 

Back up the database schema upgrade log files from SIEBEL_ROOT\siebsrvr\log:

n upgwiz.log

n upgwiz_01.log, and so on

Review all errors against the acceptable errors listed in errors.rtf. as you did in Step 11.

 

31

 

Review the list of business components that require manual migration: SIEBEL_ROOT\siebsrvr\log\upgcust.log.

Business components that require manual migration are those that are mapped to obsolete tables, or those that contain fields that are mapped to the extension columns of the obsolete tables.

 

32

 

Query in Siebel Tools version 7.5 to verify that New Customer Repository was renamed to Siebel Repository.

 

33

Siebel Upgrade Consultant, DBA

Back up the upgraded development environment database.

 

34

Siebel Upgrade Consultant

Verify that the database backup made in Step 33 was successful.