Problem

User applied interim fix pack 7.1.0.3-TIV-SRM-IF0002 on to a CCMDB/TSRM install. Afterwards it was noticed that when clicking on reports and selecting any report to run, a pop-up comes up asking which report they would like to run. Within 1/2 sec an error also pops up on the screen as follows;

BMXAA4210E - Database error number -7 has occurred.

The character "&" following "COMPANY" and runtype" is not valid.

 In the logs the following appears;

0000004f SystemOut O 15 Jul 2009 12:35:15:167 [ERROR] BMXAA6713E - The MBO fetch failed in the mboset with the SQL error code:-7

com.ibm.db2.jcc.c.SqlException: The character "&" following "COMPANY' and runtype" is not valid.

at com.ibm.db2.jcc.c.fg.e(fg.java:1596)

at com.ibm.db2.jcc.c.fg.a(fg.java:1206)

at com.ibm.db2.jcc.b.gb.g(gb.java:140)

at com.ibm.db2.jcc.b.gb.a(gb.java:39)

at com.ibm.db2.jcc.b.w.a(w.java:34)

at com.ibm.db2.jcc.b.vb.g(vb.java:139)

at com.ibm.db2.jcc.c.fg.n(fg.java:1177)

at com.ibm.db2.jcc.c.fg.a(fg.java:1832)

at com.ibm.db2.jcc.c.fg.a(fg.java:473)

at com.ibm.db2.jcc.c.fg.executeQuery(fg.java:457)

at psdi.mbo.MboSet.getNextRecordData(MboSet.java:2994)

at psdi.mbo.MboSet.fetchMbosActual(MboSet.java:2529)

at psdi.mbo.MboSet.fetchMbos(MboSet.java:2495)

at psdi.mbo.MboSet.getMbo(MboSet.java:1815)

at psdi.webclient.beans.report.ReportRoxListBean.initialize(ReportRoxListBean.java:58)

at psdi.webclient.system.beans.DataBean.getMboSet(DataBean.java:1257)

at psdi.webclient.system.beans.DataBean.getZombie(DataBean.java:2098)

at psdi.webclient.controls.TableCol.initialize(TableC 

Solution

Regenerate the report pages as follows:

Go to --> administration --> reporting- -> report administration --> press enter to display all reports --> then press the generate request pages on the bottom left of the app.

It will take a few minutes to process all the reports, after which the error message will stop appearing.

Problem

In the development system, the user wanted to increase the size of an UPPER 30 type
field across Maximo.

On the development system windows server, the 'field-size-config.xml' file was edited and the
value for an UPPER field was changed from 10 to 15.

The ear file was rebuilt and re-deployed via the WebSphere console.

Once the server was restarted, the user logged in and the changes had taken effect.

The same steps were repeated in an identical pre-production system, although the changes did not appear to have taken place and the field size was the same.

Solution

The cache needs to be cleared from the WebSphere application server;

Stop the Maximo server and delete the files located under the temp folder and restart Maximo;

IBM\WebSphere\AppServer\profiles\CustomXX\temp.

Additionally, if this doesn’t resolve the issue you can also uninstall the ear file, delete the specific ear file folder and re-deploy.

IBM\WebSphere\AppServer\profiles\CustomXX\InstalledApps