It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×7,479
×6,115
×1,308

question asked: Jun 16 '22, 11:33 a.m.
question was seen: 1,126 times
last updated: Feb 13, 9:31 a.m.

Related questions

Problem During Update -addTable CLM6.0.4 to ELM7.0.2 Invalid database URL syntax com.ibm.db2.jcc.am.SqlSyntaxErrorException:

0
1
ANdrea Marchiori (13●1) | asked Jun 16 '22, 11:33 a.m.

Greetings,
i am upgrading from clm 6.0.4 to elm 7.0.2

i have installed the product and i am launching the upgrade of the jts

upgrade / jts / jts_upgrade.sh -oldJTSHome / server / conf

 point to the old
configuration of the CLM version 6

during the
addTable I get this error:

2022-06-16 16: 15: 18,604 Repo Tools
2022-06-16 16: 15: 18,604 java.version = 1.8.0_261
2022-06-16 16:15: 18,604 java.runtime.version = 8.0.6.15 - pxa6480sr6fp15-20200724_01 (SR6 FP15)
2022-06-16 16: 15: 18,608 Provisioning using "./conf/jts/provision_profiles".
2022-06-16 16: 15: 18,626 repotools-jts -addTables
2022-06-16 16: 15: 18,648
 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 online product documentation.
2022-06-16 16: 15: 18,648 CRJAZ1363I Loading the configuration from "file: conf / jts / teamserver.properties".
2022-06-16 16: 15: 22,634 CRJAZ1779I This server is configured as a JTS.
2022-06-16 16: 15: 22,809 CRJAZ1365I The server is attempting to connect to the following database: "//db.sviluppo.pico.trn:60008/JTS:user=xxxxxxxx;password=xxxxxxxx"
2022-06-16 16: 15: 22,893 CRJAZ2654E The server was unable to connect to the database because the database connection settings are invalid or because database is unreachable (SQLSTATE: 42815, SQLCODE: -4461). Verify the connection settings in your teamserver.properties file. See the Jazz Team Server log for more information.
com.ibm.db2.jcc.am.SqlSyntaxErrorException: [jcc] [10165] [10051] [4.26.14] Invalid database URL syntax: jdbc: db2: //db.sviluppo: 60008 / JTS: user = xxxxxx; password = {xxxxxxx}. ERRORCODE = -4461, SQLSTATE = 42815

it is the same configuration of the old version where it connects and the process goes up correctly, while in the new version 7.0.2 it fails to connect to the same db with the same configurations, I also tried to change the syntax of the string but it changes nothing, I don't understand because in the old version 6.0.4 the connection happens correctly with the db while in the version 7.0.2 it gives me this error


example of some original syntax working on the old version and testing on the new one with negative result

com.ibm.team.repository.db.jdbc.location=//sviluppo.trn\:60008/JTS\:user\=xxxxxx;password\=xxxxxxx
com.ibm.team.repository.db.jdbc.location=//sviluppo.trn:60008/JTS:user=xxxxxx;password={xxxxxxx}

can you provide me with information on this?
thanks

Accepted answer

0
permanent link
Ian Barnard (2.3k●7●14) | answered Jun 16 '22, 11:46 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
edited Jun 16 '22, 11:50 a.m.

Not sure if this is the reason for your problem in 7.0.2, but it would be normal for teamserver.properties to use two lines to specify the connection string and the password separately, details below. Maybe the syntax checking of the connection string has been tightened up.



Example from a test environment where DB2 is in the same machine (localhost):

com.ibm.team.repository.db.jdbc.location=//localhost\:50000/JTS702\:user\=db2admin;password\={password};
com.ibm.team.repository.db.jdbc.password=[GIFiNqlEOhuqhIZHiC9JRg\=\=]

i.e. the password in the connection string is put as literally {password} and the actual password is specified on a separate line.

You can put the password in clear e.g.:

com.ibm.team.repository.db.jdbc.password=db2passwordcleartext

And the next time you start your JTS it will encrypt the password and update teamserver.properties.

Same for the all the other connection strings.

ANdrea Marchiori selected this answer as the correct answer
Comments
ANdrea Marchiori commented Jun 16 '22, 12:21 p.m. 
Thanks, it worked, in the old version everything was set on one line, we see that with the new versions they have increased the level of security, thank you very much

One other answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Jan Witte (1) | answered Feb 13, 9:31 a.m.

 great thank you ;-) 

Your answer

Register or 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.