Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only
Expand all | Collapse all

BMXAA0443E - ERROR -- configdb#CantAddColumn

  • 1.  BMXAA0443E - ERROR -- configdb#CantAddColumn

    Posted Tue November 24, 2020 05:00 AM

    Hi,

    We are getting following errors, when executed the Validation step in Maximo Upgrade from 6.2.8 to 7.1.1.13

    BMXAA0443E - ERROR -- configdb#CantAddColumn Thu Nov 12 05:57:44 ACT 2020

    DOWNTIMEREPORT.SITEID Thu Nov 12 05:57:44 ACT 2020

    BMXAA0443E - ERROR -- configdb#CantAddColumn Thu Nov 12 05:57:44 ACT 2020

    WOACTIVITY.CHANGEBYPARENT Thu Nov 12 05:57:44 ACT 2020

    BMXAA0443E - ERROR -- configdb#CantAddColumn Thu Nov 12 05:57:44 ACT 2020

    WOCHANGE.CHANGEBYPARENT Thu Nov 12 05:57:44 ACT 2020

    BMXAA0443E - ERROR -- configdb#CantAddColumn Thu Nov 12 05:57:44 ACT 2020

    WORELEASE.CHANGEBYPARENT Thu Nov 12 05:57:44 ACT 2020

    BMXAA0443E - ERROR -- configdb#CantAddColumn Thu Nov 12 05:57:44 ACT 2020

    WORKORDER.CHANGEBYPARENT Thu Nov 12 05:57:44 ACT 2020

    Please review the following maxvars value.

    SQL> Select varname, varvalue From maxvars where varname = 'MAXUPG';

    Output>

    VARNAME VARVALUE

    MAXUPG V600-785






    #Maximo
    #SupportMigration
    #Support
    #AssetandFacilitiesManagement


  • 2.  RE: BMXAA0443E - ERROR -- configdb#CantAddColumn

    Posted Wed November 25, 2020 07:56 AM

    check if this attribute already exists. If so you will need to update the MXVARS value for MAXUPG to V600-786 and continue. Verify V600-785 is a dbcc or class. You could perform the action on that scrip manually as an option. But I would suggest that you skip this by updating the MAXVARS and continue.






    #Maximo
    #SupportMigration
    #AssetandFacilitiesManagement
    #Support


  • 3.  RE: BMXAA0443E - ERROR -- configdb#CantAddColumn

    Posted Wed November 25, 2020 08:54 AM

    Hi nivgeo,

    Thanks for the reply.

    Checked attribute does not exists.

    Tried to following steps.

    • Update maxvars set varvalue = 'V600-786' where varname = 'MAXUPG';
    • Executed configdb.bat
    • Executed Validation through upgrade utility and getting the following error in message box.

    "Validation completed with error:

    Not a supported database version: V600-786"

    Then

    • Added below line in VersionSequence.xml file.

    <VERSION versionnum="V600-786 11/1/2008" dir="V600"/>

    • Executed Validation through upgrade utility.

    Still errors are showing in log file as mentioned initially "BMXAA0443E - ERROR -- configdb#CantAddColumn"






    #Maximo
    #SupportMigration
    #AssetandFacilitiesManagement
    #Support