Monday Jun 01, 2015

NEWS: Oracle Database Migration Assistant for Unicode 2.1

Oracle has released the Database Migration Assistant for Unicode (DMU) 2.1.

Here's what you need to know:

DMU provides an end-to-end solution for migrating your databases from legacy encodings to Unicode. Its user-interface greatly simplifies the migration process and lessens the need for character set migration expertise by guiding the DBA through the entire migration process as well as automating many of the migration tasks. Oracle DMU is the officially supported method for migrating Oracle 12c Pluggable Databases (PDBs) to the Unicode character set. Oracle DMU also supports migrating selected prior releases of Oracle Database 10.2, 11.1 and 11.2.

NOTE: The DMU repository schema has been updated in release 2.1. If you have an old repository installed with the 2.0 release, you will need to upgrade the repository using DMU 2.1 before you can perform any migration tasks with the DMU 2.1 software.


Here's what's interesting:  Migration to the Unicode character set is an intricate process that involves many time-consuming and resource intensive operations. Any misstep along the way can lead to data loss. Oracle DMU provides an end-to-end workflow that guides the DBA through a detailed and customizable migration process with real-time progress updates. Additional recovery and diagnostic mechanisms enable a fault-tolerant migration in the event of runtime contingencies.

New features in Oracle DMU 2.1 include:

  • DMU 2.1 offers a solution to achieve a near-zero downtime migration to Unicode by leveraging the DMU migration functionality in conjunction with the Oracle GoldenGate replication technology.
  • A DMU migration profile can be exported from one database instance and imported into another database instance created as a clone of the original instance.
  • Problem Data Report feature has been introduced to allow the detailed information about the data in the database objects containing convertibility issues to be generated into a spreadsheet file.
  • DMU 2.1 can detect and upgrade any existing DMU 2.0 repository in the database to the DMU 2.1 format and preserve the migration information so that the upgrade process is mostly transparent to the user without having to re-install the repository again.

Anything else you need to know about Oracle DMU 2.1?  Go to the Oracle DMU page on OTN

Ciao for now!


Tuesday May 19, 2015

Deploying a Database Cloud--And the Value of DBaaS Implementations

Hey, Hey DBAs--Do you have a plan for implementing a Database Cloud?

Here's what you need to know:

DBaaS is a cloud model that enables users to request database environments by choosing from a pre-defined service catalog using a self-service provisioning framework.

The key benefits of these database clouds are agility and faster deployment of database services.

Organizations are looking at DBaaS because it can simplify IT infrastructures and automate provisioning processes. So it makes it possible to deliver database functionality to many users and multiple divisions from the same hardware and software infrastructure.  

What's the ideal Oracle DBaaS configuration?

Start with Oracle Database 12c Its multitenant architecture option makes it possible to enable DBaaS as part of a comprehensive cloud strategy. It allows collections of pluggable databases to be easily managed as a single entity, which maximizes consolidation density and simplifies administration.

The next key element:  Oracle Enterprise Manager 12c. It's designed to manage the entire database cloud deployment lifecycle, from planning, testing and deployment to ongoing operations and performance monitoring.

Finally, the exceptional deployment platform for DBaaS:  Oracle Exadata.  A fully integrated and sophisticated engineered system from Oracle that supports multiple deployment models, multiple workloads and multiple service levels from one integrated, optimized platform.

So, start thinking about the Database Cloud, deploying DBaaS and the value it can bring to your environment.

Here are some expert resources to help you come up to speed.

Ciao for Now!

Friday May 15, 2015

Securing the Big Data Lifecycle

Let's talk about Securing the Big Data Lifecycle. 

We all have seen demos or attended tutorials with extraordinary examples of integrating, analyzing and making business decisions based on Big Data. And I always wonder...who's data is that anyway? Consider the nature and character of Big Data for a moment. What we have here is ubiquitous and indiscriminate data collection from a wide range of devices. Add to that unexpected uses of collected data, especially without customer consent. And that could possibly lead to unintended data breach risks with larger consequences.

It will be a great challenge.

You need a plan.

MIT Technology Review just released this whitepaper addressing these issues.

Give it a read to set your mind at ease about how to secure your data, no matter how big.

Ciao for Now!

Thursday May 14, 2015

Installing ODB12c on Oracle Solaris 11 in 5 Steps

Hey Hey DBAs:  You know you can  install and run Oracle Database 12c on different platforms, but if you install it on an Oracle Solaris 11 zone, you can take advantage of these capabilities:

  • Isolation - Database processes that execute in one zone have no access to database processes running in another zone. This isolation simplifies database consolidation, allowing multiple instances and versions to coexist safely on a single physical machine.
  • Independently Managed and Autonomous Environments - A non-global zone can be booted, patched, and shut down independently. A failure or reboot of one zone has no impact on other zones (unless, of course, a failure is due to a shared component). A zone reboot is faster than a full server reboot (seconds versus minutes), so a database in a rebooted zone is available more quickly.
  • Distinctive Identity - You can define virtual network interfaces for a zone, so you can give the database instance installed on that zone its own independent host name and IP address. You can also apply networking resource controls to zones, aligning network bandwidth consumption with service level targets.
  • Easy Database Instance Migration - If a database needs more CPU power, you can add CPUs to an Oracle Solaris Zone and reboot the zone. If a database needs more compute capacity than what's available in the physical server, you can migrate the zone to a larger server.
  • Hard Partitioning - Assigning a resource pool or capping CPU cores can configure Oracle Solaris Zones as hard partitions for Oracle Database licensing purposes. This can potentially lower database licensing costs.

So, you want to install Oracle Database 12c in an Oracle Solaris 11 zone...with hard partitioning?  This article from good friends Ginny Henningsen and Glynn Foster on the Oracle Solaris product management team shows you how to do it.  

Tech Article: 5 Steps to Installing Oracle Database 12c on Oracle Solaris 11

Ciao for Now!

Wednesday May 06, 2015

Schemaless Application Development with ORDS, JSON and SODA

There's a lot to talk about when it comes to JSON support in Oracle Database 12c. A big part of that story is Oracle REST Data Services 3.0, which was just released on May 4th. But there's more to it. Oracle 12c has a key set of API's:  Simple Oracle Document Access (SODA).   And it's important.

Here's the deal:

Oracle Database supports storing, indexing and querying JSON documents in the database. But the picture is completed by document-centric API's for accessing JSON documents.

Introducing Simple Oracle Document Access (SODA)

SODA, the set of APIs specifically designed to support schemaless application development.

There are 2 SODA implementations:

  1. SODA for Java-- a programmatic document-store interface for Java Developers that uses JDBC to communicate with the database. SODA for Java consists of a set of simple classes that represent a database, a document collection and a document. Methods on these classes provide all the functionality required to manage and query collections and work with JSON documents stored in an Oracle Database.

  2. SODA for REST-- a REST-based document store interface implemented as a Java servlet and delivered as part of Oracle REST Data Services (ORDS) 3.0. Applications based on SODA for REST use HTTP to communicate with the Java Servlet. The SODA for REST Servlet can also be run under the database's native HTTP Server. HTTP verbs such as PUT, POST, GET, and DELETE map to operations over JSON documents. Because SODA for REST can be invoked from any programming or scripting language that is capable of making HTTP calls, it can be used with all modern development environments and frameworks.

Want to see it in action?

Check out the oracle/json-in-db repository on Github. You'll find downloadable and installable demonstrations for the JSON capabilities of Oracle Database and later.

And get more details about Oracle as a Document Store from OTN.

Join the ORDS discussion space on the OTN Community Platform here.

Ciao for Now!


The OTN DBA/DEV Watercooler is your official source of news covering Oracle Database technology topics and community activities from throughout the OTN Database and Developer Community. Find tips and in-depth technology information you need to master Oracle Database Administration or Application Development here. This Blog is compiled by @oracledbdev, the Oracle Database Community Manager for OTN, and features insights, tech tips and news from throughout the OTN Database Community.


« August 2015