It's all about the answers!

Ask a question

Error occurred while creating data warehouse tables (SQL Server)


Carson Holmes (11113544) | asked Jun 25 '12, 5:51 p.m.
Despite the errors in these instructions:
Which tell me to execute this on database dw without first creating it:
ALTER DATABASE dw COLLATE SQL_Latin1_General_CP1_CS_AS
GO
I did create the dw database in SQL Server, set the owner, etc..  The Test Connection passes....
The database exists, but is not configured to contain the data warehouse. Use the "Create Tables" button in Step 3 to configure the data warehouse for Jazz.ID CRJAZ1744E 

However when I try to "Create Tables" I get the following error.  Please advise.  Thanks, Carson

An error occurred while creating data warehouse tables. Please try again.ID CRJAZ1745E
hide details
CRRTC8030E The creation of the data warehouse failed.
com.ibm.team.repository.common.TeamRepositoryException: ALTER DATABASE [dw] ADD FILE ( NAME = N'VNF_32K', FILENAME = N'/dw\VNF_32K.ndf' , SIZE = 51200KB , FILEGROWTH = 51200KB ) TO FILEGROUP [VNF_32K] 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.sqlserver.internal.SqlServerDataWarehouseDbProvider.createDataWarehouseCoreTables(SqlServerDataWarehouseDbProvider.java:29) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:600) 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 $Proxy1947.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:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:600) 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 $Proxy1920.createRemoteSchemas(Unknown Source) at com.ibm.team.datawarehouse.service.internal.InternalDataWarehouseService$12.run(InternalDataWarehouseService.java:1507) Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: A file activation error occurred. The physical file name '/dw\VNF_32K.ndf' may be incorrect. Diagnose and correct additional errors, and retry the operation. 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: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

2 answers



permanent link
Der M (6121418) | answered Jun 26 '12, 5:58 a.m.
Is your database server serup with SQL_Latin1_General_CP1_CS_AS collation?  If not the SQL will not run as you need to have a CASE SENSITIVE db

permanent link
Karl Weinert (2.0k52736) | answered Jun 26 '12, 8:43 a.m.
JAZZ DEVELOPER
It looks like a problem with the Database Table Space Folder
Note this part of the error.
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: A file activation error occurred. The physical file name '/dw\VNF_32K.ndf' may be incorrect. Diagnose and correct additional errors, and retry the operation

The Database Table Space Folder value needs to point to an existing directory using the full path.
i.e. C:\dw



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.