How to check if the table EJBTIMER_LMGR is part of the EngageOne database structure

According to the IBM documentation, all tables with EJBTIMER_ prefix are created when you start the server if they do not already exist.

There are four main tables (EJBTIMER_TASK, EJBTIMER_TREG, EJBTIMER_LMGR and EJBTIMER_LMPR). By default, they are created outside the EngageOne database, as EJB timer service uses different data source (jdbc/DefaultEJBTimerDataSource) instead of data sources created manually during EngageOne installation process (jdbc/ocm, jdbc/ocm-nonjta).

EJB timer service is not directly referenced anywhere in EngageOne documentation, but disabling the mentioned query can lead to instability of the WebSphere server. As a result, you may experience issues in EngageOne.

According to the IBM documentation, It is possible to disable EJB timer service from administration console. In order to do this, the number of threads used to execute concurrent EJB timer tasks needs to be set to zero. To access the mentioned field, WebSphere administrator should select:

Servers -> Server types -> WebSphere application servers -> <server_name> -> EJB Container Settings -> EJB timer service settings.

After changing the configuration, we recommend you restart the WebSphere application server and examine if everything works accordingly.
UPDATED:  August 3, 2017