Fix BMXAA9394E: Unable to add attributes to an unknown MBO

UpdateDB and other Maximo Database Configuration tools can fail when an object has an incorrectly configured electronic audit table. The log contains an error similar to this:

BMXAA7025E - Script failed while running.
 
BMXAA9394E - Unable to add attributes to unknown Mbo <TableName>. The target
table or view of the add_attributes statement is unknown to Maximo. Correct
the target of the statement or move the script to after when the target Mbo
has been created.

One cause is a stale EAUDITTBNAME value that points to an audit table Maximo no longer recognises. UpdateDB then tries to add the audit attributes to an object that is missing from the active or pending Maximo metadata.

Only use this procedure after confirming that the named object is an obsolete or incorrectly configured audit table. If the audit table is still required, repair its Database Configuration definition instead. Clearing these values disables the link to that audit table.

Check the audit table configuration

Replace YOUR_TABLE with the base Maximo table whose audit configuration is failing, then inspect both the active and pending metadata:

SELECT
  TABLENAME,
  EAUDITTBNAME
FROM
  MAXTABLE
WHERE
  TABLENAME = 'YOUR_TABLE';
 
SELECT
  TABLENAME,
  EAUDITTBNAME
FROM
  MAXTABLECFG
WHERE
  TABLENAME = 'YOUR_TABLE';

Confirm that EAUDITTBNAME contains the unknown audit table reported during database configuration. Also check Database Configuration and your change records before deciding that the audit definition should be removed.

Remove the stale audit table reference

Take a database backup and stop the Maximo application servers and administrative tools that could change metadata. Ask the database administrator to run the following statements against the Maximo schema:

UPDATE
  MAXTABLE
SET
  EAUDITTBNAME = NULL
WHERE
  TABLENAME = 'YOUR_TABLE';
 
UPDATE
  MAXTABLECFG
SET
  EAUDITTBNAME = NULL
WHERE
  TABLENAME = 'YOUR_TABLE';

MAXTABLE contains the active object metadata, while MAXTABLECFG contains the configuration metadata used when applying database changes. Clearing only one can leave the definitions inconsistent and allow the failure to return.

Verify that each statement updated the expected row only, then commit the transaction according to your database tooling and change procedure.

Run Database Configuration again

Run UpdateDB or the Database Configuration operation that originally failed. Review the complete log rather than checking only that BMXAA9394E has disappeared.

After Maximo starts, confirm that:

• Database Configuration no longer identifies the removed audit table for the object.
• The application opens and saves records for the affected object.
• Other configured audit tables still capture the expected changes.
• No pending configuration changes remain unexpectedly.

If BMXAA9394E reports another object, investigate that object separately rather than broadening the UPDATE statements. Multiple stale audit definitions can exist, but each one should be verified before it is removed.