Converting Microsoft SQL Server to support multibyte languages

If you support multibyte languages, back up your database before you begin the upgrade. If the database conversion fails for any reason, you can restore from the backup, resolve the issue, and try again. Consult with your Microsoft SQL Server administrator and review the changes that must be made.

Before you begin

Read the IBM TRIRIGA Release Notes.

Procedure

  1. Before you begin the upgrade, if you upgrade the database with multibyte character sets (MBCS) enabled, you must republish the real estate contract (triRealEstateContract), building (triBuilding), lease abstract (triLeaseAbstract), and real estate project (triREProject) business objects.
    This process avoids a possible Microsoft SQL Server error on the backing table of the business object during the upgrade. If the business object is not republished, the following error might occur: "Cannot create a row of size xxxx which is greater than the allowable maximum row size of 8060". If this error occurs on any tables, the tables are not configured correctly for MBCS support. In this case, restore the database, and consult with your administrator or implementation team for further instructions.
  2. Verify that no IBM® TRIRIGA® application instances are connected to the database, and the database user for the upgrade installation is uniquely associated to the database.
  3. Upgrade the IBM TRIRIGA Application Platform.
  4. If the upgrade fails and you identify invalid views in the ant.log file during the nvarchar conversion process, take the following recovery steps:
    1. Review the ant.log file to identify the invalid views.
    2. Run the upgrade with MBCS support turned off.
    3. Sign in to IBM TRIRIGA and republish the business objects that have invalid views.
    4. Run the upgrade with MBCS support turned on.
  5. If your IBM TRIRIGA database has custom tables, and if the automated conversion process fails (for example, the automated process does not support tables with the IDENTITY_INSERT parameter set), you can convert them manually. Custom tables that fail the automated process must either be deleted or converted manually before you restart the upgrade:
    1. Review the ant.log file to identify the custom tables that failed.
    2. Restore from your backup database.
    3. Either delete the custom tables or convert them manually. If you choose to convert the custom tables manually, alter all varchar fields to be nvarchar and alter their collation to the collation that is specified during the upgrade.
      For example, for field XXX in table YYY, when your preferred collation is Japanese_CS_AS and the size of the varchar field is 100, the script looks like the following example:
      alter table YYY alter column XXX nvarchar(100) collate Japanese_CS_AS
  6. Depending on your database size, if you are upgrading to MBCS on Microsoft SQL Server, consider setting your log file to autogrow during the database conversion process.
  7. Restart the upgrade of the IBM TRIRIGA Application Platform.