Hi Heikki et al.
I have solve my problem :). The fact about my missed table was my fault, because indeed those tables doesnt exist anymore (one developer had deleted them).
Even when my db is up and running im figuring out why there is not an option to skip commit/rollback pending transactions ?, this way i would have a quitely weekend, heheehe, no problem thanx a lot for your help.
Carlos
----Original Message Follows---- From: "Carlos Proal" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: start innodb without transactions Date: Thu, 05 Jun 2003 23:40:16 -0500
Probably i need to describe the whole story:
I did a huge insert, a file about 100Mb, and mysql crashed/restarted, the err file showed:
--------------------------------------------------------------
030605 12:11:59 mysqld restarted
030605 12:12:00 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 13 1000286684
InnoDB: Doing recovery: scanned up to log sequence number 13 1000286208
InnoDB: Last MySQL binlog file position 0 756499, file name ./catarina-bin.057
030605 12:12:01 InnoDB: Flushing modified pages from the buffer pool...
030605 12:12:01 InnoDB: Started
/centia01/final/database/mysql/libexec/mysqld: ready for connections
030605 12:14:01 InnoDB: Out of memory in additional memory pool.
InnoDB: InnoDB will start allocating memory from the OS.
InnoDB: You may get better performance if you configure a bigger
InnoDB: value in the MySQL my.cnf file for
InnoDB: innodb_additional_mem_pool_size.
mysqld got signal 10;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=67104768
read_buffer_size=131072
sort_buffer_size=524280
max_used_connections=4
max_connections=500
threads_connected=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 385528
K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
----------------------------------------------------------
(i have 256Mb in buffer pool) But the next restart stopped mysql showing:
----------------------------------------------------------
030605 12:14:30 mysqld restarted
030605 12:14:32 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 13 1002344016
InnoDB: Doing recovery: scanned up to log sequence number 13 1002343936
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: Trx id counter is 0 119167744
InnoDB: Starting rollback of uncommitted transactions
InnoDB: Rolling back trx with id 0 119167355
030605 12:14:32 InnoDB: Assertion failure in thread 1 in file btr0cur.c line 3350
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to [EMAIL PROTECTED]
mysqld got signal 11;
----------------------------------------------------------
i started with force_recovery and indeed i can recover with mysqldump some databases but i was confused because my first try was with a db that apparently i cant recover, even inside mysql i get the following:
---------------------------------------------------------
mysql> desc facturas;
ERROR 1016: Can't open file: 'facturas.InnoDB'. (errno: 1)
mysql> show table status;
+--------------+------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+-------------+-------------+------------+----------------+----------------------------------------------------+
| Name | Type | Row_format | Rows | Avg_row_length | Data_length | Max_data_length | Index_length | Data_free | Auto_increment | Create_time | Update_time | Check_time | Create_options | Comment |
+--------------+------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+-------------+-------------+------------+----------------+----------------------------------------------------+
| facturas | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | Can't open file: 'facturas.InnoDB'. (errno: 1) |
| presupuestos | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | Can't open file: 'presupuestos.InnoDB'. (errno: 1) |
| proveedores | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | Can't open file: 'proveedores.InnoDB'. (errno: 1) |
| roles | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | Can't open file: 'roles.InnoDB'. (errno: 1) |
| usuarios | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | Can't open file: 'usuarios.InnoDB'. (errno: 1) |
+--------------+------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+-------------+-------------+------------+----------------+----------------------------------------------------+
5 rows in set (0.06 sec)
---------------------------------------------------------
Heikki, thanx a lot for your help, its really appreciated.
Carlos
----Original Message Follows---- From: "Heikki Tuuri" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: Re: start innodb without transactions Date: Fri, 6 Jun 2003 04:23:57 +0300
Carlos,
----- Original Message ----- From: ""Carlos Proal"" <[EMAIL PROTECTED]> Newsgroups: mailing.database.mysql Sent: Friday, June 06, 2003 4:04 AM Subject: start innodb without transactions
>
> Hi all
> Is there any way to start mysql/innodb skipping transactions ?, i had a
> crash and i cant get the database to work.
>
> i tried the force_recovery option level 3:
> # 3 (SRV_FORCE_NO_TRX_UNDO) do not run transaction rollbacks after
recovery;
>
> this way i can get it to work, but as the manual said i cant do any update
> query while force_recovery is on and also cant do a mysqldump, so im
stucked
> :(.
why you cannot do a mysqldump? innodb_force_recovery does not prevent SELECT queries.
> any ideas ? > Im using mysql 4.0.4, solaris 8 sparc .
Upgrade to 4.0.13. Also send me the .err log. Database corruption is uncommon in Solaris, interesting to see what is in the .err log.
> thanx > Carlos
Best regards,
Heikki Tuuri Innobase Oy http://www.innodb.com Transactions, foreign keys, and a hot backup tool for MySQL Order MySQL technical support from https://order.mysql.com/
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
