Advertisement

02.11.2008 at 09:00AM PST, ID: 23153542
[x]
Attachment Details

MYSQL Server Crashing

[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
6.4
Zones:

MySQL Server, Windows 2003 Server

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.
Start your 7 day free trial to see this answer
Answered By: laurin1
Expert Since: 10/22/2002
Accepted Solutions: 15
Computer Expertise: Guru
laurin1 has been an Expert for 6 years 2 months, during which he has posted 250 comments and answered 15 questions. laurin1 is just one of 2167 experts in the MySQL Server Zone. 1 expert collaborated on this answer, which was graded an "A" by the asker.
 
 
20081119-EE-VQP-47 / EE_QW_EXPERT_20070906