Home |  MySQL Buzz |  FAQ |  Feeds |  Submit your blog feed |  Feedback |  Archive |  Aggregate feed RSS 2.0 English Deutsch Español Français Italiano 日本語 Русский Português 中文
Showing entries 1 to 30 of 32130 Next 30 Older Entries
WebScaleSQL on Windows? I wish, but not quite yet, it seems …
+0 Vote Up -0Vote Down

For fun, I tried building WebScaleSQL on Windows, even though it’s not [yet?] a support platform.

Using the following (as I would to build MySQL/MariaDB):

cd c:\mysql\webscalesql-5.6.16
mkdir bld
cd bld
cmake ..
cmake --build . --config relwithdebinfo --target package

I end up with:

...
    238 Warning(s)
    110 Error(s)
Time Elapsed 00:05:08.53

Looking through the output, the main error is this:

C:\mysql\webscalesql-5.6.16\include\atomic_stat.h(33):
fatal error C1083: Cannot open include file: 'atomic':
No such file or directory
[C:\mysql\webscalesql-5.6.16\bld\storage\innobase\innobase.vcxproj]

Of course the directory does exist, and permissions are correct.

C:\mysql\webscalesql-5.6.16\include\atomic_stat.h contains the following line:

#include <atomic>

And this exists:

  [Read more...]
Resolving Error 1918, System Error Code 126, When Installing MySQL ODBC Driver
+0 Vote Up -0Vote Down

If you are installing MySQL ODBC Driver and encounter the following error:

Error 1918. Error installing ODBC driver MySQL ODBC 5.1 Driver, 
ODBC error 13: The setup routines for the MySQL ODBC 5.1 Driver 
could not be loaded due to system error code 126: 
The specified module could not be found. 
...\myodbc5S.dll).. Verify...

Then you will need to install the Microsoft Visual C++ 2010 Redistributable Package (select the appropriate one for your OS architecture below):

64-bit version:

read more

Resolving Error 1918, System Error Code 126, When Installing MySQL ODBC Driver
+0 Vote Up -0Vote Down

If you are installing MySQL ODBC Driver and encounter the following error:

Error 1918. Error installing ODBC driver MySQL ODBC 5.1 Driver,
ODBC error 13: The setup routines for the MySQL ODBC 5.1 Driver
could not be loaded due to system error code 126:
The specified module could not be found.
...\myodbc5S.dll).. Verify...

Then you will need to install the Microsoft Visual C++ 2010 Redistributable Package (select the appropriate one for your OS architecture below):

64-bit version:

http://www.microsoft.com/en-us/download/confirmation.aspx?id=14632

32-bit version:

http://www.microsoft.com/en-gb/download/details.aspx?id=5555

After installing that, then re-attempt

  [Read more...]
Resolving MySQL ODBC "architecture mismatch" Error
+0 Vote Up -0Vote Down

If you attempt to use ODBC to run a MySQL application and run into the following error:

[Microsoft][ODBC Driver Manager] The specified DSN contains an 
architecture mismatch between the Driver and Application

This means there is a 64-bit versus 32-bit mismatch.

Most likely, you're running 64-bit Windows, as well as 64-bit MySQL ODBC connector, but the application is 32-bit.

If this is the case, you will also need to install the 32-bit MySQL ODBC connector, and then create the connection from the 32-bit ODBC.

read more

Resolving MySQL ODBC “architecture mismatch” Error
+0 Vote Up -0Vote Down

If you attempt to use ODBC to run a MySQL application and run into the following error:

[Microsoft][ODBC Driver Manager] The specified DSN contains an
architecture mismatch between the Driver and Application

This means there is a 64-bit versus 32-bit mismatch.

Most likely, you’re running 64-bit Windows, as well as 64-bit MySQL ODBC connector, but the application is 32-bit.

If this is the case, you will also need to install the 32-bit MySQL ODBC connector, and then create the connection from the 32-bit ODBC.

odbcad32.exe is the file to create the connections. Both 64-bit and 32-bit files have the same name, just differing locations.

This is the default location for the 64-bit ODBC:

C:\Windows\System32\odbcad32.exe

This is the default location for the 32-bit ODBC:

C:\Windows\SysWOW64\odbcad32.exe

And should you need to

  [Read more...]
SSL and MariaDB/MySQL
+0 Vote Up -0Vote Down

With the recent Heartbleed bug, people are clearly more interested in their MariaDB/MySQL running with SSL and if they have problems. First up, you should read the advisory notes: MariaDB, Percona Server (blog), and MySQL (blog).

Next, when you install MariaDB (or a variant) you are usually dynamically linked to the OpenSSL library that the system provides. Typically on startup

  [Read more...]
Congratulations, Ubuntu!
Employee_Team +1 Vote Up -0Vote Down
Today, we congratulate our friends at Ubuntu on a great new release, Ubuntu 14.04 LTS. As you can see in Mark Shuttleworth’s posting on Google+ from a few weeks back, MySQL has been cooperating closely with the Debian and Ubuntu communities to make sure that MySQL works very well on these platforms, and Ubuntu 14.04 […]
MySQL Enterprise Monitor 2.3.16 has been released
Employee_Team +0 Vote Up -0Vote Down

We are pleased to announce that MySQL Enterprise Monitor 2.3.16 is now available for download on the My Oracle Support (MOS) web site.

The Service Manager, Agent, and bundled MySQL Server binaries included in 2.3.16 are all updated to use OpenSSL 1.0.1g. Please see http://www.oracle.com/technetwork/topics/security/opensslheartbleedcve-2014-0160-2188454.html for further information. You can also find additional details about Enterprise Monitor 2.3.16 in the change log.

You will find binaries for the new release on My Oracle Support. Choose the "Patches & Updates"

  [Read more...]
MariaDB 5.5.37 now available
+0 Vote Up -0Vote Down

The MariaDB project is pleased to announce the immediate availability of MariaDB 5.5.37. This is a Stable (GA) release.

See the Release Notes and Changelog for detailed information on this release and the What is MariaDB 5.5? page in the MariaDB Knowledge Base for general information about the MariaDB 5.5 series.

Download MariaDB 5.5.37

Release Notes Changelog What is MariaDB

  [Read more...]
InfiDB's Response to the "Heartbleed" Bug
+0 Vote Up -0Vote Down
At InfiniDB, we take matters of communication security and privacy very seriously, and want to assure our customers and users of our software that no version of InfiniDB is affected by "Heartbleed". None of the InfiniDB database components supports SSL and none of them link with any SSL libraries.
Proposal to deprecate mysqlhotcopy
Employee +0 Vote Up -0Vote Down

In the MySQL team, we are considering deprecating the mysqlhotcopy utility. To provide some background, here is an excerpt from the MySQL manual:

mysqlhotcopy is a Perl script that was originally written and contributed by Tim Bunce. It uses FLUSH TABLES, LOCK TABLES, and cp or scp to make a database backup. It is a fast way to make a backup of the database or single tables, but it can be run only on the same machine where the database directories are located. mysqlhotcopy works only for backing up MyISAM and ARCHIVE tables. It runs on Unix.

And now let me explain the motivations leading to our proposal:

  • The name implies that this utility will work for ‘MySQL’ and is hot, but actually neither are true:
  • Only MyISAM
  [Read more...]
Abdel-Mawla Gharieb: Setting the right GCache size in Galera Cluster
+0 Vote Up -0Vote Down

One of our customers had a question related to the right value of Galera Cache size (gcache.size) in Galera Cluster for MySQL which I would like to share with you.

The question was: My maintenance window takes 4 hours for my 5TB DB. How can I avoid an SST ?!

Basically, having too small GCache size will lead to SST (Snapshot State Transfer) instead of IST (Incremental State Transfer), thus we can avoid the SST by setting the GCache to the appropriate value.

To check the current value of the GCache size:

mysql> SHOW GLOBAL VARIABLES LIKE 'wsrep_provider_options'\G Variable_name: wsrep_provider_options Value: base_host = 192.168.1.12; . . . gcache.page_size = 128M; gcache.size = 128M; gcs.fc_debug = 0; . . .

The value


  [Read more...]
MySQL Server QA is hiring
Employee +2 Vote Up -0Vote Down
Hi,
I am hiring for my team in Bangalore. If you are passionate about databases and testing please send your resume to anitha.gopi@oracle.com.


Job details at https://irecruitment.oracle.com/OA_HTML/OA.jsp?OAFunc=IRC_VIS_VAC_DISPLAY&OAMC=R&p_svid=2477587&p_spid=2529909
How to find bugs in MySQL
+0 Vote Up -0Vote Down

Finding bugs in MySQL is not only fun, it’s also something I have been doing the last four years of my life.

Whether you want to become the next Shane Bester (who is generally considered the most skilled MySQL bug hunter worldwide), or just want to prove you can outsmart some of the world’s best programmers, finding bugs in MySQL is a skill not reserved anymore to top QA engineers armed with a loads of scripts, expensive flash storage and top-range server hardware. Off course, for professionals that’s still the way to go, but now anyone with an average laptop and a standard HDD can have a lot of fun trying to find that

  [Read more...]
A little fun with InnoDB multi-versioning
+0 Vote Up -0Vote Down

Consider the following commands, executed in the MySQL CLI on a new connection with no special preparation (and pay special attention to the execution time):

mysql> show create table t \G
*************************** 1. row ***************************
       Table: t
Create Table: CREATE TABLE `t` (
  `a` int(10) unsigned NOT NULL,
  `b` int(10) unsigned NOT NULL,
  PRIMARY KEY (`a`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1
1 row in set (0.00 sec)

mysql> select * from t;
Empty set (5.20 sec)

mysql> select count(*) from t;
+----------+
| count(*) |
+----------+
|        0 |
+----------+
1 row in set (5.22 sec)

mysql> select * from t where a = 10;
Empty set (0.00 sec)

mysql> select * from t where a < 10;
Empty set (5.35 sec)

mysql> select * from t where a > 10;
Empty set (5.41 sec)

mysql> select
  [Read more...]
A Survey for DBAs, SysAdmins, and Other People who Manage Servers
+0 Vote Up -0Vote Down

Most of the world, including developers and managers, don't understand what it's like to be a database administrator or responsible for servers in an organization.

Like a doctor, you are on call pretty much 24/7. The unfortunate difference, is you are responsible for the problem that others created. You need to solve problems that were created by a bad code push, poorly written queries, a configuration change and the like.

On top of that, a DBA or server administrator has constant requests from developers and other people in an organization to fix things, optimize queries, and the like.

It's hard to communicate how all these distraction add up to a really unproductive working environment.

Several

  [Read more...]
TokuMX, MongoDB and InnoDB, IO-bound update-only with fast storage
+0 Vote Up -0Vote Down
I repeated the update-only IO-bound tests using pure-flash servers to compare TokuMX, MongoDB and InnoDB. The test setup was the same as on the pure-disk servers except for the hardware. In this case the servers have fast flash storage, 144G of RAM and 24 CPU cores with HT enabled. As a reminder, the InnoDB change buffer and TokuMX fractal tree don't help on this workload because there are no secondary indexes to maintain. Note that all collections/tables are in one database for this workload thus showing the worst-case for the MongoDB per-database RW-lock. The result summary:
  • InnoDB is much faster than MongoDB and TokuMX. This test requires a high rate of dirty page writeback and thanks to a lot of work from the InnoDB team at MySQL with help from Percona and

  [Read more...]
Types of writes
+0 Vote Up -0Vote Down

What does it mean to make writes fast? It helps to distinguish between the different types of writes. The slowest is a write that must be implemented as read-modify-write. This might require a disk read and can also create contention from preventing concurrent changes to the row for the duration of the read, modify and write. The row might not be unlocked until the change is made durable on storage (commit, fsync, etc) which lets you estimate the peak rate at which a single row can be changed on a traditional DBMS. And this latency between changes can get even worse when there is sync replication or multiple client-server round trips per transaction. The UPDATE statement in SQL is usually implemented as read-modify-write. Some DBMS engines require locking to be done above the DBMS because they don't support locking across operations where read and write are separate operations  [Read more...]

The basics of the InnoDB undo logging and history system
+0 Vote Up -0Vote Down

InnoDB implements multi-version concurrency control (MVCC), meaning that different users will see different versions of the data they are interacting with (sometimes called snapshots, which is a bit of a misleading term). This is done in order to allow users to see a consistent view of the system without expensive and performance-constraining locking which would limit concurrency. (This is where the “concurrency control” part of the term comes from; one alternative is locking everything the user may need.) Undo logging and InnoDB’s “history” system are the mechanisms that underly its implementation of MVCC, but the way this works is generally very poorly understood.

  [Read more...]
Looking for Slave Consistency: Say Yes to –read-only and No to SUPER and –slave-skip-errors
+0 Vote Up -0Vote Down

The biggest concern with a slave is to ensure your data is consistent with the master! End of story!

3 of the biggest things I see when dealing with out-of-sync slaves:

  • Many users do not use the --read-only option on their slaves.
  • Some of those who do often have numerous users with SUPER who can still perform writes.
  • Many users simply use --slave-skip-errors=… to avoid common errors.
  • Of course, if you have a slave, definitely use the --read-only option.

    However, SUPER users can still write on slaves with --read-only, so blindly granting SUPER to all users just to save a little time when creating users won’t help. I’d suggest to use SUPER as sparingly as possible (not to mention it’s good for security also).

    And the use of --slave-skip-errors=… is generally just a quick fix to avoid

      [Read more...]
    A first second look at InnoDB spatial indexes in the MySQL 5.7 april lab release ...
    +0 Vote Up -0Vote Down

    Warning: it turned out that I used a full debug build instead of a release one, and that seems to make a hell of a difference ... most numbers have been updated now, the old debug results and conclusions are still there but striked out (to document my own stupidity forever ;)

    The MySQL 5.7 April Labs release comes with a preview of spatial indexes for InnoDB, something that I've heard rumours about for quite a while but so far couldn't find any kind of actual confirmation for. Spatial indexes for InnoDB would more or less get rid of the last MyISAM-only feature (after the addition of fulltext indexing to InnoDB in MySQL 5.6)

    So it's about time to have a closer look

      [Read more...]
    More details on disk IO-bound, update only for MongoDB, TokuMX and InnoDB
    +0 Vote Up -0Vote Down
    This has a few more details on the results for update-only sysbench using a disk IO-bound workload. I describe the impact from changing innodb_flush_neighbors. The parameter can be set to write back some dirty pages early when other pages in the same extent must be written back. The goal is to reduce the number of disk seeks consumed by page writeback and this can help on disk based servers.

    There might be a small impact from changing innodb_flush_neighbors on this workload from both the TPS results and the amount of data written to disk per update.  In a previous

      [Read more...]
    Making the MTR rpl suite GTID_MODE Agnostic
    Employee_Team +1 Vote Up -0Vote Down

    In MySQL 5.6 we introduced GTID_MODE as a new server option. A global transaction identifier (GTID) is a unique identifier created and associated with each transaction when it is committed on the server of origin (master). This identifier is unique not only to the server on which it originated, but is unique across all servers in a given replication setup. There is a 1-to-1 mapping between all transactions and all GTIDs. For additional information, please refer to the MySQL manual.

    Prior to 5.6.17 and 5.7.4, we had GTID specific replication (referred to as “rpl” within the MTR suite) regression tests, and we had to separately run

      [Read more...]
    ‘Open Source Appreciation Day’ draws OpenStack, MySQL and CentOS faithful
    +1 Vote Up -0Vote Down

    210 people registered for the inaugural “Open Source Appreciation Day” March 31 in Santa Clara, Calif. The event will be held each year at Percona Live henceforth.

    To kick off the Percona Live MySQL Conference & Expo 2014, Percona held the first “Open Source Appreciation Day” on Monday, March 31st. Over 210 people registered and the day’s two free events focused on

      [Read more...]
    MongoDB, TokuMX and InnoDB for disk IO-bound, update-only by PK
    +0 Vote Up -0Vote Down
    I used sysbench to measure TPS for a workload that does 1 update by primary key per transaction. The database was much larger than RAM and the server has a SAS disk array that can do at least 2000 IOPs with a lot of concurrency. The update is to a non-indexed column so there is no secondary index maintenance which also means there is no benefit from a fractal tree in TokuMX or the change buffer in InnoDB. I also modified the benchmark client to avoid creating a secondary index. Despite that TokuMX gets almost 2X more TPS than InnoDB and InnoDB gets 3X to 5X more TPS than MongoDB.
    • TokuMX is faster because it doesn't use (or waste) random IOPs on writes so more IO capacity is

      [Read more...]
    MySQL 5.7.4 Overview and Highlights
    +2 Vote Up -0Vote Down

    MySQL 5.7.4 was recently released (it is the latest MySQL 5.7, and is the “m14″ or “Milestone 14″ release), and is available for download here and here.

    The 5.7.4 changelog begins with the following, so I felt it appropriate to include it here as well.

    In Memoriam:

    “This release is dedicated to the memory of two young engineers of the MySQL Engineering family, Astha and Akhila, whom we lost while they were in their early twenties. This is a small remembrance and a way to recognize your contribution to the 5.7 release. You will be missed.”

      [Read more...]
    How TokuMX Secondaries Work in Replication
    +0 Vote Up -0Vote Down

    As I’ve mentioned in previous posts, TokuMX replication differs quite a bit from MongoDB’s replication. The differences are large enough such that we’ve completely redone some of MongoDB’s existing algorithms. One such area is how secondaries apply oplog data from a primary. In this post, I’ll explain how.

    In designing how secondaries apply oplog data, we did not look closely at how MongoDB does it. In fact, I’ve currently forgotten all I’ve learned about MongoDB’s implementation, so I am not in a position to compare the two. I think I recall that MongoDB’s oplog idempotency was a key to their

      [Read more...]
    percona-millipede – Sub-second replication monitor
    +0 Vote Up -0Vote Down

    I recently helped a client implement a custom replication delay monitor and wanted to share the experience and discuss some of the iterations and decisions that were made. percona-millipede was developed in conjunction with Vimeo with the following high-level goal in mind: implement a millisecond level replication delay monitor and graph the results.  Please visit http://making.vimeo.com for more information and thanks to Vimeo for sharing this tool!

    Here is the rough list of iterations we worked through in developing this tool/process:

  • Standard pt-heartbeat update/monitor
  • Asynchronous, threaded update/monitor tool
  • Synchronized (via zeroMQ), threaded version of the tool
  • pt-heartbeat

    Initially, we had been running

      [Read more...]
    OurSQL Episode 181: MariaDB Goodies
    +0 Vote Up -0Vote Down

    This week we discuss more features of MariaDB 10. Ear Candy is how to avoid downtime when switching to GTIDs and At the Movies is Managing Hundreds of MySQL Servers Efficiently.

    News
    MySQL Community Awards 2014: the Winners

    MariaDB 10
    MariaDB 10.0.1 features
    Other MariaDB podcasts:
    OurSQL Episode 89, where we talk about an overview of MariaDB

    read more

    MySQL Enterprise Monitor 3.0.9 has been released
    Employee_Team +0 Vote Up -0Vote Down

    We are pleased to announce that MySQL Enterprise Monitor 3.0.9 is now available for download on the My Oracle Support (MOS) web site.

    The Service Manager, Agent, and bundled MySQL Server binaries included in 3.0.9 are all updated to use OpenSSL 1.0.1g. Please see http://www.oracle.com/technetwork/topics/security/opensslheartbleedcve-2014-0160-2188454.html for further information. You can also find additional details about Enterprise Monitor 3.0.9 in the change log.

    You will find binaries for the new release on My Oracle Support. Choose the "Patches & Updates" tab,

      [Read more...]
    Showing entries 1 to 30 of 32130 Next 30 Older Entries

    Planet MySQL © 1995, 2014, Oracle Corporation and/or its affiliates   Legal Policies | Your Privacy Rights | Terms of Use

    Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.