Re: innodb database crash

2006-05-30 Thread Heikki Tuuri

Vitaliy,

- Original Message - 
From: Vitaliy Okulov [EMAIL PROTECTED]

Newsgroups: mailing.database.myodbc
Sent: Friday, May 26, 2006 5:28 PM
Subject: innodb database crash



Hi all. I have some InooDB mysql crush logs, can somebody explain what
they mean?

Quote:
060525 18:09:43 InnoDB: Error: trying to declare trx to enter InnoDB, but
InnoDB: it already is declared.
TRANSACTION 0 550042370, ACTIVE 0 sec, process no 27054, OS thread id 
163851, thread declared inside InnoDB 0

mysql tables in use 1, locked 1
1 lock struct(s), heap size 320


this is http://bugs.mysql.com/bug.php?id=20090

The reason is not yet known.


Quote:
060525 18:09:31InnoDB: Assertion failure in thread 786465 in file 
fsp0fsp.c line 2963

InnoDB: Failing assertion: descr
InnoDB: We intentionally generate a memory trap.


That is database corruption. Please post more of the .err log, particularly 
the first errors before it shows corruption. What operating system and 
hardware are you using?



Can this errors occure if i change default value of 2 parameters to:
innodb_flush_log_at_trx_commit=0
innodb_log_archive=0


It will not help in corruption.

Best regards,

Heikki

Oracle Corp./Innobase Oy
InnoDB - transactions, row level locking, and foreign keys for MySQL

InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM 
tables

http://www.innodb.com/order.php


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



innodb database crash

2006-05-26 Thread Vitaliy Okulov
Hi all. I have some InooDB mysql crush logs, can somebody explain what
they mean?

Quote:
060525 18:09:43 InnoDB: Error: trying to declare trx to enter InnoDB, but
InnoDB: it already is declared.   
TRANSACTION 0 550042370, ACTIVE 0 sec, process no 27054, OS thread id 163851, 
thread declared inside InnoDB 0   
mysql tables in use 1, locked 1   
1 lock struct(s), heap size 320 

Quote:
060525 18:09:31InnoDB: Assertion failure in thread 786465 in file fsp0fsp.c 
line 2963
InnoDB: Failing assertion: descr   
InnoDB: We intentionally generate a memory trap.

Can this errors occure if i change default value of 2 parameters to:
innodb_flush_log_at_trx_commit=0
innodb_log_archive=0




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]