A while back I asked why, after I upgraded our OTRS install from version 1.2.3 to 2.2.6, I was getting response times in the 1 minute, 20 second range. Most of the responses I got back were about optimizing my MySQL install using the tuning-primer.sh script. I am grateful for those responses and did indeed use the script to help optimize my MySQL database install.

Unfortunately, this did not resolve my response time issue. I finally checked my logs (something I should have done in the first place) and I found the following error message:

[Wed Jul 23 09:54:25 2008][Error][Kernel::System::CalendarEvent::Events][686] Table 'otrs
.calendar_event' doesn't exist, SQL: 'SELECT e.id, e.sequence_type, e.title, e.content, e
.start_time, e.end_time, e.event_status FROM calendar_event e , calendar_event_involved
ei WHERE ((e.start_time >= '2008-7-30 00:00:00' AND e.sequence_end_time <= '2008-7-30
23:59:59') OR (e.start_time >= '2008-7-30 00:00:00' AND e.start_time <= '2008-7-30 23:5
9:59') OR (e.sequence_end_time >= '2008-7-30 00:00:00' AND e.sequence_end_time <= '2008
-7-30 23:59:59') OR (e.start_time <= '2008-7-30 00:00:00' AND e.sequence_end_time >= '2
008-7-30 23:59:59')) AND e.id = ei.event_id AND ei.user_id IN (48) ORDER BY e.start_time'

This message occurs exactly 16 times whenever I try to log in or view my ticket queue. Neither the OTRS 1.2.3 nor the OTRS 2.2.6 database has a calendar_event table so I don't know why OTRS is looking for one. I'm thinking this is what is causing my response time issues.

Should I create a dummy calendar_event table in MySQL database or is there a way to remove some entry that is making OTRS look for this table? I would be grateful for any and all advice on this issue.