Revision as of 13:53, 23 February 2022

System Properties

Para detalhes veja artigo IBM Maximo: System Properties

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

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

Reduce CronTask History

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)

Disable unused Crontask

Important: Check if you not use these crontasks before disable it

InstDepreciationCronTask – Asset depreciation calculator
KPICronTask
Old Infolink Crontask - check for error BMXAA1477E on logs

Ver também

@@ Line 21: / Line 21: @@
 = 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
+== Reduce CronTask History ==
+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:
@@ Line 37: / Line 40: @@
-== Disable Crontask ==
+== Disable unused Crontask ==
 '''Important: Check if you not use these crontasks before disable it'''