39
Upgrading Maximo 4,5,6,7.1,7.5 Ed Winchester July 6, 2012 © 2012 IBM Corp.

FLMUG Maximo upgrade 4 5 6 71 75

Embed Size (px)

Citation preview

Page 1: FLMUG Maximo upgrade 4 5 6 71 75

Upgrading Maximo 4,5,6,7.1,7.5 Ed WinchesterJuly 6, 2012

© 2012 IBM Corp.

Page 2: FLMUG Maximo upgrade 4 5 6 71 75

Introduction

Abstract:

� Upgrading IBM Maximo Asset Management from one version to the next version requires great planning, practice and time.

� To complete the upgrade(s) to the newer versions of Maximo, you also have to complete specific steps in order.

� There are some "checks and balances" along the different

© 2012 IBM Corp. 2

� There are some "checks and balances" along the different upgrade paths and help when you need it.

� Let’s begin with some very important Maximo upgrade concepts:

Page 3: FLMUG Maximo upgrade 4 5 6 71 75

Maximo Upgrade - concepts

© 2012 IBM Corp. 3

� Maximo upgrade software was written for specific database products/versions (only for the versions available at that time) and the database upgrade is only supported on those versions.

– Maximo 5-6 upgrade was written – only – for Oracle 9.2.0.8 and Microsoft SQL

server 2000 SP4. So, that means, the upgrade will fail using any later version of

either Oracle or Microsoft SQL Server.

Page 4: FLMUG Maximo upgrade 4 5 6 71 75

Maximo Upgrade - concepts

© 2012 IBM Corp. 4

� Installed products must match between source and destination before upgrading the database.

Example: Maximo with Calibration, Transportation and Project Adapter on

6.2.x means you need to install Maximo with Calibration, Transportation

and Project Adapter on 7.1.1.x before upgrading the database.

Page 5: FLMUG Maximo upgrade 4 5 6 71 75

Maximo Upgrade - concepts

© 2012 IBM Corp. 5

What is Maximo Upgrade 6.5.1.1 (Maximo 5.x/6.x upgrade/update)?

� Maximo 6.2 installations can no longer be distributed – Actuate Remediation. Therefore, the Maximo 6.5.1.1 was created as a remediated and non-operational Maximo 6.2.5 directory containing the upgrade utilities. This directory structure can be used to upgrade/update your Maximo 5.x/6.0/1/2 database to Maximo 6.2.8 in preparation for upgrade to Maximo 7.1.1.10.

Page 6: FLMUG Maximo upgrade 4 5 6 71 75

� Database connections - make sure there is a working database connection. ODBC for SQL Server as well. Watch imported DB.

� Network connections for multi-server and internet for ear building

� Utility connections – paths, properties files

� Security connections - permissions

Maximo Upgrade - concepts

© 2012 IBM Corp. 67/6/12

Page 7: FLMUG Maximo upgrade 4 5 6 71 75

� Supported by upgrade– All data– Any configurations done with the Maximo configuration tools– Data model– User interface and presentation layer– Workflow processes– Data validations and defaults– Integration definitions

Maximo Upgrade - concepts

© 2012 IBM Corp.

– Integration definitions– Escalations

� Not supported by upgrade– Database schema or objects changed outside of Maximo database

configuration– Database objects created (i.e. stored procedures, triggers, views,

synonyms)– Custom extensions of Maximo code– Moving from one database platform to another

Page 8: FLMUG Maximo upgrade 4 5 6 71 75

© 2012 IBM Corp. 8

Full MAXIMO Upgrade path 4.1.1 to 7.5.0.2

MAXIMO Software Versions

4.1.1P8

Upgrade 4.1.1 to 5.1

5.1PO

Upgrade 5.1 to 6.2 :=====::::::: 5.1PS

Upgrade 5.2 to 6.2 S.2P5

6.0

Upgrade 6.0/6.1 to 6.2 .....----.....

6.1

This 6.2.5 version i s non-operational

i nimum Upgrade relea5e 6.2.6.1 (Remedlaled

Upgrade 6.2 to 7.1

IBIR�l�...!:tl ........

'Ut.x

= �

Upgrade 7.1 to 7.5

7.S.0.1

7.S.0.2

-

7.1.1. 9 ..,_1_.1_.1_.10__, -

5.x Control Center

• • x

needs upgrade utilities

Database products/Versions

Oracle 9.2.0.8 MS SQL 2000SP4

Oracle 9.2.0.8 MS SQL 2000SP4

der vendor versions are out-of - s upport

Dl2 8.2,t.1

Oracle 9.2.0.8, 10 MS SQL 2000SP4, 2005SP2

Otder vendor versions are out-of-support

DB2 8.2, t.1, 1.5

Orade 10, 11 MS SQL 2005SP2, 2008

New database created during lnst all adon,. updated duri ng tho fhcpack

instal l, t hen d atabase not used.

Dll29.7

Orade 10, 11 MS SQL2008

WebServer products/Versions

No WebServer Supported

WebSphere S Weblogic7

ebServer required to apply patches., Ider vendor versions are out-of-supp

Since the webserver versions are superseded in the Maximo 7.5,

recommend installing the 7.5 webserver ersions below instead of these versions.

7 .5.0.2 Runs-On support for WebSphere 8

Page 9: FLMUG Maximo upgrade 4 5 6 71 75

Maximo Upgrade: Nuts & Bolts

An overview of both upgrade requirements and environments along with how to upgrade from one Maximo release to other Maximo releases.

� Maximo 4.1.1 to 5.1

© 2012 IBM Corp. 9

� Maximo 5.x to 6.2.8

� Maximo 6.0/1 to 6.2.8

� Maximo 6.2.8 to 7.1.1.10

� Maximo 7.1.1.10 to 7.5.0.2

Page 10: FLMUG Maximo upgrade 4 5 6 71 75

Breakdown: Prepare & Upgrade 4.1.1 to 5.1

•Request and install the Maximo 4.1.1 Patch 8, if needed.

© 2012 IBM Corp. 10

•Request and install the Maximo 4-5 Upgrade utilities from IBM

•Complete the pre-upgrade steps – see upgrade guide.

•Also, MIG, MEA, SAP, PeopleSoft, E-commerce considerations.

•Complete the upgrade by passing each phases of the upgrade utilities:

•Integrity Checker, Validation and Upgrade phases

•Complete post-upgrade steps – see upgrade guide

•Target release will be Maximo 5.1.0 (No Patch)

Page 11: FLMUG Maximo upgrade 4 5 6 71 75

Maximo 4.1.1 to 5.1 Upgrade utilities

© 2012 IBM Corp. 117/6/12

� The integrity checker utility checks the current database and reports on common errors. The integrity checker does not identify all of the data errors that might exist. However, you must correct all errors found by the integrity checker before you can run the validation utility.

� The integrity checker utility updates the MAXVARS table to indicate whether the integrity check completed successfully. You must run the integrity checker utility without errors before you can run the validation utility.

Page 12: FLMUG Maximo upgrade 4 5 6 71 75

Maximo 4.1.1 to 5.1 Upgrade utilities

© 2012 IBM Corp. 127/6/12

� The validation utility checks that valid data in the source Maximo database that needs user intervention is transformed correctly before the upgrade can proceed. For example, you might need to provide a unique e-mail address for users whose e-mail address is not unique.

� The database must pass the validation check successfully with no errors before you can run the validation utility.

Page 13: FLMUG Maximo upgrade 4 5 6 71 75

Maximo 4.1.1 to 5.1 Upgrade utilities

© 2012 IBM Corp. 137/6/12

� You use the upgrade utility to perform the actual database upgrade. Depending on the size of the database the upgrade can take hours… or more.

Page 14: FLMUG Maximo upgrade 4 5 6 71 75

Maximo Upgrade Nuts & Bolts

� Maximo 4.1.1 to 5.1

� Maximo 5.x to 6.2.8

� Maximo 6.0/1 to 6.2.8

© 2012 IBM Corp. 14

� Maximo 6.0/1 to 6.2.8

� Maximo 6.2.8 to 7.1.1.10

� Maximo 7.1.1.10 to 7.5.0.2

Page 15: FLMUG Maximo upgrade 4 5 6 71 75

� Before you do anything, backup both the database and the Maximo directory so you have a beginning recovery point.

� Throughout the upgrade process, there are also additional database backups (recovery points) – don’t skip them!– Post-Validation Utility

Maximo Upgrade – recovery point

© 2012 IBM Corp. 157/6/12

– Post-Validation Utility– Post-Upgrade Utility– Post-Updatedb script

Page 16: FLMUG Maximo upgrade 4 5 6 71 75

Breakdown: Prepare the Maximo 5.x environment

� Three available upgrade launch release versions for Maximo 5.x:

– 5.1P0 (upgrade from 4.1.1), 5.1P5 and 5.2P5+.

� If your system is not at one of the upgrade launch release versions, you will

© 2012 IBM Corp. 16

� If your system is not at one of the upgrade launch release versions, you will need to request and install the needed patches from IBM to update the

database to the nearest upgrade launch release version, this includes:

– Maximo 5.x Core patches

– Maximo 5.x Industry Solution patches, if applicable.

� To install a patch for a Maximo 5.x releases, you have to have a supported

and running webserver so that when you run the Maximo 5.x patch installation, the webserver can update the database.

� In case the Integrity Checker says to run Database Configuration, you will have to run the appropriate 5.x Control Center/Database Configuration. Hint: The database is still a 5.x database.

Page 17: FLMUG Maximo upgrade 4 5 6 71 75

� Request and install Maximo 6.5.1.1 Upgrade package by unzipping the file – makes a “new” Maximo 6.2.5 directory named: Upgrade6511.20101124, then modify maximo.properties to point to the

Breakdown: Prepare the Maximo 6.2.8 environment

© 2012 IBM Corp. 17

Upgrade6511.20101124, then modify maximo.properties to point to the Maximo 5.x database

� Download/install the Maximo 6.5.1.1 cumulative hotfix from: www.ibm.com/support/docview.wss?uid=swg24024327

� Download and install the Maximo 6.2.8 fixpack (point the install to new directory above) and, if applicable, also download/install Maximo 6.2 Industry Solution/patches/fixpack packages.

� If SQL Server, also request and install the latest Maximo 6.2.8 hotfix.

Page 18: FLMUG Maximo upgrade 4 5 6 71 75

Breakdown: Upgrade 5.1/2 to 6.2.8

© 2012 IBM Corp. 18

� Complete the pre-upgrade steps.

� Run the Upgrade utilities (upgradeui) from the Maximo 6.2.8 directory. Only

upgrades the database from Maximo 5.x to Maximo 6.0.0

Important Note: If Integrity Checker says to run Database Configuration you should

only run Database Configuration from the 5.x Control Center – hint: Database is

still 5.x.

� Complete the database upgrade to Maximo 6.2.8 by completing the post-upgrade steps.

Page 19: FLMUG Maximo upgrade 4 5 6 71 75

Maximo 5.x to 6 Upgrade Utilities

© 2012 IBM Corp. 197/6/12

Page 20: FLMUG Maximo upgrade 4 5 6 71 75

Maximo Upgrade Nuts & Bolts

� Maximo 4.1.1 to 5.1

� Maximo 5.x to 6.2.8

© 2012 IBM Corp. 20

� Maximo 6.0/1 to 6.2.8

� Maximo 6.2.8 to 7.1.1.10

� Maximo 7.1.1.10 to 7.5.0.2

Page 21: FLMUG Maximo upgrade 4 5 6 71 75

Breakdown: Prepare and Update 6.0/1/2 to 6.2.8

� Request and install Maximo 6.5.1.1 by unzipping file - makes “new” Maximo 6.2.5 directory named - Upgrade6511.20101124, then modify maximo.properties to point to the Maximo 5.x

© 2012 IBM Corp. 21

named - Upgrade6511.20101124, then modify maximo.properties to point to the Maximo 5.x database.

Note: The original Maximo 6.x directory is not used for the upgrade, only use the newly created

directory by unzipping the Maximo 6.5.1.1..

� Download and install the Maximo 6.5.1.1 latest cumulative hotfix from:www.ibm.com/support/docview.wss?uid=swg24024327

� Download and install the Maximo 6.2.8 fixpack (point the install to new directory above) and, if applicable, also download/install Maximo 6.2 Industry Solution/patches/fixpack packages.

� If SQL Server, request and install the latest Maximo 6.2.8 hotfix.

� Complete the database upgrade to Maximo 6.2.8 by completing the post-upgrade steps

Page 22: FLMUG Maximo upgrade 4 5 6 71 75

Maximo Upgrade Nuts & Bolts

� Maximo 4.1.1 to 5.1

� Maximo 5.x to 6.2.8

� Maximo 6.0/1 to 6.2.8

© 2012 IBM Corp. 22

� Maximo 6.0/1 to 6.2.8

� Maximo 6.2.8 to 7.1.1.10

� Maximo 7.1.1.10 to 7.5.0.2

Page 23: FLMUG Maximo upgrade 4 5 6 71 75

Breakdown: Prepare the Maximo 7.1 Database

� So, the supported database

product versions change

between Maximo versions – most companies are using a -2 version

philosophy.

� So, when you upgrade from Maximo 6.2.8 to 7.1.1.10, that is

the ideal time to move to a later supported database product

© 2012 IBM Corp. 23

supported database product version.

Note: Maximo 4 to 5 to 6 can really stay

on the same database product

version for those particular upgrades.

� So, I recommend moving to the

“latest” supported database product version because that

version will have the longest “support shelf-life”.

Page 24: FLMUG Maximo upgrade 4 5 6 71 75

Prepare the Maximo 7.1 Webserver – hard way

� So, here is how things “should go” (WebSphere example):

1. Install Maximo 7. 1 Middleware - WebSphere 6.1

2. Install Maximo 7.1 (7.1.1.5)

3. Install Maximo 7.1.1.10 fixpack (supports

WebSphere 7)

<Upgrade the 6.2.8 database to 7.1.1.10>

1. Uninstall WebSphere 6.1

2. Install Maximo 7.5 Middleware - WebSphere 7

© 2012 IBM Corp. 24

2. Install Maximo 7.5 Middleware - WebSphere 7

… that’s a lot of WebSphere juggling – right?

� Since WebSphere 7/WebLogic 10 are supported by both

7.1.1.10 and 7.5., why not install WebSphere 7/WebLogic

10 to begin with and skip the install/uninstall business…

I HOPE YOU SEE MY POINT? But, it is a little tricky…

Page 25: FLMUG Maximo upgrade 4 5 6 71 75

Prepare the Maximo 7.1 Webserver – easy way

� So, here is how things “can go” (WebSphere example):

1. Install Maximo 7. 5 Middleware - WebSphere 7

2. Install Maximo 7.1 (7.1.1.5)

3. Install Maximo 7.1.1.10 fixpack (supports

WebSphere 7)

<Upgrade the 6.2.8 database to 7.1.1.10>

… now you are ready for the Maximo 7.5 Install/Upgrade

part.

© 2012 IBM Corp. 25

� Here’s the tricky part…– If you are going to use WebSphere, download the 2 - Maximo

7.1 Launchpad packages (unzip into a single directory), but don’t download the 3 - Maximo 7.1 Middleware packages.

– Also, download the 2 - Maximo 7.5 Launchpad packages (unzip into a single directory) and download the Maximo 7.5 Middleware packages – there are 3 packages (unzip into single directory).

Tip: As a time saver, if you are just installing WebSphere, download only the largest of the 3 Middleware packages.

Note: If you are not using either WebSphere or DB2 for your middleware products, you don’t need to download any of the Maximo Middleware packages.

Page 26: FLMUG Maximo upgrade 4 5 6 71 75

Prepare the Maximo 7.1 Webserver – easy way (Cont)

Back to our story…

� After unzipping both Maximo 7.5 Launchpad packages into a

single directory, open a DOS Prompt, change to that

directory and execute the following:

cd Install\MWI

mwi-console

Note: mwi-console is one of the Middleware executables to start

the Middleware installer outside of the Launchpad – during

© 2012 IBM Corp. 26

the Middleware installer outside of the Launchpad – during

the Middleware install, point to the Maximo 7.5 Middleware

directory to install WebSphere 7.

� Once the Maximo 7.5 Middleware installation is complete,

unzip both Maximo 7.1 Launchpad packages into a single

directory, open a DOS Prompt and change to that directory

and execute the following:

launchpad

� Complete the install of both Maximo 7.1 (7.1.1.5) followed

by Maximo 7.1.1.10 fixpack.

Page 27: FLMUG Maximo upgrade 4 5 6 71 75

� Complete the pre-upgrade steps from the

upgrade manual.

� Download and install the Middleware.� Download and install Maximo 7.1 (7.1.1.5)� Download and install the Maximo 7.1.1.10

fixpack (point the install to the existing 7.1.1.5 \ibm\SMP directory).

� If applicable, also download/install Maximo

7.1.1.x Industry Solution/patches/fixpack

Breakdown: Upgrade 6.2.8 to 7.1.1.10

27

7.1.1.x Industry Solution/patches/fixpackpackages.

� Run the Upgrade utilities (upgradeui) from the

Maximo 7.1.1.10 directory. Only upgrades the

database from Maximo 6.2.8 to Maximo 7.1.1.0

Important Note: If Integrity Checker says to run

Database Configuration you should only run configdb from the 6.2.8 directory– hint:

Database is still 6.2.8. � Complete the database upgrade to Maximo

7.1.1.10 by completing the post-upgrade steps,

Page 28: FLMUG Maximo upgrade 4 5 6 71 75

Maximo 6.2.x to 7.1.1.x Upgrade utilities

© 2012 IBM Corp. 287/6/12

Page 29: FLMUG Maximo upgrade 4 5 6 71 75

Maximo Upgrade Nuts & Bolts

� Maximo 4.1.1 to 5.1

� Maximo 5.x to 6.2.8

� Maximo 6.0/1 to 6.2.8

© 2012 IBM Corp. 29

� Maximo 6.0/1 to 6.2.8

� Maximo 6.2.x to 7.1.1.10

� Maximo 7.1.1.x 7.5.0.2

Page 30: FLMUG Maximo upgrade 4 5 6 71 75

Breakdown: Upgrade 7.1.1.10 to 7.5.0.2

30

� Complete the pre-upgrade steps from the Maximo 7.1 to 7.5 upgrade guide.

� Download and install the Middleware (if needed)� Download and install Maximo 7.5.0.0 (point the existing 7.1.1.10 \ibm\SMP

directory).� Download and install the Maximo 7.5.0.2 fixpack

� If applicable, also download/install Maximo 7.5.0.x Industry Solution/patches/fixpack packages.

� Complete the database upgrade to Maximo 7.5.0.2 by completing the post-upgrade steps.

Page 31: FLMUG Maximo upgrade 4 5 6 71 75

Special: MAXIMO Upgrade 4.1.1 to 7.5.0.2

© 2012 IBM Corp. 31

Page 32: FLMUG Maximo upgrade 4 5 6 71 75

Special: MAXIMO Upgrade 5.x to 7.5.0.2

© 2012 IBM Corp. 32

Page 33: FLMUG Maximo upgrade 4 5 6 71 75

Maximo Upgrade – go shopping!

Requesting/Downloading software from IBM

Shopping List

© 2012 IBM Corp. 33

Page 34: FLMUG Maximo upgrade 4 5 6 71 75

Requesting/Downloading software from IBM

IBM Maximo Upgrade Resources – fill out and submit the request form for upgrade software

packages/programs and for updated information about Maximo Upgrades

https://www-304.ibm.com/support/docview.wss?uid=swg21266217&wv=1

IBM Passport Advantage – sign in with your IBM login ID – this is where you can download

your authorized “installation” packages from

© 2012 IBM Corp.

your authorized “installation” packages from

www.ibm.com/software/howtobuy/passportadvantage

IBM FixCentral - sign in with your IBM login ID – this is where you can download your ”fixpack”

packages from

www.ibm.com/support/fixcentral/

34

Page 35: FLMUG Maximo upgrade 4 5 6 71 75

Shopping List:Maximo 4.1.1 to 5.1

� Maximo 4.1.1 Patch 8 (Request form)� Maximo 4-5 Upgrade utilities (Request form)

Maximo 5.x to 6.2.8� Maximo 5.x Core patches (Request form)� If applicable, Maximo 5.x Industry Solution patches (Request form)� Maximo 6.5.1.1 Upgrade package (Request form)� Maximo 6.5.1.1 latest cumulative hotfix from:

www.ibm.com/support/docview.wss?uid=swg24024327� Maximo 6.2.8 fixpack (FixCentral)� Maximo 6.2.8 latest hotfix (contact support)

© 2012 IBM Corp. 35

� Maximo 6.2.8 latest hotfix (contact support)� If applicable, Maximo 6.2.x Industry Solution (Passport Advantage)

Maximo 6.2.8 to 7.1.1.10� IBM Tivoli Middleware Installer 1 of 3, 2 of 3, 3 of 3 (Passport Advantage)� IBM Maximo Asset Management Launchpad 7.1 - 1 of 2, 2 of 2 (Passport Advantage)� Maximo 7.1.1.10 fixpack (FixCentral)� If applicable, Maximo 7.1.1.x Industry Solution (Passport Advantage)

Maximo 7.1.1.10 to 7.5.0.2� Tivoli Middleware Installer Images V7.5.0, 1 of 3, 2 of 3, 3 of 3 (Passport Advantage)� IBM Maximo Asset Management V7.5.0, Launchpad 1 of 2, 2 of 2 (Passport Advantage)� Maximo 7.5.0.2 fixpack (FixCentral)� Maximo 7.5.0.2 Interim fix (IFIX) (FixCentral)� If applicable, Maximo 7.5.0.x Industry Solution (Passport Advantage)

Page 36: FLMUG Maximo upgrade 4 5 6 71 75

Other upgrade related links

Upgrade Frequently Asked Questions (detailed upgrade scenario)https://www-304.ibm.com/support/docview.wss?uid=swg21368150

Upgrade Requirements Matrix (Industry Solution version matrix)https://www-304.ibm.com/support/docview.wss?uid=swg21440174

© 2012 IBM Corp.

Configuration Maxtrixhttps://www-304.ibm.com/support/docview.wss?uid=swg27014419

Potential security vulnerability when using Web based applications on IBM WebSphere Application Server due to Java HashTable implementation vulnerability (PM53930/PM57565) – WebSphere 7.0.0.21

https://www-304.ibm.com/support/docview.wss?uid=swg21577532

36

Page 37: FLMUG Maximo upgrade 4 5 6 71 75

Questions

© 2012 IBM Corp. 37

Page 38: FLMUG Maximo upgrade 4 5 6 71 75

Backup slide

� Completing the Maximo 5 to 6 upgrade on any other database product versions than the

certified database products - Oracle 9.2.0.8 and SQL Server 2000 SP4 – is not supported

and is not recommended as other database product versions had not been released

when the version 5 to version 6 upgrade was released about 4 years ago. This did not

allow us to QA the upgrade software on any other database product versions. There are

currently no plans to develop or QA a supported version 5 to version 6 upgrade on any

other database product versions nor do we have a list of reported issues by any

customer who may have attempted to perform this upgrade using anything other than the

prescribed version of either Oracle or SQL Server for this upgrade. Performing your

© 2012 IBM Corp.

prescribed version of either Oracle or SQL Server for this upgrade. Performing your

version 5 to version 6 upgrade on other database product versions could impact the

integrity of your data and render your system inoperable post upgrade as well as

complicate future upgrades (version 6 - 7, etc.) for you.

1. The upgrade tools have been tested against 100s of upgrades at this time and take into

account all interdependencies.

2. There are archiving options for pre-upgrade that you could consider.

3. You also might consider hiring IBM Services (via your Sales representative) or a

independent consultant to assist in this upgrade effort.

4. Lastly, upgrading your data incorrectly can render your system inoperable and possibly

unsupported post upgrade as well as complicate future upgrades.

Page 39: FLMUG Maximo upgrade 4 5 6 71 75

Notes

� End of Support of Maximo 6.2.x is September 2013

� Must be at 7.1.1.10 to upgrade to 7.5.0.2

� Will be 2 release streams– 7.1.1.11 Fix Pack – 7.5.0.3 Fix Pack

� All products must be at 7.5

© 2012 IBM Corp.

� All products must be at 7.5– Cannot upgrade one product to 7.5 and others at 7

� Maximo 7.5 upgrade - No upgrade utilities like in previous upgrades– No upgradeui– No 7.5 Integrity Checker success before upgrading

– No Validation success before upgrading

– No upgrade program

� Maximo 7.5 upgrade - Database upgrade done via updatedb