AppD Archive

Issues APPDYNAMIC ( InnoDB: Error: tablespace id is 819019 in the data dictionary /

CommunityUser
Splunk Employee
Splunk Employee

We have some problems with appdynamics, as the logs are errors related to the Product Database.

        Below are the errors found, and I would appreciate your support in solving the problems.


        Error 01 -
        170111 22:38:04 [Note] C:\AppDynamics\Controller\db\bin\mysqld.exe: ready for connections.
        Version: '5.5.46-enterprise-commercial-advanced-log' socket: '' port: 3388 MySQL Enterprise Server - Advanced Edition (Commercial)
        InnoDB: Error: tablespace id is 819019 in the data dictionary
        InnoDB: but in file .\controller\metricdata_ten_min#p#part205048#sp#part205048sp0.ibd it is 829506!
        170111 22:40:17 InnoDB: Assertion failure in thread 22464 in file fil0fil.c line 768
        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 02 -
        170111 22:32:49  InnoDB: cannot calculate statistics for table controller/requestdata_summary#p#part409607
        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
        170111 22:32:49 [ERROR] MySQL is trying to open a table handle but the .ibd file for table controller/requestdata_summary#p#part409607 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.htmlhow you can resolve the problem.


        Error 03 -
        170111 23:24:52  InnoDB: Error: table 'controller/eventdata_affected#p#part410194'
        InnoDB: in InnoDB data dictionary has tablespace id 834298,
        InnoDB: but a tablespace with that id does not exist. There is
        InnoDB: a tablespace of name .\controller\eventdata_affected#p#part410194.ibd and id 881526, though. Have
        InnoDB: you deleted or moved .ibd files?
        InnoDB: Please refer to
        InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
        InnoDB: for how to resolve the issue.



        Mode Details
        170111 22:38:04 [Note] C:\AppDynamics\Controller\db\bin\mysqld.exe: ready for connections.
        Version: '5.5.46-enterprise-commercial-advanced-log'  socket: ''  port: 3388  MySQL Enterprise Server - Advanced Edition (Commercial)
        InnoDB: Error: tablespace id is 819019 in the data dictionary
        InnoDB: but in file .\controller\metricdata_ten_min#p#part205048#sp#part205048sp0.ibd it is 829506!
        170111 22:40:17  InnoDB: Assertion failure in thread 22464 in file fil0fil.c line 768
        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.
        170111 23:24:33 [Note] Plugin 'FEDERATED' is disabled.
        170111 23:24:33 InnoDB: The InnoDB memory heap is disabled
        170111 23:24:33 InnoDB: Mutexes and rw_locks use Windows interlocked functions
        170111 23:24:33 InnoDB: Compressed tables use zlib 1.2.3
        170111 23:24:33 InnoDB: Initializing buffer pool, size = 6.0G
        170111 23:24:34 InnoDB: Completed initialization of buffer pool
        170111 23:24:34 InnoDB: highest supported file format is Barracuda.
        InnoDB: Log scan progressed past the checkpoint lsn 34866073075
        170111 23:24:34  InnoDB: Database was not shut down normally!
        InnoDB: Starting crash recovery.
        InnoDB: Reading tablespace information from the .ibd files...
        170111 23:24:44 [Note] Plugin 'FEDERATED' is disabled.
        170111 23:24:44 InnoDB: The InnoDB memory heap is disabled
        170111 23:24:44 InnoDB: Mutexes and rw_locks use Windows interlocked functions
        170111 23:24:44 InnoDB: Compressed tables use zlib 1.2.3
        170111 23:24:44 InnoDB: Initializing buffer pool, size = 6.0G
        170111 23:24:44 InnoDB: Completed initialization of buffer pool
        170111 23:24:44 InnoDB: highest supported file format is Barracuda.
        InnoDB: Log scan progressed past the checkpoint lsn 34866073075
        170111 23:24:44  InnoDB: Database was not shut down normally!
        InnoDB: Starting crash recovery.
        InnoDB: Reading tablespace information from the .ibd files...
        InnoDB: Restoring possible half-written data pages from the doublewrite
        InnoDB: buffer...
        InnoDB: Doing recovery: scanned up to log sequence number 34866153163
        170111 23:24:51  InnoDB: Starting an apply batch of log records to the database...
        InnoDB: Progress in percents: 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55                 56 57 58 59 60 61 62 63 64 65 66 67 68 69                 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
        InnoDB: Apply batch completed
        170111 23:24:52  InnoDB: Error: table 'controller/eventdata_affected#p#part410194'
        InnoDB: in InnoDB data dictionary has tablespace id 834298,
        InnoDB: but a tablespace with that id does not exist. There is
        InnoDB: a tablespace of name .\controller\eventdata_affected#p#part410194.ibd and id 881526, though. Have
        InnoDB: you deleted or moved .ibd files?
        InnoDB: Please refer to
        InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
        InnoDB: for how to resolve the issue.

        Product Installed on Windows 2008
        Version - 4.2.0.2


Can you help us, please?

0 Karma

Jean-Baptiste_M
Builder
Hi Leandro,
It looks like your DB is corrupted. You need to contact AppDynamics support
to get help (but if this is really corrupted, I hope you have a backup..).
Help@appdynamics.com or by going to the AppD portal.
Good luck
JB

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...