| Bug #816 | MySQL Server shuts down abnormally | ||
|---|---|---|---|
| Submitted: | 8 Jul 2003 22:08 | Modified: | 11 Feb 2004 6:53 |
| Reporter: | mirunalini sethuraman | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server | Severity: | S1 (Critical) |
| Version: | 4.0.13 | OS: | Windows (Win 95) |
| Assigned to: | CPU Architecture: | Any | |
[8 Jul 2003 22:08]
mirunalini sethuraman
[9 Jul 2003 1:13]
Heikki Tuuri
Hi! You are not running 4.0.13, because there is no assertion in that on line 519 of row0ins.c. Please upgrade to 4.0.13 and post here the full .err log from a crash. Do not cut or omit anything. Your table is only 14 000 rows. InnoDB should delete without problems millions of rows. Regards, Heikki
[9 Jul 2003 1:26]
Heikki Tuuri
Hi! Also show your my.cnf and the table CREATE statement. What row causes the crash? Regards, Heikki
[10 Jul 2003 10:24]
mirunalini sethuraman
that was the error message i got in 3.23.47 version. i got exactly the same message in 4.0.13. but those messages wasn't available in .err file in data folder. and also after i got the error i was not able to start the server(though i start it shut down & PC hangs) then i reinstalled.
[10 Jul 2003 10:33]
mirunalini sethuraman
my.cnf content [WinMySQLAdmin] Server=C:/mysql/bin/mysqld.exe user=admin password=admin [mysqld] basedir=C:/mysql datadir=C:/mysql/data port=3306 innodb_data_file_path = ibdata1:50M;ibdata2:50M:autoextend innodb_data_home_dir = c:/mysql/ibdata innodb_log_group_home_dir = c:/mysql/iblogs innodb_log_arch_dir = c:/mysql/iblogs set-variable = innodb_mirrored_log_groups=1 set-variable = innodb_log_files_in_group=3 set-variable = innodb_log_file_size=20M set-variable = innodb_log_buffer_size=8M innodb_flush_log_at_trx_commit=1 innodb_log_archive=0 set-variable = innodb_buffer_pool_size=70M set-variable = innodb_additional_mem_pool_size=10M set-variable = innodb_file_io_threads=4 set-variable = innodb_lock_wait_timeout=50
[23 Jul 2003 9:42]
MySQL Verification Team
I would like to do a test about your case, could you please send me at least your table structure ? (mysqldump.exe does the service). I would prefer if possible with data also. You can put it into a zipped file and upload it at: ftp://support.mysql.com/pub/mysql/secret/ the name of the file should have a reference for this bug report number e.g: dump-table-bug816.zip Thanks you in advance.
[23 Jul 2003 10:05]
Heikki Tuuri
Hi!
The failing assertion is this in foreign key checks:
/* Scan index records and check if there is a matching record */
for (;;) {
rec = btr_pcur_get_rec(&pcur);
if (rec == page_get_infimum_rec(buf_frame_align(rec))) {
goto next_rec;
}
if (rec == page_get_supremum_rec(buf_frame_align(rec))) {
err = row_ins_set_shared_rec_lock(LOCK_ORDINARY, rec,
check_index, thr);
if (err != DB_SUCCESS) {
break;
}
goto next_rec;
}
cmp = cmp_dtuple_rec(entry, rec);
...
if (cmp < 0) {
err = row_ins_set_shared_rec_lock(LOCK_GAP,
rec, check_index, thr);
if (err != DB_SUCCESS) {
break;
}
if (check_ref) {
err = DB_NO_REFERENCED_ROW;
row_ins_foreign_report_add_err(
thr, foreign, rec, entry);
} else {
err = DB_SUCCESS;
}
break;
}
ut_a(cmp == 0);
The assertion can fail if records are in a wrong order in the index, that is, the table is corrupt.
What is the table CREATE statement and what are the CREATE statements for the tables associated with this through foreign key constraints? What does CHECK TABLE say about these tables?
If you dump the tables and reimport them to 4.0.14, do you still get the assertion?
Regards,
Heikki
[26 Jul 2003 2:03]
mirunalini sethuraman
SCRIPT IS FOR CREATING THE WHOLE DB.THE TABLE ACTUALLY TO BE CHECKED IS 'trnlbtdtls'
Attachment: DB_SCRIPT-BUG816.txt (text/plain), 35.07 KiB.
[11 Feb 2004 6:53]
Heikki Tuuri
Hi! Changing the status to 'no feedback'. There have not been similar assertion failure reports since this report. Regards, Heikki
