Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 

What errors indicate potential database corruption?

Errors

In some cases, database corruption can result in java errors, deadlocks, sporadic Controller shutdowns, and Controller inaccessibility. Below is a list of errors that may indicate database corruption. If you encounter one of them or other issues that you think could indicate corruption, please contact AppDynamics Support so we can assist you.

 

Error 1:

InnoDB: cannot calculate statistics for table controller/<table_or_partition_name>
InnoDB: because the .ibd file is missing. For help, please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
180302 17:40:45 [ERROR] MySQL is trying to open a table handle but the .ibd file for table controller/<table_or_partition_name> does not exist.​
Have you deleted the .ibd file from the database directory under
the MySQL datadir, or have you used DISCARD TABLESPACE?
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

 

Error 2:

InnoDB: Error: page <page_number> log sequence number <log_sequence_number>
InnoDB: is in the future! Current system log sequence number <log_sequence_number>.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.

 

Error 3:

[ERROR] mysqld.exe: Incorrect key file for table 'sql.MYI'; try to repair it
[ERROR] Got an error from unknown thread, ..\..\..\mysqlcom-pro-5.5.40\storage\myisam\mi_write.c:<line_number>
InnoDB: Error: tablespace id is <tablespace_id> in the data dictionary
InnoDB: but in file <file_name>.ibd it is <tablespace_id>!
InnoDB: Assertion failure in thread <thread_id> in file fil0fil.c line <line_number>
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.

 

Error 4:

InnoDB: Assertion failure in thread <thread_id> in file mtr0log.c line <line_number> 
InnoDB: Failing assertion: DATA_ROLL_PTR_LEN == dict_index_get_nth_col(ind, DATA_ROLL_PTR - 1 + n_uniq)->len
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.

 

Error 5:

InnoDB: Error: trying to access page number <page_number> in space <space_id>, 
InnoDB: space name <ibd_file_name>,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset <offset>, len <length>, i/o type <type_number>.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.

 

Prepare to contact Support

It is important that you do not attempt to fix database corruption without hands-on assistance from our Support team. If you notice one of the errors above, please contact Support and prepare the following information:

 

  1. Logs files:
    1. Please share all the platform log files: Platform Log Files
    2. If the Controller version is older than 4.4, provide Controller log files: Controller Log Files
    3. If you have an HA installation, provide HA log files from both primary and secondary servers: HA Log Files
  2. Is the Controller server on a physical machine or a virtual machine? If on a virtual machine, is the RAM fully reserved? If so, please share the screenshot of memory reservation: Fully Reserved RAM
  3. What is the Controller profile and does the hardware meet the system requirements: System Requirements
  4. If your Controller is on Linux, provide the /var/log/messages file for the date of the database crash and the event viewer logs for the MySQL service.
  5. Information about series of events like a Controller migration, Controller restart or a server reboot that happened before the database corruption.
Version history
Revision #:
6 of 6
Last update:
‎09-14-2018 01:10 PM
Updated by:
 
Labels (1)
0 Kudos