It's all about the answers!

Ask a question

upgrade clm 6.0.2 to 6.0.4, can I change db2 tablespace pagesize ?


Dixie Fu (82) | asked Oct 16 '17, 8:55 a.m.
Hi, 
I am stuck on a db2 error thrown from upgrade script repotools-jazz.bat -addTables while upgrading ccm from 6.0.2 to 6.0.4. Stacktrace is appended. 

The db2 error is to do with my existing ccm database whose tablespace pagesize was created as 8K instead of 16K. I got error com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-670, SQLSTATE=54010, SQLERRMC=8101;CONTENTTS;15361, DRIVER=4.21.29 during the upgrading CCM tables process. 

Is there any way I can change the tablespace pagesize to 16K? I tried to change the pagesize of bufferPool ibmdefaultbp by using this command : db2 alter bufferpool ibmdefaultbp size 16384. But this command seems to alter the number of pages to 16K instead of changing the pagesize. 

I have searched db2 forum, some posts talked about cannot change the pagesize of an existing tablespace. 

Is there any CLM upgrade scripts can save me from this problem? 

Much Thanks,
Dixie


Stacktrace appended:
===============================================================================

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, ARCHIVED 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 DECIMAL(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), MCSCPYRT_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_FILE 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, RFDSNPFX VARCHAR(250), SCP SMALLINT NOT NULL) IN CONTENTTS
at com.ibm.team.repository.service.internal.db.util.JdbcDB.executeQuery(JdbcDB.java:238)
at com.ibm.team.repository.service.internal.db.util.JdbcDB.executeQuery(JdbcDB.java:113)
at com.ibm.team.repository.service.internal.db.util.JdbcDB.executeQueryOn(JdbcDB.java:102)
at com.ibm.team.repository.service.internal.db.util.JdbcDBBuilder.executeStatement(JdbcDBBuilder.java:148)
at com.ibm.team.repository.service.internal.db.util.JdbcDBBuilder.executeStatements(JdbcDBBuilder.java:279)
at com.ibm.team.repository.service.internal.db.util.JdbcDBBuilder.buildArtifactsFromCreateStatements(JdbcDBBuilder.java:284)
at com.ibm.team.repository.service.internal.rdb.PluggableJdbcDbBuilder.buildArtifactsFromCreateStatements(PluggableJdbcDbBuilder.java:81)
at com.ibm.team.repository.service.internal.rdb.AbstractDatabaseService.internalCreateSchema(AbstractDatabaseService.java:386)
at com.ibm.team.repository.service.internal.rdb.AbstractDatabaseService.internalCreateAndSaveSchema(AbstractDatabaseService.java:324)
... 55 more
Caused by: com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-670, SQLSTATE=54010, SQLERRMC=8101;CONTENTTS;15361, DRIVER=4.21.29
at com.ibm.db2.jcc.am.kd.a(kd.java:815)
at com.ibm.db2.jcc.am.kd.a(kd.java:66)
at com.ibm.db2.jcc.am.kd.a(kd.java:140)
at com.ibm.db2.jcc.am.sp.b(sp.java:2447)
at com.ibm.db2.jcc.am.sp.c(sp.java:2430)
at com.ibm.db2.jcc.t4.bb.m(bb.java:415)
at com.ibm.db2.jcc.t4.bb.a(bb.java:62)
at com.ibm.db2.jcc.t4.p.a(p.java:50)
at com.ibm.db2.jcc.t4.wb.b(wb.java:220)
at com.ibm.db2.jcc.am.tp.uc(tp.java:3567)
at com.ibm.db2.jcc.am.tp.a(tp.java:4613)
at com.ibm.db2.jcc.am.tp.b(tp.java:4173)
at com.ibm.db2.jcc.am.tp.oc(tp.java:2870)
at com.ibm.db2.jcc.am.tp.execute(tp.java:2845)
at com.ibm.team.repository.service.internal.db.jdbcwrappers.stat.PreparedStatementStatWrapper.execute(PreparedStatementStatWrapper.java:58)
at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.PreparedStatementErrLogWrapper.execute(PreparedStatementErrLogWrapper.java:70)
at com.ibm.team.repository.service.internal.db.jdbcwrappers.leak.PreparedStatementLeakWrapper.execute(PreparedStatementLeakWrapper.java:55)
at com.ibm.team.repository.service.internal.db.util.JdbcDB.executeQuery(JdbcDB.java:227)
... 63 more
2017-10-16 22:16:52,307 CRJAZ1791E The migration completed with errors. The imported database is unstable and should not be used without further analysis.

Be the first one to answer this question!


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.