MySQL
One MySQL Plug-in customer reported an issue with reports — all charts were displaying an Oracle error and didn’t display any data as if it couldn’t connect to the EM repository. If you face this issue, follow My Oracle Support Note 374382.1 “Grid Control Repository: How to Change the Password of the MGMT_VIEW User”.
Why am I still doing a post on this? Because I still see MySQL configurations that DBAs seem to use as separate assignments without taking into account the consequences of over-allocation and what impact it has on MySQL server memory usage.
A few days ago I learned about this year’s NoCOUG SQL Challenge and decided to to put the gray matter between my ears to work. I’ve been teaching a MySQL course this week and my first impulse was to use my MySQL VM to test my solution attempts. However, I eventually decided to use Recursive Subquery Factoring to solve the proposed problem and had to switch to an Oracle 11gR2, since it’s the only database that implements this feature that I know how to use (are there any others?). I was happy with my solution, but frustrated that I couldn’t run it on MySQL. So I decided to try to make it somehow work on MySQL.
Sometimes I get questions as to whether Pythian is one of the competitors battling with Oracle for MySQL support. The answer lies in the distinction of product support and operational support.
Pythian will be at RMOUG in full force. Look for Alex Gorbachev, Kellyn Pedersen & Don Seiler. Be sure to stop by our table (#10), say hi to us & our friends from the OakTable Network, and enter our draw to win an Amazon Kindle, and software provided by Cary Millsap (MR-Trace, MR-Tools & Method-R Profiler) among a few other surprises. Pythian is agressively hiring top DBA talent. If this is you, register on our Career Center, or request a time for a short intro chat with Pythian. Alex, Kellyn or Don will be more than happy to give you the inside scoop on the company & share why they love working for Pythian.
DBIx::Class::DeploymentHandler is a fairly young module. It’s a little raw at the edges and a wee bit terse in term of documentation. It’s also a complex thing and, trust me, it’ll takes more than a few minutes of playing with it to get your mind around how it works. But once you begin to understand what it can do, Whoa, that’s one seriously powerful beast, that module is. But don’t take my word for it, let me show you.
I’ve seen many a good DBA make the master of starting slaves from the position in the master.info file, most recently this week, that I want to bring it to everyone’s attention.
Today I’ve spent some time (more than this issue was worth, actually) on a client’s system trying to find out why table was not accessible and failed. The error message suggested something went very wrong with .frm file and I already started thinking about restoring the table from backup, when I noticed that accessing any InnoDB table was producing same error. A quick check of the error log showed that when MySQL server was restarted some time ago InnoDB failed to initialize due to a memory issue.
North California Oracle User Group are planning their 2011 conferences and are looking for good presentations! We are a very friendly local user group, so if you live in NorCal and never presented before – this is a great place to start! We love seeing new presenters and we even have a public speaking expert on our board who loves giving feedback when requested. Of course, we are nice to seasoned gurus too.
One of my favorite customers had a problem. They had to load around 20G of data into a table on MySQL database. The data loaded fine, but when he tried to build few indexes on the database, he got a mysterious error: ERROR 1114 (HY000): The table ‘really_big_table’ is full. The error was mysterious because we had around 1.5T of free space on the disk. Also, if the customer created the indexes before loading the data there was no error. This gave them a work around, but one that slow and annoying. Later, I found out that we are not the first to run into this mystery.
Recent Comments