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 am after some help please. I have built a Maximo 7.5 template for our company, we intend to merge 6 Maximo instances into the template over time. The system integrator after 5 months on the job is saying he cannot use the template as it won't work with Migration Manager and that he needs to build the template from OOB so that Migration Manager knows how to do all the changes to a DEV, UAT, TEST etc region. This does not seem logical to me, however I have no experience with the Migration Manager tool and would appreciate some advice from anyone that can assist please.
Regards
Paul
MM works in 2 modes : mode 1 snapshot is basically taking a 'picture' of your changes and then try to load it into the destination
Mode 2 change is like 'recording' the changes and then load it in the destination
Your integrator seems to prefer to use the mode 2.....
In my opinion, MM is not what you need to merge databases....
I would take the template and use some third party tools to merge the data into your the template !!!
Sent from my iPhone
On 06 Jun 2012, at 21:56, "samaire77" <paul.harris@truenergy.com.au> wrote:
> I am after some help please. I have built a Maximo 7.5 template for our company, we intend to merge 6 Maximo instances into the template over time. The system integrator after 5 months on the job is saying he cannot use the template as it won't work with Migration Manager and that he needs to build the template from OOB so that Migration Manager knows how to do all the changes to a DEV, UAT, TEST etc region. This does not seem logical to me, however I have no experience with the Migration Manager tool and would appreciate some advice from anyone that can assist please.
>
> Regards
>
> Paul
>
>
What do you mean by a template? Do you mean you have configured Maximo in a
particular way? Can you tell us a little more about the granularity of what
you are trying to move from where to where etc?
On Wed, Jun 6, 2012 at 1:56 PM, samaire77 <paul.harris@truenergy.com.au>wrote:
> **
>
>
> I am after some help please. I have built a Maximo 7.5 template for our
> company, we intend to merge 6 Maximo instances into the template over time.
> The system integrator after 5 months on the job is saying he cannot use the
> template as it won't work with Migration Manager and that he needs to build
> the template from OOB so that Migration Manager knows how to do all the
> changes to a DEV, UAT, TEST etc region. This does not seem logical to me,
> however I have no experience with the Migration Manager tool and would
> appreciate some advice from anyone that can assist please.
>
> Regards
>
> Paul
>
>
>
I agree with Mohska. I've done many Maximo merges and haven't found
Migration Manager to play a critical role in that. You need to take your
Maximo user data from your standalone Maximo instance DB's and merge it
into your shared 7.5 DB (your template), handling field remappings,
changing any duplicate keys, changing all incoming sequence ID's,
converting referential data like domain values via cross-reference, etc.
However, if as a side project your integrator wants to use MM just to take
your 7.5 template configuration and move it into 7.5 DEV, UAT, and TEST
environments, then you might find a use for it there using the snapshot
mode. I normally just copy the whole DB to the other environments though
as it's much easier and you know you've got everything.
Hope that helps,
David Wadsworth
Asset Partners
On Wed, Jun 6, 2012 at 4:57 PM, <mohska@gmail.com> wrote:
> **
>
>
> MM works in 2 modes : mode 1 snapshot is basically taking a 'picture' of
> your changes and then try to load it into the destination
> Mode 2 change is like 'recording' the changes and then load it in the
> destination
> Your integrator seems to prefer to use the mode 2.....
> In my opinion, MM is not what you need to merge databases....
> I would take the template and use some third party tools to merge the data
> into your the template !!!
>
> Sent from my iPhone
>
> On 06 Jun 2012, at 21:56, "samaire77" <paul.harris@truenergy.com.au>
> wrote:
>
> > I am after some help please. I have built a Maximo 7.5 template for our
> company, we intend to merge 6 Maximo instances into the template over time.
> The system integrator after 5 months on the job is saying he cannot use the
> template as it won't work with Migration Manager and that he needs to build
> the template from OOB so that Migration Manager knows how to do all the
> changes to a DEV, UAT, TEST etc region. This does not seem logical to me,
> however I have no experience with the Migration Manager tool and would
> appreciate some advice from anyone that can assist please.
> >
> > Regards
> >
> > Paul
> >
> >
>
>
>
>
>
Hi,
We merged eight different 4.1.1 installations into one database. We did this one site at a time. Some we did with a data loader application from Interloc Solutions that used the integration objects.
We also wrote SQL scripts for a lot of data to import the data. Once you know how all of the data fits into 7 it's actually fairly easy to do.
So for about a year we had some sites on 4.1.1 and the others on 7.1.1.6.
We don't use the MM to synch sandbox and production. We manually make changes to both systems. If it fails in sandbox then we just back out the changes.
Dave Bone
--- In MAXIMO@yahoogroups.com, "samaire77" <paul.harris@...> wrote:
>
> I am after some help please. I have built a Maximo 7.5 template for our company, we intend to merge 6 Maximo instances into the template over time. The system integrator after 5 months on the job is saying he cannot use the template as it won't work with Migration Manager and that he needs to build the template from OOB so that Migration Manager knows how to do all the changes to a DEV, UAT, TEST etc region. This does not seem logical to me, however I have no experience with the Migration Manager tool and would appreciate some advice from anyone that can assist please.
>
>
> Regards
>
> Paul
>