How to connect a cloned installation to the cloned DBs ?
- DBAs cloned the DBs to the new SQL server
- copy the entire installation via 7zip to appServer, with "D:\IBM\rtc_406\JazzTeamServer\server\sqlserver\sqljdbc4.jar" in the right place.
- Modify SQLserver name in all teamserver.properties.
- Now tryinng to reindex everything as PRD cannot be shutdown to copy the installation and the indices at the same time when the DBs were copied.
- Once successful will attempt to upgrade directly to 5.0.2 without ever getting the cloned 4.0.6 up
Wonder if a listener, an SQLserver agent or something else have to be set up on the app-server after DBAs cloned the DBs (don't know if that is DBA's responsibility or mine). Note that the installation (and hence teamserver.properties) is copied from a TEST env which uses an older PRD-cloned copy of the DBs, while the DBs were recently cloned from PRD. Both PRD and TEST have the same account/passwd for their own DBs.
Or could it be that the copying of the installation only brings inert credentials masks without the encrypted part behind them.
com.ibm.team.repository.db.jdbc.location=//N01DSW227\:1433;databaseName\=ccm;user\=svc_rtc;password\={password}
Here are the error messages I got:
D:\IBM\rtc_406\JazzTeamServer\server>repotools-ccm.bat -reindex all
Repo Tools
Provisioning using "D:\IBM\rtc_406\JazzTeamServer\server\conf\ccm\provision_profiles".
Jazz Foundation - Core Libraries, Version 4.0.6 (RJF-I20140130-1407)
Change and Configuration Management - Core Libraries, Version 4.0.6 (RTC-I20140205-1437)
To submit questions about issues, go to the Jazz.net forum at https://jazz.net/forum.
To find more information about a message, see the CLM Messages Information Center at
https://jazz.net/help-dev/CLMErrorMessages/index.jsp.
CRJAZ1363I Loading the configuration from "file:conf/ccm/teamserver.properties".
CRJAZ1778I This server is configured as an application.
CRJAZ2558I Setting the local server rename state to false and the openServerDescriptionServiceTemporarily state to false.
CRJAZ1365I The server is attempting to connect to the following database: "//N01DSW227:1433;databaseName=ccm;user=xxxxxxxx;password=xxxxxxxx"
CRJAZ1840W The following driver could not be loaded and registered: com.microsoft.sqlserver.jdbc.SQLServerDriver. This JDBC driver
JAR file must be provided in a path that is configured by the server scripts. Verify that the driver is in the expected location
of "D:\IBM\rtc_406\JazzTeamServer\server\sqlserver\sqljdbc4.jar" or consult the product setup instructions to change the location.
CRJAZ1093E The "com.ibm.team.repository.service.internal.schemagen.PersistentMappingService" feature could not start.
CRJAZ1141I Cannot get the service "com.ibm.team.repository.service.IServerDescriptionService".
CRJAZ2448I The public url property is not set. This is used to determine the running state of the server. The repotools command will skip this check and continue processing the command.
CRJAZ1840W The following driver could not be loaded and registered: com.microsoft.sqlserver.jdbc.SQLServerDriver. This JDBC driver
JAR file must be provided in a path that is configured by the server scripts. Verify that the driver is in the expected location of "D:\IBM\rtc_406\JazzTeamServer\server\sqlserver\sqljdbc4.jar" or consult the product setup instructions to change the location.
CRJAZ1840W The following driver could not be loaded and registered: com.microsoft.sqlserver.jdbc.SQLServerDriver. This JDBC driver JAR file must be provided in a path that is configured by the server scripts. Verify that the driver is in the expected location of "D:\IBM\rtc_406\JazzTeamServer\server\sqlserver\sqljdbc4.jar" or consult the product setup instructions to change the location.
CRJAZ1204I The database "//N01DSW227:1433;databaseName=ccm;user=xxxxxxxx;password=xxxxxxxx" does not exist, the Jazz tables have not been created, or the database user does not have the required privileges to access the database.
Accepted answer
4.0.6 Knowledge center link for reference: Setting up an SQL Server database
Comments
Thx Erica,
After resolving the connection issue we still run into login and access issues, fortunately we dug out the resolution from DBAs who cloned the DBs for us:
- DBAs had always delivered cloned DBs to us on a silver platter, ready to go (on ourTST env), never had any issue with accessing the DBs. Now we found out what DBAs would have to do besides the bare bone cloned DBs.
- First, passwd was never copied over (and unfortunately we have no records of the raw passwd) this time so we had to get the passwd reset.
- Once it is reset we had to find out the syntax of specifying the raw passwd on the teamserver.properties file.
- It wasn't easy as we tried to debug both the syntax&the passwd set by a new DBA (eventually reset with IBM doc), not knowing which side causing the issue. IBM support advised passwd without quote in replacing {password}.
- Still no access with login seem OK. Started RTC/RRC in lame status, set/encrypted passwd via DB connection (both jts&ccm)
- Login OK but no access: DBA had to copy "access" over for each DB.
One other answer
Comments
You were right, the log did confirm that it could not find the jdbc, but the path was right, only the env var was missing as per Erica in next answer. Had been trying to post below comment in all day yesterday in vain.