This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
I have a number of Maximo 7.1.1.10 systems running on Windows 2003 SP2, and Websphere Application Server 6.1.0.45. I want to update Websphere to V7, the installation kit I have is calling itself V 7.0.0.0. No changes to Maximo are planned (at the moment).
When I run the Websphere migration wizard the migration fails, with an error 0345 indicating a version incompatibility. Do I have the wrong patch levels or something?
Is there a document from IBM that describes this process with more Maximo orientation than does the WAS v7 Migration Guide?
I have to believe others have done this. Any tips?
We upgraded WAS from 6.1 to 7.0 last year, but we did it as part of our upgrade from Mx7.1 to Mx7.5. We followed the process as outlined in document " Upgrade Guide IBM Maximo Products V7.1 to V7.5". So this is not exactly like your scenario, however looking back at my notes, after running the WAS migration, and the associated tasks like installing any plug-ins etc, at that we had Mx7.1 running on WAS7.0. So you could follow the path outlined in that document, but stop short of upgrading the application. We followed scenario 2 in that document, Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0.
Hope that helps a little bit.
-Chris H
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of jakesteijn
Sent: Wednesday, November 13, 2013 4:49 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Websphere Upgrade V6 to V7
I have a number of Maximo 7.1.1.10 systems running on Windows 2003 SP2, and Websphere Application Server 6.1.0.45. I want to update Websphere to V7, the installation kit I have is calling itself V 7.0.0.0. No changes to Maximo are planned (at the moment).
When I run the Websphere migration wizard the migration fails, with an error 0345 indicating a version incompatibility. Do I have the wrong patch levels or something?
Is there a document from IBM that describes this process with more Maximo orientation than does the WAS v7 Migration Guide?
I have to believe others have done this. Any tips?
It looks like it should, that is the document I was looking for and I was expecting the same, just stop before upgrading Maximo. I think there is an upgrade to 7.5 in the near future too, but that's neither here nor there. The upgrade fails in the postupgrade stage, replicating the profiles from WAS 6 to WAS 7. It gives me the same error every time: "MIGR0345E: The migration backup directory is not compatible with this Application Server version. com.ibm.ws.migration.utility.UpgradeException: The migration backup directory is not compatible with this Application Server version."
A couple of things I'm running down: 1) currently I'm doing this on WAS 7.0.0.0 -- the base installation prior to installing the fix packs, I will go to 7.0.0.29 eventually because Maximo 7.5 is recommended for that. My next attempt will be to install at least fixpak 7.0.0.15 or higher, as that's what is specified in the Maximo migration guide; and 2) I'm a little suspicious that the current installation is not completely correct, as WAS is installed in "c:\Program files\IBM\..." and I have always avoided paths with spaces since that's not always acceptable in Java and Unix-like environments (of which Java tends to be). Yet I don't like the idea of removing everything and reinstalling into something like c:\apps\ibm\was6 just to test to see if the space is the problem. It's a long hike for a wild guess theory.
Thoughts?
--- In MAXIMO@yahoogroups.com, "Hanna, Christopher A CTR" <christopher.a.hanna@...> wrote:
>
> We upgraded WAS from 6.1 to 7.0 last year, but we did it as part of our upgrade from Mx7.1 to Mx7.5. We followed the process as outlined in document " Upgrade Guide IBM Maximo Products V7.1 to V7.5". So this is not exactly like your scenario, however looking back at my notes, after running the WAS migration, and the associated tasks like installing any plug-ins etc, at that we had Mx7.1 running on WAS7.0. So you could follow the path outlined in that document, but stop short of upgrading the application. We followed scenario 2 in that document, Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0.
>
> Hope that helps a little bit.
>
> -Chris H
>
>
Looking back at my notes, I installed the WAS fix packs after the migration. However it probably can't hurt to try it in the other order. I'm sure we were on a lower rev of 6 then you are currently.
I use the default path with the spaces and it has never caused an issue, so I'm kinda doubtful that would be the problem.
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of jakesteijn
Sent: Thursday, November 14, 2013 6:03 PM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Websphere Upgrade V6 to V7
It looks like it should, that is the document I was looking for and I was expecting the same, just stop before upgrading Maximo. I think there is an upgrade to 7.5 in the near future too, but that's neither here nor there. The upgrade fails in the postupgrade stage, replicating the profiles from WAS 6 to WAS 7. It gives me the same error every time: "MIGR0345E: The migration backup directory is not compatible with this Application Server version. com.ibm.ws.migration.utility.UpgradeException: The migration backup directory is not compatible with this Application Server version."
A couple of things I'm running down: 1) currently I'm doing this on WAS 7.0.0.0 -- the base installation prior to installing the fix packs, I will go to 7.0.0.29 eventually because Maximo 7.5 is recommended for that. My next attempt will be to install at least fixpak 7.0.0.15 or higher, as that's what is specified in the Maximo migration guide; and 2) I'm a little suspicious that the current installation is not completely correct, as WAS is installed in "c:\Program files\IBM\..." and I have always avoided paths with spaces since that's not always acceptable in Java and Unix-like environments (of which Java tends to be). Yet I don't like the idea of removing everything and reinstalling into something like c:\apps\ibm\was6 just to test to see if the space is the problem. It's a long hike for a wild guess theory.
Thoughts?
--- In MAXIMO@yahoogroups.com, "Hanna, Christopher A CTR" <christopher.a.hanna@...> wrote:
>
> We upgraded WAS from 6.1 to 7.0 last year, but we did it as part of our upgrade from Mx7.1 to Mx7.5. We followed the process as outlined in document " Upgrade Guide IBM Maximo Products V7.1 to V7.5". So this is not exactly like your scenario, however looking back at my notes, after running the WAS migration, and the associated tasks like installing any plug-ins etc, at that we had Mx7.1 running on WAS7.0. So you could follow the path outlined in that document, but stop short of upgrading the application. We followed scenario 2 in that document, Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0.
>
> Hope that helps a little bit.
>
> -Chris H
>
>
Early today I went back to a reference system I built last year, and discovered that the WAS installation kit I am working with in the current environment is not obtained from the Maximo installation media, but is instead a separate download of the C1G0QML WAS 7 Base package. It is not the Network Deployment version. This may well be the source of my problem, it would explain the "incompatible versions" error message if the WAS 6 installation is ND and the WAS 7 is not. I'll see about getting the proper Maximo media and try again.
--- In MAXIMO@yahoogroups.com, "Hanna, Christopher A CTR" <christopher.a.hanna@...> wrote:
>
> Looking back at my notes, I installed the WAS fix packs after the migration. However it probably can't hurt to try it in the other order. I'm sure we were on a lower rev of 6 then you are currently.
>
> I use the default path with the spaces and it has never caused an issue, so I'm kinda doubtful that would be the problem.