Hot answers tagged mysql-5.0
6
It's not difficult. Just need a set section in your LOAD DATA INFILE command.
mysql> create table tst ( datecol datetime );
Query OK, 0 rows affected (0.04 sec)
mysql>
File:
[root@node1 ~]# cat /tmp/tst.dat
01-JAN-03
21-MAR-09
28-FEB-11
[root@node1 ~]#
Test:
mysql> load data infile '/tmp/tst.dat'
-> into table tst
-> fields ...
1
memlock was the issue.
turns out, memlock settings were at default (see above), and this might have been preventing the allocation of 4+gb of memory to mysql.
changed memlock settings in '/etc/security/limits.conf', and limit to 8GB.
then, allocated 7GB to mysql buffer pool. worked. mysql now starts and stops without throwing any errors in the log.
a few ...
1
The reason for the discrepancy is obvious.
When you run
SELECT A.*,B.* FROM (SELECT VERSION() MySQLVersion) A,
(SELECT COUNT(1) MySQLProcColumns FROM information_schema.columns
WHERE table_schema='mysql' AND table_name='proc') B;
you get
mysql> SELECT A.*,B.* FROM (SELECT VERSION() MySQLVersion) A,
-> (SELECT COUNT(1) MySQLProcColumns FROM ...
1
Step 01 : Run this script to Dump Everything from MySQL 5.0
cd /root
MYSQL_CONN="-uroot -p..."
SQLSTMT="SELECT schema_name FROM information_schema.schemata WHERE"
SQLSTMT="${SQLSTMT} WHERE schema_name NOT IN"
SQLSTMT="${SQLSTMT} ('information_schema','mysql','performance_schema')"
MYSQL_OPTIONS="--skip-column-names -A"
mysql ${MYSQL_CONN} ${MYSQL_OPTIONS} ...
1
MySQL 5.6 introduces Global Transaction Identifiers to replication, and complements these with new failover and switchover utilities which can automate fault recovery
You can learn more about replication in MySQL 5.6 here:
http://dev.mysql.com/tech-resources/articles/mysql-5.6-replication.html
You can also watch a tutorial demonstrating how these utilities ...
1
Believe it or not, I just answered a question like this 5 days ago: MySQL Replication and High Availability
From that answer I provided, I advise against automatic failover with pure MySQL Replication unless your specifically script it to check for replication lag or totally unavailability of the old master (STONITH)
As an alternative, just setup a DRBD ...
1
I actually wrote about this back on August 27, 2012 : Proper tuning for 30GB InnoDB table on server with 48GB RAM. Here is an excerpt from my past answer (under the section entitled Log File Size):
EXCERPT
5MB is the default size for innodb_log_file_size. Percona's mysqperformanceblog.com gave two good articles on computing the right size for your ...
Only top voted, non community-wiki answers of a minimum length are eligible
