ich habe OTRS 3.3.x von Windows (mysql,iis, perl) auf OTRS 4 Debian (mysql, apache2, mod_perl) migriert und es ist tausend mal schneller
Nun habe ich aber im Service-Center folgende Fehlermeldung bzw. Warnung.
Jemand eine Idee?Table Storage Engine (acl, acl_sync, article, article_attachment, article_flag, article_plain, article_search, article_sender_type, article_type, auto_response, auto_response_type, customer_company, customer_preferences, customer_user, dynamic_field, dynamic_field_value, faq_attachment, faq_category, faq_category_group, faq_history, faq_item, faq_language, faq_log, faq_state, faq_state_type, faq_voting, follow_up_possible, generic_agent_jobs, gi_debugger_entry, gi_debugger_entry_content, gi_object_lock_state, gi_webservice_config, gi_webservice_config_history, group_customer_user, group_role, group_user, groups, link_object, link_relation, link_state, link_type, mail_account, notification_event, notification_event_item, notifications, package_repository, personal_queues, pm_activity, pm_activity_dialog, pm_entity_sync, pm_process, pm_transition, pm_transition_action, postmaster_filter, process_id, queue, queue_auto_response, queue_preferences, queue_standard_template, role_user, roles, salutation, scheduler_task_list, search_profile, service, service_customer_user, service_preferences, service_sla, sessions, signature, sla, sla_preferences, smime_signer_cert_relations, standard_attachment, standard_template, standard_template_attachment, system_address, system_data, ticket, ticket_flag, ticket_history, ticket_history_type, ticket_index, ticket_lock_index, ticket_lock_type, ticket_loop_protection, ticket_priority, ticket_state, ticket_state_type, ticket_type, ticket_watcher, time_accounting, user_preferences, users, valid, virtual_fs, virtual_fs_db, virtual_fs_preferences, web_upload_cache, xml_storage)
Es wurden Tabellen gefunden, die nicht die Standard-Engine nutzen.