Update warehouse from 3.0.1 to 4
Shamray Alexandr (1●5●5)
| asked Aug 07 '12, 6:18 p.m.
edited Sep 19 '12, 10:47 a.m. by Ralph Schoon (63.5k●3●36●46) when I update jts for MS SQL Server an error occur: 2012-08-08 02:07:11,346 Невозможно вставить явное значение для столбца идентификаторов в таблице "D_DATE", когда параметр IDENTITY_INSERT имеет значение OFF. com.ibm.team.repository.common.TeamRepositoryException: Невозможно вставить явное значение для столбца идентификаторов в таблице "D_DATE", когда параметр IDENTITY_INSERT имеет значение OFF. at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.populateDate(RemoteDatabaseService.java:520) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.access$0(RemoteDatabaseService.java:278) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$2.run(RemoteDatabaseService.java:184) 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.upgradeRemoteSchemas(RemoteDatabaseService.java:164) 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 $Proxy414.upgradeRemoteSchemas(Unknown Source) at com.ibm.team.datawarehouse.service.internal.UpgradeDataWarehouseCommand.execute(UpgradeDataWarehouseCommand.java:19) at com.ibm.team.repotools.command.AbstractCommand.execute(AbstractCommand.java:66) at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.run(RepositoryToolsApplication.java:768) at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.start(RepositoryToolsApplication.java:843) 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:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:600) 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.microsoft.sqlserver.jdbc.SQLServerException: Невозможно вставить явное значение для столбца идентификаторов в таблице "D_DATE", когда параметр IDENTITY_INSERT имеет значение OFF. 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.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:404) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350) 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.SQLServerPreparedStatement.execute(SQLServerPreparedStatement.java:332) at com.ibm.team.repository.service.internal.db.jdbcwrappers.stat.PreparedStatementStatWrapper.execute(PreparedStatementStatWrapper.java:54) at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.PreparedStatementErrLogWrapper.execute(PreparedStatementErrLogWrapper.java:68) at com.ibm.team.repository.service.internal.db.jdbcwrappers.leak.PreparedStatementLeakWrapper.execute(PreparedStatementLeakWrapper.java:53) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.populateDate(RemoteDatabaseService.java:490) ... 31 more |
One answer
Hi Shamray,
The above error happens because the RIDW.D_DATE no longer has IDENTITY_INSERT=ON We currently set that property during creation of the data warehouse. But it looks like the SQL Server will turn it off if another table gets it. During upgrade we assume the property is still set and we do not set it. The above is error is harmless as it happens at the end of the upgrade process and it just tries to add future D_DATE entries. So for now ignore the error. We will work on handling this corner case in future releases. The D_DATE table already contains enough future dates until year 2050. |
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.