Known Issue: A Series of MySQL Errors Appear in the Windows Application Event Logs

Summary:

A series of MySQL errors may appear in the Windows Application Event logs. The events state Native table <table name> has the wrong structure.

An example event is shown below:

Log Name:      Application
      Source:        MySQL
      Date:          10/24/2013 6:25:52 PM
      Event ID:      100
      Task Category: None
      Level:         Error
      Keywords:      Classic
      User:          N/A
      Computer:      PrashantJ-PC
      Description:
      Native table 'performance_schema'.'file_instances' has the wrong structure
      
      For more information, see Help and Support Center at http://www.mysql.com.
      Event Xml:
      <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
        <System>
          <Provider Name="MySQL" />
          <EventID Qualifiers="49152">100</EventID>
          <Level>2</Level>
          <Task>0</Task>
          <Keywords>0x80000000000000</Keywords>
          <TimeCreated SystemTime="2013-10-24T12:55:52.000000000Z" />
          <EventRecordID>47841</EventRecordID>
          <Channel>Application</Channel>
          <Computer>PrashantJ-PC</Computer>
          <Security />
        </System>
        <EventData>
          <Data>Native table 'performance_schema'.'file_instances' has the wrong
      structure
      
      </Data>
        </EventData>
      </Event >
      ----------------------------------------------------------------------
      
      Following are all the messages reported:
      1. Native table 'performance_schema'.'file_instances' has the wrong structure
      
      2. Native table 'performance_schema'.'cond_instances' has the wrong structure
      
      3. Native table 'performance_schema'.'rwlock_instances' has the wrong structure
      
      4. Native table 'performance_schema'.'mutex_instances' has the wrong structure
      
      5. Native table 'performance_schema'.'file_summary_by_instance' has the wrong
      structure
      
      6. Native table 'performance_schema'.'file_summary_by_event_name' has the wrong
      structure
      
      7. Native table performance_schema'.'events_waits_summary_global_by_event_name'
      has the wrong structure
      
      8. Native table 'performance_schema'.'events_waits_summary_by_instance' has the
      wrong structure
      
      9. Native table
      performance_schema'.'events_waits_summary_by_thread_by_event_name' has the
      wrong structure
      
      10. Native table 'performance_schema'.'threads' has the wrong structure
      
      11. Native table 'performance_schema'.'performance_timers' has the wrong
      structure
      
      12. Native table 'performance_schema'.'setup_timers' has the wrong structure
      
      13. Native table 'performance_schema'.'setup_instruments' has the wrong
      structure
      
      14. Native table 'performance_schema'.'setup_consumers' has the wrong structure
      
      15. Native table 'performance_schema'.'events_waits_history_long' has the wrong
      structure
      
      16. Native table 'performance_schema'.'events_waits_history' has the wrong
      structure
      
      17. Native table 'performance_schema'.'events_waits_current' has the wrong
      structure
      

This article applies to:

Solution:

These events are completely harmless and can be ignored.

Related Articles: