Error 1065

This topic is empty.

Viewing 6 reply threads

Author

Posts
- April 24, 2004 at 10:19 pm #8407
  
  SamThornton
  Member
  
  Never mind. Just replaced the table and things worked fine. Scheduled to run every 6 hours. I'll holler if it blows up.
  
  Started getting error 1065 on one table (users) after the first few syncs. Where did I go wrong. Thanks.
- April 24, 2004 at 10:22 pm #15720
  
  SamThornton
  Member
  
  Oops, this was accidentally submitted (was duplicate of above).
- April 25, 2004 at 1:19 am #15721
  
  Ritesh
  Member
  
  Hello,
  
  Can you send me a backup of your database? (table structure with sample data to reproduce the error will be very helpful)
  
  Please tell us the MySQL version that you are using?
- April 25, 2004 at 5:28 pm #15722
  
  SamThornton
  Member
  
  Thanks for the quick response.
  
  We're using v4.0.17 of mySQL. Unfortunately, the data is proprietary/confidential/financial, so can't supply copy.
  
  Task scheduler has fired Job Agent several times on a couple of DB's since last post with no errors, so I'm assuming this is something I inadvertently did wrong.
  
  Think problem may have been I was trying to use a timestamp field being >= current_date as a trigger and trying to monitor changes of just a few fields in a fairly huge, fairly static table in one database just to optimize the process. It optimized it all right, right out the window apparently. When I restored the the tables and ran just a plain-jane update process, things seemed to settle down. I'm running two update processes daily against two DBs and one against another DB every 6 hours, so this should be a good workout.
  
  Thanks again. I'll report any glitches, if they occur.
- April 25, 2004 at 5:30 pm #15723
  
  Shadow
  Member
  
  Or accidentally put two “;” at the end of a query…
- April 25, 2004 at 5:46 pm #15724
  
  SamThornton
  Member
  
  Gee, I don't think so. In fact, I didn't terminate the WHERE clause with ';'. Maybe that was the problem. Anywho, I'm leaving the thing alone for the time being–it's now taking about 5-6 minutes to run the process in question which I can live with. The other way, it was taking only a few seconds–real fast but real wrong.
- May 10, 2004 at 12:10 pm #15725
  
  rob22202
  Member
  
  I had the same error occur.
  
  I resolved it by following your lead and removing the sqlwhere clause.
  
  Now it works fine again.
  
  Thanks for posting your experience.
  
  It sure would be nice to get that fixed.
  
  Rob
Author

Posts