How do I add an attribute, object, index or relationship in Maximo Database Configuration, and what does Persistent mean?

A persistent attribute has a column in the database. A non-persistent attribute exists only in the business object, and code must fill it. In our lab, even a non-persistent attribute needed Admin Mode to apply.

Versions: On Maximo Application Suite 9.1 we confirmed, read-only, that the same Database Configuration fields and all 16 messages below are present with the same text (17 November 2026). The behaviour described here was tested in our lab on Maximo 7.6.1.0 (3 and 4 November 2026: a new object, attributes, an index and a relationship were made, applied and removed); we have not re-run the behaviour test on Maximo Application Suite 9.1.

IBM’s page: IBM’s current Maximo Manage documentation says: “If the attribute is a persistent attribute, it is also required on the database” and “You must configure the database for your changes to take effect.”

Last checked: 17 November 2026

How it works

ItemPersistentNon-persistentNeeds Apply Configuration Changes?
AttributeHas a database columnNo column; a class or script fills itYes, both. A new non-persistent attribute is also a structural change (lab: BMXAA0578E with Admin Mode off).
ObjectHas a tableNo table (dialog objects, for example)Yes
IndexOnly on persistent tables (BMXAA0670E)–Yes, structural
Relationship––No. Saved and live at once.

When you create a new object, Maximo fills in the entity, unique ID column and trigger root when you leave the name field, and adds an ID attribute, DESCRIPTION, its long description (non-persistent) and HASLD for you. After the apply, the database had a primary key index and a sequence for the ID column that we did not create ourselves.

Rules that Maximo checks when you save (message codes from the lab system):

MessageRule
BMXAA0587EA persistent attribute cannot be LONGALN.
BMXAA0688E / BMXAA0687EA persistent attribute needs an entity and a column name; a persistent object needs an entity name.
BMXAA0585E / BMXAA0586EAn organisation-level object needs a persistent ORGID; a site-level object needs SITEID.
BMXAA0604EPersistent attributes cannot be added to an imported object.
BMXAA0611EOnly user-defined objects and attributes can be deleted.
BMXAA0615E / BMXAA0660EAn attribute cannot be made required while empty values exist and there is no default.
BMXAA0602E / 0655E / 0656EA length or scale cannot be shortened below the data already stored.
BMXAA0643EIndexes can be added and deleted, not changed.

What we observed in our lab: a new non-persistent attribute still needs Admin Mode and Apply Configuration Changes, although no column is made. A new relationship needs neither: it is live as soon as you save. And an index we asked to be unique was stored as “duplicates allowed”, so check the Unique Rule on screen before you apply.

Steps

  1. Database Configuration > New Object: enter the object name and description. Leave the field: Entity, Unique Column and Trigger Root fill in. Save. The status is “To Be Added”.
  2. Attributes tab > New Row: attribute, title, type, length. For a non-persistent attribute, clear Persistent? (the column name empties). Save.
  3. Indexes tab > New Row: index name, Unique Rule, then the columns in sequence from 1.
  4. Relationships tab > New Row: relationship name, child object, where clause. Save. It works at once.
  5. Turn on Admin Mode and run Apply Configuration Changes. This includes a new non-persistent attribute.
  6. The new field appears on a screen only after you add it in Application Designer.

Where it breaks

How we checked it

On a Maximo 7.6.1.0 lab system we created a test object in Database Configuration, then added a persistent and two non-persistent attributes, an index and a relationship, and applied the change in Admin Mode. We read the result from the Maximo configuration tables and from the database catalogue. The message rules come from the system’s own message table. On Maximo Application Suite 9.1 we read the same fields and messages; we did not change anything there. Everything we made was given a test marker and removed afterwards; we checked with read-only queries that nothing was left behind.

This page is part of our Maximo knowledge pages: answers we have checked on a real Maximo system in our lab. For questions about your own Maximo data, see Interpretos for Maximo.