Comments on: Maximo fix pack 7.1.1.6 now available

By: adonis

adonis — Mon, 20 Jun 2011 01:29:00 +0000

OH I forgot to mention below…. enhancements/changes btw 7.1.1.5 and 7.1.1.6 …

By: adonis

adonis — Mon, 20 Jun 2011 01:22:00 +0000

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

By: Madhav

Madhav — Wed, 22 Dec 2010 06:34:01 +0000

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.

By: orozcom

orozcom — Wed, 11 Aug 2010 13:46:37 +0000

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.

By: Chon

Chon — Sat, 03 Jul 2010 22:14:02 +0000

I would recommend to defer the automatic deployment. The install shouldn’t take more than a few hours if everything goes right.

By: Zee

Zee — Fri, 02 Jul 2010 17:19:19 +0000

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,

By: Chon

Chon — Thu, 17 Jun 2010 13:26:38 +0000

You can try to re import the BIRT reports into Maximo and see if that helps.

By: zee

zee — Thu, 17 Jun 2010 04:57:01 +0000

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 ?

By: Chon

Chon — Fri, 14 May 2010 13:45:17 +0000

Glad you got it working!

By: orozcom

orozcom — Fri, 14 May 2010 13:22:37 +0000

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.

By: orozcom

orozcom — Tue, 04 May 2010 13:24:56 +0000

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 SMP\maximo\tools\maximo\en\script 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

By: Chon

Chon — Wed, 14 Apr 2010 17:33:29 +0000

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.

By: Francois Paquette

Francois Paquette — Wed, 14 Apr 2010 15:41:16 +0000

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.

By: Francois Paquette

Francois Paquette — Wed, 14 Apr 2010 14:35:03 +0000

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.

By: Chon

Chon — Tue, 13 Apr 2010 19:24:20 +0000

What kind of update are you looking for?

By: Francois Paquette

Francois Paquette — Tue, 13 Apr 2010 19:17:02 +0000

any update on this?

By: Chon

Chon — Tue, 16 Mar 2010 16:13:25 +0000

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.

By: pjung

pjung — Tue, 16 Mar 2010 15:57:53 +0000

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.

By: Chon

Chon — Wed, 10 Feb 2010 00:37:18 +0000

Did you try stopping the app server then trying to run the updatedb?

By: mmd

mmd — Wed, 10 Feb 2010 00:31:40 +0000

we get the following error in the log file which are located [Drive name]:\ibm\SMP\logs\CTGInstallMessage00.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]\IBM\SMP\pmp\base_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