This technote provides information about an issue that can occur when using Microsoft SQL Server as the database vendor and attempting to upgrade IBM Rational Team Concert (RTC), Rational Requirements Composer (RRC) or Rational Quality Manager (RQM) from any 4.0.x versions to 4.0.4 which fails when running the upgrade scripts.
When using Microsoft SQL Server as the database vendor, upgrade scripts fail with error while upgrading to CLM 4.0.4 from any 4.0.x version:
Running post addTables for "com.ibm.rqm.requirement"...
Running post addTables for "Interop ClearQuest Manager Migration
Running post addTables for "Full Text Migration Handler"...
Running post addTables for "Interop WorkItem Manager Migration Handler"...
CRJAZ0577E The following SQL query did not execute properly on the server:
CREATE UNIQUE INDEX MARKERS_UNIQUE_MARKER ON MARKERS.MARKER(URI, USER_COL, APPLICATION, TYPE)
The user "ADMIN" has logged out of the database "//server:port;databaseName=db;user=xxxxxxxx;password=xxxxxxxx".
CRJAZ1425E The database encountered an error while attempting to create indices for the table "MARKER".
As per the Microsoft article http://technet.microsoft.com/en-us/library/ms191241%28v=sql.105%29.aspx, SQL Server has a 900-byte limit on cumulative size of all index key columns. This excludes nonkey columns that are included in the definition of non-clustered indexes.
In CLM 4.0.4, a new unique index MARKERS_UNIQUE_MARKER was added to the MARKERS.MARKER table in the CLM databases. Because of the index limitation in SQL server and the way it handles unicode data types, if the sum of maximum length of data in the columns that make up MARKERS_UNIQUE_MARKER index exceeds 450 characters, upgrade scripts fail for that application. The table keeps track of user history regarding pages visited. If you have large amounts of data in the table, you may run into the issue during an upgrade to 4.0.4 as the "URL" column tends to have long strings.
This issue was identified as a product defect:
APAR PM96713 / Jazz foundation work item: Change the dashboards migration handler to delete rows that result in index data that is more than 900 bytes (280057)
Resolving The Problem
There is no workaround
If you are running with Microsoft SQL Server, you should upgrade to version 4.0.5 or later versions which include a permanent fix.
16 June 2018