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

issue with SQL server migration from DB2

I have a RTC server which is also a DB2 server. RTC has been working fine. Now I need to migrate to SQL server which is on another physical box. Here was what I did:
1. download SQL JDBC driver 1.2 and extracted it to E:\temp\SQL_JDBC\sqljdbc_1.2\enu on the RTC web server, NOT on the SQL database server.

2. modified the teamserver.sqlserver.properties file for the following lines only
com.ibm.team.repository.db.vendor = SQLSERVER
com.ibm.team.repository.db.jdbc.location=//SQL SERVER MACHINE IP:SQL SERVER TCIP PORT;databaseName=JAZZ DATABASE NAME;user=JAZZ USERNAME;password={password}
com.ibm.team.repository.db.jdbc.password=JAZZ LOGIN PASSWORD

3.Set the SQLSERVER_ABSPATH system environment variable on the RTC web server. I also tried copying the sqljdbc_1.2\enu\sqljdbc.jar file to \server\sqlserver\ directory.

4. Ran repotools -copy toFile=temp.tar target.teamserver.properties=teamserver.sqlserver.properties

The following error was displayed. Any comments please? Thanks. Based on the message, it was trying to locate the 'target' repositiry in DB2 instead of SQL.


E:\Program Files\StagingRTC2\JazzTeamServer\server>repotools -copy toFile=temp.t
ar target.teamserver.properties=teamserver.sqlserver.properties
Repo Tools, Version 1.0.1 - I20081024-1335
Provisioning using "E:\Program Files\StagingRTC2\JazzTeamServer\server\\provisio
n_profiles".
Rational Jazz Team Server - Standard
Loading configuration from "file:teamserver.properties".
Attempting Initial Database Connection Using
Db Name/Location: //localhost:50000/STGRTC3:fullyMaterializeLobData=false;user
=xxxxxxxx;password=xxxxxxxx;
Initial database connection successful
Db Product Name: DB2/NT
Db Product Version: SQL09051
Db URL: jdbc:db2://localhost:50000/STGRTC3
Jdbc Driver Name: IBM DB2 JDBC Universal Driver Architecture
Jdbc Driver Version: 3.6.60
Fulltext Index Location: E:\Program Files\StagingRTC2\JazzTeamServer\server\work
itemindex\fulltext_index\
CRJAZ1093I Service failed to activate.
CRJAZ1203I Could not determine the database location.

0 votes



15 answers

Permanent link
Thanks, Matt. This the log file repotools_createTables.log for a new RTC101 instance. FYI, telnet to the SQL server thru port 1433 was successful.


2008-12-02 13:35:51,588 repotools -createTables
2008-12-02 13:35:51,618 Repo Tools, Version 1.0.1 - I20081024-1335
2008-12-02 13:35:51,628 Provisioning using "E:\Program Files\StagingRTCSQL1\JazzTeamServer\server\\provision_profiles".
2008-12-02 13:36:08,137 Rational Jazz Team Server - Standard
2008-12-02 13:36:08,237 Loading configuration from "file:teamserver.properties".
2008-12-02 13:36:13,215 Attempting Initial Database Connection Using
Db Name/Location: //204.63.157.39:1433;databaseName=StgRTCSQL1;user=xxxxxxxx;password=xxxxxxxx;
2008-12-02 13:36:13,245 CRJAZ1093I Service failed to activate.
com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ1092I The service class "com.ibm.team.repository.service.internal.schemagen.PersistentMappingService" failed during activation.

0 votes


Permanent link
>> Caused by:
java.lang.IllegalStateException: CRJAZ0808I The driver "com.microsoft.sqlserver.jdbc.SQLServerDriver" could not be loaded and registered. Support for some database vendors requires that the JDBC driver JAR be provided in a path configured by the server scripts. If you are experiencing problems changing the database vendor, refer to the product setup instructions for more information.


Looks like the path to SQL JDBC jar file is not correct. The path to the jar file should not contain any spaces. If the jar file is present in program
files folder, use progra~1 to reference the folder.

--- Balaji

Thanks, Matt. This the log file repotools_createTables.log for a new RTC101 instance. FYI, telnet to the SQL server thru port 1433 was successful.

0 votes


Permanent link
The following ios the log file whe the following system environment variable was used.

SQLSERVER_ABSPATH
E:\Progra~1\sqljdbc_1.2\enu


2008-12-02 14:07:15,048 repotools -createTables
2008-12-02 14:07:15,068 Repo Tools, Version 1.0.1 - I20081024-1335
2008-12-02 14:07:15,088 Provisioning using "E:\Program Files\StagingRTCSQL1\JazzTeamServer\server\\provision_profiles".
2008-12-02 14:07:29,741 Rational Jazz Team Server - Standard
2008-12-02 14:07:29,771 Loading configuration from "file:teamserver.properties".
2008-12-02 14:07:32,195 Attempting Initial Database Connection Using
Db Name/Location: //204.63.157.39:1433;databaseName=StgRTCSQL1;user=xxxxxxxx;password=xxxxxxxx;
2008-12-02 14:07:32,205 CRJAZ1093I Service failed to activate.
com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ1092I The service class "com.ibm.team.repository.service.internal.schemagen.PersistentMappingService" failed during activation.
at

0 votes


Permanent link
I tried the approach of copying the JDBC driver locally at: E:\Program Files\StagingRTCSQL1\JazzTeamServer\server\SQLSERVER\sqljdbc.jar

It did not work the before when the system environment variable was still in place.

After removing the system environment variable while keeping the local JDBC drive, RTC tables were created successfully. I will complete the RTC configuration to make sure everything works properly.

However, the same approach (using local JDBC driver file instead of a system environment variable), did NOT help with DB2 to SQL migration (repostools -copy).

So, there are at least two issues that I'm facing now.
1. The system environment variable did not work and it over-takes the effect of the local JDBC driver.
2. The migration from DB2 to SQL failed (repostools -copy).

Any comments please? Thanks.

0 votes


Permanent link
Any comment on the following issues? Thanks.

1. High priority - The migration from DB2 to SQL failed (repostools -copy) for DB2->SQL migration. On the other hand (repostools -createTables) worked fine for a new repositiry. Could you please confirm whether DB2->SQL migration is currently supported? We have a number of DB2 repositories in production, but DB2 is not our enterprise standard DBMS.

2. Nice to know - Why the system environment variable did not work while copying the JDBC jar file under the server\sqlserver\ folder worked fine?

Thanks.

0 votes

1–15 items
page 2of 1 pagesof 2 pages

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: Nov 26 '08, 11:03 a.m.

Question was seen: 11,752 times

Last updated: Nov 26 '08, 11:03 a.m.

Confirmation Cancel Confirm