MySQL Forums
Forum List  »  InnoDB

Re: ibdata1 Recover Help
Posted by: Etienne Douglas
Date: August 01, 2013 08:34PM

Error message from the event viewer:

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 8/1/2013
Time: 7:23:54 PM
User: N/A
Computer: STRATUS
Description:
Faulting application mysqld.exe, version 0.0.0.0, faulting module mysqld.exe, version 0.0.0.0, fault address 0x001f5d20.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6d 79 73 ure mys
0018: 71 6c 64 2e 65 78 65 20 qld.exe
0020: 30 2e 30 2e 30 2e 30 20 0.0.0.0
0028: 69 6e 20 6d 79 73 71 6c in mysql
0030: 64 2e 65 78 65 20 30 2e d.exe 0.
0038: 30 2e 30 2e 30 20 61 74 0.0.0 at
0040: 20 6f 66 66 73 65 74 20 offset
0048: 30 30 31 66 35 64 32 30 001f5d20

From MySQL hostname.err file:

130801 19:29:40 [Note] Plugin 'FEDERATED' is disabled.
130801 19:29:40 InnoDB: Initializing buffer pool, size = 8.0M
130801 19:29:40 InnoDB: Completed initialization of buffer pool
InnoDB: Page directory corruption: infimum not pointed to
130801 19:29:40 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex

asc

;InnoDB: End of page dump
130801 19:29:41 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
InnoDB: Page directory corruption: supremum not pointed to
130801 19:29:41 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex

asc

;InnoDB: End of page dump
130801 19:29:42 InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
130801 19:29:42InnoDB: Error: trying to access a stray pointer 81B9FFF8
InnoDB: buf pool start is at 01B84000, end at 02384000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery, see
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: how to force recovery.
130801 19:29:42 InnoDB: Assertion failure in thread 7976 in file G:\mysql-5.1.70-winbuild\mysql-community-nt-5.1.70-build\storage\innobase\include\buf0buf.ic line 264
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.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.

One thing I noticed was this line. I don't have a G drive.

"G:\mysql-5.1.70-winbuild\mysql-community-nt-5.1.70-build\storage\innobase\include\buf0buf.ic line 264"

Options: ReplyQuote


Subject
Views
Written By
Posted
2864
July 31, 2013 10:28PM
1155
August 01, 2013 09:18AM
Re: ibdata1 Recover Help
3622
August 01, 2013 08:34PM
2038
August 01, 2013 08:50PM
1690
August 06, 2013 02:39PM
1405
August 06, 2013 03:01PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.