IBM Support

Maximo Manage UpdateDB Fails on Script V9100_110 with SQLCODE -433 or SQLCODE -302 (Content Security Policy Truncation on MAXPROPVALUE)

Troubleshooting


Problem

During an upgrade or fix pack deployment of Maximo Manage in IBM Maximo Application Suite (MAS), the UpdateDB utility fails while executing database script V9100_110 (V9100_110.dbc) with a database truncation error (SQLCODE=-433 or SQLCODE=-302, SQLSTATE=22001).

Symptom

UpdateDB Failure Log (run-db.log):

Error running script: V9100_110
rollback
;
Script Update complete: Error
psdi.util.MXSystemException: dbchange#ScriptFailure
at psdi.dbmanage.ScriptRun.run(ScriptRun.java:311)
at psdi.tools.ScriptExecutionInfo.runDbcScriptLastGoodLine(ScriptExecutionInfo.java:529)
at psdi.tools.UpdateDB.main(UpdateDB.java:3695)
Caused by: com.ibm.tivoli.maximo.dbmanage.MXExceptionWithDefault: scriptrun#ColumnNameTooLong;
Attributename value from dbc file is longer than the allowed length for a database column name;
DB2 SQL Error: SQLCODE=-433, SQLSTATE=22001, SQLERRMC=font-src 'self' data: https://1.www.s81c.com *.walkme.com; s, DRIVER=4.35.11
at psdi.dbmanage.statement.SetPropertyStatement.run(SetPropertyStatement.java:160)


Or error:

(DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001 during <update table="MAXPROP"> in UpdateSQLStatement.java:151)in UpdateSQLStatement.java:151)in UpdateSQLStatement.java:151)in UpdateSQLStatement.java:151)in UpdateSQLStatement.java:151)

Cause

The Content Security Policy (CSP) Payload Length Exceeds Column Size:
Script V9100_110.dbc sets default CSP security headers (mxe.sec.header.Content_Security_Policy) for embedded assistance (WalkMe) and digital analytics. The out-of-the-box configuration string is 629 characters long.
In migrated or existing Db2 databases, the database column MAXPROPVALUE.PROPVALUE is defined as VARGRAPHIC(512), while Maximo metadata (MAXATTRIBUTECFG.MAXATTRIBUTE) is defined at 4000. When SetPropertyStatement attempts to write the 629-character string, the Db2 engine enforces the 512-character boundary and triggers SQLCODE -433 / SQLSTATE 22001.

Why the ConfigDB process does not update the length:
Because MAXATTRIBUTECFG.LENGTH (4000) and MAXATTRIBUTE.LENGTH (4000) already match in metadata, configdb sees Delta = 0 and skips generating the required ALTER TABLE DDL statement.

Environment

Product: IBM Maximo Application Suite (MAS) / Maximo Manage
Versions: MAS 9.1.0, 9.1.1, 9.1.24+ Continuous Delivery (CD), MAS 9.2.x
Database Platform: IBM Db2 (Db2 LUW, Db2 Warehouse, Db2u on Red Hat OpenShift)
Operating Environment: Red Hat OpenShift Container Platform (ROKS, ARO, ROSA, On-Premises)

Diagnosing The Problem

Execute the following diagnostic SQL queries in the Db2 database (BLUDB) under schema MAXIMO:

1. Check Db2 column lengths in catalog

SELECT TABNAME, COLNAME, TYPENAME, LENGTH
FROM SYSCAT.COLUMNS
WHERE TABSCHEMA = 'MAXIMO'
AND TABNAME IN ('MAXPROPVALUE', 'MAXPROP')
AND COLNAME IN ('PROPVALUE', 'MAXIMODEFAULT');

2. Check Maximo metadata active and staging dictionary lengths

SELECT OBJECTNAME, ATTRIBUTENAME, LENGTH, MAXTYPE
FROM MAXIMO.MAXATTRIBUTE
WHERE OBJECTNAME IN ('MAXPROPVALUE', 'MAXPROP')
AND ATTRIBUTENAME IN ('PROPVALUE', 'MAXIMODEFAULT');

3. Check user synchronization status distribution

SELECT MASSYNCSTATUS, COUNT(*)
FROM MAXIMO.MAXUSER
GROUP BY MASSYNCSTATUS;

If SYSCAT.COLUMNS shows LENGTH less than what is defined in the MAXATTRIBUTE.MAXPROPVALUE, column enlargement is required.

Resolving The Problem

Enlarge the Db2 Column.
The "Synthetic Delta" ConfigDB Method (Recommended for DBA Policy Compliance)
To force Maximo's automated configdb.sh tool to execute the Database alteration without manual DBA intervention:

1. Create a synthetic delta in the metadata tables by temporarily aligning MAXATTRIBUTE to the database state:

UPDATE MAXIMO.MAXOBJECTCFGSET CHANGED = 'A' WHERE OBJECTNAME = 'MAXPROPVALUE';
UPDATE MAXIMO.MAXATTRIBUTECFG SET CHANGED = 'A' WHERE OBJECTNAME = 'MAXPROPVALUE' AND ATTRIBUTENAME = 'PROPVALUE';
UPDATE MAXIMO.MAXATTRIBUTE SET LENGTH = 512 WHERE OBJECTNAME = 'MAXPROPVALUE' AND ATTRIBUTENAME = 'PROPVALUE';
COMMIT;

2. Run configdb from the manage-maxinst pod terminal

3. Re-trigger the Manage workspace activation or updatedb job. Script V9100_110.dbc will complete successfully.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m3p000000hAeaAAE","label":"Maximo Application Suite-\u003EMAS Applications-\u003EManage"}],"ARM Case Number":"TS023280645","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0;8.0.1;8.1.0;8.10.0;8.11.0;8.2.0;8.3.0;8.4.0;8.5.0;8.6.0;8.7.0;8.8.0;8.9.0;9.0.0;9.1.0;9.2.0;9.3.0"}]

Product Synonym

IBM Maximo Application Suite; MAS; Maximo Application Suite; Maximo Manage; MAS Manage; Maximo Asset Management; MAM

Document Information

Modified date:
12 November 2026

UID

ibm17295557