IBM Maximo: My Configuration Tips: Difference between revisions

From Wiki
Line 30: Line 30:
| less than 1d  || 1000 || -
| less than 1d  || 1000 || -
|-
|-
| 1d or greater || 100 || history of the last 100 days
| 1d or greater || 100 || history of the last 100 days (3 months)
|-
|-
| 1w || 100 || history of the last 100 weeks
| 1w || 10 || history of the last 10 weeks (3 months)
|}
|}



Revision as of 21:55, 14 February 2022


System Properties

Para detalhes veja artigo IBM Maximo: System Properties

mxe.mbocount=1
mxe.db.logSQLTimeLimit=1000
mxe.crontask.donotrun and mxe.crontask.dorun
mxe.db.closelongrunconn=true
mxe.db.longruntimelimit=60
mxe.db.detectlongrunconninterval=30

Logging

  • Maximo DB Connection watchdog logger (log4j.logger.maximo.dbconnection)=INFO
Define to INFO. Generate this message on logs. BMXAA7084I - The DbConnectionWatchDog class has been trying to close the database connection for:


Crontask & Escalation

Crontask/Escalation can store the task execution times. This feature is enable when mark ‘Keep history’ checkbox in crontask. This information is recorded in CRONTASKHISTORY table

I use the following table to define history records and reduce the size of CRONTASKHISTORY table:

Schedule History Records Description
less than 1d 1000 -
1d or greater 100 history of the last 100 days (3 months)
1w 10 history of the last 10 weeks (3 months)

Ver também