Maximo MBO Set and MBO flags from psdi.mbo.MboConstants


NOADD

1

1

NOUPDATE

2

10

NODELETE

4

100

NOSAVE

8

1000

NO_RELATEDMBOS_OF_OWNERSCHILDREN_FETCH

16

10000

READONLY

7

111

DISCARDABLE

32

100000

NOSETVALUE

64

1000000

REQUIRED

128

10000000

HIDDEN

263

100000111

SAMEVALUEVALIDATION

512

1000000000

DBCONFIG

1024

10000000000

GOTCOMPLETEWHERE

2048

100000000000

 

4096

1000000000000

 

8192

10000000000000

 

16384

100000000000000

 

32768

1000000000000000

 

65536

10000000000000000

 

131072

100000000000000000

 

262144

1000000000000000000

SETBYPARENT

524288

10000000000000000000

USER

1048576

100000000000000000000

NOVALIDATION

1

1

NOACCESSCHECK

2

10

DELAYVALIDATIONONLY

4

100

NOACTION

8

1000

NOVALIDATION_AND_NOACTION

9

1001

CHANGEDBY_USER

16

10000

NOOVERWRITE

32

100000

DELAYVALIDATION

36

100100

NOVALIDATION_AND_NOACTION_ALLOWCROSSOVER

64

1000000

NONE

0

0

ALLROWS

10000000

10000000

REBUILD

1

1

NOCOMMIT

2

10

COUNT_DATABASE

1

1

COUNT_ADDITIONS

2

10

COUNT_DELETED

4

100

COUNT_EXISTING

8

1000

COUNT_AFTERSAVE

16

10000

 okay, but why?

Comments

Post a Comment

Popular posts from this blog

BMXAA6713E - The record could not be retrieved from the database. Error

Getting below error in Maximo System Logs [ERROR] [MAXIMO] [] BMXAA6713E - The MBO fetch operation failed in the mboset with the SQL error code 17006. The record could not be retrieved from the database. See the log file for more details about the error. java.sql.SQLException : Invalid column name at oracle.jdbc.driver.OracleStatement.getColumnIndexPrimitive(OracleStatement.java : 3810 ) at oracle.jdbc.driver.OracleStatement.getColumnIndex(OracleStatement.java : 3777 ) at oracle.jdbc.driver.InsensitiveScrollableResultSet.findColumn(InsensitiveScrollableResultSet.java : 268 ) at oracle.jdbc.driver.GeneratedResultSet.getObject(GeneratedResultSet.java : 570 ) at psdi.mbo.MboSet.getNextRecordData(MboSet.java : 3457 ) at psdi.mbo.MboSet.fetchMbosActual(MboSet.java : 2941 ) at psdi.mbo.MboSet.fetchMbos(MboSet.java : 2898 ) at psdi.mbo.MboSet.getMbo(MboSet.java : 2114 ) at psdi.app.common.purchasing.FldPurContractRefNum.validate(FldPurContractRefNum.java : 86 ) at psdi.mbo.MboVa...
Read more

Rebuilding Maximo Text Indexes due to Query performance issues

Image
Sometimes it is necessary to rebuild text indexes after database move or copy from Prod to other instances. IBM does have an article for Rebuilding Oracle Text Indexes . Basically this process drops all the domain indexes and recreates them.  These are the steps are just walkthrough with the same process in detail. 1. Follow the steps in the above article to remove any DBMS jobs Remove any occurrences of DBMS_JOB Determine how many DBMS_JOBS are running by executing this from SQLPLUS logged in as the schema owner: select job, substr(what,1,80) from user_jobs; For each result where "what" contains maximo_ts_job, execute the following commands: begin dbms_job.remove(####); commit; end; / Substituting one of the job numbers from the select for the ####. 2. Change the job  Change to use DBMS_SCHEDULER Recreate the job submission procedure and run it: CREATE OR REPLACE PROCEDURE maximo_ts_job_call AS BEGIN   dbms_scheduler.create_job(   job_name => 'MAXIMOTSSYNC', ...
Read more

List of things checked by Maximo Integrity checker

Maximo Integrity checker is a pretty useful tool to identify issues in Maximo database  Below are some of the things checked by integrity checker and the sample errors returned. 1. Extra tables in database which are not part of Maximo BMXAA0442W -- Warning - BMXAA0475W -- The following tables should be removed from the database because they do not exist in the schema: Sun May 30 12:08:47 GST 2021    APPLICATIONAUTH_BKP    DOCLINKS_POBKP    ABC_MIGR_TEST 2. Missing Indexes BMXAA0443E -- Error - BMXAA0465E -- The following indexes are missing from the database. Use the Database Configuration application to remove the index definition. 3. Missing user groups, invalid users etc BMXAA0455E -- The following users should be removed because they are not authorized. To correct this error, run the Integrity Checker in repair mode. BMXAA0458E -- The following user groups were not found in the MAXGROUPS table. Run the Integrity Checker in repair mode. 4. Invalid M...
Read more