It's all about the answers!

Ask a question

Unable to jts/setup for RTC for system z V4.0.3


Kenji Kitajima (1379) | asked Nov 19 '13, 6:15 p.m.
edited Nov 19 '13, 6:24 p.m.

Help me,please...

Having installed RTC for system z V4.0.3 (All in z/OS with z/WAS & z/DB2),

I'm facing the subject trouble.

The following is a pice of jts.log.

How should I do to resolve this issue?

---------------------------------------------------------------------------------------------------------

2013-11-19 07:03:10,869 [WebSphere:ORB.thread.pool t=008c5e88]  INFO .repository.service.internal.rdb.ConnectionFactory  - CRJAZ1364I The connection to the
following database was successful:
 Db Product Name: DB2
  Db Product Version: DSN09015
  Db URL: jdbc:db2://zswzos01.hakozaki.ibm.com:5027/ADCDDB9H:user=xxxxxxxx;password=xxxxxxxx;
  Jdbc Driver Name: IBM DB2 JDBC Universal Driver Architecture
  Jdbc Driver Version: 3.52.99
2013-11-19 07:03:15,223 [WebSphere:ORB.thread.pool t=008c5e88] ERROR ComponentVersionMismatch                            - CRJAZ1042I The component has a se
 version mismatch between the installed code and the database.
        Package URI == com.ibm.team.process
        Installed Version == 13
        Database Version == 23
-----------------------------------------------------------------------------------------------------------------

Thanks in advance,

One answer



permanent link
Kot T. (1.5k11219) | answered Nov 19 '13, 7:51 p.m.
JAZZ DEVELOPER

Hi Kenji,

Since your DB is DB2, I wonder if the root cause identified in this technote would apply...

http://www-01.ibm.com/support/docview.wss?uid=swg21574093

Please also confirm your DB2 version is supported: see https://jazz.net/wiki/bin/view/Deployment/CLMSystemRequirements403

Is this a brand new install OR an upgrade? If new install, could you confirm that the DB that the server is connecting to does not have any data in it?

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.