Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Error when creating DW tables in CLM beta 3

Hi,

I followed instructions for setup CLM beta 3. I did everything, but I am confused regarding one thing. During the setup of server, I was asked to create DW tables. When I clicked Create I got error:

The database creation failed with an exception
com.ibm.team.repository.common.TeamRepositoryException: CREATE TABLE ETL_INFO (ETL_ID VARCHAR(36) NOT NULL, START_DATETIME TIMESTAMP DEFAULT CURRENT TIMESTAMP NOT NULL , END_DATETIME TIMESTAMP, STATUS INTEGER, DATASOURCE_ID VARCHAR(36) NOT NULL, LOAD_TYPE CHAR(1) DEFAULT 'D' NOT NULL) IN VNF_32K INDEX IN VNF_IDX at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.internalExecuteSql(AbstractDataWarehouseDbProvider.java:215) at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.executeSql(AbstractDataWarehouseDbProvider.java:92) at com.ibm.team.datawarehouse.service.db2.internal.DB2DataWarehouseDbProvider.createDataWarehouseCoreTables(DB2DataWarehouseDbProvider.java:32) 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 $Proxy616.createDataWarehouseCoreTables(Unknown Source) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$1.run(RemoteDatabaseService.java:125) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$4.run(RemoteDatabaseService.java:191) at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:346) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.write(RemoteDatabaseService.java:181) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.createRemoteSchemas(RemoteDatabaseService.java:113) 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 $Proxy46.createRemoteSchemas(Unknown Source) at com.ibm.team.datawarehouse.service.internal.InternalDataWarehouseService$10.run(InternalDataWarehouseService.java:1213) Caused by: com.ibm.db2.jcc.am.io: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=VNF_32K, DRIVER=3.57.82 at com.ibm.db2.jcc.am.bd.a(bd.java:676) 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.c(km.java:2506) at com.ibm.db2.jcc.am.km.d(km.java:2483) at com.ibm.db2.jcc.am.km.b(km.java:1903) at com.ibm.db2.jcc.t4.db.h(db.java:220) at com.ibm.db2.jcc.t4.db.b(db.java:46) at com.ibm.db2.jcc.t4.t.b(t.java:38) at com.ibm.db2.jcc.t4.sb.g(sb.java:114) at com.ibm.db2.jcc.am.km.db(km.java:1898) at com.ibm.db2.jcc.am.km.a(km.java:2899) at com.ibm.db2.jcc.am.km.e(km.java:985) at com.ibm.db2.jcc.am.km.execute(km.java:969) 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.internalExecuteSql(AbstractDataWarehouseDbProvider.java:203)

but I didn't also seen some repotools batch for creating DW tables.
So, when I open every teamserver.properties file, in first location lines, I must configure DB name of its application, right?

com.ibm.team.repository.db.vendor = DB2
com.ibm.team.repository.db.jdbc.location=//<fully>:50000/JTS:user=db2admin;password={password};
com.ibm.team.repository.db.jdbc.password=db2admin

What about second location below?

com.ibm.team.datawarehouse.db.vendor = DB2
com.ibm.team.datawarehouse.db.jdbc.location=//<fully>:50000/DW:user=db2admin;password={password};
com.ibm.team.datawarehouse.db.jdbc.password=db2admin

Must I in every teamserver.properties file configure this location to be for DW database?

Any help would be appreciated!

Regards,

0 votes



3 answers

Permanent link
Hi,

I followed instructions for setup CLM beta 3. I did everything, but I am confused regarding one thing. During the setup of server, I was asked to create DW tables. When I clicked Create I got error:

The database creation failed with an exception
com.ibm.team.repository.common.TeamRepositoryException: CREATE TABLE ETL_INFO (ETL_ID VARCHAR(36) NOT NULL, START_DATETIME TIMESTAMP DEFAULT CURRENT TIMESTAMP NOT NULL , END_DATETIME TIMESTAMP, STATUS INTEGER, DATASOURCE_ID VARCHAR(36) NOT NULL, LOAD_TYPE CHAR(1) DEFAULT 'D' NOT NULL) IN VNF_32K INDEX IN VNF_IDX at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.internalExecuteSql(AbstractDataWarehouseDbProvider.java:215) at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.executeSql(AbstractDataWarehouseDbProvider.java:92) at com.ibm.team.datawarehouse.service.db2.internal.DB2DataWarehouseDbProvider.createDataWarehouseCoreTables(DB2DataWarehouseDbProvider.java:32) 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 $Proxy616.createDataWarehouseCoreTables(Unknown Source) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$1.run(RemoteDatabaseService.java:125) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$4.run(RemoteDatabaseService.java:191) at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:346) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.write(RemoteDatabaseService.java:181) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.createRemoteSchemas(RemoteDatabaseService.java:113) 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 $Proxy46.createRemoteSchemas(Unknown Source) at com.ibm.team.datawarehouse.service.internal.InternalDataWarehouseService$10.run(InternalDataWarehouseService.java:1213) Caused by: com.ibm.db2.jcc.am.io: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=VNF_32K, DRIVER=3.57.82 at com.ibm.db2.jcc.am.bd.a(bd.java:676) 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.c(km.java:2506) at com.ibm.db2.jcc.am.km.d(km.java:2483) at com.ibm.db2.jcc.am.km.b(km.java:1903) at com.ibm.db2.jcc.t4.db.h(db.java:220) at com.ibm.db2.jcc.t4.db.b(db.java:46) at com.ibm.db2.jcc.t4.t.b(t.java:38) at com.ibm.db2.jcc.t4.sb.g(sb.java:114) at com.ibm.db2.jcc.am.km.db(km.java:1898) at com.ibm.db2.jcc.am.km.a(km.java:2899) at com.ibm.db2.jcc.am.km.e(km.java:985) at com.ibm.db2.jcc.am.km.execute(km.java:969) 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.internalExecuteSql(AbstractDataWarehouseDbProvider.java:203)

but I didn't also seen some repotools batch for creating DW tables.
So, when I open every teamserver.properties file, in first location lines, I must configure DB name of its application, right?

com.ibm.team.repository.db.vendor = DB2
com.ibm.team.repository.db.jdbc.location=//<fully>:50000/JTS:user=db2admin;password={password};
com.ibm.team.repository.db.jdbc.password=db2admin

What about second location below?

com.ibm.team.datawarehouse.db.vendor = DB2
com.ibm.team.datawarehouse.db.jdbc.location=//<fully>:50000/DW:user=db2admin;password={password};
com.ibm.team.datawarehouse.db.jdbc.password=db2admin

Must I in every teamserver.properties file configure this location to be for DW database?

Any help would be appreciated!

Regards,


I worked with Milan offline on this one, he was successful in his second attempt, and we were unable to recreate the problem.

james
RTC Reports Team Lead

0 votes


Permanent link
I am trying to install Beta 3 on DB2 (Red Hat 5.5) and running in to the exact same problem and can't figure it out. I have a reproducible case...... Stuck...

Thanks,
-David




Hi,

I followed instructions for setup CLM beta 3. I did everything, but I am confused regarding one thing. During the setup of server, I was asked to create DW tables. When I clicked Create I got error:

The database creation failed with an exception
com.ibm.team.repository.common.TeamRepositoryException: CREATE TABLE ETL_INFO (ETL_ID VARCHAR(36) NOT NULL, START_DATETIME TIMESTAMP DEFAULT CURRENT TIMESTAMP NOT NULL , END_DATETIME TIMESTAMP, STATUS INTEGER, DATASOURCE_ID VARCHAR(36) NOT NULL, LOAD_TYPE CHAR(1) DEFAULT 'D' NOT NULL) IN VNF_32K INDEX IN VNF_IDX at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.internalExecuteSql(AbstractDataWarehouseDbProvider.java:215) at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.executeSql(AbstractDataWarehouseDbProvider.java:92) at com.ibm.team.datawarehouse.service.db2.internal.DB2DataWarehouseDbProvider.createDataWarehouseCoreTables(DB2DataWarehouseDbProvider.java:32) 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 $Proxy616.createDataWarehouseCoreTables(Unknown Source) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$1.run(RemoteDatabaseService.java:125) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$4.run(RemoteDatabaseService.java:191) at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:346) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.write(RemoteDatabaseService.java:181) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.createRemoteSchemas(RemoteDatabaseService.java:113) 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 $Proxy46.createRemoteSchemas(Unknown Source) at com.ibm.team.datawarehouse.service.internal.InternalDataWarehouseService$10.run(InternalDataWarehouseService.java:1213) Caused by: com.ibm.db2.jcc.am.io: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=VNF_32K, DRIVER=3.57.82 at com.ibm.db2.jcc.am.bd.a(bd.java:676) 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.c(km.java:2506) at com.ibm.db2.jcc.am.km.d(km.java:2483) at com.ibm.db2.jcc.am.km.b(km.java:1903) at com.ibm.db2.jcc.t4.db.h(db.java:220) at com.ibm.db2.jcc.t4.db.b(db.java:46) at com.ibm.db2.jcc.t4.t.b(t.java:38) at com.ibm.db2.jcc.t4.sb.g(sb.java:114) at com.ibm.db2.jcc.am.km.db(km.java:1898) at com.ibm.db2.jcc.am.km.a(km.java:2899) at com.ibm.db2.jcc.am.km.e(km.java:985) at com.ibm.db2.jcc.am.km.execute(km.java:969) 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.internalExecuteSql(AbstractDataWarehouseDbProvider.java:203)

but I didn't also seen some repotools batch for creating DW tables.
So, when I open every teamserver.properties file, in first location lines, I must configure DB name of its application, right?

com.ibm.team.repository.db.vendor = DB2
com.ibm.team.repository.db.jdbc.location=//<fully>:50000/JTS:user=db2admin;password={password};
com.ibm.team.repository.db.jdbc.password=db2admin

What about second location below?

com.ibm.team.datawarehouse.db.vendor = DB2
com.ibm.team.datawarehouse.db.jdbc.location=//<fully>:50000/DW:user=db2admin;password={password};
com.ibm.team.datawarehouse.db.jdbc.password=db2admin

Must I in every teamserver.properties file configure this location to be for DW database?

Any help would be appreciated!

Regards,


I worked with Milan offline on this one, he was successful in his second attempt, and we were unable to recreate the problem.

james
RTC Reports Team Lead

0 votes


Permanent link
I am trying to install Beta 3 on DB2 (Red Hat 5.5) and running in to the exact same problem and can't figure it out. I have a reproducible case...... Stuck...

Thanks,
-David

Please take a lok at CLM forum, there is the same post like this, with the same subject, and I described how I resolved the problem, here is the link:

http://jazz.net/forums/viewtopic.php?t=16290

Hi,

I followed instructions for setup CLM beta 3. I did everything, but I am confused regarding one thing. During the setup of server, I was asked to create DW tables. When I clicked Create I got error:

The database creation failed with an exception
com.ibm.team.repository.common.TeamRepositoryException: CREATE TABLE ETL_INFO (ETL_ID VARCHAR(36) NOT NULL, START_DATETIME TIMESTAMP DEFAULT CURRENT TIMESTAMP NOT NULL , END_DATETIME TIMESTAMP, STATUS INTEGER, DATASOURCE_ID VARCHAR(36) NOT NULL, LOAD_TYPE CHAR(1) DEFAULT 'D' NOT NULL) IN VNF_32K INDEX IN VNF_IDX at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.internalExecuteSql(AbstractDataWarehouseDbProvider.java:215) at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.executeSql(AbstractDataWarehouseDbProvider.java:92) at com.ibm.team.datawarehouse.service.db2.internal.DB2DataWarehouseDbProvider.createDataWarehouseCoreTables(DB2DataWarehouseDbProvider.java:32) 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 $Proxy616.createDataWarehouseCoreTables(Unknown Source) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$1.run(RemoteDatabaseService.java:125) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$4.run(RemoteDatabaseService.java:191) at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:346) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.write(RemoteDatabaseService.java:181) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.createRemoteSchemas(RemoteDatabaseService.java:113) 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 $Proxy46.createRemoteSchemas(Unknown Source) at com.ibm.team.datawarehouse.service.internal.InternalDataWarehouseService$10.run(InternalDataWarehouseService.java:1213) Caused by: com.ibm.db2.jcc.am.io: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=VNF_32K, DRIVER=3.57.82 at com.ibm.db2.jcc.am.bd.a(bd.java:676) 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.c(km.java:2506) at com.ibm.db2.jcc.am.km.d(km.java:2483) at com.ibm.db2.jcc.am.km.b(km.java:1903) at com.ibm.db2.jcc.t4.db.h(db.java:220) at com.ibm.db2.jcc.t4.db.b(db.java:46) at com.ibm.db2.jcc.t4.t.b(t.java:38) at com.ibm.db2.jcc.t4.sb.g(sb.java:114) at com.ibm.db2.jcc.am.km.db(km.java:1898) at com.ibm.db2.jcc.am.km.a(km.java:2899) at com.ibm.db2.jcc.am.km.e(km.java:985) at com.ibm.db2.jcc.am.km.execute(km.java:969) 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.internalExecuteSql(AbstractDataWarehouseDbProvider.java:203)

but I didn't also seen some repotools batch for creating DW tables.
So, when I open every teamserver.properties file, in first location lines, I must configure DB name of its application, right?

com.ibm.team.repository.db.vendor = DB2
com.ibm.team.repository.db.jdbc.location=//<fully>:50000/JTS:user=db2admin;password={password};
com.ibm.team.repository.db.jdbc.password=db2admin

What about second location below?

com.ibm.team.datawarehouse.db.vendor = DB2
com.ibm.team.datawarehouse.db.jdbc.location=//<fully>:50000/DW:user=db2admin;password={password};
com.ibm.team.datawarehouse.db.jdbc.password=db2admin

Must I in every teamserver.properties file configure this location to be for DW database?

Any help would be appreciated!

Regards,


I worked with Milan offline on this one, he was successful in his second attempt, and we were unable to recreate the problem.

james
RTC Reports Team Lead

0 votes

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Apr 05 '11, 10:58 a.m.

Question was seen: 6,594 times

Last updated: Apr 05 '11, 10:58 a.m.

Confirmation Cancel Confirm