When a record is inserted into a data table
"Mysql-dt.ext .... Memory 0x ?????? It cannot be read or the like"
No logs found, so I modified my. ini and added it to the end.
Log = F:/Program Files/MySQL Server 5.0/logs/log. log
Log-error = F:/Program Files/MySQL Server 5.0/logs/error. log
The error message is displayed, but you still cannot understand it...
- 081212 23:18:28 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...
- 081212 23:18:28 InnoDB: Starting log scan based on checkpoint
- InnoDB: log sequence number 0 407574894.
- InnoDB: Doing recovery: scanned up to log sequence number 0 407574894
- 081212 23:18:28 InnoDB: Started; log sequence number 0 407574894
- 081212 23:18:29 [Note] F:/Program Files/MySQL Server 5.0/bin/mysqld-nt: ready for connections.
- Version: '5. 0.21-community-nt-log' socket: ''port: 3306 MySQL Community Edition (GPL)
- InnoDB: Next record offset is nonsensical 52066 in record at offset 0
- InnoDB: rec address 010C8000, first buffer frame 00F84000
- InnoDB: Buffer Pool high end 01f84000, Buf fix count 2
- 081212 23:18:34 InnoDB: Page dump in ASCII and hex (16384 bytes ):
- Len 16384; hex (00000... 000 of dozens of K) 00000; ASC
The mysqldump full database page does not work. The same error occurs...
