It's all about the answers!

Ask a question

Addressing upgrade script error while upgrading from CLM 501 to 6.0


anoop mc (74811199221) | asked Oct 23 '15, 7:38 a.m.
 Hi,

We are getting an error while upgrading the CLM 501 to 6.0 iFix003 version after running the upgrade scripts from the JTS server.

CLM Architecture: Distributed. Current version 5.0.1
Database: SQL Server 2012
OS: Windows Server 2012 R2
Application Server: Apache Tomcat 

On JTS Server

repotools-jts_migration_jts_updateConfigurationFiles went fine

repotools-jts_addTables succeeded.

repotools-jts_mergeLPAJTS – Failed at the last stage.

 2015-10-23 06:46:49,059 CRJZS5656I Text indexer for private applications has started

2015-10-23 06:46:53,965 CRJZS5801I The application /rm is using a transactional RDF index

2015-10-23 06:47:52,341 The user "ADMIN" has logged out of the database "//<database server> ;databaseName=jts;user=xxxxxxxx;password=xxxxxxxx;".

2015-10-23 06:47:52,341 Time out after 60000ms

java.lang.RuntimeException: Time out after 60000ms

2015-10-23 06:47:52,341 CRJAZ1728E A Repository Tools error occurred


Accepted answer


permanent link
Arun K Sriramaiah (3.2k13477) | answered Oct 28 '15, 5:07 a.m.
edited Oct 28 '15, 5:08 a.m.
It was getting timeout when running repotools-jts -mergeLPAJTS due to indices folder Copied into a wrong location.
anoop mc selected this answer as the correct answer

Comments
Antoinette Iacobo commented Oct 28 '15, 9:24 a.m.

Great news!

5 other answers



permanent link
anoop mc (74811199221) | answered Oct 28 '15, 4:34 a.m.
edited Oct 28 '15, 4:37 a.m.
 Hi Toni,

Finally the issue was figured out working with @Arun Sriramaiah from IBM technical support.

Cause of the issue is :-  The indices folder was not properly copied from the previous version (CLM 501). After copying the indices folder one more time from 501 to 6.0 installation directory and rerunning the command got the issue resolved.

2015-10-28 04:22:25,662 Repo Tools
2015-10-28 04:22:25,662 java.version=1.6.0
2015-10-28 04:22:25,662 java.runtime.version=pwa6460sr16fp3ifx-20150314_01 (SR16 FP3)
2015-10-28 04:22:25,662 Provisioning using "C:\Program Files\IBM\JazzTeamServer6\server\conf\jts\provision_profiles".
2015-10-28 04:22:25,694 repotools-jts -mergeLPAJTS oldJTSHome=C:\Program Files\IBM\JazzTeamServer\server\conf
2015-10-28 04:22:25,709   Jazz Foundation - Core Libraries, Version 6.0 (RJF-I20150519-1056)

2015-10-28 04:22:25,756 
 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.
2015-10-28 04:22:25,756 CRJAZ1363I Loading the configuration from "file:conf/jts/teamserver.properties".
2015-10-28 04:22:28,819 CRJAZ1779I This server is configured as a JTS.
2015-10-28 04:22:29,412 CRJAZ1365I The server is attempting to connect to the following database: "//<database server>;databaseName=jts;user=xxxxxxxx;password=xxxxxxxx;"
2015-10-28 04:22:41,131 CRJAZ1364I The connection to the following database was successful:
 Db Product Name: Microsoft SQL Server
  Db Product Version: 11.00.3000
  Db URL: jdbc:sqlserver://<database server> ;databaseName=jts;user=xxxxxxxx;password=xxxxxxxx;
  Jdbc Driver Name: Microsoft JDBC Driver 4.0 for SQL Server
  Jdbc Driver Version: 4.0.2206.100
2015-10-28 04:22:43,225 CRJAZ2558I Setting the local server rename state to false and the openServerDescriptionServiceTemporarily state to false.
2015-10-28 04:22:45,428 CRJAZ1971I The server is configured with: 
  Public URI: "https://<jts_server>.com:9443/jts"
2015-10-28 04:22:45,710 CRJAZ2523I Setting the global server rename state to false and the validation state to false.
2015-10-28 04:23:04,163 CRJAZ2105I Checking for a running server...
2015-10-28 04:23:06,257 The user "ADMIN" has logged in to the database "//<databaseserver>;databaseName=jts;user=xxxxxxxx;password=xxxxxxxx;".
2015-10-28 04:23:06,257 Checking the old JTS version...
2015-10-28 04:23:14,351 CRJZS5650I Indices directory is C:\Program Files\IBM\JazzTeamServer6\server\conf\jts\indices
2015-10-28 04:23:14,382 CRJZS5800I  Private applications are using a transactional RDF index
2015-10-28 04:23:15,851 Backing up the JTS teamserver properties "C:\Program Files\IBM\JazzTeamServer6\server\conf\jts\teamserver.properties" to "C:\Program Files\IBM\JazzTeamServer6\server\conf\jts\teamserver-1446020595851backup.properties"...
2015-10-28 04:23:15,851 Backup file "C:\Program Files\IBM\JazzTeamServer6\server\conf\jts\teamserver-1446020595851backup.properties" created. 
2015-10-28 04:23:15,851 
2015-10-28 04:23:15,867 
2015-10-28 04:23:15,867 The LPA is migrated successfully.
2015-10-28 04:23:15,867 The user "ADMIN" has logged out of the database "//<databaseserver>;databaseName=jts;user=xxxxxxxx;password=xxxxxxxx;".
2015-10-28 04:23:16,023 CRJZS5652I Indexing services are being shut down ...
2015-10-28 04:23:16,057 CRJZS5651I Indexing services finished shutting down in 34 ms


permanent link
Antoinette Iacobo (650712) | answered Oct 23 '15, 9:57 a.m.
 Anoop, this seems to fail logging in to the JTS database.  Was the jts addTables run immediately before this?  Or was there some gap that would have affected the database? 

Comments
Antoinette Iacobo commented Oct 23 '15, 9:58 a.m.

 Nevermind, I misinterpreted that message... 


permanent link
Antoinette Iacobo (650712) | answered Oct 23 '15, 10:32 a.m.
The change from LPA as a fronting app. and part of the JTS was from 4 to 5. This being a 5 to 6, I'm confused why this repotools function is being called.  Are you sure this is being run from the 6.x environment? 

permanent link
anoop mc (74811199221) | answered Oct 25 '15, 10:17 a.m.

Yes this is being ran from 6.x enviornment. Please find the command line 

cmd


Comments
Antoinette Iacobo commented Oct 26 '15, 9:58 a.m.
I tried to see if I could glean anything more by comparing a successful run.  After the logging in to the JTS repository and ater the statement: 

The application /rm is using a transactional RDF index

it proceeds to process the "triple live" and "text live" indexes, basically reconfiguring the storage areas and reindexing.  And it reports on those details.  Your log looks like it never rebuilt anything.  Is this the complete log or did you edit it for the posting?  Then it backs up the teamserver.properties file, gives a status "complete" message, logs out of the database and shuts down the indexing services.  Yours has the error immediately after logging out.  

If it's the complete log, I suggest looking at the jts.log or its application server log to see if that gives any clues what it was doing in between logging out and the error.  

permanent link
anoop mc (74811199221) | answered Oct 26 '15, 9:57 p.m.
edited Oct 28 '15, 4:38 a.m.
 I am not sure if the JTS.log or the application server log will have some entry. Because the application was not started while running the command. Attached is the complete log after execution of batch file - repotools-jts_mergeLPAJTS.bat.

2015-10-23 06:46:05,886 Repo Tools
2015-10-23 06:46:05,902 java.version=1.6.0
2015-10-23 06:46:05,902 java.runtime.version=pwa6460sr16fp3ifx-20150314_01 (SR16 FP3)
2015-10-23 06:46:05,902 Provisioning using "C:\Program Files\IBM\JazzTeamServer6\server\conf\jts\provision_profiles".
2015-10-23 06:46:05,933 repotools-jts -mergeLPAJTS oldJTSHome=C:\Program Files\IBM\JazzTeamServer\server\conf
2015-10-23 06:46:05,933   Jazz Foundation - Core Libraries, Version 6.0 (RJF-I20150519-1056)

2015-10-23 06:46:06,027 
 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.
2015-10-23 06:46:06,027 CRJAZ1363I Loading the configuration from "file:conf/jts/teamserver.properties".
2015-10-23 06:46:08,792 CRJAZ1779I This server is configured as a JTS.
2015-10-23 06:46:09,464 CRJAZ1365I The server is attempting to connect to the following database: "//<Database Server>;databaseName=jts;user=xxxxxxxx;password=xxxxxxxx;"
2015-10-23 06:46:11,386 CRJAZ1364I The connection to the following database was successful:
 Db Product Name: Microsoft SQL Server
  Db Product Version: 11.00.3000
  Db URL: jdbc:sqlserver://<db_server>;databaseName=jts;user=xxxxxxxx;password=xxxxxxxx;
  Jdbc Driver Name: Microsoft JDBC Driver 4.0 for SQL Server
  Jdbc Driver Version: 4.0.2206.100
2015-10-23 06:46:12,027 CRJAZ2558I Setting the local server rename state to false and the openServerDescriptionServiceTemporarily state to false.
2015-10-23 06:46:13,464 CRJAZ1971I The server is configured with: 
  Public URI: "https://<jts_server>:9443/jts"
2015-10-23 06:46:16,495 CRJAZ2523I Setting the global server rename state to false and the validation state to false.
2015-10-23 06:46:24,293 CRJAZ2105I Checking for a running server...
2015-10-23 06:46:26,371 The user "ADMIN" has logged in to the database "//<Database Server >;databaseName=jts;user=xxxxxxxx;password=xxxxxxxx;".
2015-10-23 06:46:26,371 Checking the old JTS version...
2015-10-23 06:46:34,605 CRJZS5650I Indices directory is C:\Program Files\IBM\JazzTeamServer6\server\conf\jts\indices
2015-10-23 06:46:34,683 CRJZS5800I  Private applications are using a transactional RDF index
2015-10-23 06:46:41,027 CRJZS5673I  The "triple history" index for private applications does not exist. The missing index will be automatically recreated
2015-10-23 06:46:43,605 CRJZS5673I  The "triple live" index for private applications does not exist. The missing index will be automatically recreated
2015-10-23 06:46:43,637 CRJZS5658I RDF indexer for private applications has started
2015-10-23 06:46:46,449 CRJZS5673I  The "text history" index for private applications does not exist. The missing index will be automatically recreated
2015-10-23 06:46:49,043 CRJZS5673I  The "text live" index for private applications does not exist. The missing index will be automatically recreated
2015-10-23 06:46:49,059 CRJZS5656I Text indexer for private applications has started
2015-10-23 06:46:53,965 CRJZS5801I The application /rm is using a transactional RDF index
2015-10-23 06:47:52,341 The user "ADMIN" has logged out of the database "//USTR-ERL-2973.na.uis.unisys.com;databaseName=jts;user=xxxxxxxx;password=xxxxxxxx;".
2015-10-23 06:47:52,341 Time out after 60000ms
java.lang.RuntimeException: Time out after 60000ms
at com.ibm.team.jfs.indexing.service.internal.HttpIndexingService.reindexStorageAreasOffline(HttpIndexingService.java:1760)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at com.sun.proxy.$Proxy497.reindexStorageAreasOffline(Unknown Source)
at com.ibm.team.jfs.sdk.storage.internal.StorageService.moveStorageAreasToInternal(StorageService.java:3105)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at com.sun.proxy.$Proxy533.moveStorageAreasToInternal(Unknown Source)
at com.ibm.team.lpa.app.migration.MigrateLPACommand.mergeIndex(MigrateLPACommand.java:179)
at com.ibm.team.lpa.app.migration.MigrateLPACommand.execute(MigrateLPACommand.java:150)
at com.ibm.team.repotools.command.AbstractCommand.execute(AbstractCommand.java:68)
at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.run(RepositoryToolsApplication.java:816)
at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.start(RepositoryToolsApplication.java:891)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
2015-10-23 06:47:52,341 CRJAZ1728E A Repository Tools error occurred. For more information, see this log file: C:\Program Files\IBM\JazzTeamServer6\server\repotools-jts_mergeLPAJTS.log
2015-10-23 06:47:52,513 CRJZS5652I Indexing services are being shut down ...
2015-10-23 06:47:53,106 CRJZS5651I Indexing services finished shutting down in 593 ms


Comments
1
Antoinette Iacobo commented Oct 27 '15, 5:48 p.m.

Of course, it would be down when this is running...
 
It seems to be failing when creating the indices offline.  Given the time stamps and the messages, it didn't seem to create any new indexes.

The only tracing I can think of for repotools commands is for SQL and won't help here. 

Let me see what else I can think of.

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.