It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×4,316
×2

question asked: May 10 '13, 1:42 p.m.
question was seen: 5,641 times
last updated: May 29 '13, 1:50 p.m.

Related questions

An error occurred while creating data warehouse tables. Please try again.ID CRJAZ1745E

0
John Marinelli (13●1●1●1) | asked May 10 '13, 1:42 p.m.

The data warehouse tables get created for CCM but fails on QM. My dba think it's tring to create the same tables. Any Idea's?

version 4.0.1

CRRTC8030E The creation of the data warehouse failed.
com.ibm.team.repository.common.TeamRepositoryException: CREATE TABLESPACE VNF_IDX LOGGING DATAFILE '+DATA/RATIONAL/DATAFILE/VNF_IDX_1.ora' SIZE 200M AUTOEXTEND ON NEXT 50M MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.internalExecuteSql(AbstractDataWarehouseDbProvider.java:247) at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.executeSql(AbstractDataWarehouseDbProvider.java:113) at com.ibm.team.datawarehouse.service.oracle.internal.OracleDataWarehouseDbProvider.createDataWarehouseCoreTables(OracleDataWarehouseDbProvider.java:27) 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 $Proxy2521.createDataWarehouseCoreTables(Unknown Source) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$1.run(RemoteDatabaseService.java:141) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$5.run(RemoteDatabaseService.java:254) at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:381) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.write(RemoteDatabaseService.java:244) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.createRemoteSchemas(RemoteDatabaseService.java:130) 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 $Proxy2453.createRemoteSchemas(Unknown Source) at com.ibm.team.datawarehouse.service.internal.InternalDataWarehouseService$12.run(InternalDataWarehouseService.java:1540) Caused by: java.sql.SQLException: ORA-01543: tablespace 'VNF_IDX' already exists at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395) at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521) at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:194) at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1000) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1307) at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1882) at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1847) at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:301) at com.ibm.team.repository.service.internal.db.jdbcwrappers.stat.StatementStatWrapper.execute(StatementStatWrapper.java:178) at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.StatementErrLogWrapper.execute(StatementErrLogWrapper.java:169) at com.ibm.team.repository.service.internal.db.jdbcwrappers.leak.StatementLeakWrapper.execute(StatementLeakWrapper.java:70) at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.executeStatement(AbstractDataWarehouseDbProvider.java:108) at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.internalExecuteSql(AbstractDataWarehouseDbProvider.java:227) ... 24 more

Accepted answer

1
permanent link
Zachary Demers (201●3●7) | answered May 29 '13, 1:50 p.m.
This issue was solved by the PMR John had opened.

In the jts data warehouse connected successfully.  When testing connection in the ccm data warehouse in setup, it connected successfully and mentioned that they needed to create tables for the data warehouse.  Once the customer created tables, it gave the error "Caused by: java.sql.SQLException: ORA-01543: tablespace 'VNF_IDX' already exists".

The cause of this error was that the schema prefix not being set for the CCM data warehouse, as it was set for the JTS database.  After adding the schema prefix, they were able to proceed with the ccm data warehouse configuration.
John Marinelli selected this answer as the correct answer

2 other answers

Most liked answers ↑|Newest answers|Oldest answers

2
permanent link
Kot T. (1.5k●1●13●19) | answered May 10 '13, 2:16 p.m.
JAZZ DEVELOPER
Hi John,

The error message indicates that tablespace 'VNF_IDX' already exists. So, it is possible that the data warehouse database was created before. If you do not expect any data warehouse database to exist (for this CLM and any other CLMs using this same Oracle) and would like to drop/clean data files that were incorrectly created before, you can review the steps the 'Dropping the data warehouse' section in
https://jazz.net/wiki/bin/view/Main/MoreControlOverTheOracleDataWarehouseSetup

Only one data warehouse database is needed per JTS. All the applications registered with the JTS will be using the same data warehouse database. So, when you step thru the jts/setup, you will need to enter the DW database connection information and create tables for the DW database only in the JTS's configure data warehouse section. The 'configure data warehouse' page of the other application (CCM, QM) will reuse the same information you entered previously.
0
permanent link
Indradri Basu (1.8k●1●5●14) | answered May 10 '13, 3:15 p.m.
Hi John,
You may want to double check if the user has DBA rights as I suppose that is necessary to configure the DW successfully.

Your answer

Register or to post 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.