MySQL man pages silently relicensed away from GPL

[Amended] According to this was a bug


It has recently been brought to attention that the MySQL man pages have been relicensed. The change was made rather silently going from MySQL 5.5.30 to MySQL 5.5.31. This affects all pages in the man/ directory of the source code.

You can tell the changes have come during this short timeframe (5.5.30->5.5.31). The old manual pages were released under the following license:

This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.

The new man pages (following 5.5.31 and greater – still valid for 5.5.32) are released under the following license:

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

This is clearly not very friendly of MySQL at Oracle.



Oracle NoSQL Database 2.0.39 released

Oracle NoSQL Database 2.0.39 has been released and introduce several improvements, a couple of new Oracle product integration points as well as a number of important bug fixes. These new features and fixes include:

– An integration with Oracle Coherence has been provided that allows Oracle NoSQL Database to be used as a cache for Oracle Coherence applications, also allowing applications to directly access cached data from Oracle NoSQL Database. Documentation can be found

– Oracle NoSQL Database Enterprise Edition now has support for semantic technologies. Specifically, the Resource Description Framework (RDF), SPARQL query language, and a subset of the Web Ontology Language (OWL) are now supported. These capabilities are referred to as the RDF Graph feature of Oracle NoSQL Database. The RDF Graph feature provides a Java-based interface to store and query semantic data in Oracle NoSQL Database Enterprise Edition. Documentation can be found

Find the complete list of changes in the change log.


Oracle NoSQL Database 2.0 has been released

The Oracle NoSQL Database 11gR2 Version 2.0 is now available

Release 2.0 of the Oracle NoSQL Database introduce the following new and enhanced features:

  • Better Performance: enterprise-class elasticity with near linear scalability
  • Automatic Re-balancing
  • Enhanced Manageability
  • C APIs Support
  • Tighter Integration with Oracle Database
  • Improved Management & Monitoring Support: SNMP/JMX support
  • Improved Hadoop Integration




Oracle NoSQL Database 11gR2.2.0.22 Community Edition

Oracle NoSQL Database 11gR2.2.0.22 Community Edition has moved to Admin version 2.

This version is available for download at this address.

This is an on-disk format change which affects internal data stored by the Admin services. The change is forward compatible in that Admin services deployed using 11gR2.2.0.22 Community Edition can read data created by older releases. The change is not backwards compatible in that Admin services which have been deployed with the new release cannot be restarted using older NoSQL releases.

See the section on Updating an Existing Oracle NoSQL Database Deployment in the Admin Guide.

New Features:

  1. This release provides the ability to add storage nodes to the system after it has been deployed. The system will rebalance and redistribute the data onto the new nodes without stopping operations. See Chapter 6, of the Admin Guide, Determining your Store’s Configuration, for more details.
  2. A new oracle.kv.lob package provides operations that can be used to read and write Large Objects (LOBs) such as audio and video files. As a general rule, any object larger than 1 MB is a good candidate for representation as a LOB. The LOB API permits access to large values without having to materialize the value in its entirety by providing streaming APIs for reading and writing these objects.
  3. A C API has been added. The implementation uses Java JNI and requires a Java virtual machine to run on the client. It is available as a separate download.
  4. Added a new remove-storagenode plan. This command will remove a storage node which is not hosting any NoSQL Database components from the system’s topology. Two examples of when this might be useful are:

    A storage node was incorrectly configured, and cannot be deployed.
    A storage node was once part of a NoSQL Database, but all components have been migrated from it using the migrate-storagenode command, and the storage node should be decommissioned.


  5. Added the ability to specify additional physical configuration information about storage nodes including:
    • Capacity – the number of RepNodes the SN may host
    • Number of CPUs
    • Amount of memory to use
    • Specific directory paths (mount points) to use for RepNodes

    This information is used by the system to make more intelligent choices about resource allocation and consumption. The administration documentation discusses how these parameters are set and used. [#20951]

  6. Added Avro support. The value of a kv pair can now be stored in Avro binary format. An Avro schema is defined for each type of data stored. The Avro schema is used to efficiently and compactly serialize the data, to guarantee that the data conforms to the schema, and to perform automatic evolution of the data as the schema changes over time. Bindings are supplied that allow representing Avro data as a POJO (Plain Old Java Object), a JSON object, or a generic Map-like data structure. For more information, see Chapter 7 – Avro Schemas and Chapter 8 – Avro Bindings in the Getting Started Guide. The oracle.kv.avro package is described in the Javadoc. The use of the Avro format is strongly recommended. NoSQL DB will leverage Avro in the future to provide additional features and capabilities. [#21213]
  7. Added Avro support for the Hadoop KVInputFormat classes. A new oracle.kv.hadoop.KVAvroInputFormat class returns Avro IndexedRecords to the caller. When this class is used in conjunction with Oracle Loader for Hadoop, it is possible to read data directly from NoSQL Database using OLH without using an interim Map-Reduce job to store data in HDFS. [#21157]
  8. Added a feature which allows Oracle Database External Tables to be used to access Oracle NoSQL Database records. There is more information in javadoc for the oracle.kv.exttab package and an “cookbook” example in the examples/externaltables directory. [#20981] Javadoc

Step by step Oracle NoSQL Database with Hadoop

From Oracle, a step by step article to play round Oracle NoSQL database with Hadoop.

Introduced in 2011, Oracle NoSQL Database is a highly available, highly scalable, key/value storage based (nonrelational) database that provides support for CRUD operations via a Java API. A related technology, the Hadoop MapReduce framework, provides a distributed environment for developing applications that process large quantities of data in parallel on large clusters.

In this article we discuss integrating Oracle NoSQL Database with Hadoop on Windows OS via an Oracle JDeveloper project (download). We will also demonstrate processing the NoSQL Database data in Hadoop using a MapReduce job.


Access the Oracle’s official tutorial

MySQL 5.6 DMR has been released

MySQL 5.6 Development Milestone Release has been released and introduces new features Focus on Improved Availability, Performance and Manageability for Web, Cloud and Embedded Applications

Redwood Shores, Calif. – April 10, 2012

News Facts

Today, Oracle announced a new Development Milestone Release (DMR) for MySQL 5.6, the world’s most popular open source database
Available for download in the MySQL Developer Zone, this MySQL 5.6 DMR delivers new replication features enhancing availability with self-healing recovery, increased performance, and improved manageability.
In addition to the new DMR, Oracle is providing early access to significant features under development for community testing and feedback through The features include online operations for ADD index and NoSQL access to InnoDB via the Memcached protocol.

MySQL 5.6 DMR Focuses on Enhanced Availability, Increased Performance and Improved Manageability

The new MySQL 5.6 DMR delivers:
Enhanced high availability with new replication features, including: Global Transactions Identifiers (GTIDs), enabling replication progress to be tracked through a replication topology, providing a foundation for self-healing recovery, and the ability to deploy more complex replication topologies without administrative overhead. Coupled with the new MySQL replication utilities to provide monitoring with automatic failover and switchover, GTIDs alleviate the need for additional third party High-Availability solutions, protecting web and cloud-based services against both planned and unplanned downtime.
New optimizer features for better throughput of complex queries, such as: Subquery optimizations: included in the optimizer path, allow developers to simplify application code by consolidating multiple queries or result sets into a single unit of work. CURRENT_TIMESTAMP: now part of the optimizer and used as the default for DATETIME columns, eliminates the need for the application to assign this value when blank by default. Faster range based queries: by using ready statistics vs. index based scans, improves the speed of queries with multiple range values. Faster filesort and ORDER BY queries: by selecting the best query execution method at optimization vs. parsing stage. Quick and easy readability: with EXPLAIN output delivered in JSON format.
An improved PERFORMANCE_SCHEMA enables better in-depth optimization of application performance and analysis of the MySQL environment with new query statement summaries and a new host_cache diagnostics table.
The following key features are also available through, for early testing and feedback from the MySQL community:
Online Operations for ADD Index: improve InnoDB’s availability and performance by enabling true online, non-blocking ADD index operations, and enable faster and simpler schema evolution to support rapidly evolving Web services.
High performance NoSQL access to InnoDB from Memcached: provides the flexibility of using NoSQL techniques to access InnoDB data alongside the existing SQL query model.
Additional performance improvements on modern hardware: increasing InnoDB query performance by better handling frequently updated hot data regions in multi-core CPUs.

Supporting Quote

“Working with the user community, Oracle continues to lead MySQL innovation, delivering new and anticipated features and enhancements,” said Tomas Ulin, Oracle’s MySQL vice president of Engineering. “With this new MySQL 5.6 development milestone release, Oracle has further improved the performance, manageability and availability of the MySQL Database, making it an even better choice for web, cloud-based and embedded applications.”

Supporting Resources

The MySQL 5.6 development milestone release can be downloaded here. Terms, conditions and restrictions apply.

The Time For NoSQL Is Now

The Time For NoSQL Is Now is the conclusion made in a recent article by Andrew C. Oliver, practicing Oracle since 1998 and which thought Oracle was magical.


From its long experience he also share the following conclusion:

  • NoSQL solution requires less transformation which brings
    •  better the performance of the system
    • more automatic scalability
    • fewer bugs
  • In the end, applications almost always bottleneck on the DB
  • I truly think this is one technology that isn’t just marketing


You can read the full article available here:


Submitted by acoliver on Wed, 01/25/2012 – 11:08

In 1998 I had my first hardcore introduction to Oracle as well as HP/UX. I’d been working with SQL Server. I thought Oracle was magical. Unlike SQL Server there were so many knobs to turn! I could balance the crap out of the table spaces and rollback segments and temp segments. Nothing would ever have to be contending for IO on the same disk again (if only someone would buy enough disks)! HP/UX oddly led me to Linux. I had a graphical workstation and a Windows machine on my desk. The graphical workstation rarely remained in working order. A co-worker who had quit Red Hat, (before the IPO!) to join me at Ericsson USA, introduced me to Red Hat Linux 5.0. The great thing about it was that the X-Windows implementation allowed me to connect to the HP/UX box’s X-Windows with no problems. Eventually, I came to prefer Unix and Linux to Windows because they never seemed to crash and on relatively old hardware they performed better.

At some point, due to turnover, I became the final person around who knew how to care and feed Oracle. I knew what all the mystical ORA- numbers meant. Oracle was far better/faster for reporting than SQL Server. However, in normal business applications, not only was SQL Server cheaper but it didn’t need constant attention, care and feeding. Over the next 10 years, I watched the industry homogenize. Sure, SQL Server is around and far better than the one I used, but every large company I’ve worked with has an Oracle site license. Even the “Microsoft Shop” tends to have Oracle around for the big stuff.

I’ve made hundreds of thousands if not a million dollars tuning Oracle, caring for Oracle and scaling Oracle. I’ve written ETL processes, I’ve tuned queries, I’ve done PL/SQL procedures that call into other systems and even into caches to squeak a little more performance. I’ve scaled systems with millions of users on Oracle. The trouble with Oracle is that it is both frequently misused and that it really isn’t very scalable. I’m not saying to can’t make it scale, just saying it is expensive to do (the license costs are the tip of the iceberg) and that it is difficult work to do so.

The problem is not transactions so much as the relational model combined with the process model. You can work around these with flatter table structures and by using different instances for different data (think of the lines for voting A-N, O-R, S-Z), but that is work! Oracle RAC sorta makes things better on the read side, but with all new headaches and often with worse write performance. You can add a cache like Gemfire or Infinispanand indeed these are good solutions for the interim where you can’t fix the Oracle. However, fundamentally you’re trying to fix a broken foundation with struts and support beams. You can shift the weight, but really you’re not addressing the actual problem.

NoSQL databases, especially document databases like MongoDB or Couch, structure the data the way your system uses it. They shard the data automatically, they store your actual JSON structure without all of the transformation like Hibernate or JPA. The less transformation the better the performance of the system, the more automatic the scalability concerns, the fewer bugs! I don’t usually jump on bandwagons: the new language of the week (all compile to the same thing, none have significant productivity gains when you have a team size of more than say 2), whooo touchpads (I want a keyboard), filesystem of the day (I kept ext3 until I switched to an SSD drive), however, this particular bandwagon truly is a game-changer and completely necessary for cloud/Internet scale applications.

Yes SQL databases are completely fine for a departmental IT system. While Open Software Integrators does a lot of varied work with applications that don’t need to handle 8 million users, I don’t personally work on those applications. Most of the systems I work on are at least dealing with thousands to hundreds of thousands and in some cases millions of users. In the end, applications almost always bottleneck on the DB and most of what I do for customers is actually DB consulting in the end. The transition to NoSQL databases will take time. We still don’t have TOAD, Crystal Reports, query language standardization and other essential tools needed for mass adoption. There will be missteps (i.e. I may need a different type of database for reporting than for my operational system), but I truly think this is one technology that isn’t just marketing.


IBM answering to Oracle NoSQL database

Following the recent Oracle attack on the NoSQL market ,with the announcement of its Orcale NoSQL solution,  IBM ‘s response didn’t last and unveil its plans to roll out NoSQL technology inside the DB2 product line.


According to Curt Cotner, the company’s vice president and chief technology officer for database servers, who spoke yesterday during a keynote address at IBM’s Information On Demand 2011 conference:

 “All of the DB2 and IBM Informix customers will have access to that and it will be part of your existing stack and you won’t have to pay extra for it,” Cotner said. “We’ll put that into our database products because we think that this is [something] that people want from their application programming experience, and it makes sense to put it natively inside of DB2.”

IBM’s plan to roll out NoSQL technology inside of DB2 made sense to conference attendee Gerard Ruppert, an IT consultant with John Daniel Associates in McKees Rocks, Pa.

“I think ultimately [IBM has] to go there because of the size of the data that’s moving around nowadays,” Ruppert said. “But it’s going to be a learning curve for a lot of the midmarket people because they just don’t have that expertise yet.”

The appeal of NoSQL lies in its ability to handle large volumes of data faster and more efficiently than traditional relational database management systems, according to Ruppert. He advised that before taking advantage of the new technology, organizations should make sure they have the right skills in-house. Those that don’t should consider bringing in some outside expertise before things get messed up, he added.

“In our own practice, we often go in and clean up after other people who don’t know what they’re doing,” he said.

NoSQL database management systems have a reputation for helping organizations analyze so-called big data stores. But “the jury is still out” on whether the technology is right for handling transactional systems, such as those used by banks and other institutions to process things like credit card orders, online purchases and stock trades.

“I think that if you asked our database guys, they would say that they’re generally not seeing deployments of technology like that for OLTP [online transaction processing] purposes,” said Ted Friedman, a data management analyst with Stamford, Conn.-based IT research firm Gartner Inc. “The vast majority of the usage is going in the analytics direction.”

Friedman added that IBM’s decision to offer NoSQL capabilities is in line with other industry giants who have made Hadoop, NoSQL and big data announcements of late. For example, Oracle yesterday announced the general availability of its new NoSQL database.

“It’s consistent with how we see the relational database model evolving over time.” he said. “IBM is doing it and others are as well. You saw Oracle at OpenWorld the other week making announcements around Hadoop and NoSQL capabilities and you see Microsoft doing some other things, so it’s a really big deal.”


Oracle launches attack on NoSQL market

Better late than never, Oracle (the database sofware company) is finally entering the NoSQL market with a product.

No big code name here but a dead simple “Oracle NoSQL Database”, it’s a distributed key-value database designed to provide highly reliable, scalable and available data storage across a configurable set of systems that function as storage nodes. Storage nodes are replicated to ensure high availability, rapid fail over in the event of  a node failure and optimal load balancing of queries. Customer applications are written using an easy-to-use Java API to read and write data. The NoSQL Database links with the customer application, providing access to the data via the appropriate storage node for the requested key-value. The NoSQL Database provides easy administration via either a web console or command line interface.

The Oracle NoSQL Database aims to bring the following key features:

  • Simple Data Model
    • Key-value pair data structure, keys are composed of Major & Minor keys
    • Easy-to-use Java API with simple Put, Delete and Get operations
  • Scalability
    • Automatic, hash-function based data partitioning and distribution
    • Intelligent NoSQL Database driver is topology and latency aware, providing optimal data access
  • Predictable behavior
    • ACID transactions, configurable globally and per operation
    • Bounded latency via B-tree caching and efficient query dispatching
  • High Availability
    • No single point of failure
    • Built-in, configurable replication
    • Resilient to single and multi-storage node failure
    • Disaster recovery via data center replication
  • Easy Administration
    • Web console or command line interface
    • System and node management
    • Shows system topology, status, current load, trailing and average latency, events and alerts


All product details are available on Oracle website:

MySQL 5.6 new features unveiled

From an Oracle press release today, mysql 5.6 new features have been made available for community to test.

From the press release:

These latest open source features are focused on better scalability, performance and flexibility.
Enhancements include the InnoDB storage engine, to provide support for full text search, greater performance for write-intensive applications, and better scalability under high concurrency/user loads.
New and improved MySQL replication features help with performance, scale-out and data integration.
Oracle is providing early access to MySQL 5.6 features which are in active development, to enable customers and the MySQL community to provide feedback. After development is complete, these features are intended to move into future Development Milestone and General Availability Releases.

Find out more information on: