MYSQL Server Crashing

I recently built a new server to replace our old PHP/MYSQL. I've had quite a bit of trouble getting the database transferred, but I thought I had successfully done it. Both the old and new are running 5.016 (Server 2003 SP2, IIS.) However, once I started testing, I immediately had problems. I seem to be able run most queries, but this one crashes my server the second time it runs (not the first.) It's a critical query to my operation.

SELECT c.*, u.username, s.status, s.status_order, p.priority, u.extension, u.did, u2.username assigned_to, t.total_hours FROM tickets c, users u, tickets_status s, tickets_priority p, users u2, tickets c2 LEFT JOIN tickets_total_time t ON c2.id=t.ticket_id WHERE c.userid=u.id AND c.statusid=s.id AND c.priorityid=p.id AND u2.id=c.assigned_userid AND c.categoryid=1 AND c2.id=c.id AND status_order<20 AND c.statusid<>9 ORDER BY c.priorityid, creation_date, id ASC

Log info about crash:

080211 10:16:25  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
080211 10:16:25  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 467966560.
InnoDB: Doing recovery: scanned up to log sequence number 0 467966560
InnoDB: Last MySQL binlog file position 0 0, file name
080211 10:16:26  InnoDB: Started; log sequence number 0 467966560
080211 10:16:26 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.16-nt'  socket: ''  port: 3306  Official MySQL binary

Event Logs just state that the process terminated unexpectedly.
LVL 2
laurin1Asked:
Who is Participating?
 
laurin1Connect With a Mentor Author Commented:
Never mind. I fixed it by upgrading the new server to MYSQL 5.0.51a. Strange.
0
All Courses

From novice to tech pro — start learning today.