Troubleshooting
Problem
After upgrading Maximo 7.1 to 7.5, if you run Integrity Checker it may report error: BMXAA0443E -- ERROR -- BMXAA0500E -- The Maximo-defined length for this column is invalid: ISSUEITEMTOASSET.UNITCOST AMOUNT(10)
Cause
All Maximo AMOUNT column (MaxAttribute.MaxType='AMOUNT') must be defined consistently. The Maximo definition of column ISSUEITEMTOASSET.UNITCOST is incorrect.
Environment
Maximo 7.1 or 7.5 database, upgraded from 6.2. Error is known to occur on Oracle.
Diagnosing The Problem
All Maximo AMOUNT columns must be defined the same. To learn how AMOUNT columns must be defined on your database, run this SQL query:
Select varname, varvalue From maxvars Where varname In ('AMTLENGTH', 'AMTSCALE')
Resolving The Problem
All Maximo AMOUNT columns must be defined according to the results of the above query. The Maximo-defined length of the column should be the same as the value for AMTLENGTH. The Maximo-defined scale of the column should be the same as the value for AMTSCALE. Modify the definition of the column in Maximo tables MaxAttribute and MaxAttributeCfg. For example, if the results of the above query are:
VARNAME VARVALUE
AMTLENGTH 20
AMTSCALE 2
Then to resolve the error, apply these two SQL updates:
Update maxattribute Set length=20, scale=2 Where objectname='ISSUEITEMTOASSET' And attributename='UNITCOST' ;
Update maxattributecfg Set length=20, scale=2 Where objectname='ISSUEITEMTOASSET' And attributename='UNITCOST' ;
Because column ISSUEITEMTOASSET.UNITCOST is defined as nonpersistent, there is no database column that must be altered. After applying the updates, again run Integrity Checker in report mode in order to verify that the error is resolved.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21698592