Hi All,
We applied the Maximo 7613 fix pack on the existing Maximo 7611 version and there were around 5000 integrity checker errors under the below headers. We went ahead with running the update db as we believe most of these get fixed while the updatedb utility does its job. Updatedb only failed on 3 tables- maxmessages , maxpresentation and maxlabel and it completed successfully.
After we brought up the Maximo application on 7613,we were unable to create any new records on PR,PO,Work order application and everywhere we were getting this error
BMXAA4211E - Database error number 2601 has occurred when operating on MULTIASSETLOCCI : MULTI ID=13,349,299. Report the error to the owner of the deployment.
Do we have to mandatorily fix the integrity checker errors and warnings before we run the update db or what could have gone wrong?We didnt use the SQL Server 2019 database which is one of the prerequisities for the Maximo 7613 upgrade and we used the existing 2016 SQL Server database.Could that also be one of the factors?
Warnings
1 BMXAA0442W -- Warning - BMXAA0328E -- The class name in the language code column is not correct: Attribute INVENTORY.LANGCODE Class null
2 BMXAA0442W -- Warning - BMXAA0328E -- The class name in the language code column is not correct: Attribute TEUP6ATTRIBUTES.LANGCODE Class null
3 BMXAA0442W -- Warning - BMXAA0328E -- The class name in the language code column is not correct: Attribute TEUP6MAIN.LANGCODE Class null
4 BMXAA0442W -- Warning - BMXAA0328E -- The class name in the language code column is not correct: Attribute TEURDEPT.LANGCODE Class null
5 BMXAA0442W -- Warning - BMXAA0521W -- All applications should be mapped to a table. The following apps are not mapped.
6 BMXAA0442W -- Warning - BMXAA0519W -- The following autokeys should be removed from the AUTOKEY system table because they are not referenced by a column.
7 "BMXAA0442W -- Warning - BMXAA9564W -- There are security records defined for groups that do not exist. These groups are found in the ApplicationAuth table but are not found in the MaxGroup table.
8 "BMXAA0442W -- Warning - BMXAA9023W -- The following indexes should not be marked as required. Run the Integrity Checker in repair mode.
Custom indexes
9 "BMXAA0442W -- Warning - BMXAA0475W -- The following tables should be removed from the database because they do not exist in the schema:
"
10 BMXAA0442W -- Warning - BMXAA0471W -- No primary key sequence is defined on the table. Review the table and decide if a primary key sequence is required.
11 BMXAA0442W -- Warning - BMXAA0469W -- There was no unique index found for the primary key sequence on the table. Determine whether the table requires an index for the primary key column sequence.
12 "BMXAA0442W -- Warning - BMXAA7726W -- Unique column ID does not have the BIGINT maxtype on the following tables: Wed Apr 30 15:38:22 BST 2025
Custom tables
13 BMXAA0442W -- Warning - BMXAA0498W -- The following columns are defined to be 'same-as', but have different must-be settings. Go to the Database Configuration application and fix the mismatch.
Error
Serial No. Errors--> 5538 Total Errors
1 BMXAA0443E -- Error - BMXAA0456E -- The following users should be removed from the security tables because they are not valid users: groupuser. Data for these users is in the GroupUser table, but there are no parent records in the MaxUser table. To remove these users, run the Integrity Check in repair mode.
2 BMXAA0443E -- Error - BMXAA0465E -- The following indexes are missing from the database. Use the Database Configuration application to remove the index definition. All the custom indexes were missing
4 BMXAA0443E -- Error - BMXAA0538E -- Column ASSET.ASSETNUM is mapped to AutoKey ASSETNUM, but the autokey does not exist.
5 BMXAA0443E -- Error - BMXAA0538E -- Column BUDGETRULE.BUDGETRULENUM is mapped to AutoKey BUDGETRULE, but the autokey does not exist.
6 BMXAA0443E -- Error - BMXAA0538E -- Column LABORVIEW.CONTRACTNUM is mapped to AutoKey CONTRACTNUM, but the autokey does not exist.
13 BMXAA0443E -- Error - BMXAA0538E -- Column PLUSGBYP.WONUM is mapped to AutoKey WORKORDERNUM, but the autokey does not exist.
14 BMXAA0443E -- Error - BMXAA0538E -- Column PLUSGDRL.WONUM is mapped to AutoKey WORKORDERNUM, but the autokey does not exist.
15 BMXAA0443E -- Error - BMXAA0538E -- Column PLUSGIMPROVE.WONUM is mapped to AutoKey WORKORDERNUM, but the autokey does not exist.
16 BMXAA0443E -- Error - BMXAA0538E -- Column PLUSGMOC.WONUM is mapped to AutoKey WORKORDERNUM, but the autokey does not exist.
17 BMXAA0443E -- Error - BMXAA0538E -- Column PLUSGMOCREQUEST.WONUM is mapped to AutoKey WORKORDERNUM, but the autokey does not exist.
18 BMXAA0443E -- Error - BMXAA0538E -- Column PM.PMNUM is mapped to AutoKey PMNUM, but the autokey does not exist.
19 BMXAA0443E -- Error - BMXAA0538E -- Column PO.PONUM is mapped to AutoKey PONUM, but the autokey does not exist.
20 BMXAA0443E -- Error - BMXAA0538E -- Column PR.PRNUM is mapped to AutoKey PRNUM, but the autokey does not exist.
21 BMXAA0443E -- Error - BMXAA0538E -- Column PURCHVIEW.CONTRACTNUM is mapped to AutoKey CONTRACTNUM, but the autokey does not exist.
22 BMXAA0443E -- Error - BMXAA0538E -- Column RESOURCELEVELS.RESOURCELEVELSNUM is mapped to AutoKey RESOURCELEVELS, but the autokey does not exist.
24 BMXAA0443E -- Error - BMXAA0538E -- Column SFWVIEW.CONTRACTNUM is mapped to AutoKey CONTRACTNUM, but the autokey does not exist.
25 BMXAA0443E -- Error - BMXAA0538E -- Column TEUDEVIATION.WONUM is mapped to AutoKey WORKORDERNUM, but the autokey does not exist.
26 BMXAA0443E -- Error - BMXAA0538E -- Column TOOLINV.ITEMNUM3 is mapped to AutoKey ITEMNUM, but the autokey does not exist.
27 BMXAA0443E -- Error - BMXAA0538E -- Column WARRANTYVIEW.CONTRACTNUM is mapped to AutoKey CONTRACTNUM, but the autokey does not exist.
28 BMXAA0443E -- Error - BMXAA0538E -- Column WMASSIGNMENT.WONUM is mapped to AutoKey WORKORDERNUM, but the autokey does not exist.
30 BMXAA0443E -- Error - BMXAA0538E -- Column WOCHANGE.WONUM is mapped to AutoKey WORKORDERNUM, but the autokey does not exist.
31 BMXAA0443E -- Error - BMXAA0538E -- Column WORELEASE.WONUM is mapped to AutoKey WORKORDERNUM, but the autokey does not exist.
32 BMXAA0443E -- Error - BMXAA0538E -- Column WORKORDER.WONUM is mapped to AutoKey WORKORDERNUM, but the autokey does not exist.
33 BMXAA0443E -- Error - BMXAA0538E -- Column ITEM.ITEMNUM is mapped to AutoKey ITEMNUM, but the autokey does not exist.
34 BMXAA0443E -- Error - BMXAA0538E -- Column SERVICEITEMS.ITEMNUM is mapped to AutoKey ITEMNUM, but the autokey does not exist.
35 BMXAA0443E -- Error - BMXAA0538E -- Column TOOLITEM.ITEMNUM is mapped to AutoKey ITEMNUM, but the autokey does not exist.
36 BMXAA0443E -- Error - BMXAA0496E -- This column is defined to be the 'same-as' a column that does not exist. Run the Integrity Checker in repair mode.
37 BMXAA0443E -- Error - BMXAA0513E -- This column is both a root column and is same-as linked to another column. Use the Database Configuration application to change the same-as child of the column so the same-as parent of the child equals this same-as parent of the column.
38 BMXAA0443E -- Error - BMXAA6292E -- Records exist in the Wogen table which need be deleted. Run repair mode to delete records from the table.
39 BMXAA0443E -- Error - BMXAA0497E -- The following columns are defined to be 'same-as', but have different definitions:
40 BMXAA0443E -- Error - BMXAA0537E -- maxattribute definition differs from maxattributecfg for IOTRESTENDPOINTS.READINGDATETAGNAME. maxattribute.DEFAULTVALUE has "NA" while maxattributecfg.DEFAULTVALUE has "null". Use the Database Configuration application to correct the configuration metadata.
41 5499 same error we have BMXAA0443E -- Error - BMXAA0494E -- The definition of this column does not match the actual column. The native column definition does not match the servers metadata. Run the Integrity Checker in repair mode.