Nice to meet you.
I am andou.
Slave DB : though is several-time re-synchronization. It is sure to have
entered the state that the process of the slave stops because of the same
error.
Excerpt from show slave status(a part of Fge)
Last_error: error 'unexpected success or fatal error' on query 'CREATE
TEMPORARY TABLE book_continue_target_data SELECT t1.***, t2.id AS ***,
t2.* , t2.*** AS last_day FROM *** AS t1, *** AS t2, service AS t3
WHERE (DATE_FORMAT(t2.***, "%Y-%m-%d") BETWEEN '2004-10-21' AND
'2004-10-25') AND t1.id=t2.*** AND t2.service_id=t3.id AND t2.status
IN ('active', 'continue', 'dropping', 'withdrawing') AND t3.name_en
='***''
Is it a problem of the bug of MySQL or the communication because the
stopping part is every time different?
There is no packet loss a similar error occurred though
re-synchronization was tested for the time being by changing
set-variable=innodb_lock_wait_timeout=200 (50 ahead).
Master Server and Slave Server installs it from
MySQL-client-4.0.14-0.i386.rpm in MySQL.
OS uses RedHat AS.
Because a similar error had not been seen to be reported, it
contributed.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
