Problems running repotools -CreateTables... CRJAZ0256I
Hi All
I am currently tryging to install 3.0.1.3 on Linux box, when i try to run repotools createTables i get the following error "CRJAZ0256I An exception occurred creating content tablespace." My DB is on a different box (rhelbox), db connection with user id and pwd used in teamproperties has been tested. COuld you please assist on how to proceed. Any help is appricated. Thanks and Regards Pradeep ------------------- Repo Tools Provisioning using "./conf/jts/provision_profiles". Jazz Foundation - Core Libraries, Version 3.0.1.3 (RJF-I20120322-1607) CRJAZ1363I Loading the configuration from "file:conf/jts/teamserver.properties". CRJAZ1779I This server is configured as a JTS. CRJAZ1781W The Public URI Root has not been set. Use the server setup wizard to enter the public URI. This property is required to enforce consistent URL management in the application. The public URI represents the URL that all clients must use to access the application. CRJAZ1365I The server is attempting to connect to the following database: "//rtcrhel:50001/JTS301:user=xxxxxxxx;password=xxxxxxxx;" CRJAZ1364I The connection to the following database was successful: Db Product Name: DB2/LINUX Db Product Version: SQL09070 Db URL: jdbc:db2://rtcrhel:50001/JTS301:user=xxxxxxxx;password=xxxxxxxx; Jdbc Driver Name: IBM DB2 JDBC Universal Driver Architecture Jdbc Driver Version: 3.57.82 CRJAZ8192I: Fulltext Index Location: /opt/IBM/JazzTeamServer/server/conf/jts/indices/workitemindex/fulltext_index Creating the tables for the database "//rtcrhel:50001/JTS301:user=xxxxxxxx;password=xxxxxxxx;" with indices. CRJAZ0256I An exception occurred creating content tablespace. The database tables were not created. ----------------- Team proprties ----------------- # DB2 configuration # # Comment out the above lines, uncomment the following five database properties # and customize the example database location to use DB2. # NOTE THAT EVERY APPLICATION INSTANCE AND JAZZ TEAM SERVER REQUIRES ITS OWN UNIQUE DATABASE. com.ibm.team.repository.db.vendor = DB2 com.ibm.team.repository.db.jdbc.location=//rtcrhel:50001/JTS301:user=db2inst2;password={password}; com.ibm.team.repository.db.jdbc.password=xxxxxxx # DB2 requires a path where the content tablespace should be created, examples for Win and Linux follow com.ibm.team.repository.db.db2.content.tablespace.location=/opt/IBM/JazzTeamServer/server/conf/jts/indices/content_tablespace # Configure the size of the tablespace to be created, in 16K pages. # This is a hard limit and will need to be raised for a production database. # Your DB2 DBA will need to monitor the utilization of the CONTENTS tablespace and grow it as needed. # Defaulting to 250,000 pages, or 4GB. com.ibm.team.repository.db.db2.content.tablespace.numpages=250000 # Comment out the Derby datawarehouse properties, uncomment the following # five lines and customize the location to use DB2 for managing datawarehouse. com.ibm.team.datawarehouse.db.vendor = DB2 com.ibm.team.datawarehouse.db.jdbc.location=//rtcrhel:50001/DW3013:user=db2inst2;password={password}; com.ibm.team.datawarehouse.db.jdbc.password=xxxxxxx # The path where the warehouse tablespace should be created com.ibm.team.datawarehouse.db.base.folder = //rtcrhel:50001/DW3013/jazzdw # The database user for whom proper permissions will be granted com.ibm.team.datawarehouse.report.user = ADMIN ------------------ # Fulltext index location com.ibm.team.fulltext.indexLocation=/opt/IBM/JazzTeamServer/server/conf/jts/indices/workitemindex # Location of JFS index root directory com.ibm.team.jfs.index.root.directory=/opt/IBM/JazzTeamServer/server/conf/jts/indices ------- |
6 answers
When you run the -createTables command I believe there is a separate log file (repotools-jts_createTables.log ?) that is created in that same directory that should have a more detailed stack trace on why the DB command is blowing up.
The last time I saw this error my userId for the DB did not have permission to create tablespaces (SYSADM). |
Thanks Scot
I reckon my error is bit different, here is the log extract: Its talking about having problems while creating content tablespace. See if you can understand and help me out here. Thanks Pradeep 2012-05-17 16:10:43,132 Repo Tools 2012-05-17 16:10:43,133 java.version=1.5.0 2012-05-17 16:10:43,133 java.runtime.version=pxi32devifx-20110209 (SR11 FP2 +IZ94331) 2012-05-17 16:10:43,137 Provisioning using "./conf/jts/provision_profiles". 2012-05-17 16:10:43,161 repotools-jts -createTables 2012-05-17 16:10:43,161 Jazz Foundation - Core Libraries, Version 3.0.1.3 (RJF-I20120322-1607) 2012-05-17 16:10:43,174 CRJAZ1363I Loading the configuration from "file:conf/jts/teamserver.properties". 2012-05-17 16:10:43,874 CRJAZ1779I This server is configured as a JTS. 2012-05-17 16:10:43,875 CRJAZ1781W The Public URI Root has not been set. Use the server setup wizard to enter the public URI. This property is required to enforce consistent URL management in the application. The public URI represents the URL that all clients must use to access the application. 2012-05-17 16:10:44,703 CRJAZ1365I The server is attempting to connect to the following database: "//rtcrhel:50001/JTS301:user=xxxxxxxx;password=xxxxxxxx;" 2012-05-17 16:10:45,993 CRJAZ1364I The connection to the following database was successful: Db Product Name: DB2/LINUX Db Product Version: SQL09070 Db URL: jdbc:db2://rtcrhel:50001/JTS301:user=xxxxxxxx;password=xxxxxxxx; Jdbc Driver Name: IBM DB2 JDBC Universal Driver Architecture Jdbc Driver Version: 3.57.82 2012-05-17 16:10:46,939 CRJAZ8192I: Fulltext Index Location: /opt/IBM/JazzTeamServer/server/conf/jts/indices/workitemindex/fulltext_index 2012-05-17 16:10:47,277 Creating the tables for the database "//rtcrhel:50001/JTS301:user=xxxxxxxx;password=xxxxxxxx;" with indices. 2012-05-17 16:10:48,025 CRJAZ0256I An exception occurred creating content tablespace. com.ibm.team.repository.common.TeamRepositoryException: CRJAZ0256I An exception occurred creating content tablespace. at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.internalCreateDataTablespace(Db2Provider.java:368) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.createTablespaces(Db2Provider.java:341) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.prepareDbForInitialization(Db2Provider.java:290) 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 $Proxy56.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.internalRebuildAllSchemas(DatabaseCreationService.java:114) at com.ibm.team.repository.service.internal.rdb.DatabaseCreationService.access$0(DatabaseCreationService.java:112) at com.ibm.team.repository.service.internal.rdb.DatabaseCreationService$3.run(DatabaseCreationService.java:102) 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:458) at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase$1.run(RepositoryDatabase.java:285) at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:379) 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 $Proxy58.withCurrentConnection(Unknown Source) at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase.runTransaction(RepositoryDatabase.java:281) at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase.runExclusive(RepositoryDatabase.java:259) 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 $Proxy91.runExclusive(Unknown Source) at com.ibm.team.repository.service.internal.rdb.DatabaseCreationService.doRebuildSchemas(DatabaseCreationService.java:98) at com.ibm.team.repository.service.internal.rdb.DatabaseCreationService.rebuildAllSchemas(DatabaseCreationService.java:89) 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 $Proxy116.rebuildAllSchemas(Unknown Source) at com.ibm.team.repotools.commands.local.internal.CreateTablesCommand.createTables(CreateTablesCommand.java:89) at com.ibm.team.repotools.commands.local.internal.CreateTablesCommand.execute(CreateTablesCommand.java:194) at com.ibm.team.repotools.command.AbstractCommand.execute(AbstractCommand.java:64) at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.run(RepositoryToolsApplication.java:736) at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.start(RepositoryToolsApplication.java:811) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) 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.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) Caused by: com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-970, SQLSTATE=55009, 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) 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:625) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.executeStatement(Db2Provider.java:615) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.createDataTablespace(Db2Provider.java:473) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.internalCreateDataTablespace(Db2Provider.java:366) ... 66 more When you run the -createTables command I believe there is a separate log file (repotools-jts_createTables.log ?) that is created in that same directory that should have a more detailed stack trace on why the DB command is blowing up. |
The important part is "SQLCODE=-970, SQLSTATE=55009". Looks like that is caused by an inability to write to a particular file system (maybe because the file system is ready only or because the userid doesn't have access?). http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=%2Fcom.ibm.db2.luw.messages.sql.doc%2Fdoc%2Fmsql00970n.html.
You might check the DB2 log file or get your DBA to check to see if there are any additional clues. It also looks like somebody else hit this problem previously and resolved it by creating the tablespace manually. https://jazz.net/forums/viewtopic.php?p=5294 |
Looking at your config file, is the tablespace location for JTS correct? Shouldn't it be something like:
com.ibm.team.repository.db.db2.content.tablespace.location=/JTS301/content Just basing that on similar to the path for your DW tablespace. |
Thanks for the reply Scott
2 questions: 1. How to i create tablespace manually (what commands do i use) 2. My DB is on a different box and RTC is on a differnt box based on this how do I alter the location should i point to the RTC box or on the DB box if so what is the syntax which i need to use. Thanks Pradeep quote="sac625"]Looking at your config file, is the tablespace location for JTS correct? Shouldn't it be something like: com.ibm.team.repository.db.db2.content.tablespace.location=/JTS301/content Just basing that on similar to the path for your DW tablespace. |
com.ibm.team.repository.db.db2.content.tablespace.location is the location on the DB box where the tablespace should be created. It's a relative path, so the default ("content_tablespace" I think?) would create the tablespace under the Database's directory on the DB server. Unless you have reason to put the content tablespace on a specific filesystem I'd leave the default. But really your DBA should be telling you where it should go as they might have specific requirements.
|
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.