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

create DB warehouse failed

Hi,

When i tried to setup CLM, it failed to create DB Warehouse tables because of following errors:

The data warehouse tables could not be created. Try the action again.ID CRJAZ1745E

CRRTC8030E The creation of the data warehouse failed.
com.ibm.team.repository.common.TeamRepositoryException: ALTER DATABASE [dw_dev] ADD FILE ( NAME = N'VNF_32K', FILENAME = N'D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\VNF_32K.ndf' , SIZE = 51200KB , FILEGROWTH = 51200KB ) TO FILEGROUP [VNF_32K] 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.sqlserver.internal.SqlServerDataWarehouseDbProvider.setupDataWarehouseCoreSpace(SqlServerDataWarehouseDbProvider.java:33) 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.$Proxy2209.setupDataWarehouseCoreSpace(Unknown Source) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$1.run(RemoteDatabaseService.java:235) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$6.run(RemoteDatabaseService.java:547) at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:476) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.write(RemoteDatabaseService.java:509) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.createRemoteSchemas(RemoteDatabaseService.java:223) 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.$Proxy77.createRemoteSchemas(Unknown Source) at com.ibm.team.datawarehouse.service.internal.InternalDataWarehouseService$6.run(InternalDataWarehouseService.java:769) Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: One or more files listed in the statement could not be found or could not be initialized. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216) at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515) at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:792) at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:689) at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696) at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715) at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180) at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155) at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(SQLServerStatement.java:662) 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) ... 24 more


please suggest solutions.

Thanks,

Wei

0 votes

Comments

Hi Wei,

What are you specifying for the Database Table Space Folder in JTS Setup for the data warehouse?

This filename = N in the error you provided does not look correct:
FILENAME = N'D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\VNF_32K.ndf'

I cannot recall if that needs to be in quotes if there are spaces in the patch, e.g. Program Files.

Thanks,
Brett

more details :

This is new CLM install, my plan was to use one MS SQL DB to support three installations.

back to few weeks ago, i installed CLM (test servers), it went fine, test servers (table name is dw_test) are up and running.  now i start to install Dev servers, which share same DB but with different tables (for example, dw_dev).

and yes, on MS SQL server, there is an existing "D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\VNF_32K.ndf" file.

Wei


thanks Brett,

the path i defined in Database Table Space Folder (D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA) worked before, it is the DB path on MS SQL server.

my concern is to use same DB to support two sets of CLM servers, "DATA\VNF_32K.ndf" may not able to be shared by two set of CLM Servers.

Wei





Accepted answer

Permanent link
Hi Wei,
I am not familiar with MS SQL Server, but it sounds like you are creating a new tablespace where there is already an existing tablespace. The error is caused by that VNF_32K.ndf already exists in the folder you specified as table space location.
In Setup Wizard, you need to specify the empty folder such as D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA2\.
I am not sure if it means they are using the same DB in MS SQL perspective, but if it is overwritten, then the data in dw_test will be lost.
wei yu selected this answer as the correct answer

0 votes

Comments

Second that. This looks to have the exact same symptom as this post more than 2 years ago.
https://jazz.net/forum/questions/158429/creation-of-datawarehouse-for-clm-406-failing

thanks guys. solution works

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: Dec 12 '16, 10:46 a.m.

Question was seen: 1,532 times

Last updated: Dec 18 '17, 3:26 a.m.

Confirmation Cancel Confirm