[opencms-dev] Problem upgrading mySQL version 3.23

[maria.freixes_graells at alcatel.es]

Hello to all,

I've tried to update my sql version 3.23 to 4.0.21 as Gustavo says in
http://dev.mysql.com/doc/refman/4.1/en/upgrading-from-3-23.html
/etc/init.d/mysql stop
rpm -Uvh MySQL-server-4.0.21-0.i386.rpm
rpm -Uvh MySQL-devel-4.0.21-0.i386.rpm
rpm -Uvh MySQL-client-4.0.21-0.i386.rpm
/etc/init.d/mysql start
But the mysql doesn't start anymore.
Could you help me, please?
If I try to launch the mysqld, the results are:
-bash-2.05b$ /usr/sbin/mysqld
060626 18:46:54 Warning: Asked for 196608 thread stack, but got 126976
InnoDB: You are downgrading from the multiple tablespace format of
InnoDB: >= MySQL-4.1.1 back to the old format of MySQL-4.0.
InnoDB:
InnoDB: MAKE SURE that the mysqld server is idle, and purge and the
insert
InnoDB: buffer merge have run to completion under >= 4.1.1 before
trying to
InnoDB: downgrade! You can determine this by looking at SHOW INNODB
STATUS:
InnoDB: if the Main thread is 'waiting for server activity' and SHOW
InnoDB: PROCESSLIST shows that you have ended all other connections
InnoDB: to mysqld, then purge and the insert buffer merge have been
InnoDB: completed.
InnoDB: If you have already created tables in >= 4.1.1, then those
InnoDB: tables cannot be used under 4.0.
InnoDB: NOTE THAT this downgrade procedure has not been properly
tested!
InnoDB: The safe way to downgrade is to dump all InnoDB tables and
recreate
InnoDB: the whole tablespace.
InnoDB: You are downgrading from an InnoDB version which allows
multiple
InnoDB: tablespaces. Wait that purge and insert buffer merge run to
InnoDB: completion...
060626 18:46:55InnoDB: Assertion failure in thread 28680 in file
dict0load.c line 243
InnoDB: Failing assertion: ut_dulint_cmp(table->id,
mach_read_from_8(field)) == 0
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. See section 6.1 of
InnoDB: http://www.innodb.com/ibman.php about forcing recovery.
mysqld got signal 11;
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=8388600
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
Attempting backtrace. You can use the following information to find
out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0xbfebe698, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8072614
0x826ac98
0x810fdda
0x8113fd9
0x8114648
0x8134e91
0x813500f
0x81351a7
0x811997e
0x81852f8
0x80fadff
0x826844c
0x829df0a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/en/Using_stack_trace.html and
follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please
do
resolve it
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.

I am not expert in mysql, so I need a detailed information on how I can
proceed in order to have the mysql working.

In fact, I wish to have a mysql 5.0 version, previously I had 3.23 one,
if it's more easy to solve the problem going to 5.0 version instead of
4.0, it will be more usefully for me. THANKS!!



4.0, it will be more usefully for me. THANKS!!




proceed in order to have the mysql working.