IBM Support

Incorrect version information after installing Maximo 7.6.0.0 Interim Fixes.

Technical Blog Post


Abstract

Incorrect version information after installing Maximo 7.6.0.0 Interim Fixes.

Body

It was recently brought to my attention by a customer who installed an Interim Fix for Maximo 7.6.0.0 that the Maximo Asset Management version number had been updated from Maximo 7.6.0.0 to 7.6.0.9.  This was a cause for alarm which in term had them contact IBM to confirm the version of the application and look in to why it was showing incorrectly.  After reviewing the system information which looked similar to the following, but not the same. (I don't have an environment with this versioning issue).

 

Version Tivoli's process automation engine 7.6.0.0-IFIX20160812-1037 Build 20141117-2230 DB Build V7600-218 HFDB Build HF7600-06
IBM TPAE Integration Framework 7.6.0.0 Build 20141117-1800 DB Build V7600-15
IBM Maximo Asset Management 7.6.0.9 Build 20141117-2230 DB Build V7600-0

 

My first thought was that the version here was being pulled from the mam.xml located in the ibm\smp\maximo\application\maximo\properties\product folder and this XML contained the incorrect information.  After opening the mam.xml from the latest interim fix  it showed the following xml,  confirming my thoughts.  As you can see below the <patch> information being reported for Maximo Asset Management is now 9 instead of the 0 it should be for the product.

 

<?xml version="1.0" encoding="UTF-8"?>
<product>
    <name>IBM Maximo Asset Management</name>
    <version>
        <major>7</major>
        <minor>6</minor>
        <modlevel>0</modlevel>
        <patch>9</patch>
        <build>20141117-2230</build>
    </version>
    <dbmaxvarname>AMUPG</dbmaxvarname>
    <dbscripts></dbscripts>    
    <dbversion>V7600-00</dbversion>    
    <lastdbversion>V7501-00</lastdbversion>
    <checklicense>1</checklicense>
</product>

 

After speaking with our development team and having the hot fixes corrected, it was noted this is only a visual issue with the wrong number being entered.  This means you have nothing to worry about when it comes to your TPAE code or the rest of the interim fix that was installed.  If you were one of the customers that installed this fix before it was re-bundled correcting the Maximo Asset Management version number is easy!  Open up the same mam.xml in a text editor and change the <patch>9</patch>  to <patch>0</patch>,  once you files looks like you see below, save it, then rebuild and redeploy the maximo ear.

 

<?xml version="1.0" encoding="UTF-8"?>
<product>
    <name>IBM Maximo Asset Management</name>
    <version>
        <major>7</major>
        <minor>6</minor>
        <modlevel>0</modlevel>
        <patch>0</patch>
        <build>20141117-2230</build>
    </version>
    <dbmaxvarname>AMUPG</dbmaxvarname>
    <dbscripts></dbscripts>    
    <dbversion>V7600-00</dbversion>    
    <lastdbversion>V7501-00</lastdbversion>
    <checklicense>1</checklicense>
</product>

 

This is a shorter blog then I would normally write, but for the customers out there that do have the incorrect Maximo version after installing a 7.6.0.0 interim fix, this should provide some ease of mind and also assist in correcting the version.  Alternatively you could also apply the latest interim fix which also has the correct version information being reported.

 

Please note this issue has only be found in the later interim fixes for Maximo 7.6.0.0 and no other Industry Solution or Maximo version.  If you have incorrect version information relating to another area or product you should open a PMR rather then update the files yourself.  Any questions, comments or concerns please post below.

 

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

UID

ibm11130811