During the upgrade of CCM from 502 to 606RC1, we got the error below. It looks like it had issues creating the table. Any ideas on what's causing this issue ?
2018-06-07 11:31:29,178 CRJAZ1442I The component model of "com.ibm.team.links" was updated from "6" to "8".
2018-06-07 11:31:29,660 CRJAZ1438I A new attribute "internal" was added to class "com.ibm.team.repository.common.model.ConfigurationAwareAuditable".
2018-06-07 11:31:29,661 CRJAZ1438I A new attribute "ignored" was added to class "com.ibm.team.repository.common.model.ConfigurationAwareAuditable".
2018-06-07 11:31:29,662 CRJAZ1438I A new attribute "uri" was added to class "com.ibm.team.repository.common.model.ConfigurationAwareAuditable".
2018-06-07 11:31:29,662 CRJAZ1438I A new attribute "changeSetId" was added to class "com.ibm.team.repository.common.model.ConfigurationAwareAuditable".
2018-06-07 11:31:29,663 CRJAZ1438I A new attribute "componentId" was added to class "com.ibm.team.repository.common.model.ConfigurationAwareAuditable".
2018-06-07 11:31:30,907 CRJAZ1438I A new attribute "linkTypeInstanceId" was added to class "com.ibm.team.links.internal.links.AuditableLink".
2018-06-07 11:32:22,233 CRJAZ0577E The following SQL query did not execute properly on the server:
CREATE TABLE MODEL0.FMID_ITEM_DEFINITION(STATE_ID CHAR(23) NOT NULL, ITEM_ID CHAR(23) NOT NULL, CONTEXT_ID CHAR(23) NOT NULL, MODIFIED TIMESTAMP NOT NULL, MODIFIED_BY_ITEM_ID CHAR(23) NOT NULL, A
RCHIVED SMALLINT NOT NULL, IGNORED_ONCE_FOR_BUILD SMALLINT NOT NULL, MIGRATED_ITEM_ID VARCHAR(250), MIGRATED_STATE_ID VARCHAR(250), NAME_COL VARCHAR(250) NOT NULL, NON_IMPACTING SMALLINT NOT NULL
, PROJECT_AREA_ITEM_ID CHAR(23) NOT NULL, ALIAS_COL VARCHAR(250), BASE SMALLINT NOT NULL, FESN VARCHAR(250), FUNCTION_ITEM_ID CHAR(23) NOT NULL, IGNORE_COL SMALLINT NOT NULL, INITIAL_REVISION DEC
IMAL(28, 4), JCLIN_CALLLIBS SMALLINT NOT NULL, JCLIN_DISTLIB_ITEM_ID CHAR(23), JCLIN_ID VARCHAR(250), JCLIN_IN_SOURCE SMALLINT NOT NULL, JCLIN_LOCATION_ITEM_ID CHAR(23), MCSCPYRT VARCHAR(1000), M
CSCPYRT_ID VARCHAR(250), MCSCPYRT_LOCATION_ITEM_ID CHAR(23), MCS_DEL VARCHAR(1000), MCS_DEL_FILE VARCHAR(1000), MCS_NPR VARCHAR(1000), MCS_NPR_FILE VARCHAR(1000), MCS_PRE VARCHAR(1000), MCS_PRE_F
ILE VARCHAR(1000), MCS_REQ VARCHAR(1000), MCS_REQ_FILE VARCHAR(1000), MCS_SUP VARCHAR(1000), MCS_SUP_FILE VARCHAR(1000), MCS_VER VARCHAR(1000), MCS_VER_FILE VARCHAR(1000), OS_PLATFORM INTEGER, RF
DSNPFX VARCHAR(250), SCP SMALLINT NOT NULL) IN CONTENTTS
com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-670, SQLSTATE=54010, SQLERRMC=8101;CONTENTTS;15361, DRIVER=4.21.29
Comments
Seems you are using DB2. The underlying cause is that a table is too small for the data (DB2 SQL Error: SQLCODE=-670, SQLSTATE=54010) but you should immediately involve IBM support on this one and probably report a defect against 6.0.6 RC1 just in case.
Why a non GA version? Do you have an environment where you can test if the ugprade works to 6.0.5 (ifix 5) ?
You do have a backup of the database(s) before upgrade just in case, right?
Thanks for replying Ulf. I already opened a PMR for this issue. I'm hoping to get a response or fix to my problem.
We would like to upgrade to 6.0.6 once it GAs. In the meantime, while waiting for 6.0.6, we are testing the 6.0.6 RC1 upgrade on a clone of our production environment.