Problem creating tables using SQL server 2005 -PersistentMap
Hi All,
We just ran into some problems configuring RTC on a SQL Server 2005. The problem was caused by the sqljdbc.jar file being the wrong version. Upgrading this file to a version 2.0 (read the manual on where to put the file) fixed the problem. This was the stacktrace: D:\APP\IBM\JazzTeamServer\server>repotools.bat -createTables Repo Tools Jazz Foundation - Jazz Team Server, Version 1.0.0.1 (I20090914-1300) Rational Team Concert, Version 2.0.0.1 (I20090914-1300) Rational Jazz Team Server - Enterprise CRJAZ1363I Loading configuration from "file:conf/jazz/teamserver.properties". CRJAZ1365I Attempting Initial Database Connection Using Db Name/Location: //W86671:1433;databaseName=RTC_POC;user=xxxxxxxx;password=xx xxxxxx; CRJAZ1364I Initial database connection successful Db Product Name: Microsoft SQL Server Db Product Version: 9.00.3200 Db URL: jdbc:sqlserver://W86671:1433;selectMethod=direct;lastUpdateCount=true; databaseName=RTC_POC; Jdbc Driver Name: Microsoft SQL Server 2005 JDBC Driver Jdbc Driver Version: 1.1.1501.101 CRJAZ1093I Service class "com.ibm.team.repository.service.internal.schemagen.PersistentMappingService" failed to activate. CRJAZ1141I Failed to get the service "com.ibm.team.repository.service.internal.rdb.IDatabaseStateService". CRJAZ1203I Could not determine the database location. CRJAZ1306I The service "com.ibm.team.repository.service.internal.rdb.IDatabaseStateService" is not available. Creating the tables for the database "//W86671:1433;databaseName=RTC_POC;user=xx xxxxxx;password=xxxxxxxx;" with indices. CRJAZ1141I Failed to get the service "com.ibm.team.repository.service.internal.rdb.IDatabaseCreationService". CRJAZ1309I The database connectivity service is not ready. The database tables were not created. :idea: |
3 answers
Hi All, Hi Kim If you could file this as a defect, development can take a look at this and sort it out. regards anthony |
Is there an update to this?
I'm getting the exact same error with SQL Server 2008/RTC 3.5M1. |
Is there an update to this? In my case an investigation of the logs revealed a JDBC exception trying to perform an INTERSECT with the Jazz databases and the master database. The instructions for 3.5M1 that the SQL Server "is installed with case sensitive database collation selected as default" do not fully specify the collation required when the install of SQL Server is performed. Selecting the case sensitive collation checkbox during SQL Server install gives Latin1_General_CS_AS collation on the master database, which gives rise to the JDBC error. During install the SQL Server collation must be set to SQL_Latin1_General_CP437_CS_AS. |
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.