Re: log sequence number InnoDB: is in the future!?

2013-01-28 Thread Reindl Harald
Am 28.01.2013 16:01, schrieb walter harms: > > > Am 28.01.2013 14:40, schrieb Andrew Moore: >> Dump and reload or use some scripting to create and drop some fake data to >> increase the lsn towards the 'future' value. >> >> http://dba.stackexchange.com/questions/8011/any-better-way-out-of-mysql

Re: adding column breaks query

2013-01-28 Thread Larry Martell
Not sure what you mean. On Mon, Jan 28, 2013 at 8:49 AM, Douglas Nelson wrote: > two different fields?? > > Thanks Doug > > SELECT data_ppl.name as 'P/P/L', data_recipe.name as Recipe, > data_cstmeta.date_time as 'Last Run' > FROM data_recipe, data_ppl, data_cstmeta >INNER JOIN (SELECT id,rec

Re: adding column breaks query

2013-01-28 Thread Shawn Green
Hello Larry, On 1/28/2013 10:42 AM, Larry Martell wrote: I have a query that works fine: SELECT data_ppl.name as 'P/P/L', data_recipe.name as Recipe, data_cstmeta.date_time as 'Last Run' FROM data_recipe, data_ppl, data_cstmeta INNER JOIN (SELECT id,recipe_id, MAX(date_time) as MaxDateTime

Re: adding column breaks query

2013-01-28 Thread Larry Martell
On Mon, Jan 28, 2013 at 8:56 AM, Shawn Green wrote: > Hello Larry, > > > On 1/28/2013 10:42 AM, Larry Martell wrote: >> >> I have a query that works fine: >> >> >> SELECT data_ppl.name as 'P/P/L', data_recipe.name as Recipe, >> data_cstmeta.date_time as 'Last Run' >> FROM data_recipe, data_ppl, da

Re: log sequence number InnoDB: is in the future!?

2013-01-28 Thread walter harms
Am 28.01.2013 14:40, schrieb Andrew Moore: > Dump and reload or use some scripting to create and drop some fake data to > increase the lsn towards the 'future' value. > > http://dba.stackexchange.com/questions/8011/any-better-way-out-of-mysql-innodb-log-in-the-future > For now i tend to soluti

Re: log sequence number InnoDB: is in the future!?

2013-01-28 Thread Andrew Moore
So this isn't production - well just rebuild it from a backup? It's a pain in the rear to get the lsn aligned again through data creation/removal but if it's a system critical instance without possible downtime you've got some work to do... On Mon, Jan 28, 2013 at 2:21 PM, walter harms wrote: >

Re: log sequence number InnoDB: is in the future!?

2013-01-28 Thread walter harms
Am 28.01.2013 15:01, schrieb Manuel Arostegui: > 2013/1/28 walter harms > >> hi list, >> >> i am using mysql 5.1.53. >> after a crash i have the follwing error in my log: >> >> 130128 10:45:25 InnoDB: Error: page 61 log sequence number 0 2871649158 >> InnoDB: is in the future! Current system l

Mirror Status

2013-01-28 Thread B.Baransel BAĞCI
hi; We are mirrorring Mysql for a while, but when i check mirror list (http://dev.mysql.com/downloads/mirrors.html) i didn't see our mirror. Can you add? Server: ftp.itu.edu.tr/Mirror/Mysql/ Protocol: Ftp & HTTP IP: IPv4 & IPv6 (ftp.itu.edu.tr has both A and ) Owner: İTÜ-BİDB (Istanbul

Re: log sequence number InnoDB: is in the future!?

2013-01-28 Thread Manuel Arostegui
2013/1/28 walter harms > hi list, > > i am using mysql 5.1.53. > after a crash i have the follwing error in my log: > > 130128 10:45:25 InnoDB: Error: page 61 log sequence number 0 2871649158 > InnoDB: is in the future! Current system log sequence number 0 2494349480. > InnoDB: Your database may

Re: log sequence number InnoDB: is in the future!?

2013-01-28 Thread Andrew Moore
Dump and reload or use some scripting to create and drop some fake data to increase the lsn towards the 'future' value. http://dba.stackexchange.com/questions/8011/any-better-way-out-of-mysql-innodb-log-in-the-future On Mon, Jan 28, 2013 at 12:01 PM, walter harms wrote: > hi list, > > i am usi