upgrade/rm/rm_upgrade.sh CLM5.0.2 RC1
the Db Product Name: Apache Derbyscript upgrade is not loading the proper "teamserver.properties" and instead of using the DB2 is connecting to Apache Derby
and to script hangs ...
Repo Tools
Provisioning using "./conf/rm/provision_profiles".
Jazz Foundation - Core Libraries, Version 5.0.2 RC1 (RJF-I20141015-1939)
Rational DOORS Next Generation, Version 5.0.2 RC1 (RDNG5.0.2-I20141015_2105)
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.
CRJAZ1363I Loading the configuration from "bundleresource://209.fwk132319203:1/teamserver.properties".
......
CRJAZ1778I This server is configured as an application.
CRJAZ1365I The server is attempting to connect to the following database: "/tmp/jazz-repo"
CRJAZ1364I The connection to the following database was successful:
Db Product Name: Apache Derby
Db Product Version: 10.10.2.0 - (1582446)
Db URL: jdbc:derby:/tmp/jazz-repo;create=true
Jdbc Driver Name: Apache Derby Embedded JDBC Driver
Jdbc Driver Version: 10.10.2.0 - (1582446)
Thanks, Adriano
3 answers
thanks for replay, the scenario is the following:
from the Interactive Guide step 12.
12 Copy the Jazz Team Server database
To create a copy of the Jazz Team Server database to use as the RM application database, you back up your Jazz Team Server database and restore it into the RM databaseI do the following command:
db2 backup database JTS to /home/db2inst1/sqllib/backup
then:
db2 restore database JTS from /home/db2inst1/sqllib/backup into RM
I receive the following message (ERROR)
SQL2563W The restore process completed successfully. However, one or more
table spaces from the backup image were not restored.
the db2diag.log show me the following message:
A severe error was encountered while trying to set new
table space containers for table space CONTENTTS (4)
....
If then I run the " upgrade/rm/rm_upgrade.sh " the script ends with error.
My doubt is or the DB2 RESTORE command is not complete or there is something that its missing in the guide
Thanks, Adriano
2014-11-13 13:56:16,951 CRJAZ1778I This server is configured as an application.
2014-11-13 13:56:18,421 CRJAZ1365I The server is attempting to connect to the following database: "//clmdb2.romelab.it.ibm.com:50000/RM:user=xxxxxxxx;pa
ssword=xxxxxxxx;"
2014-11-13 13:56:18,954 CRJAZ1364I The connection to the following database was successful:
Db Product Name: DB2/AIX64
Db Product Version: SQL10054
Db URL: jdbc:db2://clmdb2.romelab.it.ibm.com:50000/RM:user=xxxxxxxx;password=xxxxxxxx;
Jdbc Driver Name: IBM Data Server Driver for JDBC and SQLJ
Jdbc Driver Version: 4.17.28
2014-11-13 13:56:19,503 CRJAZ2558I Setting the local server rename state to false and the openServerDescriptionServiceTemporarily state to false.
2014-11-13 13:56:19,915 CRJAZ1093E The "com.ibm.team.repository.service.internal.PrimitiveTransactionService" feature could not start.
com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ1092E The "com.ibm.team.repository.service.internal.PrimitiveTransactionServ
ice" feature could not start.
I get ahead with the backup/restore of the JTS into RM using the REDIRECT generate script, then edit the script
to correct the CONTAINERS from jtstblsp/jazzts into rmtblsp/jazzts and uncomment the rollfowards
then run the script (db2 -t -f /dati/rm_restore.txt)
2014-11-13 15:47:44,346 Running post addTables for "com.ibm.team.repository.auth"...
2014-11-13 15:47:44,347 Post addTables for com.ibm.team.repository.auth took 1 ms.
2014-11-13 15:47:44,347 Running post addTables for "com.ibm.team.process"...
2014-11-13 15:47:45,559 Starting RM Server Migration. Current repository version set at [null]
2014-11-13 15:47:45,560 Updating RM Storage Areas
2014-11-13 15:47:45,601 Error running migration
java.lang.NullPointerException at com.ibm.rdm.fronting.server.core.serviceInfo.internal.RRSServiceInfoRegistry.trimTrailingSlashes(RRSServiceInfoRegistry.java:320)
at com.ibm.rdm.fronting.server.core.serviceInfo.internal.RRSServiceInfoRegistry.getResourceMapping(RRSServiceInfoRegistry.java:161)
......
Running post addTables for "Full Text Migration Handler"...
2014-11-13 15:47:45,826 Post addTables for Full Text Migration Handler took 1 ms.
2014-11-13 15:47:45,832 The user "ADMIN" has logged out of the database "//clmdb2.romelab.it.ibm.com:50000/RM:user=xxxxxxxx;password=xxxxxxxx;".
2014-11-13 15:47:45,832 CRJAZ1791E The migration completed with errors. The imported database is unstable and should not be used without further analysis.
Any further SUGGESTION is appreciated.
THanks, Adriano
Comments
Adriano
I think there are too many issues to review via a forum topic. Perhaps it would be best if you opened a support ticket. The db2 backup/restore should have been ok on its own. however, I am not sure if you are using tomcat if all your CLM wars have exploded properly. Too many possibilities.
If you do not want to open a support ticket, then try opening a workitem against RDNG on jazz.net. Include the logs that are generated in the server directory when rm_upgrade runs.
Hopefully you backed up your JTS DB2 database. Try creating another copy prior to starting the RM upgrade.
Also, have you already upgraded the JTS?
No, the db2 restore when table space containers have been defined must be done as Adriano has described. This is because table space containers represent physical locations for storage and are not path relative. The container configuration is part of the db2 restore.
The initial install of any of the jazz applications require that a physical location be given for the tablespace CONTENTTS.
Comments
Rosa Naranjo
FORUM MODERATOR / JAZZ DEVELOPER Nov 12 '14, 4:54 p.m.Adriano,
in order to help, you will need to post more, specifically the command and parameters you used to do the upgrade. I can't tell what step 14 is. I can tell you that the repotools used during an upgrade know what teamserver.properties to reference based on commandline parameters submitted to the rm_upgrade script, for example, -oldApplicationHome. One of the first substeps is to migrate the config files from the oldApplicationHome to the newApplicationHome.
Check your upgrade script parameters and try again!