It's all about the answers!

Ask a question

Create Table while running JTS Set Up Error CRJAZ1571E


Kartik Manchanda (767) | asked Sep 23 '14, 12:54 p.m.
While running the intial jts setup, on creation of JTS tables, I am getting the below error. RTC version is 5.0 and DB2 10.5. DB user is DBA on the database and has all the authorities granted. Any idea?
An error occurred while creating database tables. Please try again.ID CRJAZ1571E
hide details
The database creation failed with an exception
com.ibm.team.repository.common.TeamRepositoryException: CRJAZ0256E An exception occurred creating content tablespace. at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.internalCreateDataTablespace(Db2Provider.java:396) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.createTablespaces(Db2Provider.java:366) 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.$Proxy1085.prepareDbForInitialization(Unknown Source) at com.ibm.team.repository.service.internal.rdb.AbstractDatabaseService.internalCreateAllSchemas(AbstractDatabaseService.java:192) 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:501) at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase$1.run(RepositoryDatabase.java:322) at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:448) at sun.reflect.GeneratedMethodAccessor120.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.$Proxy1087.withCurrentConnection(Unknown Source) at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase.runTransaction(RepositoryDatabase.java:318) at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase.runExclusive(RepositoryDatabase.java:296) at com.ibm.team.repository.service.internal.PrimitiveTransactionService.runExclusive(PrimitiveTransactionService.java:125) 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.$Proxy1106.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.$Proxy1214.createAllSchemas(Unknown Source) at com.ibm.team.repository.service.internal.DatabaseCreationProgressService$1.run(DatabaseCreationProgressService.java:190) at java.lang.Thread.run(Thread.java:796) Caused by: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-552, SQLSTATE=42502, SQLERRMC=RTCADMNT;CREATE TABLESPACE, DRIVER=4.17.28 at com.ibm.db2.jcc.am.fd.a(fd.java:747) at com.ibm.db2.jcc.am.fd.a(fd.java:66) at com.ibm.db2.jcc.am.fd.a(fd.java:135) at com.ibm.db2.jcc.am.uo.b(uo.java:2422) at com.ibm.db2.jcc.am.uo.c(uo.java:2405) at com.ibm.db2.jcc.t4.ab.l(ab.java:408) at com.ibm.db2.jcc.t4.ab.a(ab.java:62) at com.ibm.db2.jcc.t4.o.a(o.java:50) at com.ibm.db2.jcc.t4.ub.b(ub.java:220) at com.ibm.db2.jcc.am.vo.sc(vo.java:3526) at com.ibm.db2.jcc.am.vo.b(vo.java:4489) at com.ibm.db2.jcc.am.vo.mc(vo.java:2833) at com.ibm.db2.jcc.am.vo.execute(vo.java:2808) 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.db.provider.AbstractDbProvider.executeStatement(AbstractDbProvider.java:777) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.executeStatement(Db2Provider.java:640) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.createDataTablespace(Db2Provider.java:501) at com.ibm.team.repository.jdbcdriver.internal.db2.Db2Provider.internalCreateDataTablespace(Db2Provider.java:394) ... 47 more

3 answers



permanent link
Benjamin Silverman (4.1k610) | answered Sep 23 '14, 5:45 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The error in the "Caused By" section of the error seems to indicate a permissions problem when creating the tablespace.  Are you sure this user is a member of the db2admins group and has been granted dba permissions to the database?  Try the commands below (substituting <db name> for your actual database name).

db2 connect to <db name>
db2 grant dbadm on database to user RTCADMNT
db2 disconnect <db name>

permanent link
Lonnie VanZandt (88417) | answered Aug 31 '16, 10:28 a.m.
 The error can also occur when the specified DB2 server does not yet have folders created for "content_tablespace".

When I track down the recipe for creating those folders in the proper locations with the right ownership and permissions, I will reply here to advise what are the missing steps.

For now, I see the same error and only know that I never configured any "content_tablespace" folders on the new DB2 server intended for use with Jazz.

Comments
Lonnie VanZandt commented Aug 31 '16, 5:45 p.m.

 Kevin's reply is very helpful.


With the db2 commands, I can see where DB2 is storing the databases (although "find / -type d -name "db2inst1" is also informative) and I can see how it forms the tablespace containers from that default database path prefix.

What is not helpful is IBM's choice for content for their teamserver.properties comments that are disabled. There are better conventions for indicating that some sequence of strings is meant to be substituted with a real value.

For example:

com.ibm.team.repository.db.db2.content.tablespace.location=<Your path from db2 list tablespace containers for &lt;#&gt; here>

A line like that would be much more indicative of how to use the property.


permanent link
Kevin Ramer (4.5k8180199) | answered Aug 31 '16, 1:13 p.m.
The location for the tablespace containers should be owned by the DB2 instance ID.  If a relative path is used then containers are placed relative to the value of DFTBPATH that is in the db2 admin configuration ( db2 get dbm cfg ).
e.g.
Default database path                       (DFTDBPATH) = /db2/data3


As I recall, the teamserver.properties is used to define the initial name and size ( in pages ) of the contentts tablespace.

com.ibm.team.repository.db.db2.content.tablespace.location=/db2/data3/rtcdb7/contentts/c1.dbf

Only the folders need to exist, with ownership of the instance ID.   Following the above example this is the container for  contentts on one of my many RTC setups:

db2 list tablespace containers for 3

            Tablespace Containers for Tablespace 3

 Container ID                         = 0
 Name                                 = /db2/data3/rtcdb7/contentts/c1.dbf
 Type                                 = File

$ id
uid=215(rtcinst2) gid=206(rtcinst2) groups=217(dasadm)
$ ls -l /db2/data3
total 0
drwxrwxr-x    4 rtcinst2 rtcinst2        256 Oct 15 2011  RTCDB
drwx------    2 rtcinst2 rtcinst2        256 May 17 2012  backup
drwxr-xr-x    2 rtcinst2 rtcinst2        256 Oct 15 2011  lost+found
drwxr-xr-x    4 rtcinst2 rtcinst2        256 Feb 18 2012  rtcdb15
drwxrwxr-x    4 rtcinst2 rtcinst2        256 Nov 12 2011  rtcdb17
drwxr-xr-x    4 rtcinst2 rtcinst2        256 Feb 18 2012  rtcdb6
drwxrwxr-x    4 rtcinst2 rtcinst2        256 Nov 12 2011  rtcdb7

This requirement is ONLY for the initial population of the database as I've added containers to many of our databases.


Your answer


Register or to post your answer.