IBMDO YOU?Hi, I'm MBO!

Settings

Make the site feel at home on your screen.

Theme

Loading your theme preference.

Keyboard shortcuts

Open search from anywhere, then move through the results without leaving the keyboard.

Open settings
Ctrl,or⌘,
Open search
CtrlKor⌘K
Select a search result
↑↓
Open the selected result
Enter
Close an open dialog
Esc

I Break Maximo

Fix BMXAA1332E: The interface tables list could not be populated

Configure the interface-table endpoint and diagnose database access when Maximo cannot populate the Create Interface Tables list.

I Beat Maximo — confirmed solution

When you select Create Interface Tables in the External Systems application, Maximo can return:

BMXAA1332E - The interface tables list could not be populated.
Verify that the database where the interface tables are being created is
accessible to the server. See the server logs and error logs for more
information about the underlying exception.

This often happens because the external system does not have an interface-table endpoint. The endpoint tells Maximo which database contains the interface tables and how to connect to it. An enterprise service does not carry those database connection details itself.

Configure the interface-table endpoint

Open Integration > External Systems and select the external system for the enterprise service or publish channel. Set Interface Table End Point to the endpoint for the database in which the tables should be created, then save the external system.

For interface tables in the Maximo application database, the predefined endpoint is normally MXIFACETABLE. A remote interface database needs an IFACETABLE endpoint configured with that database's connection details.

Return to Select Action > Create Interface Tables. The dialog should now list eligible interface tables and allow you to select the endpoint. IBM's interface-table overview confirms that the external-system or publish-channel endpoint identifies the database location. The creation procedure also requires an endpoint when the table is created.

If the error remains

BMXAA1332E is the top-level message. Read the application-server log at the same timestamp for the nested exception before changing anything else. It usually separates the remaining causes into three groups:

  • Connection failure: verify the endpoint URL, driver, port, database name, DNS and network path from the Maximo server or container.
  • Authentication failure: verify the endpoint credentials and confirm that the account can connect from the Maximo runtime environment.
  • Database or schema failure: verify the target schema and the account's permission to inspect and create the required tables.

IBM has documented the same error for SQL Server connection and credential problems, so adding an endpoint is not sufficient when its connection properties are wrong.

Also confirm that the interface definition is eligible to appear in the dialog:

  1. The enterprise service or publish channel is enabled on the selected external system.
  2. Its object structure has Support Flat Structure selected.
  3. Any alias conflicts in the flat object structure are resolved.
  4. An interface-table name has been assigned.

These checks affect which tables appear after Maximo can connect; they do not repair a failed database connection.

Be careful when recreating tables

Do not delete or recreate an existing interface table merely to clear this error. Interface and queue tables can contain unprocessed transactions. Back up the data, account for rows in MXIN_INTER_TRANS and MXOUT_INTER_TRANS, and follow an agreed recovery plan before replacing a table. IBM warns that recreating an interface table without a backup can lose its data.

Once the endpoint connects and the list is populated, create only the intended tables. Then confirm that the inbound or outbound integration uses the same external system and endpoint you just tested.

Find the fix

Search articles

Esc

Search titles, technical terms or error codes.