Re: mysql_upgrade then mysqld. I feel very ID-10-T PEBKAC today

2018-02-23 Thread Bob Eby
Subject: Re: mysql_upgrade then mysqld. I feel very ID-10-T PEBKAC today
> 2018-02-23T14:02:33.962240Z 0 [ERROR] [MY-010735] Can't open the
mysql.plugin table. Please run mysql_upgrade to create it.

> How do I run mysql_upgrade if the mysqld server won't start?

Please don't bother to answer, I did figure it out, I'm sorry, for a bad
question and worse followup.  Apparently I'm a spammer as well.

Apparently the error was caused by something else besides plugins in
my configuration.  After carefully running --initialize from scratch
and modifying my.ini I was able to get mysqld.exe up and running just
fine on Windows 64 for MySQL 8.0 RC.  After that mysql_upgrade worked
a treat.  I did have a couple issues since it was my first time *NOT*
using --initialize_insecure in this configuration but it all works if
you do it right.  As per usual.

Sorry for the noise here,

Robert Eby


mysql_upgrade then mysqld. I feel very ID-10-T PEBKAC today

2018-02-23 Thread Bob Eby
2018-02-23T14:02:33.962240Z 0 [ERROR] [MY-010735] Can't open the
mysql.plugin table. Please run mysql_upgrade to create it.

How do I run mysql_upgrade if the mysqld server won't start?

Man how stupid am I?

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql



Re: mysql Digest 12 Aug 2015 13:08:20 -0000 Issue 5317

2015-08-12 Thread Bob Eby
converting from MyISAM to innodb would certainly pose problems, I
guess the main question would be is MyISAM functionality a strict
sub-set of innodb?

I'm not sure, but maybe someone else here knows better.

Good luck,
Robert

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql



Re: Sequence Numbering

2015-06-30 Thread Bob Eby
 If the return value of the UPDATE stmt is zero, the following stmt is ran:

By return value I assume you mean rows affected ?

 This is working great, and has been for many years; however,
 today I noticed it was not working on a particular MySQL server.

By not working what exactly is the failure mode?

Not getting 0 rows affected?  0 rows affected not triggering
subsequent INSERT? Something else?

Note: It would make me uneasy to use LAST_INSERT_ID()
where there is no AUTO_INCREMENT column myself...

Good luck,
Robert

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql



Re: get row inserted time or modified time

2015-06-09 Thread Bob Eby
 if you define a column with any name and a type of

 timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP

Thanks Lucio,

This is much better advice than the NOW() built-in function I would
have suggested.

Kind Regards,
-Bob

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql



Re: Fresh install of MySQL 5.6.23 fails to start on CentOS 7.0

2015-02-19 Thread Bob Eby
Cameron,

Did you run the recommended configuration script manually?

mysql_install_db

This is run once after install to put the stuff in your datadir= location
which I pointed out may be missing (and was empty upon your inspection).

Thanks,
Robert


Re: Merging multiple SQL requests

2015-02-17 Thread Bob Eby
Hi Learner,

You might want to try reading about SQL JOIN and/or CLIENT_MULTI_STATEMENTS.


Using databases is all about conglomerating results, but it helps to know
the environment first.


Re: Fresh install of MySQL 5.6.23 fails to start on CentOS 7.0

2015-02-12 Thread Bob Eby
Hi Cameron,

I've seen a similar error running on windows 7.

When you look in your datadir= specified in my.ini what is there exactly
(hopefully not empty)?  Do you have a mysql folder containing plugin.*
files at this location? (say .MYI etc)

It sounds like your data folders were either not copied to the correct
place or not properly configured before starting the server.

It's been a while, but I recall there being an install step to getting
the correct basic database files into your datadir specified in my.ini.

Good Luck,
Robert Eby


Re: mysql Digest 15 Aug 2014 12:32:06 -0000 Issue 5209

2014-08-18 Thread Bob Eby
Wouldn't you run mysql_upgrade *before* upgrading?  (ie: copy new stuff
onto old DB, *then* mysql_upgrade *then* start running new software?)

So I went to google, and realised that I’d probably upgraded without
 running mysql_upgrade.  So I try..

 [~] john@server% (872) mysql_upgrade -u root -p mysql



More details I'm sure, but just my initial thought.

Thanks,
Bob


On Fri, Aug 15, 2014 at 8:32 AM, mysql-digest-h...@lists.mysql.com wrote:


 mysql Digest 15 Aug 2014 12:32:06 - Issue 5209

 Topics (messages 230517 through 230517)

 Incorrect Infomation in tables_priv.frm
 230517 by: John McIntyre

 Administrivia:

 To unsubscribe from the digest, e-mail:
 mysql-digest-unsubscr...@lists.mysql.com
 or click:
 http://lists.mysql.com/mysql-digest?unsub=##L@##H

 To post to the list, e-mail:
 mysql@lists.mysql.com


 --



 -- Forwarded message --
 From: John McIntyre joh98@gmail.com
 To: mysql@lists.mysql.com
 Cc:
 Date: Fri, 15 Aug 2014 13:31:29 +0100
 Subject: Incorrect Infomation in tables_priv.frm
 Hi,
 I have MySQL 5.1.73 running on a CentOS 6.5 Linux system. Recently, I
 was adding a couple of users, and when I tried to FLUSH PRIVILEGES, I got
 this …

 (root@root.server [(none)] 13:24:19 (1) $ FLUSH PRIVILEGES ;
 ERROR 1033 (HY000): Incorrect information in file:
 './mysql/tables_priv.frm’

 So I went to google, and realised that I’d probably upgraded without
 running mysql_upgrade.  So I try..

 [~] john@server% (872) mysql_upgrade -u root -p mysql
 Enter password:
 Looking for 'mysql' as: mysql
 Looking for 'mysqlcheck' as: mysqlcheck
 Running 'mysqlcheck with default connection arguments
 Running 'mysqlcheck with default connection arguments
 0wn3lou4.oc_appconfig  OK
 0wn3lou4.oc_clndr_calendarsOK

 That for a lot of lines, and then …

 mysql.help_relationOK
 mysql.help_topic   OK
 mysql.host OK
 mysql.innodb_index_stats
 Error: Incorrect information in file: './mysql/innodb_index_stats.frm'
 error: Corrupt
 mysql.innodb_table_stats
 Error: Incorrect information in file: './mysql/innodb_table_stats.frm'
 error: Corrupt
 mysql.ndb_binlog_index OK
 mysql.plugin   OK
 mysql.proc
 Error: Incorrect information in file: './mysql/proc.frm'
 error: Corrupt
 mysql.procs_priv
 Error: Incorrect information in file: './mysql/procs_priv.frm'
 error: Corrupt
 mysql.proxies_priv
 Error: Incorrect information in file: './mysql/proxies_priv.frm'
 error: Corrupt

 .. for loads of lines, and then …

 ERROR 1033 (HY000) at line 659: Incorrect information in file:
 './mysql/event.frm'
 ERROR 1033 (HY000) at line 661: Incorrect information in file:
 './mysql/event.frm'
 ERROR 1033 (HY000) at line 663: Incorrect information in file:
 './mysql/event.frm'
 ERROR 1033 (HY000) at line 666: Incorrect information in file:
 './mysql/event.frm'
 ERROR 1033 (HY000) at line 669: Incorrect information in file:
 './mysql/event.frm'
 ERROR 1033 (HY000) at line 672: Incorrect information in file:
 './mysql/event.frm'
 ERROR 1033 (HY000) at line 675: Incorrect information in file:
 './mysql/event.frm'
 ERROR 1033 (HY000) at line 678: Incorrect information in file:
 './mysql/event.frm'
 ERROR 1033 (HY000) at line 681: Incorrect information in file:
 './mysql/event.frm'
 ERROR 1033 (HY000) at line 684: Incorrect information in file:
 './mysql/event.frm'
 ERROR 1033 (HY000) at line 686: Incorrect information in file:
 './mysql/event.frm'
 ERROR 1033 (HY000) at line 714: Incorrect information in file:
 './mysql/tables_priv.frm'
 FATAL ERROR: Upgrade failed

 There are four databases on that server, two of them critical, production
 databases.  I can get around the privileges problem by stopping and
 starting the database out of office hours, but even then, when I do …

 140815 13:28:29 mysqld_safe Starting mysqld daemon with databases from
 /var/lib/mysql
 140815 13:28:29  InnoDB: Initializing buffer pool, size = 8.0M
 140815 13:28:29  InnoDB: Completed initialization of buffer pool
 140815 13:28:29  InnoDB: Started; log sequence number 4 2002382636
 140815 13:28:29 [ERROR] /usr/libexec/mysqld: Incorrect information in
 file: './mysql/tables_priv.frm'
 140815 13:28:29 [ERROR] /usr/libexec/mysqld: Incorrect information in
 file: './mysql/event.frm'
 140815 13:28:29 [ERROR] Cannot open mysql.event
 140815 13:28:29 [ERROR] Event Scheduler: An error occurred when
 initializing system tables. Disabling the Event Scheduler.
 140815 13:28:29 [Note] /usr/libexec/mysqld: ready for connections.

 The user changes are taken into account, however.

 Needless to say, mysql_dump doesn’t work either.

 Any advice gratefully received.

 John.






Re: Help with cleaning up data

2014-03-31 Thread Bob Eby
delete b from icd9x10 a
join icd9x10 b on a.icd9 = b.icd9 and a.id  b.id

...
 CREATE TABLE `ICD9X10` (
 ...
 id   icd9  icd10
 25   29182 F10182
 26   29182 F10282
 ...

Good luck,
Bob


RE: Unable to connect to foreign data source

2014-03-31 Thread Bob Eby
 CONNECTION =  'mysql://root:root@*stripped*:3306/Prelude_copy/test001';

Should be more like:

CONNECTION = 'mysql://root:stripped_password@localhost/penrepository/test001';

Just seems word if you're showing us your password is root but not host...
I ran your example just fine against localhost on MySQL 5.6 Win7-64bit.

-Bob