Siebel Upgrade Process

S.No			Task
Pre-Upgrade Tasks - Hardware/Software
1			Verify you have identified all the maintenance releases, Fix Packs, and quick-fix patches required for the upgrade.
2			Upgrade the RDBMS to Oracle 10g.
3			Install 7.8.2 Siebel Tools on development workstation
4			Install the Gateway Name Server, Siebel Servers, and Siebel Database Server files on the Siebel Server you will use to perform the upgrade.
5			Before starting Webserver Extensions Installation ensure that the IISLockdown Tool is unlocked
6			Install the Siebel Web Server Extension (SWSE).
7			After Successful installation,Relock the IISLockdown and Restart server
8			Change the value of the OverWriteConfig parameter to “Yes” in the siebel.ini files under the various locations: Siebel_Enterprise_Server\\siebel.ini Siebel_Enterprise_Server\siebel.ini Siebel_Web_Server_Extension\ \siebel.ini Siebel_Web_Server_Extension\siebel.ini Siebel_Web_Client\\siebel.ini Siebel_Web_Client\siebel.ini
9			Apply the Siebel Fix Pack version 7.8.2.5 for all Siebel components.
10			Clear the Browser Cache and remove all ActiveX files: Do not delete the files but remove them via the browser menu Tools > Internet Options > Settings > View Objects, right-click on each and select the Remove option. Alternatively, log a new Service Request requesting the ActiveX clean-up utility to automate removal.
11			Upgrade third-party software: Actuate Server
12			Upgrade Operating system software: WINDOWS or UNIX.
13			Create test data in 7.5.3 application.
Pre-Upgrade Tasks - Siebel Database
14			Review Siebel Technical Notes and Siebel Alerts on upgrading to the current release.
15			Review Technical Note 521.
16			Review guidelines for configuring the RDBMS.
17			Verify all developers have checked in their projects.
18			Verify that the Workflow Monitor and Workflow action agents have processed all pending requests
19			Backup the 7.5.3 database.
20			Back up of .SAF files from filesystem directory of 7.5.3.
21			Backup the stored procedures, views, triggers, indexes, and packages etc.,
22			Identify the obsolete columns which were used in 7.5.3 IFB files.
23			Backup the 7.5.3 database
24			Delete any unnecessary repositories from Siebel Tools and verify there are no open DB connections.
25			Drop temporary tables and non-Siebel tables.
26			Disable customized triggers.
27			Drop defined database views on Siebel tables.
28			Export EIM table data that you want to preserve. Truncate EIM table data
29			Notate any custom indexes that were created outside of Siebel Tools
30			Notate Custom indexes against extension columns on obsolete tables.
31			Notate Custom indexes on interface tables.
Pre-Upgrade Tasks - Oracle
32			Create a copy of the 7.5.3 database
33			Verify Oracle sort order is set to 'BINARY' by running the following query: select VALUE from nls_database_parameters WHERE PARAMETER='NLS_SORT'
34			Verify that your Oracle clients and Oracle database server are at the same release level.
35			verify tablespaces have enough free space to accommodate expected growth. Increase if necessary
36			compute a high enough value for pctincrease on tablespaces that contain application tables and indexes so that upgrading does not create a large number of extents.
37			Rebuild the larger tables in Siebel with a large value for pctfree (30 or higher)
38			DB_CACHE_SIZE. Set this parameter to a minimum of 600 megabytes
39			SORT_AREA_SIZE. Set this parameter to a minimum of 1524288.
40			Verify that init.ora paremeters sort_area_retained size ,log_buffers are set appropirately.
41			Verify that there is only one large rollback segment on line that is appropriately sized so that the largest of transactions can be accommodated. Take all other rollback segments off line.
42			Verify that the following parameters are set correctly (Only Oracle DB with Multiple CPUs): (1) parallel_max_servers should be > 1 (2) Check parallel_max_servers and _db_block_lru_latches parameters
43			Verifying the Oracle ODBC Definition on Siebel 7.8.2 Server. In the Registry editor , navigate to HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.INI\ODBC_Name and verify that the following entries are present: Name Type Data ColumnsAsChar REG_SZ 1 ColumnSizeAsCharacter REG_SZ 1
44			Create a new ODBC connection to the "COPY" of 7.5.3 Siebel Database. Name it: Siebel753Server
45			Set Optimizer mode to Rule Based Optimizer (RULE) or Cost Based Optimizer (COST). Make update to init.ora
46			Run the Oracle Analyze command on the Siebel database.
Pre-Upgrade Tasks - Application Data
47			Deactivate all workflow processes before doing the upgrade.
48			Verify that all tasks with status = QUEUED are removed from S_SRM_REQUEST and S_DOCK_TXN tables.
49			Verify all customized workflows and all seed workflows from the production database are present in the development environment Siebel Database
50			Perform a partial synchronization for mobile users, sending all transactions to the server database.
51			Verify that Mobile Web Clients have synchronized and that all changes have been merged into the server database as follows: Check that no transaction files remain in the synchronization inbox and outbox for any mobile user. The synchronization inbox for each user is on the Siebel Server: Windows: SIEBEL_ROOT\docking\MOBILEUSERNAME. Transaction files are in the format number.dx; for example, 00000023.dx.
52			Log onto a Siebel Business Application, such as Call Center, as the Siebel Administrator. Use the Server Administration - Server Tasks screen to make sure that each Transaction Merger task has successfully completed.
53			Verify that Workflow Monitor and Workflow Action agents have processed all pending requests. If Workflow Manager has completed successfully, the S_ESCL_REQ table should not have any rows.
54			Stop or disable all Siebel Remote components on all Siebel Servers.
55			Disconnect all Web Clients from the Siebel Server by stopping the appropriate Application Object Managers.
56			Make sure that Dedicated Web Clients have disconnected from the Siebel Database Server.
Upgrade Tasks - Upgrade Siebel Database Schema (UPGREP)
57			Log onto Siebel 7.5.3 Tools and connect to the "COPY" 7.5.3 development database
58			Rename the 7.5.3 Siebel Repository to "Prior Customer Repository"
59			Shutdown all Services: Gateway, Siebel Servers, Report Server,Enterprise Server on 7.5.3 Development.
60			Run the Database Server Configuration Utility.
61			Enter the required information when prompted. Upgrade Options -> UPGREP, EnviromentType -> Development. *****THE UPGREP STARTS HERE.*****
62			Migrate Address data from custom extension columns
63			Edit generated SQL files as required by Siebel Technical Notes or Siebel Alerts.
64			Resume the upgrade.Incase the upgrade wizard stops due to error, delete the SIEBEL_ROOT\Log\Process\Output|Output.Log and SIEBEL_ROOT\Log\Process|state\State.Log files.
65			Review upgrade logs for errors after completion. Archive log files
66			Install new license keys. Use Tools
67			Backup upgraded database
Upgrade Tasks - Prepare for Repository Merge
68			Set the Upgrade Ancestor property for copied objects.
69			In the Oracle init.ORA file, Set UNDO_MANAGEMENT = MANUAL before the repository merge. This turns off Automatic Undo Management (AUM). You can turn AUM back on after the repository merge, as desired.
70			Before Merge ,Set the Sieebl Tools Configuration file SQLStyle=Oracle, incase you are using Cost based Optimization.
71			After Merge ,Set the Sieebl Tools Configuration file SQLStyle=OracleCBO, incase you are using Cost based Optimization.
72			Run database statistics on the Siebel Database on the following tables: S_SYM_STR and SYM_STR_INT.
Upgrade Tasks - Perform Repository Merge
73			Verify Upgraded version's tools configuration file has the following parameters: EnableToolsConstrain=FALSE SymStrPrefix=X_ Change to these values as necessary
74			Log onto a workstation that is running 7.8.2 tools and connect to the 7.8.2 database
75			Run Repository Merge **REPOSITORY MERGE STARTS HERE**
76			Check log files for erros upon merge completion
77			Migrate customer workflows
78			Reset Siebel Tools configuration parameters
Upgrade Tasks - Run Post Merge Utilities
79			Rename the existing SIEBEL_TOOLS_INSTALL_DIR\reppatch\log\reputility.log
80			Run Post Merge Utilities in Siebel Tools, navigate to Screens > Application Upgrader > Application Upgrade Object List.
81			Review reputility.log upon completion of post merge utilities
82			Review and verify grid-based applets after the merge
83			Review and verify UI Navigation after the merge
84			Review and verify MVG Applets after the merge
85			Review and verify Rich-Text controls after the merge
86			Review and correct the new aggregate categories that are defined in Screen views
87			Review and verify visibility filters after the merge
88			Review and verify the Chart views after the merge. Assign a category and type to Chart views
89			Review and verify the Explorer views after the merge. Assign a category and type to Explorer views
90			Review and correct navigation to inaccessible detail views after the merge
91			Eliminating obsolete UI fields after the merge
92			Reviewing UI Objects Affected by ICL After the Merge
93			Assigning an Item Identifier to web template items
94			Reviewing Required Fields in the UI After Merge.
95			Setting Label Alignment for Text Fields.
96			Generate EIM temporary columns after the merge
Upgrade Tasks - Upgrade Custom Database Schema (UPGPHYS)
97			Run the DB Server Configuration Utility from Start > Programs > Siebel Enterprise Servers 7.x > Configure DB Server.
98			Verify SIEBEL_ROOT and LANGUAGE enviroment variables are set correctly
99			Enter the required information when prompted. Upgrade Options -> UPGPHYS, EnviromentType -> Development. *****THE UPGPHYS STARTS HERE.*****
100			Review the upgrade logs and address errors. Archive log files
101			Back up the upgraded development database.
Post Upgrade Tasks - Environment Setup
102			Create new SRF File
103			Generate a Siebel Remote database template file.
104			Extract developers databases.
105			Initialize the local database on development machines.
106			Check for inactivated EIM table columns
107			Run database statistics.
Post Upgrade Tasks - Configuration
108			Review obsolete objects in the repository merge
109			Review deleted objects in the repository merge
110			Resolve any business component and join conflicts.
111			Reapply custom extensions and FK columns on obsolete tables
112			Delete unneeded repository files
113			Activate and deploy workflows
114			Verify that EAI and EIM integrations are set up correctly.
115			Updating Enterprise Application Integration (EAI) After Upgrade.
Post Upgrade Tasks - Application Administration
116			Review the results of the Person and Organization merge. Make configuration changes as required.
117			Generating reporting relationships after upgrade.
Perform System Tests
118			Use available test data to perform unit testing. Validate application function in the following areas: 1. User interface 2. Data interfaces 3. Integrity of migrated data 4. Workflow function