BMXAA6713E-MBO fetch operation failed in the mboset with the SQL error code 208. Record could not be retrieved from the database

BMXAA6713E-MBO fetch operation failed in the mboset with the SQL error code 208

Symptom

The error above can happen on a Maximo 7.x running on SQL Server and the SQL error 208 happens when you try simple actions like filter by application object description in Security Groups app.

Security Groups --> Everyone --> Applications --> Filter the applications and type in WORKORDER in the MAIN Object box and hit enter. You get the following error:

BMXAA6713E - The MBO fetch operation failed in the mboset with the SQL error code 208. The record could not be retrieved from the database.

See the log file for more details about the error. More information.

In the logs you may see something like this :

[ERROR] [MAXIMO] [CID-UIASYNC-36] BMXAA6714E - The data for the next record in the mboset could not be retrieved for the SQL query select * from maxapps where (exists (select 1 from maximo.maxobject where ((upper (description) like '%WORKORDER%')) and (objectname = maxapps.maintbname))) and (1=1) and (app in ('CONDCODE','DRAWINDEX','ACTIVITY','TZRULE','SETS','PMOOB','SRVCOMMOD','SCHSUPER','MASTERPM','INTSRV','DM','TAGLOCKS','WOTRACKOOB','INTOBJECT','
TOOL','TECHPHONE','SROOB','QUICKREPOO','SCCONFIG','ACTION','BBOARD','FACONFIG','COMPANY','LAUNCH','TKTEMPLATE','OSLCRES','AMCREW','TERMCOND','FO
RGOTPSWD','CUSTAPP','INVUSAGE','MFMAILCFG','VIEWDRFT','RLADMIN','ASSETCAT','POOOB','INTERROR','WFADMIN','RFQ','REPLISTCFG','CONTPURCH','ASSET','LABOROOB','INVENTOR','VIEWSR','ROLE','RECEIPTS','CONTMASTER','INBXCONFIG','PRECAUTN','MOBDATAMAN','SCVNDIFACE','HAZARDS','CREATESROO','KPIGCONFIG','VIEWDR','DEPLCOLLS','INTMSGTRK','INVOICE','INVISSUEOO','WORKVIEW','ESCALATION','AMCREWT','DESIGNER','WOTRACK','KPITPL','IPC','AUTOSCRIPT','SCGLTIFACE','ITEMOOB','KPILCONFIG','SOLUTION','WSREGISTRY','SCTAXMAT','SCFMEA','SHIPREC','CIRCUITS','USER','PM','LOCATION','PO','PERSON','CURRENCY','METER','OSLCPROV','INVOKE','COMMTMPLT','RACEWAYS','CRAFT','SCVOIFACE','CREATEDROO','TOOLINV','JOBPLANOOB','REPORT','MPMAN','PLUSCTMPLT','MOBILEINV','SLA','COGNOSHOME','DOMAINADM','STOREROOM','RECEIPTSOO','COMPANI
ESO','IM','RPTOUTPUT','STARTCNTR','CHRTACCT','QUAL','KPIVIEWER','FAILURE','VIEWSROOB','SECUGRPMOB','INVISSUE','EXCHANGE','EMAILSTNER','CREATEINT','ECOMMADAPT','COLLECTION','PR','INVOICEOOB','SEARCHSOL','JOBPLAN','CRONTASK','SRVAD','RSCONFIG','PERSONGR','CONTLABOR','CONTLEASE','LOCATI_OOB','WORKMAN','VIEWTMPL','QUICKREP','MOBILEINST','ENDPOINT','FMEA','ITEM','TECHTABLET','TECHLITE','SAFEPLAN','RELATION','SELFREG','LOGGING','SRVITEM','MOBERRHND','LABOR','ASSETOOB','CONTWARRTY','LMO','PROPMAINT','ACTIONSCFG','EXTSYSTEM','SECURGROUP','ROUTES','INVENTOROO','KPI','METERGRP','FINCNTRL','RFQOOB','SR','CHANGEPSWD','DEPLGROUPS','CONDEXPMGR','CREATEDR','CREATESR','MULTISITE','COMPMASTER','CALENDR','COND','CONFIGUR','WFDESIGN','LABREP','PUBLISH','CITYPE','MANAGEINT')) order by description OPTION (FAST 1000) . See the log file for more details about the error.
com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'maximo.maxobject'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteCursored(SQLServerStatement.java:1879)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:766)
at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:689)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeQuery(SQLServerStatement.java:616)
at psdi.mbo.MboSet.getNextRecordData(MboSet.java:3186)
at psdi.mbo.MboSet.fetchMbosActual(MboSet.java:2798)
at psdi.mbo.MboSet.fetchMbos(MboSet.java:2755)
at psdi.mbo.MboSet.getMbo(MboSet.java:2002)

If you run the faulty query into SQL without the 'maximo.' before the object name in the SQL Server tool, it works perfectly

Resolving the problem

This could be related with database ownership or a mismatch between the mxe.db.schemaowner / mxe.db.user in the System Properties app and the same info the maximo.properties file.

For example, in your System Properties app in Maximo, you have the following configuration :

mxe.db.schemaowner = dbo
mxe.db.user = maximo

However, in your maximo.properties file, your schema owner is not set to dbo, as in the property below :

mxe.db.schemaowner=maximo


As a solution for this, take these actions :

Please make sure the maximo.properties file is configured with schema owner property set to dbo, then restart both DB and Maximo servers and test.

In maximo.properties file, you should have :

mxe.db.schemaowner=dbo

Ensure there are no other maximo.properties file in the server, as there should not be any duplicates in the server.