Share

How To Correct Repositories With Incorrect or Missing INTL Records When Installing or Upgrading To Siebel Versions 7.7 or 7.8

If you are installing or upgrading to Siebel versions 7.7 or 7.8, review and complete the steps in this document to ensure that the New Customer Repository contains only valid records for repository strings stored in the _INTL tables. 

In some cases erroneous NULL value INTL records may exist. These records must be deleted in order for the new symbolic string model to properly display your string values. To correct the INTL records and have the symbolic string model treat the records correctly and display the correct text value, you need to run the utility provided in this document.

Run the provided utility when upgrading or installing to Siebel versions 7.7 or 7.8 to ensure that any NULL value INTL records are corrected. 

Possible Symptoms

Failure to run the scripts provided in this document prior to your next upgrade results in some language strings (new Siebel terminology) after future upgrades not being displayed. Instead, the corresponding language string values in the prior Siebel release displays in the application UI. It is very difficult to correct these issues once you upgrade to the next version of the Siebel application without running the scripts described in this document. 

Workaround or Resolution

All customers upgrading to Siebel versions 7.7 or 7.8 should run this utility immediately after the successful completion of the repository merge process during the development upgrade. Customers installing Siebel versions 7.7 or 7.8 should run this utility after completing the installation. 

Repository to Use: 

  • Customers who are upgrading from a previous version should run this utility against the New Customer repository.  
  • Customers who did not run this tool during the Siebel 7.7 or 7.8 upgrade should run this utility against the Siebel Repository.  
  • Customers who performed a new installation of Siebel 7.7 or 7.8 should run this utility against the Siebel Repository.  

Complete the steps outlined below to correct any NULL INTL records. 

  1. Update the redundant string overrides. 
  1.  
    1. Download the soret_update.sql file available at the end of this section to the $SIEBEL_ROOT\siebsrvr\bin directory, where $SIEBEL_ROOT is the root directory where you installed the Siebel Server.

 

  1.  
    1. On Windows, open a command window from within the administrative client. To launch a command window, select Start > Programs > Accessories > Command Prompt. If you are running the database server client on UNIX, open a Korn Shell window and continue with the following steps.

 

  1.  
    1. Go to the $SIEBEL_ROOT\siebsrvr\bin directory.

 

  1.  
    1. Run the following command at the command prompt:

 

odbcsql /s odbc_dsn /u table_owner /p table_owner_password /r / /v /l log_file soret_update.sql table_owner ”Repository_Name”

 

where:

 

Parameter

Value

odbc_dsn name of your ODBC source
table_owner table owner
table_owner_password password for table owner
log_file name of log file to contain query results
Repository_Name repository name to run this script against

 

NOTE: Repository_Name must be specified in double quotation marks.

 

  1. Delete the obsolete locale records.

 

  1.  
    1. Download the soret_delete.sql file available at the end of this section under the $SIEBEL_ROOT\siebsrvr\bin directory, where $SIEBEL_ROOT is the root directory where you installed the Siebel Server.

 

  1.  
    1. On Windows, open a command window from within the administrative client. To launch a command window, select Start > Programs > Accessories > Command Prompt. If you are running the database server client in UNIX, open a Korn Shell window and continue with the following steps.

 

  1.  
    1. Go to $SIEBEL_ROOT\siebsrvr\bin directory.

 

  1.  
    1. Run the following command at the command prompt:

 

odbcsql /s odbc_dsn /u table_owner /p table_owner_password /r / /v /l log_file soret_delete.sql table_owner ”Repository_Name”

 

where:

 

Parameter

Value

odbc_dsn name of your ODBC source
table_owner table owner
table_owner_password password for table owner
log_file name of log file to contain query results
Repository_Name repository name to run this script against

 

NOTE: Repository_Name must be specified in double quotation marks.

 

  1. Verification

 

Re-run steps 1 and 2 to confirm that the repository has been cleaned of the redundant string overrides. Review the log files for each query to confirm that all of the queries returned zero counts. Make sure to create new log files (by renaming the log files) to avoid overwriting the original version.

 

Below are examples for running the scripts on the various database platforms.

 

Oracle:

 

odbcsql /s SblDev /u ora04523 /p ora04523pwd /r / /v /l soret_repository_update.log soret_update.sql ora04523 “New Customer Repository”

 

where:

 

Parameter Value

Description

SblDev name of your ODBC source
ora04523 table owner
ora04523pwd password for table owner
soret_repository_update.log name of log file to contain query results created under $SIEBEL_ROOT\siebsrvr\bin
soret_update.sql SQL file to execute
New Customer Repository repository name to run this script against

 

DB2UDB:

 

odbcsql /s SblDev /u siebel /p db2 /r / /v /l soret_repository_update.log soret_update.sql siebel “New Customer Repository”

 

where:

 

Parameter Value

Description

SblDev name of your ODBC source
siebel table owner
db2 password for table owner
soret_repository_update.log name of log file to contain query results created under $SIEBEL_ROOT\siebsrvr\bin
soret_update.sql SQL file to execute
New Customer Repository repository name to run this script against

 

DB2 OS/390:

 

odbcsql /s SblDev /u sadmin /p db2 /r / /v /l soret_repository_update.log soret_update.sql siebel “New Customer Repository”

 

where:

 

Parameter Value

Description

SblDev name of your ODBC source
sadmin user name
db2 password for user name
soret_repository_update.log name of log file to contain query results created under $SIEBEL_ROOT\siebsrvr\bin
soret_update.sql SQL file to execute
siebel table owner
New Customer Repository repository name to run this script against

 

MSSQL Server:

 

odbcsql /s SblDev /u MS04221 /p MSSQL /r / /v /l soret_repository_update.log soret_update.sql dbo “New Customer Repository”

 

where:

 

Parameter Value

Description

SblDev name of your ODBC source
MS04221 table owner
MSSQL password for table owner
soret_repository_update.log name of log file to contain query results created under $SIEBEL_ROOT\siebsrvr\bin
soret_update.sql SQL file to execute
dbo must be specified as dbo for SQL Server
New Customer Repository repository name to run this script against

 

Download alert1008-1_soret.zip which contains the soret_update.sql and soret_delete.sql files. 

  1.  
    1. Download the soret_update.sql file available at the end of this section to the $SIEBEL_ROOT\siebsrvr\bin directory, where $SIEBEL_ROOT is the root directory where you installed the Siebel Server.

 

  1.  
    1. On Windows, open a command window from within the administrative client. To launch a command window, select Start > Programs > Accessories > Command Prompt. If you are running the database server client on UNIX, open a Korn Shell window and continue with the following steps.

 

  1.  
    1. Go to the $SIEBEL_ROOT\siebsrvr\bin directory.

 

  1.  
    1. Run the following command at the command prompt:

 

odbcsql /s odbc_dsn /u table_owner /p table_owner_password /r / /v /l log_file soret_update.sql table_owner Repository_Name

 

where:

 

Parameter

Value

odbc_dsn

name of your ODBC source

table_owner

table owner

table_owner_password

password for table owner

log_file

name of log file to contain query results

Repository_Name

repository name to run this script against

 

NOTE: Repository_Name must be specified in double quotation marks.

 

  1. Delete the obsolete locale records.

 

  1.  
    1. Download the soret_delete.sql file available at the end of this section under the $SIEBEL_ROOT\siebsrvr\bin directory, where $SIEBEL_ROOT is the root directory where you installed the Siebel Server.

 

  1.  
    1. On Windows, open a command window from within the administrative client. To launch a command window, select Start > Programs > Accessories > Command Prompt. If you are running the database server client in UNIX, open a Korn Shell window and continue with the following steps.

 

  1.  
    1. Go to $SIEBEL_ROOT\siebsrvr\bin directory.

 

  1.  
    1. Run the following command at the command prompt:

 

odbcsql /s odbc_dsn /u table_owner /p table_owner_password /r / /v /l log_file soret_delete.sql table_owner Repository_Name

 

where:

 

Parameter

Value

odbc_dsn

name of your ODBC source

table_owner

table owner

table_owner_password

password for table owner

log_file

name of log file to contain query results

Repository_Name

repository name to run this script against

 

NOTE: Repository_Name must be specified in double quotation marks.

 

  1. Verification

 

Re-run steps 1 and 2 to confirm that the repository has been cleaned of the redundant string overrides. Review the log files for each query to confirm that all of the queries returned zero counts. Make sure to create new log files (by renaming the log files) to avoid overwriting the original version.

 

Below are examples for running the scripts on the various database platforms.

 

Oracle:

 

odbcsql /s SblDev /u ora04523 /p ora04523pwd /r / /v /l soret_repository_update.log soret_update.sql ora04523 New Customer Repository

 

where:

 

Parameter Value

Description

SblDev

name of your ODBC source

ora04523

table owner

ora04523pwd

password for table owner

soret_repository_update.log

name of log file to contain query results created under $SIEBEL_ROOT\siebsrvr\bin

soret_update.sql

SQL file to execute

New Customer Repository

repository name to run this script against

 

DB2UDB:

 

odbcsql /s SblDev /u siebel /p db2 /r / /v /l soret_repository_update.log soret_update.sql siebel New Customer Repository

 

where:

 

Parameter Value

Description

SblDev

name of your ODBC source

siebel

table owner

db2

password for table owner

soret_repository_update.log

name of log file to contain query results created under $SIEBEL_ROOT\siebsrvr\bin

soret_update.sql

SQL file to execute

New Customer Repository

repository name to run this script against

 

DB2 OS/390:

 

odbcsql /s SblDev /u sadmin /p db2 /r / /v /l soret_repository_update.log soret_update.sql siebel New Customer Repository

 

where:

 

Parameter Value

Description

SblDev

name of your ODBC source

sadmin

user name

db2

password for user name

soret_repository_update.log

name of log file to contain query results created under $SIEBEL_ROOT\siebsrvr\bin

soret_update.sql

SQL file to execute

siebel

table owner

New Customer Repository

repository name to run this script against

 

MSSQL Server:

 

odbcsql /s SblDev /u MS04221 /p MSSQL /r / /v /l soret_repository_update.log soret_update.sql dbo New Customer Repository

 

where:

 

Parameter Value

Description

SblDev

name of your ODBC source

MS04221

table owner

MSSQL

password for table owner

soret_repository_update.log

name of log file to contain query results created under $SIEBEL_ROOT\siebsrvr\bin

soret_update.sql

SQL file to execute

dbo

must be specified as dbo for SQL Server

New Customer Repository

repository name to run this script against

 

Download alert1008-1_soret.zip which contains the soret_update.sql and soret_delete.sql files.

Leave A Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!