Bookshelf Home | Contents | Index | PDF     

Siebel Database Upgrade Guide > Performing the Siebel Incremental Repository Merge > Process of Upgrading the Siebel Development Environment from Siebel CRM Version 8.1.1.x (SIA Repository) >

Upgrading the Siebel Database Schema

This task is a step in Process of Upgrading the Siebel Development Environment from Siebel CRM Version 8.1.1.x (SIA Repository). Use this task to upgrade the Siebel database schema.

NOTE:  Before you upgrade the Siebel database schema using the upgrep process, it is strongly recommended to back up the entire database. This step is mentioned in Table 30, as Step 21. If this upgrade operation fails, then you can restore the database to its preupgrade state, and rerun the upgrade operation.

To upgrade the Siebel database schema

  1. Execute the Siebel Database Configuration Wizard by specifying the following parameter values:
    • Environment Type: Development
    • Upgrade Options: Upgrade Siebel Database Schema (upgrep)
  2. Start the Siebel Upgrade Wizard.

    The Siebel Upgrade Wizard reads the steps from the driver file, which is determined by your Siebel CRM version. The Siebel Upgrade Wizard performs the commands listed in the steps. The driver file shown in Table 30 contains the following information:

    • Environment: Development
    • Upgrade mode: upgrep
    • Database: Oracle
    • Multilingual: No
  3. After the incremental repository merge has been completed successfully, review the merge log files in SIEBEL_TOOLS_ROOT\log.

See Table 30 for the Siebel Upgrade Wizard steps.

Table 30. Steps That the Siebel Upgrade Wizard Executes
Step
Script or Input File
Description
Comments
1 Verify Siebel Version

verify_siebel_ver.sql

Verifies whether the correct Siebel CRM version (from which you are upgrading) was selected when the Siebel Database Configuration Wizard is started.

If this step stops because of an error, then it was because the wrong Siebel CRM version was selected during the launch of the Database Configuration Wizard. Select the Current Siebel Version as explained in Table 27.

  1. Verify Repository Name

rename_existing_repositories.sql

Renames the Siebel Repository to Prior Customer Repository.

None.
  1. Drop Interface tables

dropif-db.sql

Removes all Siebel Enterprise Integration Manager tables.

None.
  1. Drop triggers

trigdrop-db.sql

Removes all dynamically created triggers.

None.
  1. Remove database-level functions and procedures

drop_db_func_proc.sql

Removes the exchange rate function: exrate.

None.
  1. Prepare for table creation

pret_irm.sql

Performs DDL operations, such as adding columns to tables.

Performs DML operations, such as revising date formats.

None.
  1. Create and update tables

ddlimp utility

ddl.ctl as input

The ddl.ctl file specifies the structure of tables to be created or updated.

None.
  1. Prepare for index creation

preschm_irm.sql

Performs DML operations. Moves data between tables. Changes the data in the existing fields, depending on the specified conditions.

None.
  1. Create indexes

ddlimp utility

ddl.ctl as input

The input file specifies the structure of indexes to be created.

None.
  1. Import seed data

dataimp utility

seedupg0.inp as input

seedupg1.inp as input

seedupg_locale.inp as input

Before importing seed data, the dataimp utility deletes the existing seed data.

The three seedupg files contain filters that the dataimp utility uses to prevent the deletion of seed data that you have modified or seed data that meets specified criteria.

Unmodified seed data has a last update date (LAST_UPD) of 1980-01-01. The dataimp utility does not delete records in which the last update date (LAST_UPD) is later than this date.

None.
  1. Upgrade data after seed data import

upg_data_afterseed.sql

upg_data_afterseed_sia.sql

Updates existing seed data if any new columns have to be populated.

None.
  1. Set system pref for Codepage DB

set_codepage.sql

Sets the database code page in the S_SYS_PREF table.

None.
  1. Set system pref for unicode DB

set_unicode.sql

Sets the Unicode code page to UTF-8 in the S_SYS_PREF table.

None.
  1. Update version component information

upd_upgcomp.sql

Updates the S_UPG_COMP table with the product release level. Also updates the location of the SRF file. The S_UPG_COMP table stores version information for application executables.

None.
  1. Run Oracle-specific DDL commands

ddlora.sql

Creates Oracle-specific DDL information, such as default storage parameters for docking objects, repository objects, and seed objects.

None.
  1. Update Siebel database version

update_ver.sql

seeduver.sql

The update_ver.sql script creates a temporary table, S_APP_VER_TEMP, which contains new version information for the database schema. The seeduver.sql script updates the S_APP_VER table with this information.

None.
  1. Export Prior Customer Repository

repimexp utility

Export Prior Customer Repository

Exports the existing Prior Customer Repository to create New Customer Repository.

None.
  1. Import Prior Siebel, New Siebel and New Customer repositories in parallel

repimexp utility

Import the Prior Siebel Repository, New Siebel Repository, and New Customer Repository.

Imports the Prior Siebel Repository, New Siebel Repository, and New Customer Repository in parallel to the repository tables.

If this step produces an error while creating the New Customer Repository, check the log file in: SIEBEL_ROOT\siebsrvr\log\upgrade_path\output).

For Oracle Database: If you receive an error similar to the following, then you must restart the upgrade from the previous step Export Prior Customer Repository by changing the state.log of that step to Incomplete.

Error message: [DataDirect][ODBC Oracle driver][Oracle]ORA-12899: value too large for column "S_ACCELERATOR"."INACTIVE_FLG" (actual: 4, maximum: 1)
  1. Install SQL packages

seeduver.sql

Verifies that correct versions are set in the S_APP_VER table.

None.

ifstrg.sql

Sets the storage parameters for Siebel Enterprise Integration Manager tables.

None.

ifindxstrg.sql

Sets the storage parameters for Siebel Enterprise Integration Manager table indexes.

None.

pkgseq.sql

Adds a suffix to row IDs in the S_SEQUENCE table. Ensures that row IDs are unique.

The pkgldel.sql script defines s_txn_log_del_proc. The procedure periodically deletes transactions from the S_DOCK_TXN_LOG file. It also deletes rows from the S_DOCK_TXN SET table. This action prevents the need for a large rollback segment.

None.

trgreset.sql

Ensures that denormalized rows in the S_TERR table have the correct values.

None.

ddlseq.sql

Sets the sequence numbers for the specified tables.

None.

pkgvis.sql

Creates a function that modifies how Oracle Optimizer performs the visibility check.

None.
  1. Create temporary indexes for merge performance

crt_temp_indexes_merge.sql

Creates temporary indexes to improve the merge performance.

None.
  1. Take backup of the Siebel database and update database statistics

None

Pauses the Siebel Upgrade Wizard to enable a database backup and the execution of database statistics before the merge.

At this point in the upgrade, back up the database, and execute database statistics, then click Yes to continue the upgrade.

To stop at this step and restart the wizard later, click No.

To resume the upgrade, see Preparing to Start the Siebel Upgrade Wizard.
  1. Execute Incremental Repository Merge

siebdev

Starts the incremental repository merge automatically for Windows. If you are using a Windows computer and Siebel Tools is installed for Siebel Enterprise servers in UNIX environment, then you must perform this step manually.

For UNIX or Linux:
You must execute the incremental repository merge process manually. (On Microsoft Windows, incremental repository merge starts automatically.) See Executing Incremental Repository Merge on UNIX.

  1. Generate Merge Report

MergeReport.jar

Generates the hierarchical merge report in HTML format.

Also creates the file IRM_Merge*_ERROR.txt in SIEBEL_TOOLS_ROOT\log, which contains only the errors that are present in the IRM_Merge*.txt file.

For more information about the hierarchical merge report, see Reviewing the Hierarchical Merge Report.

For UNIX or Linux:
You must generate the hierarchical merge report manually, by running MergeReport.bat. Typically, you run this report after running incremental repository merge. (On Microsoft Windows, this report runs automatically.)
  1. Upgrade history

store_history.sql

Stores the upgrade history in the S_INST_UPG_HIST table.

None.
      
Siebel Database Upgrade Guide Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices.