Upgrade Guide for UNIX > Postupgrade Tasks >

Upgrading to RC2 Encryption

Release 7.5 delivers a new default encryption method based on the RC2 standard. The previous default encryption method (the Release 6.x or 7.x standard encryptor) is no longer supported, and data that used the standard encryptor cannot be read by 7.5 applications unless you upgrade your encryption method to RC2. Use the Encryption Upgrade Utility to convert unencrypted data and data that was encrypted using the standard encryptor to the RC2 encryption method.

CAUTION:  Using a non-RC2 encryption method in a Unicode environment results in irrecoverable data loss.

Perform the following procedures to upgrade your encryption method:

Prerequisites for Upgrading to RC2 Encryption

In order to upgrade to the RC2 encryption method, the following prerequisites must be fulfilled:

Modifying the Input File

The input file encrypt_colums.inp indicates the table and column that store the encrypted data, and the table and column that store the key index. The input file is located in $SIEBEL_ROOT/ dbsrvr/bin directory. If you wish to execute the utility from the command line, place this file in the $SIEBEL_ROOT/ siebsrvr//bin directory.

The input file must include every column that you want to upgrade. The first line of the input file indicates a table name with brackets around it. The table name should be followed on subsequent lines by all the columns to be upgraded for that table. Each column requires a table column to store the key index, so this is specified after the column name; for example:

[TABLE_NAME]
COLUMN_NAME TABLE_NAME_FOR_KEY COLUMN_NAME_FOR_KEY

After each table, skip a line, and continue with subsequent tables. Here is a sample input file:

[S_ORDER]
CC_NUMBER S_ORDER CCNUM_ENCRPKEY_REF

[S_DOC_ORDER]
CC_NUMBER S_DOC_ORDER CCNUM_ENCRPKEY_REF

[S_PER_PAY_PRFL]
PAY_ACCNT_NUM S_PER_PAY_PRFL CCNUM_ENCRPKEY_REF

To support upgrade of non-encrypted field to RC2 encryption, add the letter N to the end of the column; for example:

[S_NEW_TABLE]
NAME S_NEW_TABLE NAME_KEY_INDEX N

Changing User Properties

If you customized business component fields to use the old encryption method (the standard encryptor), make sure that your custom buscomp field user properties are defined with the values provided in the table below. (An example is provided for the Quote business component.)

NOTE:  By default, data encrypted using the old encryption method uses ROW_ID as the Encrypt Key Field. You may need to create a calculated field on each business component for the Encrypt Read Only Field.

Field User Property
Value
Example for the Quote BusComp
Encrypted
Y
Y
Encrypt Service Name
RC2 Encryptor
RC2 Encryptor
Encrypt Key Field
Key Index Field
Credit Card Number Key Index
Encrypt Read Only Field
Read Only Field
Credit Card Number Read Only

Changing the Password or Adding a New Key to a Database

If you need to change the password or add a new key to your database, perform the following steps.

To change the password or add a new key

Upgrading Your Encryption Method

Follow the instructions below for the encryption you are going to use: 56-bit encryption or 128-bit encryption.

To upgrade to 128-bit encryption (for the Strong Encryption Pack)

  1. Backup your existing keyfile.
  2. Run the keydbmgr.exe utility to change the keyfile password. See Changing the Password or Adding a New Key to a Database.
  3. Install the Strong Encryption Pack that you purchased separately.
  4. Run keydbupgrade.exe to upgrade to 128-bit encryption.
    From $SIEBEL_ROOT/siebsrvr/bin, enter the following command:

    keydbupgrade.exe /U USERNAME /P PASSWORD /C CONFIGURATION_FILE_NAME /L LANGUAGE

    where:

    • USERNAME = user name
    • PASSWORD = password
    • CONFIGURATION_FILE_NAME = name of the configuration file (the default is siebel.cfg)
    • LANGUAGE = base language for your installation (the default is enu)

      Example

    keydbupgrade.exe /u sadmin /p PASSWORD /c siebel.cfg /l enu

  5. Continue by upgrading to 56-bit encryption. See To upgrade to 56-bit encryption.
  6. Use srvrmgr to update entparam in the Siebel Gateway:

    change entparam password=db_password

  7. Restart the server.
  8. Repeat these steps on each machine that has an existing Strong Encryption Pack installed.

To upgrade to 56-bit encryption

  1. Verify that the input file encrypt_colums.inp includes all columns that you want to upgrade. If necessary, review Modifying the Input File.
  2. Run encryptupg.exe to upgrade to 56-bit encryption.
    From $SIEBEL_ROOT/siebsrvr/bin, enter the following command:

    encryptupg.exe /U USERNAME /P PASSWORD /C ODBC_CONNECT_STRING /D TABLEOWNER /J INPUT_FILE /N "REPOSITORY_NAME" /K KEY_FILE_NAME /L LOG_FILE

    where:

    • USERNAME = user name for the database
    • PASSWORD = password for the database
    • ODBC_CONNECT_STRING = ODBC connect string for the database
    • TABLEOWNER = tableowner for the database
    • INPUT_FILE = name of your input file
      (The default name is encrypt_columns.inp.)
    • "REPOSITORY_NAME" = name of the repository entered in quotation marks
      (The default name is Siebel Repository.)
    • KEY_FILE_NAME = absolute path to the key file
      (The default location is siebsrvr\admin\keyfile.bin.)
    • LOG_FILE = name of the log file
      (The default name is encryptupg.log.)

      NOTE:  If you have custom encrypted fields, you can validate that all business component fields are pointing to the same column by appending the command with "/v y". For example,

      encryptupg.exe /U       USERNAME /P PASSWORD /C ODBC_CONNECT_STRING /D TABLEOWNER /J INPUT_FILE /N REPOSITORY_NAME /K KEY_FILE_NAME /L LOG_FILE /v y

      But, some business components may not use the same column intentionally.

  3. Repeat Step 2, encryptupg.exe, for each additional database. For each database, use the appropriate user name, password, ODBC connect string, and tableowner.
  4. After the upgrade is complete, compile a new Siebel repository file. See Producing a New Custom Configuration File.

Troubleshooting the Upgrade to RC2 Encryption

If you fail to change user properties, you may get one or more of the following repository validation error messages. Examples of possible errors and sample remedies are provided below:


 Upgrade Guide for UNIX
 Published: 20 October 2003