Upgrade Guide for DB2 UDB for z/OS > Postupgrade Tasks for Applications >

Upgrading File System for Household Notes and Attachments

Upgrades: Release 6.2.1 only.

Environments: Production test, production.

This topic is part of an upgrade process. See How to Perform the Upgrade.

If you are upgrading a Siebel Financial Services application, and you are migrating your implementation to the new household design, perform the following procedure to update the file system for household notes and attachments.

The upgrade migrates household note attachments from S_ORGGRP_ATT to S_CONTACT_ATT. This updates the records in the database, but does not update file system attachments, which use a naming convention that includes the name of the table they are associated with: TableName_RowID_Revision#.saf.

You must run two scripts to complete this migration. First, run a script to migrate attachments from S_ORGGRP_ATT to S_CONTACT_ATT, and notes from S_NOTE_ORGGROUP to S_NOTE_CON in the database. Then, run a script to copy and rename all files named S_ORGGRP*.SAF to S_CONTACT*.SAF so that they correspond to new table names.

To update file attachments

1. Run Mig_HH_note_att.sql to migrate attachments from S_ORGGRP_ATT to S_CONTACT_ATT.
2. Navigate to the following directory:

   Windows: SIEBEL_ROOT\bin

   UNIX: $SIEBEL_ROOT/bin

3. Run the following utility:

   Windows: chng_file_sys.bat OLD_TABLE NEW_TABLE "FILE_SYSTEM"

   UNIX: chng_file_sys.ksh -s OLD_TABLE -t NEW_TABLE -f "FILE_SYSTEM"

   where:

   • OLD_TABLE = Name of the original table.
   • NEW_TABLE = Name of the new table to which the original data was migrated.
   • "FILE_SYSTEM" = Name of the directory where the file system resides (entered inside quotation marks).

     Windows example:

   chng_file_sys.bat S_ORGGRP_ATT S_CONTACT_ATT "C:\siebfile\att"

   UNIX example:

   chng_file_sys.ksh -s S_ORGGRP_ATT -t S_CONTACT_ATT
-f "/usr/siebel/siebfile/att"

4. Review the renamed files carefully to verify that they can be accessed by Siebel Financial Services applications.

Opportunity Product Migration

During the upgrade, data is migrated from S_OPTY_PROD to S_REVN. As a result, if you have custom objects that point to S_OPTY_PROD, you must remap the affected base or extension tables. You may have to remap extension columns pointing to S_OPTY_PROD as well.

The following base or extension tables are affected in the migration from S_OPTY_PROD to S_REVN:

For example, if a child object pointed to S_OPTY_PROD, that child object needs to be manually remapped to S_REVN.

A report generated during the upgrade identifies which columns or tables you need to examine. This report, xtndobstbl.log, lists extension columns that reside on obsolete tables and therefore need to be moved to alternate tables. For more information about reapplying custom extension columns on obsolete tables, see Checking for Inactivated EIM Table Columns.