The JITL Job JobSchedulerExistsEventJob uses the wrong database and wrong table for check

Current Situation

The job JobSchedulerExistsEventJob does use a wrong table for the check of existing events.

Desired Behavior

The job JobSchedulerExistsEventJob should use the table REPORTING_CUSTOM_EVENTS for the check of existing events.

Workaround

• You can use the job JobSchedulerCheckEventsJSAdapterClass. This job has more functionallity and already uses the correct table and database. E.g. you are able not only for checking the existing of one event but also you can evaluate conditions like (e1 or e2)
• Download the patch from here
• Unzip the path to $scheduler_home/lib/patches