It's all about the answers!

Ask a question

Error when creating DW tables


Milan Krivic (98010172140) | asked Apr 05 '11, 3:23 a.m.
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, 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,

8 answers



permanent link
Milan Krivic (98010172140) | answered Apr 06 '11, 3:55 p.m.


OK, I have the same problem as you had. Can you explain in details what you did to fix this. The setup wizard "should" take care of this, is this a bug ?

Thanks Henrik


Hi Henrik,
I created these five table spaces for DW database:
VNF_32K,
VNF_IDX,
VSTR_32K,
VSTR_IDX and
REQHIS_F20.

these five TS were missing...

after that, I run for every application this command:

ex: repotools-jts -createWarehouse -clean
repotools-ccm -createWarehouse -clean etc...

you should get the message about successfully created warehouse.
after that, you can do your setup.

hope it will help you too.

P.S. You can add a comment to this work item which I opened today:
http://jazz.net/jazz/web/projects/Jazz%20Collaborative%20ALM#action=com.ibm.team.workitem.viewWorkItem&id=160777

even I wrote that I solved the problem, you can write that problem appeared at you also so they could investigate this.

permanent link
Milan Krivic (98010172140) | answered Apr 05 '11, 6:39 a.m.
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, 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,


Actually,

this is the error message:

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) ... 24 more

permanent link
Milan Krivic (98010172140) | answered Apr 06 '11, 8:28 a.m.
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, 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,


Actually,

this is the error message:

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) ... 24 more

permanent link
Milan Krivic (98010172140) | answered Apr 06 '11, 8:32 a.m.
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, 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,


Actually,

this is the error message:

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) ... 24 more

This problem is solved by creating additional table spaces in DW table for all three applications.

permanent link
Milan Krivic (98010172140) | answered Apr 06 '11, 8:33 a.m.
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, 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,


This problem is solved by creating additional table spaces in DW table for all three applications.

permanent link
Henrik Westrell (43143) | answered Apr 06 '11, 2:11 p.m.


OK, I have the same problem as you had. Can you explain in details what you did to fix this. The setup wizard "should" take care of this, is this a bug ?

Thanks Henrik

permanent link
Henrik Westrell (43143) | answered Apr 06 '11, 5:14 p.m.
Thanks. Hmm how did you figure out those tablespaces were missing ?
Anyway, it worked Thanks again.

Cheers
Henrik

permanent link
Milan Krivic (98010172140) | answered Apr 07 '11, 3:14 a.m.
Thanks. Hmm how did you figure out those tablespaces were missing ?
Anyway, it worked Thanks again.

Cheers
Henrik


I got some -204 sql error, and contacted one of my db2 administrators, and he explained to me that this message points to missing some of db2 objects, in this case, VNF_32K first, which was table space. I created one, and after running createWarehouse, I got messages for other TS. Creating one by one, I solved the problem.

I am glad it helped to you also.

Regards,

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.