RRC 2.0 Configuration Issues - Oracle
![]()
In the database configuration steps during the initialization of RRC 2.0 (specifically steps 2.2 and 2.3) I get errors when trying to create the tables for oracle.
Once I test the connection I get this error - The configuration test resulted in errors. Resolve errors to continue.Hide DetailsThe database exists, but is not configured to contain Jazz. Use the "Create Tables" button in Step 2.3 to configure the database for Jazz. Not really a problem, until the next step when I go to create the tables and it comes back with this: An error occurred while creating database tables. Please try again.Hide Details The database creation failed with an exception com.ibm.team.repository.common.TeamRepositoryException: Sql Exception thrown while testing case sensitivity of the database at com.ibm.team.repository.service.db.provider.CaseSensitivityValidator.testCaseSensitivity(CaseSensitivityValidator.java:233) at com.ibm.team.repository.service.db.provider.AbstractDbProvider.assertCaseSensitivity(AbstractDbProvider.java:1063) at com.ibm.team.repository.service.db.provider.AbstractDbProvider.checkDatabaseConfiguration(AbstractDbProvider.java:1055) at com.ibm.team.repository.service.db.provider.AbstractDbProvider.prepareDbForInitialization(AbstractDbProvider.java:458) at com.ibm.team.repository.jdbcdriver.internal.oracle.OracleProvider.prepareDbForInitialization(OracleProvider.java:443) 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 $Proxy159.prepareDbForInitialization(Unknown Source) at com.ibm.team.repository.service.internal.rdb.AbstractDatabaseService.internalCreateAllSchemas(AbstractDatabaseService.java:163) at com.ibm.team.repository.service.internal.rdb.DatabaseCreationService$1.run(DatabaseCreationService.java:47) 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:466) at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase$1.run(RepositoryDatabase.java:292) at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:331) at sun.reflect.GeneratedMethodAccessor75.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 $Proxy358.withCurrentConnection(Unknown Source) at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase.runTransaction(RepositoryDatabase.java:288) at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase.runExclusive(RepositoryDatabase.java:267) at com.ibm.team.repository.service.internal.TransactionService.runExclusive(TransactionService.java:84) 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 $Proxy368.runExclusive(Unknown Source) at com.ibm.team.repository.service.internal.rdb.DatabaseCreationService.createAllSchemas(DatabaseCreationService.java:42) at com.ibm.team.repository.service.internal.rdb.DatabaseCreationService.createAllSchemas(DatabaseCreationService.java:38) 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 $Proxy389.createAllSchemas(Unknown Source) at com.ibm.team.repository.service.internal.DatabaseCreationRestService$1.run(DatabaseCreationRestService.java:38) Caused by: java.sql.SQLException: ORA-01950: no privileges on tablespace 'REQCOMPOSER' at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:213) at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:952) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1160) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3285) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3368) at com.ibm.team.repository.service.internal.db.jdbcwrappers.stat.PreparedStatementStatWrapper.executeUpdate(PreparedStatementStatWrapper.java:62) at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.PreparedStatementErrLogWrapper.executeUpdate(PreparedStatementErrLogWrapper.java:86) at com.ibm.team.repository.service.internal.db.jdbcwrappers.leak.PreparedStatementLeakWrapper.executeUpdate(PreparedStatementLeakWrapper.java:58) at com.ibm.team.repository.service.db.provider.CaseSensitivityValidator.buildTable(CaseSensitivityValidator.java:165) at com.ibm.team.repository.service.db.provider.CaseSensitivityValidator.setupTestTable(CaseSensitivityValidator.java:160) at com.ibm.team.repository.service.db.provider.CaseSensitivityValidator.testCaseSensitivity(CaseSensitivityValidator.java:213) ... 47 more Does anyone know a way around this or an easy way to create the tables? |
4 answers
![]()
Have you reviewed this topic in the online help for setting up an Oracle database prior to configuring the server?
https://publib.boulder.ibm.com/infocenter/rpcmpose/v2r0/index.jsp?topic=/com.ibm.rational.rrc.install_upgrade.doc/topics/t_setup_oracle.html |
![]()
To resolve this error, assign the DBA Role for the database user created.
In the database configuration steps during the initialization of RRC 2.0 (specifically steps 2.2 and 2.3) I get errors when trying to create the tables for oracle. |
![]()
The DBA role seemed to solve the problem for us. It was the only role left out in the documentation for setting up permissions for Oracle.
Thanks for the help. |
![]()
grant dba role to jazzdbuser is not the best solution.
just adjust quota on default tablespace of jazzdbuser alter user USERNAME quota unlimited on TABLESPACE_NAME; it works fine. |
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.