7Preparing a Development Environment for a Siebel Upgrade

Preparing a Development Environment for a Siebel Upgrade

This chapter describes the steps in preparing a development environment for upgrade. It includes the following topics:

• Requirements for Upgrading the Development Environment

• About Moving Tables

• Checking In Development Repository Projects

• Determining Which Template File Was Used During an Extract or Merge

Requirements for Upgrading the Development Environment

Upgrades: All upgrades.

Environments: Development environment only.

Before you upgrade your development environment, make sure that the development database configuration meets the database requirements outlined in Verifying Database Configuration, and meets the requirements depicted in Siebel Installation Guide for the operating system you are using.

If your development environment platform is DB2 for Windows and UNIX, see Siebel Database Upgrade Guide.

If you have not already done so, copy the Upgrade Planning Worksheet, located in Siebel Upgrade Planning Worksheet and fill out the appropriate fields with the information you require to perform the upgrade. Contact your database administrator or systems programmer for help in completing the worksheet. Also, refer to Information Required by the Database Configuration Wizard for a description of the information you are required to enter when you run the Database Configuration Wizard to perform upgrade operations.

About Moving Tables

Upgrades: All upgrades.

Environments: Development environment only.

This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.

Some of the Siebel tables will have columns added to them as part of the upgrade. When this happens, the length of the record will increase, which might cause it to require a larger table space or bufferpool. Moving the identified tables to a new, larger, and differently named table space allows you to maintain the model of multiple tables for each table space which is present for all pre-7.7 schemas.

Before you move the tables, you must remove any standard or custom views using an SQL DROP command.

Note: If you remove an object that you want to reapply to the database after the upgrade is completed, make sure that you can rebuild it. For example, you can obtain a view definition from the DB2 catalog before removing the view so that you can re-create it after the tables have been moved to a larger table space. You can also use third-party products or other methods to preserve objects that are to be reapplied to the upgraded database.

Complete the following procedure to find the views that are defined on a table. The example in the procedure assumes that you are creating a new 16K table space within the same database as the older, smaller table space.

To find views that are defined on a table

• Run the following SQL statement to produce the list of views:

  select * from sysibm.sysVIEWdep
  WHERE Bcreator = ‘yourschema’
  AND BNAME IN ('S_ASSET', 'S_PROD_INT');

  This SQL statement produces the drop statements into a sequential data set:

  SELECT DISTINCT 'DROP VIEW '||'yourschema.'||V.DNAME||' ;'
  FROM SYSIBM.SYSVIEWDEP V
  WHERE V.BNAME IN ('S_ASSET', 'S_PROD_INT')
  AND V.BNAME = 'S_ASSET'
  AND BCREATOR = 'yourschema';

To process these drop statements on the z/OS host, you must create a PDS member with the output from the preceding statement. Then submit this member through DSNTEP2 using JCL.

If you are using the preconfigured storage control file, you do not have to move any tables as a preupgrade task. This is because the existing schema is not being preserved and all tables will be recreated in the 1:1:1 model.

Checking In Development Repository Projects

Upgrades: All upgrades.

Environments: Development environment only.

Developers who are using Siebel Tools with a local database must check in their projects to the development repository.

Make sure that all project locks in your current Siebel repository have been released to prevent inadvertent loss of development work during the upgrade.

If you are using Siebel Workflow Manager, you must run the Workflow Monitor Agent and Workflow Action Agent to completion before upgrading to the current Siebel CRM release. The S_ESCL_REQ table does not have any rows if Workflow Manager has completed successfully.

Determining Which Template File Was Used During an Extract or Merge

Upgrades: All upgrades.

Environments: Development environment only.

This topic describes how to determine which template file was used for an extract or merge operation when a storage control file is created.

This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.

To determine the template file that was used for an extract or merge operation

1. Open the dbextract.log file and review the command line that was entered.

2. Check the value for the /i parameter. You can also check the upgwiz.log file for the strgupgd.exe command string.

   /i D:\18025\dbsrvr\db2390\storage_p_u.ctl
   
   UpgradeLogUpgradeInfo30000000254290624:0 2014-09-29 12:06:59 Executing 
   (C:\81_23039QF3_390CV\ses\siebsrvr\bin\strgupgd.exe /s 
   C:\81_23039QF3_390CV\ses\dbsrvr\db2390\storage_p_u.ctl /d 
   C:\81_23039QF3_390CV\ses\dbsrvr\db2390\SStempstore.txt /i 
   C:\81_23039QF3_390CV\ses\dbsrvr\db2390\strgvar.inp /m 
   C:\81_23039QF3_390CV\ses\siebsrvr\bin\master_dbconfig_extract_merge_mf.ucf)