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 the following task to upgrade the Siebel database schema.

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 29 contains the following information:

    • Environment: Development
    • Upgrade mode: upgrep
    • Database: Oracle
    • Multilingual: No
    • See Table 29 for the Siebel Upgrade Wizard steps.
      Table 29. Siebel Upgrade Wizard Steps
      Step
      Script or Input File
      Description
      Comments
      1 Verify Siebel Version

      verify_siebel_ver.sql

      Verifies whether the correct Siebel CRM version has been selected when the Siebel Database Configuration Wizard is started. This step applies only to upgrades from Siebel CRM version 8.1.1.10, and it is used to verify whether the database and the Siebel application have been upgraded to version Siebel CRM version 8.1.1.10, using the incremental repository merge.

      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 Server Configuration Wizard. You must configure the database server again by selecting the current Siebel CRM version as v8_1_1SIA_To_v8_1_1_9SIA.
      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 under: Siebel server installation directory\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 DB and update DB stats

      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. Compile SRF

      siebdev

      Compiles the SRF file automatically for Windows.

      If you are using a Windows computer, and if Siebel Tools is installed for Siebel Enterprise servers in UNIX environment, then you must perform this step manually.

      For Windows:

      This step automatically starts Siebel Tools to compile the SRF file of New Siebel Repository. The SRF file is called IRM_PreCompile.srf, and it is created in the following directory: Siebel Tools Installation Directory\OBJECTS\Language.

      If the compilation is successful, then the existing siebel_sia.srf is renamed to siebel_sia_preIRM.srf, and the IRM_PreCompile.srf file is copied as siebel_sia.srf.

      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 Windows: Incremental repository merge is started automatically. You must execute the process manually under UNIX. See Executing Incremental Repository Merge Under UNIX.

      Upgrade history

      store_history.sql

      Stores the upgrade history in the S_INST_UPG_HIST table.

      None.
  3. After the incremental repository merge has been completed successfully, review the merge log files under: Siebel Tools installation directory\LOG.
    
Siebel Database Upgrade Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.