Bookshelf Home | Contents | Index | Search | PDF |
Upgrade Guide for UNIX > Postupgrade Tasks > Additional Postupgrade Tasks for Specific Applications >
Postupgrade Tasks for Siebel Financial Services
NOTE: If you are upgrading from Release 7.x to Release 7.5, you do not need to perform these procedures.
If you are upgrading a Siebel Financial Services application, perform the following tasks in addition to the postupgrade tasks described earlier in this chapter.
The information in this section is specific to Siebel Financial Services. If you are not upgrading a Siebel Financial Services application, you should skip this section and go to Postupgrade Tasks for Siebel Life Sciences.
Updating File System Attachments for Call Reports
When you performed the Siebel database upgrade to Release 7.x, call report attachments from
S_ACTIVITY_ATT
migrated toS_COMM_ATT
. This data migration updated the records in the database and the pointer to the physical file, but did 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
.Therefore, you need to run a script to copy and rename all files named
S_ACTIVITY*.SAF
toS_COMM*.SAF
so that they correspond to new table names.To generate the file attachment update script
- From your
$SIEBEL_ROOT/siebsrvr/bin
directory, type the following command:
odbcsql /s "$
ODBC_DATASOURCE
" /u $TABLEOWNER
/p $
PASSWORD /
separator
/ /a /c rem
/o $FILESYSTEM_LOCATION
/mv_act_to_comm_att_unix.ksh/l $
LOGFILE_LOCATION
/mv_act_to_comm_att_unix.log $SCRIPT_LOCATION
/mv_act_to_comm_att_unix.sql /v
"ODBC_DATASOURCE"
= Data source of the database (entered in quotation marks)
PASSWORD
= Tableowner password
FILESYSTEM_LOCATION
= Location of the file systemTo update the file names of call report attachments
Updating File System for Household Notes and Attachments
If 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 Siebel database upgrade to Release 7.x migrated household note attachments from
S_ORGGRP_ATT
toS_CONTACT_ATT
. This data migration updated the records in the database, but did 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.
Therefore, you need to run two scripts to complete this migration. First, run a script to migrate attachments from
S_ORGGRP_ATT
toS_CONTACT_ATT,
and notes fromS_NOTE_ORGGROUP
toS_NOTE_CON
in the database. Then run a script to copy and rename all files namedS_ORGGRP*.SAF
toS_CONTACT*.SAF
so that they correspond to new table names.
- Run
HHMignot.sql
to migrate attachments fromS_ORGGRP_ATT
toS_CONTACT_ATT
.- From
$
SIEBEL_ROOT
/siebsrvr/bin,
enter the following command:
chng_file_sys.ksh -s
SOURCE_TABLE
-t
TARGET_TABLE
-f "
FILE_SYSTEM"
SOURCE_TABLE = Name of the original table
TARGET_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)
chng_file_sys.ksh -s S_ORGGRP_ATT -t S_CONTACT_ATT
-f"D:\DBSRVR_ROOT\files"
- Review the renamed files carefully to verify that they can be accessed by Siebel Financial Services.
Opportunity Product Migration
During the upgrade, data is migrated from S_OPTY_PROD to S_REVN. As a result of this migration, if you have custom objects which point to S_OPTY_PROD, you need to remap the affected base or extension tables. Extension columns pointing to S_OPTY_PROD may need to be repointed 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 Reapplying Custom Extensions and FK Columns on Obsolete Tables.
Bookshelf Home | Contents | Index | Search | PDF |
Upgrade Guide for UNIX Published: 20 October 2003 |