Error running the repotools -createTables command

Can you please post the output from repotools -createTables at the time that it fails?
That will help us in giving you some other suggestions.
Thanks,
John

We have migrated the RQM Databases from Derby to DB2 9.5.

inorder to have the tables created for the DB2 databases, while running the repotools -createTables commmand it throwed an error saying Tables cannot be created.

From the lot of posts Tried setting the page size to 16k but no luck :(

From the repotools_createTables.log file we have copied the sql statements and executed them manually from the DB2 command editor which got executed successfully.

But we are unable to see the tables being populated in the DB.

Hi John,

Please find the output from the repotools -createTables tool

2009-08-25 14:20:06,328 Jazz Foundation Server, Version 1.0 (I20090618-1753)
Rational Quality Manager, Version 2.0 (I20090713_1659)

2009-08-25 14:20:06,437 Provisioning using "C:\Program Files\IBM\RQM20\server\conf\jazz\provision_profiles".
2009-08-25 14:20:06,624 CRJAZ0298I The profile "C:\Program Files\IBM\RQM20\server\conf\jazz\provision_profiles\rqm-license-profile.ini" must contain a url and featureId property.
2009-08-25 14:20:18,515 Rational Jazz Team Server (RQM) - Enterprise
2009-08-25 14:20:18,609 CRJAZ1363I Loading configuration from "file:conf/jazz/teamserver.properties".

2009-08-25 14:22:40,639 CRJAZ0487I An exception occurred while creating the database schema for the package "com.ibm.rational.test.lm".
com.ibm.team.repository.common.TeamRepositoryException: CRJAZ0487I An exception occurred while creating the database schema for the package "com.ibm.rational.test.lm".
at com.ibm.team.repository.service.internal.rdb.AbstractDatabaseService.internalCreateAndSaveSchema(AbstractDatabaseService.java:327)


at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
Caused by:
com.ibm.team.repository.service.internal.db.util.JdbcDB$2: CRJAZ0577I Error preparing or executing statement => CREATE TABLE LM.ABSTRACT_INSTANCE(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,


Caused by:
com.ibm.db2.jcc.b.co: DB2 SQL Error: SQLCODE=-286, SQLSTATE=42727, SQLERRMC=16384;DB2ADMIN, DRIVER=3.53.70
at com.ibm.db2.jcc.b.bd.a(bd.java:676)
at com.ibm.db2.jcc.b.bd.a(bd.java:60)
at com.ibm.db2.jcc.b.bd.a(bd.java:127)
at com.ibm.db2.jcc.b.fm.b(fm.java:2132)
at com.ibm.db2.jcc.b.fm.c(fm.java:2115)
at com.ibm.db2.jcc.t4.db.k(db.java:353)
at com.ibm.db2.jcc.t4.db.a(db.java:59)
at com.ibm.db2.jcc.t4.t.a(t.java:50)
at com.ibm.db2.jcc.t4.tb.b(tb.java:200)
at com.ibm.db2.jcc.b.gm.Zb(gm.java:2445)
at com.ibm.db2.jcc.b.gm.e(gm.java:3287)
at com.ibm.db2.jcc.b.gm.Tb(gm.java:1901)
at com.ibm.db2.jcc.b.gm.execute(gm.java:1885)
at com.ibm.team.repository.service.internal.db.jdbcwrappers.stat.PreparedStatementStatWrapper.execute(PreparedStatementStatWrapper.java:51)
at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.PreparedStatementErrLogWrapper.execute(PreparedStatementErrLogWrapper.java:65)
at com.ibm.team.repository.service.internal.db.jdbcwrappers.leak.PreparedStatementLeakWrapper.execute(PreparedStatementLeakWrapper.java:50)
at com.ibm.team.repository.service.internal.db.util.JdbcDB.executeQuery(JdbcDB.java:226)
... 65 more
2009-08-25 14:22:40,639 The database tables were not created.

Can you please post the output from repotools -createTables at the time that it fails?
That will help us in giving you some other suggestions.
Thanks,
John

We have migrated the RQM Databases from Derby to DB2 9.5.

inorder to have the tables created for the DB2 databases, while running the repotools -createTables commmand it throwed an error saying Tables cannot be created.

From the lot of posts Tried setting the page size to 16k but no luck :(

From the repotools_createTables.log file we have copied the sql statements and executed them manually from the DB2 command editor which got executed successfully.

But we are unable to see the tables being populated in the DB.

Hi All,

I found a workaround to this issue.

I have tried installing RQM 2.0 on a different machine and had it configured with DB2 database with the same DB name as I have in the problematic server.

Copied the team.properties file from new to old server and then tried running the repotools -createTables which populated tables.

Since my old server have got two Jazz Server installed one is standalone and the other one which comes along with RQM my assumption was due to that.

regards
mc

Hi John,

Please find the output from the repotools -createTables tool

2009-08-25 14:20:06,328 Jazz Foundation Server, Version 1.0 (I20090618-1753)
Rational Quality Manager, Version 2.0 (I20090713_1659)

2009-08-25 14:20:06,437 Provisioning using "C:\Program Files\IBM\RQM20\server\conf\jazz\provision_profiles".
2009-08-25 14:20:06,624 CRJAZ0298I The profile "C:\Program Files\IBM\RQM20\server\conf\jazz\provision_profiles\rqm-license-profile.ini" must contain a url and featureId property.
2009-08-25 14:20:18,515 Rational Jazz Team Server (RQM) - Enterprise
2009-08-25 14:20:18,609 CRJAZ1363I Loading configuration from "file:conf/jazz/teamserver.properties".

2009-08-25 14:22:40,639 CRJAZ0487I An exception occurred while creating the database schema for the package "com.ibm.rational.test.lm".
com.ibm.team.repository.common.TeamRepositoryException: CRJAZ0487I An exception occurred while creating the database schema for the package "com.ibm.rational.test.lm".
at com.ibm.team.repository.service.internal.rdb.AbstractDatabaseService.internalCreateAndSaveSchema(AbstractDatabaseService.java:327)


at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
Caused by:
com.ibm.team.repository.service.internal.db.util.JdbcDB$2: CRJAZ0577I Error preparing or executing statement => CREATE TABLE LM.ABSTRACT_INSTANCE(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,


Caused by:
com.ibm.db2.jcc.b.co: DB2 SQL Error: SQLCODE=-286, SQLSTATE=42727, SQLERRMC=16384;DB2ADMIN, DRIVER=3.53.70
at com.ibm.db2.jcc.b.bd.a(bd.java:676)
at com.ibm.db2.jcc.b.bd.a(bd.java:60)
at com.ibm.db2.jcc.b.bd.a(bd.java:127)
at com.ibm.db2.jcc.b.fm.b(fm.java:2132)
at com.ibm.db2.jcc.b.fm.c(fm.java:2115)
at com.ibm.db2.jcc.t4.db.k(db.java:353)
at com.ibm.db2.jcc.t4.db.a(db.java:59)
at com.ibm.db2.jcc.t4.t.a(t.java:50)
at com.ibm.db2.jcc.t4.tb.b(tb.java:200)
at com.ibm.db2.jcc.b.gm.Zb(gm.java:2445)
at com.ibm.db2.jcc.b.gm.e(gm.java:3287)
at com.ibm.db2.jcc.b.gm.Tb(gm.java:1901)
at com.ibm.db2.jcc.b.gm.execute(gm.java:1885)
at com.ibm.team.repository.service.internal.db.jdbcwrappers.stat.PreparedStatementStatWrapper.execute(PreparedStatementStatWrapper.java:51)
at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.PreparedStatementErrLogWrapper.execute(PreparedStatementErrLogWrapper.java:65)
at com.ibm.team.repository.service.internal.db.jdbcwrappers.leak.PreparedStatementLeakWrapper.execute(PreparedStatementLeakWrapper.java:50)
at com.ibm.team.repository.service.internal.db.util.JdbcDB.executeQuery(JdbcDB.java:226)
... 65 more
2009-08-25 14:22:40,639 The database tables were not created.

Can you please post the output from repotools -createTables at the time that it fails?
That will help us in giving you some other suggestions.
Thanks,
John

We have migrated the RQM Databases from Derby to DB2 9.5.

inorder to have the tables created for the DB2 databases, while running the repotools -createTables commmand it throwed an error saying Tables cannot be created.

From the lot of posts Tried setting the page size to 16k but no luck :(

From the repotools_createTables.log file we have copied the sql statements and executed them manually from the DB2 command editor which got executed successfully.

But we are unable to see the tables being populated in the DB.