RM not accessible after Derby migration
After migrating from Derby to DB2 following the steps in the infocenter, I find that RM is not accessible. I suspect it is a difference in the consumer keys. See the entry here https://jazz.net/forums/viewtopic.php?t=18404&postdays=0&postorder=asc&start=0 As I have nothing in RM (except for the MTM sample data) I'm wondering if I remove the application and re-register it if that will resolve my problem.
Similarly, I have LPA not showing the previous MTM sample that was created. The Registered applications page shows a similar problem as RM. That is, the manage settings link is grayed out.
CCM and QM seem ok.
Bottom line, I'm willing to "start over" with no projects. I need DB2 and will recreate the MTM sample in order to work through the Reporting Workshop here: https://jazz.net/library/article/675
rns
Similarly, I have LPA not showing the previous MTM sample that was created. The Registered applications page shows a similar problem as RM. That is, the manage settings link is grayed out.
CCM and QM seem ok.
Bottom line, I'm willing to "start over" with no projects. I need DB2 and will recreate the MTM sample in order to work through the Reporting Workshop here: https://jazz.net/library/article/675
rns
One answer
Hi Robert,
I suspect something went wrong during the migration of the database. The registration should not be affected by migrating the database. I'd suggest to look into the migration and the database logs. If you did a repotools export you should check there is enough space on that drive.
One thing I find likely is using the wrong repotools command. This could render the whole migration corrupt. If the LPA application is not reachable most likely something went wrong migrating the JTS database, because that is where the LPA stores its data, I believe.
If it was a playground setup only, I'd suggest a fresh start.
I suspect something went wrong during the migration of the database. The registration should not be affected by migrating the database. I'd suggest to look into the migration and the database logs. If you did a repotools export you should check there is enough space on that drive.
One thing I find likely is using the wrong repotools command. This could render the whole migration corrupt. If the LPA application is not reachable most likely something went wrong migrating the JTS database, because that is where the LPA stores its data, I believe.
If it was a playground setup only, I'd suggest a fresh start.