Issue migrating from tomcat/DB2 to WAS/Oracle
Hi,
we are trying to migrate an installation of RTC 3.0.1 from tomcat / DB2 to WAS_6.1 / Oracle and we are experiencing some problems with it. We are just using jts, admin and ccm applications.
The steps that we are following are based on a Derby to DB2 migration ( we have been unable to find any official info about DB2 to Oracle ) http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Ft_migrate_derby_oracle.html
the steps are:
- Install a RTC in a WAS/Oracle platform -> it seems to be ok.
- Repotools export ( jts and ccm) from the old installation -> seems ok.
- Repotools import jts and ccm, on the new installation -> no errors found
- start new server.
Problem:
the ccm application does not work at all. It isn't accessible.
Hints:
- /ccm looks like it isn't well reconized as it isn't reconized on the /jts/admin page and it does appear on the registered applications.
- on the diagnosis of JTS appears the error:CRJAZ2055W Some indices were missing from the database, and missing indices can negatively impact application performance. To add the missing indices, you should stop your server and execute the -rebuildIndices command in repotools. We have launched the repotools command but the error keeps appering.
- on the diagnosis of CCM appears the error:"CRJAZ2052E" There is no friend to Jazz Team Server configuration.
Anyone has any tip on how we could manage this?
Thanks!
we are trying to migrate an installation of RTC 3.0.1 from tomcat / DB2 to WAS_6.1 / Oracle and we are experiencing some problems with it. We are just using jts, admin and ccm applications.
The steps that we are following are based on a Derby to DB2 migration ( we have been unable to find any official info about DB2 to Oracle ) http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Ft_migrate_derby_oracle.html
the steps are:
- Install a RTC in a WAS/Oracle platform -> it seems to be ok.
- Repotools export ( jts and ccm) from the old installation -> seems ok.
- Repotools import jts and ccm, on the new installation -> no errors found
- start new server.
the ccm application does not work at all. It isn't accessible.
- /ccm looks like it isn't well reconized as it isn't reconized on the /jts/admin page and it does appear on the registered applications.
- on the diagnosis of JTS appears the error:
- on the diagnosis of CCM appears the error:
Anyone has any tip on how we could manage this?
Thanks!
8 answers
Hi,
the general approach is correct.
Please see https://jazz.net/library/article/547 for some more details e.g. which files are also necessary.
Please check the export and import logs and make sure there is enough disk space available for the files.
Did you copy and merged the various configuration files from the server/conf folders for admin, ccm, jts and modified them for the new database?
I would typically make sure the applications run in WAS first. This would help verifying things like security settings, LDAP setup, JAZZ_HOME, DB connection etc. You could use some of the information from the teamserver.properties later.
If you don't copy the index files over, or make sure they are accessible in the location specified in the teamserver.properties you have to recreate the indexes, I think.
the general approach is correct.
Please see https://jazz.net/library/article/547 for some more details e.g. which files are also necessary.
Please check the export and import logs and make sure there is enough disk space available for the files.
Did you copy and merged the various configuration files from the server/conf folders for admin, ccm, jts and modified them for the new database?
I would typically make sure the applications run in WAS first. This would help verifying things like security settings, LDAP setup, JAZZ_HOME, DB connection etc. You could use some of the information from the teamserver.properties later.
If you don't copy the index files over, or make sure they are accessible in the location specified in the teamserver.properties you have to recreate the indexes, I think.
Hi Ralph,
In this case, if we copy and merge the teamserver.properties files then is not necessary the setup process?
the steps are:
- Install a RTC in a WAS/Oracle platform -> it seems to be ok.
- Make the jts/setup, adding applications ccm and admin.
- jts setup -> ok
- ccm setup -> seems to be ok, but after restart the application server, jts is working with the ccm tablespace with the ccm user.
Looking at the configuration we conclude that:
when we was done the ccm setup, the ccm properties are wrotten in /jts/teamserver.properties overwriting the jts setup.
Where is the reference app-teamserver.properties files?
Regards,
Val
In this case, if we copy and merge the teamserver.properties files then is not necessary the setup process?
the steps are:
- Install a RTC in a WAS/Oracle platform -> it seems to be ok.
- Make the jts/setup, adding applications ccm and admin.
- jts setup -> ok
- ccm setup -> seems to be ok, but after restart the application server, jts is working with the ccm tablespace with the ccm user.
Looking at the configuration we conclude that:
when we was done the ccm setup, the ccm properties are wrotten in /jts/teamserver.properties overwriting the jts setup.
Where is the reference app-teamserver.properties files?
Regards,
Val
Hi,
the test setup is only necessary if you are in doubt the deployment on WAS is correct. It is not needed if you are sure. The setup is not necessary at all, if the various teamserver.propertes are correct and point to the correct file and db locations.
During operation, when saving the properties each application saves backups in the conf/ folder and marks them as a backup. These are the best templates.
If there is no backup of the teamserver.properties it is possible to run the setup again and enter the correct values for the DB, tablespace, context root etc, provided the registered applications can be found.
The values can also be fixed in the teamserver.properties themselves. E.g. fixing the wrong tablespace entry.
the test setup is only necessary if you are in doubt the deployment on WAS is correct. It is not needed if you are sure. The setup is not necessary at all, if the various teamserver.propertes are correct and point to the correct file and db locations.
During operation, when saving the properties each application saves backups in the conf/ folder and marks them as a backup. These are the best templates.
If there is no backup of the teamserver.properties it is possible to run the setup again and enter the correct values for the DB, tablespace, context root etc, provided the registered applications can be found.
The values can also be fixed in the teamserver.properties themselves. E.g. fixing the wrong tablespace entry.
Ralph,
I understand that setup only modify the teamserver.properties files and register applications.
In this case, we will try without setup:
- copy and merge teamserver.properties
- Register the applications in /jts/admin
- export/import.
This should work.
Thanks,
Val
Hi Val,
If the applications were registered in Tomcat/Derby and you provide the correct values in the teamserver.properties, you do not need to register again. If the applications are no longer registered after the import, the operation failed.