Since the update of osTicket to version 1.9.5.1, we get a DB Error 1142 message when a ticket is edited (see error message below). It indicates that table "_ticket__cdata" could not be dropped. We run osTicket version 1.9.11 on another test server and there, we see the same message when a new ticket is created via the agent API and when a new ticket is edited. However, the modifications are done for the tickets and new tickets are created.From other posts I learned that the "__cdata" table is dropped now and then on purpose in order to "refresh" the table. My questions are:Why do we get this error message now and not with earlier versions of osTicket?Does it cause a problem for the ticket handling or ticket system if the table can not be dropped?Do we really need to grand the right to drop the table to osticket in the DB system in order to avoid the error? I don't like this idea... and we did not grant the right before.Thank you for any explanation and/or suggestion for solving the issue.Error message:

DROP command denied to user 'ooo'@'host' for table 'ooo_ticket__cdata'<br />

<br />

---- Backtrace ----<br />

#0 (root)/include/mysqli.php(177): osTicket->logDBError('DB Error #1142', '[DROP TABLE IF ...')<br />

#1 (root)/include/class.dynamic_forms.php(309): db_query('DROP TABLE IF E...')<br />

#2 (root)/include/class.dynamic_forms.php(335): TicketForm:()<br />

#3 : TicketForm:(Object(DynamicFormEntryAnswer), Array)<br />

#4 (root)/include/class.signal.php(98): call_user_func_array(Array, Array)<br />

#5 (root)/include/class.orm.php(233): Signal:('model.updated', Object(DynamicFormEntryAnswer), Array)<br />

#6 (root)/include/class.dynamic_forms.php(947): VerySimpleModel->save()<br />

#7 (root)/include/class.ticket.php(2166): DynamicFormEntry->save()<br />

#8 (root)/scp/tickets.php(217): Ticket->update(Array, Array)<br />

#9 {main}System setup in attached file.

osTicket_setup.JPG

Does your DB user have DROP permissions?

No, the user has no drop permission.Therefore my third question above, is it really the only way to get it working?Our DB user never had drop permission but we receive the error message only since we updated to version 1.9.5.1.

Older versions didnt have this table and didn't need to drop it from time to time... so I would say if you gave your user drop permissions on your osTicket DB it would resolve that error.

    3 years later

    ntozier

    Hello sir, Can you please tell how to give drop permission to user

      11 days later

      @Akash

      Something like:

      mysql> GRANT DROP ON TABLE `name_of_database`.* TO 'database_user';
mysql> FLUSH PRIVILEGES;

      Cheers.

      Write a Reply...