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.
For those of you looking to upgrade from Maximo 5.2, you should pay special attention to how your auto-numbering has been setup before you upgrade to Maximo 7.x. I am in the process of cleaning up a small problem we were having with job plans because of how our auto numbering was setup. In Maximo 5.2, some records were set down to only go down to an certain level of access (System, Org, Site). With Maximo 7.x, the data hierarchy added a new level, set, but also changed the level some programs could access.
Our problem stemmed from the fact that job plans in Maximo 5.2 were an Site level record. This meant that for each organization we had, there could be a job plan with the same number for a given SiteID. So for Maximo system that has 5 organizations, there could be 5 job plans with the same JPNUM.
Fast forward to Maximo 7.x and the job plan is now a System level record, meaning a job plan can exist with no Org or SiteID data. But our auto-numbering settings from Maximo 5.2 were set at an Org level and didn't caught when the database was upgraded to Maximo 7.x. Job plans were getting auto numbered at a data level that didn't match to where it actually sat in the data hierarchy. This eventually caused problems with planners getting duplicate record warnings when creating new job plans because of seeding numbers from one organization finally catching up to another.
Maximo 5.2 Patch 9 Cluster Environment
Websphere: 5.1.1 Patch 13
OS: Windows 2003
Does anyone know if Maximo 5.2 has any compatibility issues running on Virtual Servers?
My intigration cluster keep crashing since I moved of the Websphere Node servers on vitual boxes which is causing stop communication between MEA and Webmethonds until I reboot the cluster manually.
Application performance is quite slow as well
Thanks,
Fawad
--- On Wed, 2/15/12, Jason Verly <jason.verly@yahoo.com> wrote:
From: Jason Verly <jason.verly@yahoo.com>
Subject: [MAXIMO List] Maximo 5.2 Upgrade Tip – Review Auto Numbering
To: MAXIMO@yahoogroups.com
Received: Wednesday, February 15, 2012, 3:55 PM
For those of you looking to upgrade from Maximo 5.2, you should pay special attention to how your auto-numbering has been setup before you upgrade to Maximo 7.x. I am in the process of cleaning up a small problem we were having with job plans because of how our auto numbering was setup. In Maximo 5.2, some records were set down to only go down to an certain level of access (System, Org, Site). With Maximo 7.x, the data hierarchy added a new level, set, but also changed the level some programs could access.
Our problem stemmed from the fact that job plans in Maximo 5.2 were an Site level record. This meant that for each organization we had, there could be a job plan with the same number for a given SiteID. So for Maximo system that has 5 organizations, there could be 5 job plans with the same JPNUM.
Fast forward to Maximo 7.x and the job plan is now a System level record, meaning a job plan can exist with no Org or SiteID data. But our auto-numbering settings from Maximo 5.2 were set at an Org level and didn't caught when the database was upgraded to Maximo 7.x. Job plans were getting auto numbered at a data level that didn't match to where it actually sat in the data hierarchy. This eventually caused problems with planners getting duplicate record warnings when creating new job plans because of seeding numbers from one organization finally catching up to another.
Dear Fawad,
We already implemented max52 under Virtualization (VMWare) for one year
with excellent result without any issues. Given specs: Maximo 5.2 patch
02A, Bea Weblogic, SQL Server 2000 SP4 under windows 2000 split into 2VMs
8gb ram each in 2 blades.
Best Regards,
Yudi Irianto
fawad ullah <fawadullah@yahoo.com>
Sent by: MAXIMO@yahoogroups.com
16-02-2012 22:50
Please respond to
MAXIMO@yahoogroups.com
To
MAXIMO@yahoogroups.com
cc
Subject
[MAXIMO List] Maixmo 5.2 With VM servers
Maximo 5.2 Patch 9 Cluster Environment
Websphere: 5.1.1 Patch 13
OS: Windows 2003
Does anyone know if Maximo 5.2 has any compatibility issues running on
Virtual Servers?
My intigration cluster keep crashing since I moved of the Websphere Node
servers on vitual boxes which is causing stop communication between MEA
and Webmethonds until I reboot the cluster manually.
Application performance is quite slow as well
Thanks,
Fawad
--- On Wed, 2/15/12, Jason Verly <jason.verly@yahoo.com> wrote:
From: Jason Verly <jason.verly@yahoo.com>
Subject: [MAXIMO List] Maximo 5.2 Upgrade Tip – Review Auto Numbering
To: MAXIMO@yahoogroups.com
Received: Wednesday, February 15, 2012, 3:55 PM
For those of you looking to upgrade from Maximo 5.2, you should pay
special attention to how your auto-numbering has been setup before you
upgrade to Maximo 7.x. I am in the process of cleaning up a small problem
we were having with job plans because of how our auto numbering was setup.
In Maximo 5.2, some records were set down to only go down to an certain
level of access (System, Org, Site). With Maximo 7.x, the data hierarchy
added a new level, set, but also changed the level some programs could
access.
Our problem stemmed from the fact that job plans in Maximo 5.2 were an
Site level record. This meant that for each organization we had, there
could be a job plan with the same number for a given SiteID. So for Maximo
system that has 5 organizations, there could be 5 job plans with the same
JPNUM.
Fast forward to Maximo 7.x and the job plan is now a System level record,
meaning a job plan can exist with no Org or SiteID data. But our
auto-numbering settings from Maximo 5.2 were set at an Org level and
didn't caught when the database was upgraded to Maximo 7.x. Job plans were
getting auto numbered at a data level that didn't match to where it
actually sat in the data hierarchy. This eventually caused problems with
planners getting duplicate record warnings when creating new job plans
because of seeding numbers from one organization finally catching up to
another.