Maximo fix pack 7.1.1.6 now available

Written by Chon Neth, Editor-in-Chief

On December 14, 2009, IBM Software released the Base Services 7.1.1.6 fix pack for Maximo Asset Management, Maximo Asset Management Essentials, and Tivoli Asset Management for IT.

Download Description
This product update corresponds to fixes for Base Services (MBS), which is not a product, but is the base platform component for the products listed in this section. This document provides information for you to use when upgrading your product to the latest version.

Although Base Services has an internal version number of its own (v7.1.1.6), when referring to updates, please refer to the version number for your specific product.

Note the MBS README included in this document supersedes the README file that is included in the fix pack download .ZIP file and should be reviewed prior to applying this product update.

Products

IBM(R) Maximo(R) Asset Management 7.1.0.6
IBM Maximo Asset Management Essentials 7.1.0.6
IBM Tivoli(R) Asset Management for IT 7.1.0.6

Considerations

–Do not apply the 7.1.1.6 MBS fixpack if your system has any of the below products and components installed. Verification is ongoing for these products and additional information will be provided when MBS 7.1.1.5 can be applied to the following:

  • IBM Tivoli Change and Configuration Management Database 7.1
  • IBM Tivoli Service Request Manager 7.1.
  • IBM Tivoli Provisioning Manager 7.1
  • IBM Tivoli Change and Configuration Management Database 7.2
  • IBM Tivoli Service Request Manager 7.2
  • IBM Tivoli Service Automation Manager 7.2
  • IBM Maximo Asset Management for Energy Optimization 7.1
  • IBM Maximo Asset Management Scheduler 7.1

-There is no 7.1.1.6 update for the Maximo Asset Navigator or IBM Tivoli Integration Composer (ITIC) products. Tivoli Asset Management for IT 7.1.0.6 users can upgrade to ITIC 7.2.0.0. ITIC 7.2.0.0 is backward compatible with MBS 7.1.1.6.

–Do not apply the 7.1.1.6 Fix Pack if you installed any 7.1.1.x hot fixes after 12/1/09 as they may not be included. If you received any hot fixes after this date, you should not apply the 7.1.1.6 Fix Pack until the first 7.1.1.6 cumulative hot fix is released. At that time, you will need to apply both the 7.1.1.6 Fix Pack and the 7.1.1.6 hot fix. Look to this page for additional information and availability date for this hot fix.

-With the release of the 7.1.1.6 MBS Fix Pack, Maximo 6.2.5 users can now upgrade to Maximo v7. If your Maximo 6.2.5 has any Industry Solutions installed you will need to wait until the latest v7 industry Solution Fix Packs and/or hot fixes are available. These updates are slated to be released on 12/18/09.

For additional information on MBS 7.1.1.6, please click here

Prerequisites

  • IBM Maximo Asset Management 7.1.0
  • IBM Maximo Asset Management Essentials 7.1.0
  • IBM Tivoli Asset Management for IT 7.1.0
Download the Maximo 7.1.1.6 fix pack

Did You Know...

As Maximo Experts, we have developed several add-on products for Maximo that mobilize the work force, simplifies assignments, provides ad-hoc reporting capabilities and facilitates the seamless integration of Service Requests into Maximo.

Check out our products by clicking on the following links: EZMaxMobile, EZMaxPlanner and EZMaxRequest.

Find Out More

23 thoughts on “Maximo fix pack 7.1.1.6 now available”

  1. Hello Chon,
    Long time, hope everything is OK.

    We are working on updating to fix pack 7.1.1.6-173 (or V7116-173), currently it seems from running the updatedb.bat file we got the following issue / error
    (Side Note: The current version of Maximo we are on is 7115-87, checked the current version by going to the following file ibmSMPmaximotoolsmaximoenxliffMAXUPGMAXMESSAGES.xliff –> open with notepad):

    Product Base Services updatedb process starts…

    MAXUPG: V7116-173, Current release DB build: V7115-149, Last release DB build: V7114-118

    Cannot run database script update.

    DB version(MAXUPG) is not same as either Last release DB build or Current release DB build.

    Updatedb process ends: ERROR

    Please check the log file.

    java.lang.Exception: Cannot run database script update.

    DB version(MAXUPG) is not same as either Last release DB build or Current releas

    e DB build.

    at psdi.tools.UpdateDB.startProcess(Unknown Source)

    at psdi.tools.UpdateDB.startProcess(Unknown Source)

    at psdi.tools.UpdateDB.loadScriptInfo(Unknown Source)

    at psdi.tools.UpdateDB.main(Unknown Source)

    ===========================================
    did some online search and found following for reference: http://www-01.ibm.com/support/docview.wss?rs=3211&context=SSLKNW&uid=swg21315960&loc=en_US&cs=UTF-8&lang=en

    mentions that we need to do the following: update maxvars set varvalue = ‘V7110-00’ where varname = ‘DBPROJECT’

    in our case:
    Our version of Maximo is: V7115-149 so we run the following query in db:
    varvalue = ‘V7115-149’ where varname = ‘MAXUPG’

    The MAXUPG information is derived from the following document:
    http://www-01.ibm.com/support/docview.wss?uid=swg27016367&aid=1

    On page 5:
    select*from maxvars where varname=’MAXUPG’;

    =============================================
    After setting the variable to the V7115-149, it moved forward, but it still hangs on us at the end.

    Based on your other document: https://www.maximotimes.com/maximotimes/maximo/maximo-7115-fix-pack-now-available/
    We have tried updatedb.bat command and delete and deploy the .era file we still are getting it to hang up on us.

    Do you have any suggestion ideas solutions.
    Please let us know.
    Thank you.
    Regards,
    MMD

  2. we get the following error in the log file which are located [Drive name]:ibmSMPlogsCTGInstallMessage00.log

    SEVERE: CTGIN0143E: An action error ocurred during the processing of a deployment operation. Action identifier: “Upgrade_Maximo_Update_DB”. Action display name: “Stop Application Server, Run Maximo UpdateDB Script, Start Application Server”.
    Feb 9, 2010 1:23:43 PM class com.ibm.tivoli.ccmdb.install.ps.event.handlers.PsiActionProgressHandler handleSIEvent
    INFO: CTGIN0144I: Completed action “16” of “16”. Action display name: “Stop Application Server, Run Maximo UpdateDB Script, Start Application Server”.
    Feb 9, 2010 1:47:50 PM class com.ibm.tivoli.ccmdb.install.ps.request.ASolutionElementRequestMixin handleRequestCompletion
    SEVERE: CTGIN0130E: Errors were detected during an attempt to upgrade the [Drive Name]IBMSMPpmpbase_services_7.1.1.6.zip package.

    Also, for others who are trying to fix pack updates be sure to read the readme for the fix where it gives information on how to install and what issues have been resolved in the fix pack: ftp://public.dhe.ibm.com/software/tivoli_support/maximo/v7/7116/readme_mbs7116.txt

  3. Hello to all. We are trying to install the fixpack 7.1.1.6 but none of the three installations was working fine. Here are the problems:

    First update on a “naked” 7.1.1.5 system: Best run and the result seems to be ok. Only problem: All reports have empty labels (shown as )

    Second update on a 7.1.1.5 vm system with two instances, the update was practised to the second instance (maxtest as described in another article). Result: Many, many errors because the fixpack wanted to install LDAP but that wasn’t configured in none of the property files. After fixing manx things in WebSphere the system works but the “Goto…” menu in Maximo doesn’t work (NullPointerException in log file)

    Third update on a copy of the second 7.1.1.5 vm system (see above). Result: After calling the install.exe the update of deployment engine ended with unspecified error (no log outputs) and updating wasn’t possible since now.

    Is there anybody out there in the world whose fixpack was installed with success? For everbody who wants to do that: Take two or three days to do that, it’s not only pressing the install.exe.

    1. I successfully patch one of my clients from 7.1.1.4 to 7.1.1.6 and I am now in the process of patching another client to 7.1.1.6. It wasn’t easy at first, but I eventually got it working and patched. I had issues running the install.exe and I opted to run the install manually which then worked for me. As for patching a second instance on a server, I’m not sure if that is possible in Maximo 7. It was with Maximo 6 though. I can’t help you without looking at your system setup, but if you require some professional service, I will be glad to send you a quote to patch your system and I will be doing the patch personally.

          1. I’m running Maximo 7.1.1.4 and 7.1.1.5 with SQL 2005. Not able to install the 7.1.1.6 patch, even manually :

            Product Base Services updatedb process starts…
            MAXUPG: V7116-0, Current release DB build: V7116-173, Last release DB build: V71
            15-149
            Database script update in progress, please wait……….
            Current version :V7116-0
            Updating To :V7116-173
            Error running file: V7116_01
            Script Update complete: Error
            Updatedb process ends: ERROR
            Please check the log file.
            java.lang.Exception: DATABASE SCRIPT UPDATE COMPLETED WITH ERROR. dbchange#Scrip
            tFailure;
            sql#2601;
            [MAXIMOT-1]Cannot insert duplicate key row in object ‘dbo.maxmenu’ with unique i
            ndex ‘maxmenu_ndx1’.

            I don’t know what to do next… any help would be appreciated.

  4. I noticed something in Websphere during the automatic installation of fixpack 7.1.1.6. In Applications, my enterprise Applications (Maximo, Maximo Help) they both disappers and then I have the error message in the installer windows…. CTGIN0143E: An action error ocurred during the processing of a deployment operation. Action identifier: “Upgrade_Maximo_Update_DB”. Action display name: “Stop Application Server, Run Maximo UpdateDB Script, Start Application Server”.

    I’m glad im using Vmware, so I can revert to snapshot, but I need to find a way to install fixpack 7.1.1.6. Thank you in advance for your help.

    1. That is supposed to happen to your enterprise applications. They are removed and reinstalled for you by the fixpack installation. The reason you can’t install the fixpack is because it is failing when it’s trying to run update DB. It is trying to insert a record into the maxmenu table and of course that record already exists. What record is it inserting? I don’t know. Double check that unique index on that table to see what the values are and maybe that might give you an idea.

  5. We have Maximo 7.1.1.5 installed. and we have successfully upgraded from 6.2.4. We are now just trying to upgrade from 7.1.1.5 to 7.1.1.6. I keep getting the same type of error with the duplicate key row error. I am looking at the log files, but I would really like to see the script file. I took a look in the SMPmaximotoolsmaximoenscript directory for the V7116-files. They are not there? That is usually where they are. The file that I get stuck on is V7116-169.

    insert into maxvartype (varname, vartype, defaultvalue, description, maxvartypeid) select varname, vartype, defaultvalue, description, maxvartypeid from xxmaxvartype
    ;

    — BEGINUPDATEDBERROR
    — Error running file: V7116_169
    — UPDATEDBFILE:V7116_169.dbc
    — Script: Error
    dbchange#ScriptFailure;
    sql#2601;
    [GVPTSQL01]Cannot insert duplicate key row in object ‘dbo.maxvartype’ with unique index ‘maxvartype_ndx1’.
    at psdi.dbmanage.ScriptRun.run(Unknown Source)
    at psdi.tools.UpdateDB.runDbcFileInfo(Unknown Source)
    at psdi.tools.UpdateDB.runScripts(Unknown Source)
    at psdi.tools.UpdateDB.startProcess(Unknown Source)
    at psdi.tools.UpdateDB.startProcess(Unknown Source)
    at psdi.tools.UpdateDB.loadScriptInfo(Unknown Source)
    at psdi.tools.UpdateDB.main(Unknown Source)
    Caused by: sql#2601;
    [GVPTSQL01]Cannot insert duplicate key row in object ‘dbo.maxvartype’ with unique index ‘maxvartype_ndx1’.
    at psdi.dbmanage.connection.DatabaseConnection.doSql(Unknown Source)
    at psdi.dbmanage.connection.SQLServerDatabaseConnection.doSql(Unknown Source)
    at psdi.dbmanage.connection.DatabaseConnection.doSql(Unknown Source)
    at psdi.dbmanage.statement.TempTableModel.copyRows(Unknown Source)
    at psdi.dbmanage.statement.TempTableModel.copyFromTempRows(Unknown Source)
    at psdi.dbmanage.statement.TempTableModel.insertRows(Unknown Source)
    at psdi.dbmanage.statement.FreeFormStatement.fillInMissingRequiredFields(Unknown Source)
    at psdi.dbmanage.statement.FreeFormStatement.executeFreeFormStatement(Unknown Source)
    at psdi.dbmanage.statement.FreeFormStatement.run(Unknown Source)
    at psdi.dbmanage.statement.Script.run(Unknown Source)
    … 7 more
    Caused by: com.inet.tds.at: Msg 2601, Level 14, State 1, Line 1, Sqlstate 23000
    [GVPTSQL01]Cannot insert duplicate key row in object ‘dbo.maxvartype’ with unique index ‘maxvartype_ndx1’.
    at com.inet.tds.aq.a(Unknown Source)
    at com.inet.tds.k.b(Unknown Source)
    at com.inet.tds.k.a(Unknown Source)
    at com.inet.tds.k.a(Unknown Source)
    at com.inet.tds.af.b(Unknown Source)
    at com.inet.tds.af.execute(Unknown Source)
    … 17 more

    1. Ok. I figured this out. It is actually a bug. The query: Cannot insert duplicate key row in object ‘dbo.maxvartype’ with unique index ‘maxvartype_ndx1′.
      was getting a resultset back instead of a distinct value. We made the query return a distinct value, and it worked. If you are doing an out of the box upgrade, the value that you return will be distinct, but if you are doing an upgrade, and you multiple values returned it will not. I submitted a PMR, and an APAR was created. I do not know when this bug will be fixed.

  6. Hi CHon,

    I just installed a new 7115 environment. After installation, generated the request pages. When I am trying to run OOB reports, it is giving me the error below for ALL the reports. I tried the same steps in my local vm but same issue.

    If you notice in the screenshot, It does open the BIRT Viewer. But once it starts processing the report, gives this error. Any clue?

    I cannot attach the screenshot here but it says “Multipl Exceptions occured” it further says mxReportscriptcontext is not defined .. and then long errors … any clue ?

  7. Thanks Chon, my reports are working now … btw I have 7115 new installation with Oracle 11g and planning to upgrade it to 7116. Are there any Gotchaaz that I need to be aware of? ANYONE ?? and how long this whole process should take? approx idea ?

    Thanks,

      1. Zee,

        We just upgraded from 7.1.1.5 to 7.1.1.6. The gotcha we had we fixed. We only got the error after we applied the 7.1.1.5 hotfix to it before we upgrade. Once we left out the 7.1.1.5 hotfix, and went directly to 7.1.1.6 it worked fine. Then we added the 7.1.1.6 hot fixes.

  8. Hi,

    I get the error. We are in BS 7116.

    DB version(MAXUPG) is not same as either Last release DB build or Current release DB build.

    Any suggestions will help me a lot. Thank you.

  9. can you please provide a simpler list of changes or enhancements that came with 7.1.1.6 and please don’t refer me to the readme file(think of what a user can easily be told) …. Just a basic may be 20 bullet point on new features specifically to Work Order Tracking, PM, Job Plan modules. Unfortunately I dont have the two versions to log into, compare screens, play with menus and so forth…… thanks in advance

Leave a Reply