Unable to create DB2 Tables.
Sathya moorthy (35●2●9●13)
| asked Aug 04 '13, 2:45 p.m.
retagged Sep 03 '13, 5:01 p.m. by Amy Laird (165●1●4)
Hi Team,
We have setup the JAZZ and RTC server on one linux image and DB2 on another linux image. Database Connection Information Database server = DB2/LINUXX8664 10.5.0 SQL authorization ID = DB2INST1 Local database alias = JTS We went for the custom setup. We are able to make successful connection to DB2. but we are unable to create the tables. Getting the below error. An error occurred while creating database tables. Please try again.ID CRJAZ1571E show details Details: The database creation failed with an exception com.ibm.team.repository.common.TeamRepositoryException: CRJAZ0258I Error querying tablespace size. at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.shouldCreateNewTablespace(Db2Provider.java:491) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.shouldCreateNewDataTablespace(Db2Provider.java:472) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.createTablespaces(Db2Provider.java:361) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.prepareDbForInitialization(Db2Provider.java:315) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) at com.sun.proxy.$Proxy817.prepareDbForInitialization(Unknown Source) at com.ibm.team.repository.service.internal.rdb.AbstractDatabaseService.internalCreateAllSchemas(AbstractDatabaseService.java:189) at com.ibm.team.repository.service.internal.rdb.DatabaseCreationService$1.run(DatabaseCreationService.java:57) 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:497) at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase$1.run(RepositoryDatabase.java:321) at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:434) at sun.reflect.GeneratedMethodAccessor99.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) at com.sun.proxy.$Proxy819.withCurrentConnection(Unknown Source) at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase.runTransaction(RepositoryDatabase.java:317) at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase.runExclusive(RepositoryDatabase.java:295) at com.ibm.team.repository.service.internal.PrimitiveTransactionService.runExclusive(PrimitiveTransactionService.java:139) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) at com.sun.proxy.$Proxy837.runExclusive(Unknown Source) at com.ibm.team.repository.service.internal.rdb.DatabaseCreationService.createAllSchemas(DatabaseCreationService.java:52) at com.ibm.team.repository.service.internal.rdb.DatabaseCreationService.createAllSchemas(DatabaseCreationService.java:48) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) at com.sun.proxy.$Proxy938.createAllSchemas(Unknown Source) at com.ibm.team.repository.service.internal.DatabaseCreationProgressService$1.run(DatabaseCreationProgressService.java:190) at java.lang.Thread.run(Thread.java:738) Caused by: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-440, SQLSTATE=42884, SQLERRMC=SNAPSHOT_TBS_CFG;FUNCTION, DRIVER=4.14.121 at com.ibm.db2.jcc.am.ed.a(ed.java:677) at com.ibm.db2.jcc.am.ed.a(ed.java:60) at com.ibm.db2.jcc.am.ed.a(ed.java:127) at com.ibm.db2.jcc.am.oo.c(oo.java:2715) at com.ibm.db2.jcc.am.oo.d(oo.java:2703) at com.ibm.db2.jcc.am.oo.a(oo.java:2136) at com.ibm.db2.jcc.am.po.a(po.java:7793) at com.ibm.db2.jcc.t4.ab.h(ab.java:141) at com.ibm.db2.jcc.t4.ab.b(ab.java:41) at com.ibm.db2.jcc.t4.p.a(p.java:32) at com.ibm.db2.jcc.t4.qb.i(qb.java:135) at com.ibm.db2.jcc.am.oo.ib(oo.java:2105) at com.ibm.db2.jcc.am.po.uc(po.java:3629) at com.ibm.db2.jcc.am.po.b(po.java:4424) at com.ibm.db2.jcc.am.po.hc(po.java:756) at com.ibm.db2.jcc.am.po.executeQuery(po.java:725) at com.ibm.team.repository.service.internal.db.jdbcwrappers.stat.PreparedStatementStatWrapper.executeQuery(PreparedStatementStatWrapper.java:62) at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.PreparedStatementErrLogWrapper.executeQuery(PreparedStatementErrLogWrapper.java:80) at com.ibm.team.repository.service.internal.db.jdbcwrappers.leak.PreparedStatementLeakWrapper.executeQuery(PreparedStatementLeakWrapper.java:59) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.getTablespaceSize(Db2Provider.java:612) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.shouldCreateNewTablespace(Db2Provider.java:478) ... 48 more Could you please let us know. why we are unable to create tables. Regards, Sathya |
Accepted answer
Hi, Sathya,
Can you make sure the user you used to connect to DB2 has SYSADMIN authority?
And looked like from the technote below that 10.5 is not yet supported.
Hope that helps. Thanks.
Sathya moorthy selected this answer as the correct answer
Comments
Kevin Ramer
commented Sep 03 '13, 1:59 p.m.
DBADM is also sufficient authority and from where I sit, less attention is put on IDs with this role vs SYSADM. One could temporarily allow the connection ID to be SYSADM until the needed function is completed (addTables, createTables)
|
2 other answers
Hello Satya,
I see that this is known issue when you are trying (unsupported) 10.5 version. See jazz.net workitem for that: https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=274877 Comments
john norris
commented Sep 03 '13, 1:50 p.m.
I tried migrating from a derby db to DB2 Express-C 10.5 and get the "CRJAZ0258I Error querying tablespace size." error in RTC 4.0.1. So to make this work I would need DB2 Express-c 9.7? I do not want to upgrade to 4.0.3 yet in RTC. Out of interest what causes the error and is there a way of getting round it? Regards, John |
Thanks Clement and Krzysztof. We will go for the supported DB2 version 10.1 and continue.
|
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.