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

Problem during the migration from Derby to MSQL

Hi all,

I would like to increase the number of users in my platform so I have tried to migrate my DERBY databases to Microsoft SQL Server 2005.

I have followed these documentations :
- General procedure
- Database creation on MSQL
- Manuel configuration of the database connections

So, I have configured for the jts application the file conf/jts/teamserver.properties :

com.ibm.team.repository.user.registry.type=DETECT
com.ibm.team.repository.db.jdbc.location=//192.168.1.157\:1433;databaseName\=rtc_test_jts;user\=rtc_test_user;password\={password}
com.ibm.team.repository.db.jdbc.password=
com.ibm.team.jfs.index.root.directory=/opt/IBM/JazzTeamServer/server/conf/jts/indices
com.ibm.team.repository.changeEvent.expirationDefault=1209600
com.ibm.team.repository.server.webapp.url=https\://rtc-test.mydomain.com/jts
com.ibm.team.repository.db.repoLockId=_CVYKAHKWEaGw5dNSMJSQcA
com.ibm.team.datawarehouse.db.vendor=SQLSERVER
com.ibm.team.repository.ws.allow.admin.access=false
com.ibm.team.repository.web.suppressedPages={"com.ibm.team.repository.web.admin"\: }
com.ibm.team.repository.db.vendor=SQLSERVER
com.ibm.team.datawarehouse.db.jdbc.password=
com.ibm.team.repository.notification.mail.from=rtc-test@mydomain.com
com.ibm.team.datawarehouse.datawarehouse.provider=Remote
com.ibm.team.repository.web.helpuri=/clmhelp/index.jsp
com.ibm.team.repository.notification.mail.smtp.server=mail.mydomain.com
com.ibm.team.datawarehouse.auth.userId=reportrtc
com.ibm.team.repository.server.repourl.port.http=80
com.ibm.team.datawarehouse.db.automatic.setup=true
com.ibm.team.datawarehouse.auth.password=
com.ibm.team.fulltext.indexLocation=/opt/IBM/JazzTeamServer/server/conf/jts/indices/workitemindex
com.ibm.team.datawarehouse.db.jdbc.location=//192.168.1.157\:1433;databaseName\=rtc_test_jts;user\=rtc_test_user;password\={password}
com.ibm.team.repository.notification.mail.enabled=true
com.ibm.team.datawarehouse.db.base.folder=C:\\Program Files\\Microsoft\ SQL\ Server\\MSSQL.1\\MSSQL\\Data\\jazztestdw
com.ibm.team.datawarehouse.report.user=RPTUSER
com.ibm.team.repository.web.pageorder={"com.ibm.team.repository.web.admin"\: , "com.ibm.team.process.web.projectArea"\: ,"com.ibm.team.process.web.projectAreaList"\: }
com.ibm.team.repository.ws.allow.identity.assertion=false
com.ibm.team.repository.server.repourl.port.https=443
com.ibm.team.repository.changeEvent.expirationByCategory=SystemLog\:259200
com.ibm.team.datawarehouse.datawarehouse.jobs.enabled=true


With the command repotools-jts -createTables there is no problem. The SQL connection is established and tables are created.

Then, the problem is with the command repotools-jts -createWarehouse, I have this error :

root@rtc-test:/opt/IBM/JazzTeamServer/server# more /opt/IBM/JazzTeamServer/server/repotools-jts_createWarehouse.log
2012-03-20 15:39:26,179 Repo Tools
2012-03-20 15:39:26,180 java.version=1.5.0
2012-03-20 15:39:26,180 java.runtime.version=pxi32devifx-20110209 (SR11 FP2 +IZ94331)
2012-03-20 15:39:26,185 Provisioning using "./conf/jts/provision_profiles".
2012-03-20 15:39:26,208 repotools-jts -createWarehouse
2012-03-20 15:39:26,214 Jazz Foundation - Core Libraries, Version 3.0.1.2 (RJF-I20111207-1350)

2012-03-20 15:39:26,225 CRJAZ1363I Loading the configuration from "file:conf/jts/teamserver.properties".
2012-03-20 15:39:26,959 CRJAZ1779I This server is configured as a JTS.
2012-03-20 15:39:26,961 CRJAZ1971I The server is configured with:
Public URI: "https://rtc-test.mydomain.com/jts"
2012-03-20 15:39:28,562 CRJAZ1365I The server is attempting to connect to the following database: "//192.168.1.157:1433;databaseName=rtc_test_jts;user=xxxxxxxx;password=xxxxxxxx"
2012-03-20 15:39:28,874 CRJAZ1364I The connection to the following database was successful:
Db Product Name: Microsoft SQL Server
Db Product Version: 9.00.1399
Db URL: jdbc:sqlserver://192.168.1.157:1433;databaseName=rtc_test_jts;user=xxxxxxxx;password=xxxxxxxx
Jdbc Driver Name: Microsoft SQL Server JDBC Driver 2.0
Jdbc Driver Version: 2.0.1803.100
2012-03-20 15:39:29,457 CRJAZ8192I: Fulltext Index Location: /opt/IBM/JazzTeamServer/server/conf/jts/indices/workitemindex/fulltext_index
2012-03-20 15:39:56,614 INSERT INTO RIDW.D_DATE (DATE_ID,PERIOD_START_DATE ,DAY_OF_WEEK,DAY_OF_MONTH,DAY_OF_YEAR,DAY_NAME,WEEK_OF_MONTH,WEEK_OF_YEAR,WEEK_NO,MONTH_OF_YEAR,MONTH_NAME,MONTH_NO,QUARTER_OF_YEAR,QUARTER_NO,YEAR_OF,DAY_OF_WEEK_ISO,WEEK_OF_MONTH_ISO,WEEK_OF_YE
AR_ISO,WEEK_NO_ISO) VALUES (-1,'1899-12-31',-1,-1,-1,'No dayname',-1,-1,-1,-1,'No month',-1,-1,-1,-1,-1,-1,-1,-1)
com.ibm.team.repository.common.TeamRepositoryException: INSERT INTO RIDW.D_DATE (DATE_ID,PERIOD_START_DATE ,DAY_OF_WEEK,DAY_OF_MONTH,DAY_OF_YEAR,DAY_NAME,WEEK_OF_MONTH,WEEK_OF_YEAR,WEEK_NO,MONTH_OF_YEAR,MONTH_NAME,MONTH_NO,QUARTER_OF_YEAR,QUARTER_NO,YEAR_OF,DAY_OF_WEEK_
ISO,WEEK_OF_MONTH_ISO,WEEK_OF_YEAR_ISO,WEEK_NO_ISO) VALUES (-1,'1899-12-31',-1,-1,-1,'No dayname',-1,-1,-1,-1,'No month',-1,-1,-1,-1,-1,-1,-1,-1)
at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.internalExecuteSql(AbstractDataWarehouseDbProvider.java:229)
at com.ibm.team.datawarehouse.service.AbstractDataWarehouseDbProvider.executeSql(AbstractDataWarehouseDbProvider.java:93)
at com.ibm.team.datawarehouse.service.sqlserver.internal.SqlServerDataWarehouseDbProvider.createDataWarehouseCoreTables(SqlServerDataWarehouseDbProvider.java:44)
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 $Proxy361.createDataWarehouseCoreTables(Unknown Source)
at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$1.run(RemoteDatabaseService.java:133)
at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$4.run(RemoteDatabaseService.java:206)
at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:379)
at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.write(RemoteDatabaseService.java:196)
at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.createRemoteSchemas(RemoteDatabaseService.java:114)
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.CreateDataWarehouseCommand.execute(CreateDataWarehouseCommand.java:17)
at com.ibm.team.repotools.command.AbstractCommand.execute(AbstractCommand.java:64)
at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.run(RepositoryToolsApplication.java:736)
at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.start(RepositoryToolsApplication.java:811)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
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:368)
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:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Caused by:
com.microsoft.sqlserver.jdbc.SQLServerException: La conversion d'un type de donnes CHAR en type DATETIME a donn une valeur hors limite de date et d'heure.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:196)
at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:246)
at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:83)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1449)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:786)
at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:685)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4026)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1416)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:185)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:160)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(SQLServerStatement.java:658)
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:212)
... 40 more
2012-03-20 15:39:56,616 CRJAZ1728E An unexpected error has been detected. See the log file "/opt/IBM/JazzTeamServer/server/repotools-jts_createWarehouse.log" for more details.


Have you got an idea about my problem ?
I have read on Internet that the date format should be YYYYMMDD in order of YYYY-MM-DD when MSQL is used.

Thanks for your help
Mathieu

0 votes



One answer

Permanent link
Hi Mathieu,

following http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Ft_manually_update_config_sql.html

There is a statement to change the data warehouse property to a database.
The *datawarehouse* properties look strange, especially com.ibm.team.datawarehouse.datawarehouse.provider=Remote looks like Derby settings to me. I am not used to SQLServer however. Have you considered to try to run the setup e.g. for a testsytem and compared the teamserver.properties you would get for the datawarehouse?

0 votes

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: Mar 20 '12, 11:25 a.m.

Question was seen: 4,904 times

Last updated: Mar 20 '12, 11:25 a.m.

Confirmation Cancel Confirm