Updating the collating sequence

The following information describes how you can modify the collating sequence for DB2 and Oracle.

DB2

WebSphere Partner Gateway 6.0 on DB2 utilizes the UCA400_NO collating sequence, which improves the sorting of unicode data. DB2 does not allow the collating sequence of an existing database to be changed. When WebSphere Partner Gateway migrates your existing database to version 6.0 it will not change the collating sequence setting. If you would like your installation to utilize the UCA400_NO collating sequence, follow these steps:

  1. From the DB2 UDB Control Center, make a backup of your current WebSphere Partner Gateway database (ie BCGAPPS).
  2. Drop your current WebSphere Partner Gateway database (BCGAPPS).
  3. Create a new database using the Create_db2.sql file created by the DBLoader tool provided with WebSphere Partner Gateway 6.0.
    db2 -td! -f Create_db2.sql -z Create_db2.log
  4. From the DB2 UDB Control Center, restore the backup of the previous WebSphere Partner Gateway database to the database you just created. Be sure to select the 'Restore to Existing Database' option.

Oracle

Oracle databases allow the changing of collation sequences dynamically. In order to utilize this functionality, WebSphere Partner Gateway changes the value of the NLS_SORT session variable when the BCGUpgrade_422FP4_600.sql script is executed.

For more information on collating sequences, refer to the Troubleshooting chapter in the Administrators Guide.

Copyright IBM Corp. 2003, 2005