IBM Support

IJ45640: 7.6.1.2 UPDATEDB FAILING AT DB SCRIPT V7612_211 WHILE UPGRADING TO 7.6.1.3

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Updatedb failing at DB script V7612_211, below error can se
    seen:
    
    
    alter table a_maxuser alter column esigpass varbinary (50) null
    ;
    
    // Failed.
    
    create table zxa_maxuser (
    	databaseuserid varchar (18),
    	defsite varchar (8),
    	defstoreroom varchar (25),
    	failedlogins integer,
    	forceexpiration smallint,
    	loginid varchar (50),
    	maxuserid bigint,
    	memo varchar (256),
    	password varbinary (128),
    	personid varchar (30),
    	pwexpiration datetime,
    	pwhintanswer varbinary (2000),
    	pwhintquestion varchar (25),
    	querywithsite smallint,
    	screenreader smallint,
    	status varchar (12),
    	storeroomsite varchar (8),
    	sysuser smallint,
    	type varchar (30),
    	userid varchar (30),
    	eauditusername varchar (30),
    	eaudittimestamp datetime,
    	eaudittype varchar (1),
    	eaudittransid varchar (40),
    	esigtransid varchar (40),
    	inactivesites smallint,
    	defaultrepfacsiteid varchar (8),
    	defaultrepfac varchar (25),
    	isconsultant smallint,
    	sidenav integer,
    	ibmid varchar (100),
    	licmetrictype varchar (20),
    	integuser smallint,
    	esigpass varbinary (50),
    	rowstamp timestamp
    ) on 'PRIMARY'
    ;
    
    // Success.
    
    insert into zxa_maxuser (databaseuserid, defsite, defstoreroom,
    failedlogins, forceexpiration, loginid, maxuserid, memo,
    password, personid, pwexpiration, pwhintanswer, pwhintquestion,
    querywithsite, screenreader, status, storeroomsite, sysuser,
    type, userid, eauditusername, eaudittimestamp, eaudittype,
    eaudittransid, esigtransid, inactivesites, defaultrepfacsiteid,
    defaultrepfac, isconsultant, sidenav, ibmid, licmetrictype,
    integuser, esigpass) select databaseuserid, defsite,
    defstoreroom, failedlogins, forceexpiration, loginid, maxuserid,
    memo, password, personid, pwexpiration, pwhintanswer,
    pwhintquestion, querywithsite, screenreader, status,
    storeroomsite, sysuser, type, userid, eauditusername,
    eaudittimestamp, eaudittype, eaudittransid, esigtransid,
    inactivesites, defaultrepfacsiteid, defaultrepfac, isconsultant,
    sidenav, ibmid, licmetrictype, integuser, esigpass from
    a_maxuser
    ;
    
    // Failed.
    
    ERROR: BMXAA7025E -- Script failed while running.;
    Implicit conversion from data type varchar to varbinary is not
    allowed. Use the CONVERT function to run this query.
    	at psdi.dbmanage.ScriptRun(ScriptRun.java: 272)
    	at psdi.tools.ScriptExecutionInfo(ScriptExecutionInfo.java:
    514)
    	at psdi.tools.ScriptExecutionInfo(ScriptExecutionInfo.java:
    361)
    	at psdi.tools.ScriptExecutionInfo(ScriptExecutionInfo.java:
    313)
    	at psdi.tools.RunScripts(RunScripts.java: 160)
    	at psdi.tools.UpdateDB(UpdateDB.java: 3008)
    	at psdi.tools.UpdateDB(UpdateDB.java: 2925)
    	at psdi.tools.UpdateDB(UpdateDB.java: 2333)
    	at psdi.tools.UpdateDB(UpdateDB.java: 5883)
    	at psdi.tools.UpdateDB(UpdateDB.java: 320)
    	at psdi.tools.UpdateDB(UpdateDB.java: 3443)
    Caused by: Implicit conversion from data type varchar to
    varbinary is not allowed. Use the CONVERT function to run this
    query.
    	at psdi.dbmanage.connection.DatabaseConnection(DatabaseConnect
    ion.java:623)
    	at psdi.dbmanage.connection.DatabaseConnection(DatabaseConnect
    ion.java:567)
    	at psdi.dbmanage.statement.TempTableModel(TempTableModel.java:
    430)
    	at psdi.dbmanage.statement.TempTableModel(TempTableModel.java:
    470)
    	at psdi.dbmanage.connection.DatabaseConnection(DatabaseConnect
    ion.java:1483)
    	at psdi.dbmanage.statement.MaximoMboModel(MaximoMboModel.java:
    605)
    	at psdi.dbmanage.statement.MaximoMboModel(MaximoMboModel.java:
    416)
    	at psdi.dbmanage.statement.AddAttributesStatement(AddAttribute
    sStatement.java:88)
    	at psdi.dbmanage.statement.MaximoMboModel(MaximoMboModel.java:
    694)
    	at psdi.dbmanage.statement.MaximoMboModel(MaximoMboModel.java:
    416)
    	at psdi.dbmanage.statement.AddAttributesStatement(AddAttribute
    sStatement.java:88)
    	at psdi.dbmanage.statement.Script(Script.java: 332)
    	at psdi.dbmanage.statement.Script(Script.java: 313)
    	at psdi.dbmanage.ScriptRun(ScriptRun.java: 266)
    	at psdi.tools.ScriptExecutionInfo(ScriptExecutionInfo.java:
    514)
    	... 9 more
    
    
    Reported on Version:
    Maximo 7.6.1.2
    

Local fix

  • Disable ESIGENABLED and eauditenabled, then run updatedb. Later
    enable them back again.
    
    update sigoption set ESIGENABLED =0 WHERE app = 'USER' and
    ESIGENABLED =1;
    update maxobject set where eauditenabled=0 objectname ='MAXUSER'
    and eauditenabled=1;
    update maxobjectcfg set where eauditenabled=0 objectname
    ='MAXUSER' and eauditenabled=1;
    update maxattribute set where eauditenabled=0 objectname
    ='MAXUSER' and eauditenabled=1;
    update maxattributecfg set where eauditenabled=0 objectname
    ='MAXUSER' and eauditenabled=1;
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo users upgrading from a version less than 7.6.1.2      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * UPDATEDB FAILING AT DB SCRIPT V7612_211 WHILE UPGRADING TO   *
    * 7.6.1.3                                                      *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR will be contained in a future release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ45640

  • Reported component name

    MAXIMO SYSTEMS

  • Reported component ID

    5724R46AV

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-02-28

  • Closed date

    2024-05-02

  • Last modified date

    2024-05-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    MAXIMO SYSTEMS

  • Fixed component ID

    5724R46AV

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
03 May 2024