SOLVED: Configure RTC 3.0.0.1 with DB2
Hi,
I am having some problems doing the setup of CCM on a Win2k3 Server. I've installed everything OOTB except by i'm using a db2-express database. I haven't had problems with the JTS installation part. The problem is when i try to configure the CCM Database. I 've created a specific database with DB2 for CCM, I tested the connection and it worked fine. The problem is when, following the steps shown, i try to create the tables to enable CCM work it shows an error saying it can't crete those tables: com.ibm.team.repository.common.RetryableDatabaseException: CRJAZ1318I Se ha producido un error de conexin de base de datos. CRJAZ0265I El almacenamiento virtual o el recurso de la base de datos no estn disponibles. SQL: CREATE LARGE TABLESPACE CONTENTTS MANAGED BY DATABASE USING (file 'jazzdata' 250000) AUTORESIZE YES DROPPED TABLE RECOVERY OFF SQL Exception #1 SQL Message: DB2 SQL Error: SQLCODE=-968, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.57.82 SQL State: 57011 Error Code: -968 at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.AbstractErrLogWrapper.logAndReturnException(AbstractErrLogWrapper.java:99) at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.StatementErrLogWrapper.logAndReturnException(StatementErrLogWrapper.java:66) at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.PreparedStatementErrLogWrapper.execute(PreparedStatementErrLogWrapper.java:67) at com.ibm.team.repository.service.internal.db.jdbcwrappers.leak.PreparedStatementLeakWrapper.execute(PreparedStatementLeakWrapper.java:50) at com.ibm.team.repository.service.db.provider.AbstractDbProvider.executeStatement(AbstractDbProvider.java:571) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.executeStatement(Db2Provider.java:555) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.createDataTablespace(Db2Provider.java:413) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.internalCreateDataTablespace(Db2Provider.java:319) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.createTablespaces(Db2Provider.java:294) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.prepareDbForInitialization(Db2Provider.java:243) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) at $Proxy1000.prepareDbForInitialization(Unknown Source) at com.ibm.team.repository.service.internal.rdb.AbstractDatabaseService.internalCreateAllSchemas(AbstractDatabaseService.java:181) at com.ibm.team.repository.service.internal.rdb.DatabaseCreationService$1.run(DatabaseCreationService.java:48) at com.ibm.team.repository.service.internal.rdb.ConnectionRunnable.runWithResult(ConnectionRunnable.java:40) at com.ibm.team.repository.service.internal.rdb.ConnectionRunnable.run(ConnectionRunnable.java:34) at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase$Transaction.run(RepositoryDatabase.java:440) at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase$1.run(RepositoryDatabase.java:267) at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:332) at sun.reflect.GeneratedMethodAccessor268.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) at $Proxy1746.withCurrentConnection(Unknown Source) at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase.runTransaction(RepositoryDatabase.java:263) at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase.runExclusive(RepositoryDatabase.java:242) at com.ibm.team.repository.service.internal.TransactionService.runExclusive(TransactionService.java:139) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) at $Proxy1763.runExclusive(Unknown Source) at com.ibm.team.repository.service.internal.rdb.DatabaseCreationService.createAllSchemas(DatabaseCreationService.java:43) at com.ibm.team.repository.service.internal.rdb.DatabaseCreationService.createAllSchemas(DatabaseCreationService.java:39) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) at $Proxy1798.createAllSchemas(Unknown Source) at com.ibm.team.repository.service.internal.DatabaseCreationRestService$1.run(DatabaseCreationRestService.java:42) at java.lang.Thread.run(Thread.java:811) Caused by: com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-968, SQLSTATE=57011, SQLERRMC=null, DRIVER=3.57.82 at com.ibm.db2.jcc.am.bd.a(bd.java:679) at com.ibm.db2.jcc.am.bd.a(bd.java:60) at com.ibm.db2.jcc.am.bd.a(bd.java:127) at com.ibm.db2.jcc.am.km.b(km.java:2164) at com.ibm.db2.jcc.am.km.c(km.java:2147) at com.ibm.db2.jcc.t4.db.k(db.java:354) at com.ibm.db2.jcc.t4.db.a(db.java:60) at com.ibm.db2.jcc.t4.t.a(t.java:50) at com.ibm.db2.jcc.t4.tb.b(tb.java:218) at com.ibm.db2.jcc.am.lm.ec(lm.java:2692) at com.ibm.db2.jcc.am.lm.b(lm.java:3552) at com.ibm.db2.jcc.am.lm.Yb(lm.java:2130) at com.ibm.db2.jcc.am.lm.execute(lm.java:2114) 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) ... 52 more I've also tried to use the same database as in the JTS part but on the next step setup it also fails Any idea on what is going on? |
4 answers
|
I've finally found the solution....
It's quite simple, the problem is that there is not enough space in the drive to allocate the necessary capacity for the 2nd database. So the solution is as simple as cleaning up a bit your HDD, :) ! How much do you have to clean up your HDD? For the JTS database around 6,5GB and for the CCM Database 4,5GB!! Is quite a big space allocated for an almost empty database but is like the OOB installiation works... |
Ralph Schoon (63.4k●3●36●46)
| answered May 27 '11, 9:50 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi,
which DB2 version do you use? In case it was 9.7: If you installed DB2 9.7 and you created the database as another user than the user db2admin (or whatever other user you use in the teamserver.properties), you must grant dbadm authority to that user using the following command sequence db2 connect to CCM db2 grant dbadm on database to user db2admin db2 disconnect CCM Thanks, Ralph |
|
Ralph Schoon (63.4k●3●36●46)
| answered May 27 '11, 9:51 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Your error number also comes up tin this topic. Maybe another hint: http://jazz.net/forums/viewtopic.php?p=18180
You could lso try to narrow down the issue having a look into the DB2 logs and searching for the Error numbers. Maybe that reveals something. Ralph |
I've finally found the solution.... Thanks for the post. I met similar issue and it turned out it's caused by not enough hard disk -_-!. |
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.