It's all about the answers!

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

×7,451
×6,108
×4

question asked: Mar 29 '17, 12:33 p.m.
question was seen: 1,484 times
last updated: Aug 20 '18, 6:50 p.m.

Related questions

[RESOLVED] Adding a data warehouse to an existing CLMv6 environment?

0
Erich Wolz (162●2●7●11) | asked Mar 29 '17, 12:33 p.m.
edited Aug 20 '18, 6:50 p.m.

I am trying to retroactively add a DB2 data warehouse to an existing CLM environment.  https://jazz.net/wiki/bin/view/Main/MoreControlOverTheDB2DataWarehouseSetup?cm_mc_uid=88543592626814889867658&cm_mc_sid_50200000=1490051697 says that "repotools-jts -createWarehouse" will create the various tablespaces that will be used by the data warehouse, but as near as i can tell from the below log file contents (/opt/IBM/JazzTeamServer/server/repotools-jts_createWarehouse.log), that does not seem to be the case.  (This page goes on to say that tablespace creation is implemented by the createDB/bufferpool.sql and createDB/tbspace.sql scripts... but I don't even see a createDB directory.)  Any ideas how to proceed?

:
:
2017-03-29 10:33:15,482 CRRTC8039I The connection to the following data warehouse database was successful:
 DB Product Name: DB2/AIX64
  DB Product Version: SQL10058
  DB URL: //localhost:50000/DW:user=xxxxxxxx;password=xxxxxxxx;
  JDBC Driver Name: IBM Data Server Driver for JDBC and SQLJ
  JDBC Driver Version: 4.17.28
2017-03-29 10:33:15,511 CREATE TABLE ETL_INFO (ETL_ID VARCHAR(36) NOT NULL, START_DATETIME TIMESTAMP DEFAULT CURRENT TIMESTAMP NOT NULL , E
ND_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
com.ibm.team.repository.common.TeamRepositoryException: CREATE TABLE ETL_INFO (ETL_ID VARCHAR(36) NOT NULL, START_DATETIME TIMESTAMP DEFAUL
T CURRENT TIMESTAMP NOT NULL , END_DATETIME TIMESTAMP, STATUS INTEGER, DATASOURCE_ID VARCHAR(36) NOT NULL, LOAD_TYPE CHAR(1) DEFAULT 'D' NO
T NULL) IN VNF_32K INDEX IN VNF_IDX
        at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.internalExecuteSql(AbstractDataWarehouseDbProvider.java:409)
        at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.executeSql(AbstractDataWarehouseDbProvider.java:232)
        at com.ibm.team.datawarehouse.service.db2.internal.DB2DataWarehouseDbProvider.createDataWarehouseCoreTables(DB2DataWarehouseDbProvider.java:37)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
        at java.lang.reflect.Method.invoke(Method.java:620)
        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.$Proxy595.createDataWarehouseCoreTables(Unknown Source)
        at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$1.run(RemoteDatabaseService.java:239)
        at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$6.run(RemoteDatabaseService.java:549)
        at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:476)
        at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.write(RemoteDatabaseService.java:511)
        at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.createRemoteSchemas(RemoteDatabaseService.java:225)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
        at java.lang.reflect.Method.invoke(Method.java:620)
        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.$Proxy61.createRemoteSchemas(Unknown Source)
        at com.ibm.team.datawarehouse.service.internal.CreateDataWarehouseCommand.execute(CreateDataWarehouseCommand.java:27)
        at com.ibm.team.repotools.command.AbstractCommand.execute(AbstractCommand.java:68)
        at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.run(RepositoryToolsApplication.java:833)
        at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.start(RepositoryToolsApplication.java:908)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
        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:369)
        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:95)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
        at java.lang.reflect.Method.invoke(Method.java:620)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
        at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
Caused by: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=VNF_32K, 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.c(uo.java:2771)
        at com.ibm.db2.jcc.am.uo.d(uo.java:2759)
        at com.ibm.db2.jcc.am.uo.b(uo.java:2126)
        at com.ibm.db2.jcc.t4.ab.i(ab.java:226)
        at com.ibm.db2.jcc.t4.ab.c(ab.java:48)
        at com.ibm.db2.jcc.t4.o.b(o.java:38)
        at com.ibm.db2.jcc.t4.tb.h(tb.java:124)
        at com.ibm.db2.jcc.am.uo.jb(uo.java:2121)
        at com.ibm.db2.jcc.am.uo.a(uo.java:3294)
        at com.ibm.db2.jcc.am.uo.e(uo.java:1091)
        at com.ibm.db2.jcc.am.uo.execute(uo.java:1070)
        at com.ibm.team.repository.service.internal.db.jdbcwrappers.stat.StatementStatWrapper.execute(StatementStatWrapper.java:242)
        at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.StatementErrLogWrapper.execute(StatementErrLogWrapper.java:173)
        at com.ibm.team.repository.service.internal.db.jdbcwrappers.leak.StatementLeakWrapper.execute(StatementLeakWrapper.java:71)
        at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.executeStatement(AbstractDataWarehouseDbProvider.java:262)
        at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.internalExecuteSql(AbstractDataWarehouseDbProvider.java:384)
        ... 40 more
2017-03-29 10:33:15,513 CRJAZ1728E A Repository Tools error occurred. For more information, see this log file: /opt/IBM/JazzTeamServer/server/repotools-jts_createWarehouse.log

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Erich Wolz (162●2●7●11) | answered Jun 14 '17, 12:04 p.m.

As it turns out, by skipping the data warehouse creation during initial setup, a var was set in the teamserver.properties file preventing the automatic setup of the data warehouse db.   

Changing com.ibm.team.datawarehouse.db.automatic.setup from false to true and stopping/restarting WAS allowed me to create the data warehouse tables.

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.