Error Initialising Cron Tasks After Server Restart

Technote (troubleshooting)


Problem(Abstract)

Errors in the logs when escalations begin to run after a server restart

[ERROR] [SR] BMXAA6350E - Object name CRONTASKPARAM in the dictionary was not found for user MAXADMIN.
[maximo-ESCALATION.ESCPMZHBCONTCOMNODE] [ERROR] [SR]
java.lang.NullPointerException


Note this is for a particular Escalation, but can occur for any Cron Task.

Resolving the problem

In the System Properties Application create a new System Property:

mxe.cronTaskInitDelay

And set it's value to

300

Select the checkbox next to your new property, and select Live Refresh from the tool bar.
The next time the server(s) starts it will take 300 seconds for any Cron Task to start making sure the Data Dictionary cache is fully loaded.

The default value is 60 seconds. See below infocenter for detail on parameter

Related information

Cron task Manager Properties


Cross reference information
Segment Product Component Platform Version Edition
Systems and Asset Management IBM SmartCloud Control Desk
Systems and Asset Management Tivoli Asset Management for IT
Systems and Asset Management Tivoli Change and Configuration Management Database
Systems and Asset Management Tivoli Service Request Manager

Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Maximo Asset Management

Software version:

7.1.1, 7.5

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

1616140

Modified date:

2014-10-02

Translate my page

Machine Translation

Content navigation