Friday Apr 04, 2014

Webcast: Database Cloning in Minutes using Oracle Enterprise Manager 12c Database as a Service Snap Clone

April 10 — 7:00 a.m. PT | 10:00 a.m. ET | 4:00 p.m. CET
April 24 — 10:00 a.m. PT | 1:00 p.m. ET
May 8 — 7:00 a.m. PT | 10:00 a.m. ET | 4:00 p.m. CET
May 22 — 10:00 a.m. PT | 1:00 p.m. ET

Since the demands from the business for IT services is non-stop, creating copies of production databases in order to develop, test and deploy new applications can be labor intensive and time consuming. Users may also need to preserve private copies of the database, so that they can go back to a point prior to when a change was made in order to diagnose potential issues. Using Snap Clone, users can create multiple snapshots of the database and “time travel” across these snapshots to access data from any point in time.

Join us for an in-depth technical webcast and learn how Oracle Cloud Management Pack for Oracle Database's capability called Snap Clone, can fundamentally improve the efficiency and agility of administrators and QA Engineers while saving CAPEX on storage. Benefits include:

  • Agile provisioning (~ 2 minutes to provision a 1 TB database)
  • Over 90% storage savings
  • Reduced administrative overhead from integrated lifecycle management

Register Now!


Stay Connected:
Twitter |
Facebook | YouTube | Linkedin | Newsletter
Download the Oracle Enterprise Manager 12c Mobile app

Wednesday Apr 02, 2014

Cloud Odyssey in London

The Cloud Odyssey event happened in London recently. Here is the Storify from the event. Enjoy!

Stay Connected:
Twitter |
Facebook | YouTube | Linkedin | Newsletter
Download the Oracle Enterprise Manager 12c Mobile app

Tuesday Apr 01, 2014

Managing Pluggable Database as a Service: Questions and Answers

Since the launch of Oracle Enterprise Manager 12c Release 3, we have received tons of questions around managing Oracle Multitenant, an Oracle Database 12c Enterprise Edition option, and pluggable databases (PDBs)—more specifically; questions about pluggable database as a service (PDBaaS). In this blog, we provide answers to some of the common questions from people.

Question: What qualifies a database to be pluggable?
Answer: A pluggable database must be a current Oracle Database 12c database, configured for multitenant through a new enterprise edition option called Oracle Multitenant. It delivers a new architecture that allows a multitenant container database (CDB) to hold many pluggable databases (PDBs). An Oracle Database in the old architecture (a “non-CDB”) may be upgraded to the multitenant architecture via a simple process known as “adopting the non-CDB as a PDB”. A PDB is a self-contained, fully functional Oracle Database, and includes its own system, sysaux and user tablespaces. You can learn more about Oracle Multitenant and pluggable database in this whitepaper.

Can the pluggable databases be plugged and unplugged across multiple platforms such as Solaris, AIX, and Linux?
The pluggable database must be endian compatible. Cross endian operations require OGG, Data pump or restore from backup.

In terms of database consolidation, what are the differences between using VMs, dedicated schemas and pluggable databases?
To describe the advantages of using pluggable database vs. other consolidation methods, it can be best illustrated in a simply comparison table.


Comparison of Database as a Service Consolidation Models

Pluggable database combines the best of all the other models and offers excellent consolidation, isolation, manageability and is suitable for any application that is certified to run on Oracle Database 12c. With the other models, we see certain shortcomings. For example, server virtualization offers good isolation but creates compliance and administrative headaches. Schema based consolidation offers ease of management and patching, but limited isolation.

How do you track configuration drift with a pluggable database? I certainly understand drift in the container database, but in what ways would a pluggable database drift from its standard baseline?
This pertains to Configuration Drift Tracking via Oracle Enterprise Manager 12c. One can compare any two Enterprise Manager targets or a complete system such as an Oracle Exadata Database Machine. When you compare at the PDB level, they can differ in the tablespace names, the storage settings of tablespace with same name, or users, etc. Using Oracle Enterprise Manager to track drift, it is particularly useful in comparing difference in your development, testing, and production environments. It is even useful for comparing your standby systems to set standards for compliance requirements.

What is a zone? Is it physical? Regional?
The Oracle Enterprise Manager 12c Cloud resource model involves pooling the same target types where it’s combining similar hosts, databases, hardware or other similar resources in to a zone. Zones can therefore be defined by the boundary of the Cloud and exposed through Oracle Enterprise Manager 12c’s self-service portal. In terms of the pluggable database as a service model, you can create Oracle Multitenant container databases and group them to form a database pool that users can then draw from. When the self-service user provisions a pluggable database, they need to simply specify the Zone where they want to deploy. Internally, Oracle Enterprise Manager uses load or configuration driven algorithms to place the PDB in the right CDB.

What will be the DBA and SYSADMIN role in the pluggable DBaaS environment?
With pluggable databases you have common users and local users as well as common roles and associated privileges and local roles and associated privileges. You can isolate user/role/privilege to the PDB by defining only local user/role/privilege. To leverage the manage many as one, you would define common user/role/privilege to act on all PDBs or a subset of PDBs where the common user has create session privileges within the PDB. You would define DBA roles and SYSADMIN roles based on common and/or local user roles.

What if you need custom configurations on a pluggable database? Once the database is deployed via self-service how do you make changes?
Some parameters are modifiable at the PDB level. You would check v$parameter ISPDB_MODIFIABLE value to determine what can be changed. Some customization can be done at the CDB level; however, they would affect all PDBs for that CDB. Oracle Enterprise Manager’s self-service provides a TNS Connect string to connect to the PDB with the right privilege and execute “ALTER SYSTEM” for the parameters that are permissible to change.

If I'm an application developer and I request a database with a certain pre-defined service level, what level of permissions should I expect with that database? Am I getting DBA or SYSDBA privileges with that request?
It depends on what was negotiated as part of the service definition and associated user/role/privileges defined for that service.

Are the pluggable database as a service capabilities for Oracle Database 12c included in Oracle Enterprise Manager 12c? Do we need a plug-in? Do we need to license Oracle Enterprise Manager 12c Database Management Packs?
You need the Oracle Enterprise Manager 12c database and cloud plug-ins. License-wise; the self-service provisioning from Oracle Enterprise Manager is licensed as part of Cloud Management Pack for Database. The Oracle Multitenant option must be licensed if two or more PDBs are plugged into a single CDB.
Watch this short demo called “Using Pluggable Database as a Service (PDBaaS) Self-Service Portal” for a better understanding of deploying PDBaaS using Oracle Enterprise Manager 12c.

Which Oracle Enterprise Manager 12c Management Packs are required to be able to provide DBaaS?
You need the Oracle Enterprise Manager 12c Cloud Management Pack for Database and Oracle Enterprise Manager 12c Lifecycle Management Pack for Database to do database as a service. Both of which must be licensed.

If you have shared memory and background processes in the container database, how do you allocate server resources to a particular pluggable database? Can you assign specific amount of CPU cycles, RAM and IOPS for a given pluggable database?
SQL execution is scoped to the PDB as identified by the con_id created during session create. In Oracle Database 12c, Resource Manager (RM) has been extended to include support for Oracle Multitenant. Policies may be defined at the PDB level in terms of the simple-yet-powerful concepts of “caps” and “shares” to determine the allocation of resources between PDBs. In this way, resource manager can control allocation of CPU, sessions and parallel execution servers. Additionally, on Oracle Exadata, Resource Manager can also manage IO and network. Memory management currently is implicitly managed through SGA LRU algorithms and CPU share management.

What is the largest number of pluggable databases you can deploy on Oracle Exadata?
Currently the PDB limit per CDB is 252 PDBs. In Oracle Real Application Clusters environments such as Oracle Exadata, the density of PDB consolidation greatly increases as you may have multiple CDBs per physical server and 252 PDBs per CDB. The maximum limit would be bound by compute resource constraints/limits. And as mentioned in the question on Zone, Oracle Enterprise Manager gives an ability to combine multiple CDBs into a Pool and handle transparent placement. The Oracle Enterprise Manager self-service user therefore won’t be exposed to the underlying limit.

Can I use pluggable database as a service if the target database is 9i or 10g?
You would need to migrate the Oracle Database 9i, 10g and 11g databases to Oracle Database 12c non-CDB and convert them into pluggable databases. The architectural changes within Oracle Database 12c are not backward compatible.

Can Active Data Guard be configured for selective pluggable databases from a container database? I do not want all pluggable databases to have a standby.
In the current release, Oracle Active Data Guard operates at the container level, however, PDB annotations are tagged in the redo stream, so PDB operations on the primary are reflected on the standby.

Does RMAN support pluggable databases?
Scheduled backups are at the CDB layer and include all PDBs. Ad-hoc backups can be executed on individual PDBs. Individual PDBs can be restored from backup.

For complete details of managing pluggable database as a service, be sure to watch this webcast: Delivering Pluggable Database as a Service

Stay Connected:
Twitter |
Facebook | YouTube | Linkedin | Newsletter
Download the Oracle Enterprise Manager 12c Mobile app

Monday Mar 31, 2014

Munhowen to Reduce Maintenance Costs and TCO by More Than 50 Percent

Munhowen, a leading Luxembourg beverage distributor, decided to replace its existing IT environment. By selecting Oracle technology, including Oracle Real Application Clusters, Oracle Enterprise Manager, Oracle Linux and Oracle ZFS Storage Appliances, the company was able to enhance system performance and reduce maintenance costs associated with sustaining an optimal hardware environment.

Jean-Pierre Rasquin, CIO, Munhowen, explains: “Implementing Oracle Real Application Clusters, Oracle Enterprise Manager, and Oracle ZFS Storage Appliance helped us to significantly increase our IT environment’s availability, scalability, and manageability—providing superior support, tailored to our business needs, while helping us to reduce maintenance costs.” Read the press release.

Stay Connected:
Twitter |
Facebook | YouTube | Linkedin | Newsletter
Download the Oracle Enterprise Manager 12c Mobile app

Thursday Mar 27, 2014

Cisco Improves Service Quality with Self-Managing Automation

Learn how Cisco improves its database application service delivery using Oracle Enterprise Manager.


Stay Connected:
Twitter |
Facebook | YouTube | Linkedin | Newsletter
Download the Oracle Enterprise Manager 12c Mobile app

Wednesday Mar 26, 2014

Infographic: Database Manageability—Getting Ahead of the Curve

As a DBA, getting ahead of the demands of the job are challenging enough, day in and day out. A recent IOUG survey on database management sheds new light on some of the top challenges facing administrators. Here's an infographic breakdown on what you need to know.

Download the IOUG Survey.

Stay Connected:
Twitter |
Facebook | YouTube | Linkedin | Newsletter
Download the Oracle Enterprise Manager 12c Mobile app

Tuesday Mar 25, 2014

Demo: Setting Up a Database Cloud Self Service Portal for Data Cloning Using Snap Clone

This demo shows how to setup a database cloud self service portal for data cloning using Snap Clone in Oracle Enterprise Manager 12c.

Stay Connected:
Twitter |
Facebook | YouTube | Linkedin | Newsletter
Download the Oracle Enterprise Manager 12c Mobile app

Monday Mar 17, 2014

Installing a JDBC patch to an EM agent

If you have an Enterprise Manager 12c Release 3 or older agent monitoring database targets, Support may recommend that you install a JDBC (Java database connectivity) patch, such as patch 17591700, to prevent high CPU consumption by the agent.


JDBC patches, including 17591700, have readme files containing instructions for installing the patches to a database, not to an EM agent. This post provides an example of how to install a JDBC patch to an EM agent. It walks through the steps of installing patch 17591700 to an EM12c Release3 agent.


Here are the steps:

1.  Identify the version of the JDBC client in the Agent Binaries home.

  • Set the ORACLE_HOME environment variable to the Agent Binaries home.

$ setenv ORACLE_HOME /u01/em12/core/12.1.0.3.0


Note: One way to find out the Agent Binaries home is to look in file /etc/oragchomelist on the agent host. It should contain an entry for an agent install in the format of:

<Agent Binaries home>:<Agent home>

For example, file /etc/oragchomelist contains:

/u01/em12/core/12.1.0.3.0:/u01/em12/agent_inst



  • Run the following command to identify the version of the JDBC client.

$ $ORACLE_HOME/OPatch/opatch lsinv -details | grep 'Oracle JDBC/OCI Instant Client'
Oracle JDBC/OCI Instant Client           11.1.0.7.0

In this case, the version of the JDBC client is 11.1.0.7.0.


2.  Download the patch from MOS (My Oracle Support) website. The version of the JDBC client should match the version of the database for which the patch is intended. Stage the patch zip file, p17591700_111070_Generic.zip, on the agent host. I stage the patch in directory /u01/stage/jdbc_patch. I will refer to this location as the patch stage directory.


3.  Go to the patch stage directory and extract files from the zip file.

$ cd /u01/stage/jdbc_patch

$ unzip p17591700_111070_Generic.zip

Archive: p17591700_111070_Generic.zip

creating: 17591700/

inflating: 17591700/README.txt

creating: 17591700/files/

creating: 17591700/files/jdbc/

creating: 17591700/files/jdbc/lib/

inflating: 17591700/etc/xml/GenericActions.xml

inflating: 17591700/etc/xml/ShiphomeDirectoryStructure.xml


4.  Stop the agent.

$ /u01/em12/agent_inst/bin/emctl stop agent

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved.

Stopping agent ..... stopped.


5.  Install the patch.

  • Go to the <patch stage directory>/<patch number>.

$ cd /u01/stage/jdbc_patch/17591700

  • Run opatch apply command.

$ $ORACLE_HOME/OPatch/opatch apply

Oracle Interim Patch Installer version 11.1.0.10.0

Copyright (c) 2013, Oracle Corporation. All rights reserved.

Oracle Home : /u01/em12/core/12.1.0.3.0

Central Inventory : /u01/app/oraInventory

from : /u01/em12/core/12.1.0.3.0/oraInst.loc

OPatch version : 11.1.0.10.0

OUI version : 11.1.0.11.0

Log file location : /u01/em12/core/12.1.0.3.0/cfgtoollogs/opatch/17591700_Mar_17_2014_12_03_05/apply2014-03-17_12-03-05PM_1.log

Applying interim patch '17591700' to OH '/u01/em12/core/12.1.0.3.0'

Verifying environment and performing prerequisite checks...

Patch 17591700: Optional component(s) missing : [ oracle.dbjava.jdbc, 11.1.0.7.0 ]

Interim patch 17591700 is a superset of the patch(es) [ 16087066 ] in the Oracle Home

OPatch will roll back the subset patches and apply the given patch.

All checks passed.

Backing up files...

Rolling back interim patch '16087066' from OH '/u01/em12/core/12.1.0.3.0'

Patching component oracle.dbjava.ic, 11.1.0.7.0...

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc6.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc6.jar/oracle/jdbc/aq/AQNotificationEvent$EventType.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc6.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc6.jar/oracle/jdbc/aq/AQNotificationEvent.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc6.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc6.jar/oracle/jdbc/dcn/DatabaseChangeEvent$AdditionalEventType.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc6.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc6.jar/oracle/jdbc/dcn/DatabaseChangeEvent$EventType.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc6.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc6.jar/oracle/jdbc/dcn/DatabaseChangeEvent.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc6.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc6.jar/oracle/jdbc/driver/NTFAQEvent.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc6.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc6.jar/oracle/jdbc/driver/NTFConnection.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc6.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc6.jar/oracle/jdbc/driver/NTFDCNEvent.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc6.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc6.jar/oracle/jdbc/driver/NTFManager.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc6.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc6.jar/oracle/jdbc/driver/T4CConnection.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc6.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc6.jar/oracle/jdbc/driver/T4CTTIokpn.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc5.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc5.jar/oracle/jdbc/aq/AQNotificationEvent$EventType.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc5.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc5.jar/oracle/jdbc/aq/AQNotificationEvent.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc5.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc5.jar/oracle/jdbc/dcn/DatabaseChangeEvent$AdditionalEventType.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc5.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc5.jar/oracle/jdbc/dcn/DatabaseChangeEvent$EventType.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc5.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc5.jar/oracle/jdbc/dcn/DatabaseChangeEvent.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc5.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc5.jar/oracle/jdbc/driver/NTFAQEvent.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc5.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc5.jar/oracle/jdbc/driver/NTFConnection.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc5.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc5.jar/oracle/jdbc/driver/NTFDCNEvent.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc5.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc5.jar/oracle/jdbc/driver/NTFManager.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc5.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc5.jar/oracle/jdbc/driver/T4CConnection.class"

Updating jar file "/u01/em12/core/12.1.0.3.0/jdbc/lib/ojdbc5.jar" with "/u01/em12/core/12.1.0.3.0/.patch_storage/16087066_Feb_4_2013_04_52_18/files//jdbc/lib/ojdbc5.jar/oracle/jdbc/driver/T4CTTIokpn.class"

RollbackSession removing interim patch '16087066' from inventory

OPatch back to application of the patch '17591700' after auto-rollback.

Patching component oracle.dbjava.ic, 11.1.0.7.0...

Verifying the update...

Patch 17591700 successfully applied

Log file location: /u01/em12/core/12.1.0.3.0/cfgtoollogs/opatch/17591700_Mar_17_2014_12_03_05/apply2014-03-17_12-03-05PM_1.log

OPatch succeeded


6. Start the agent.

$ /u01/em12/agent_inst/bin/emctl start agent

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved.

Starting agent ............. started.


The above step completes the process of installing patch 17591700 to the 12.1.0.3 agent.

Friday Feb 07, 2014

VIDEO: Nationwide Deploys Database Applications 600% Faster

Watch the latest Nationwide video to see how they saved administrative time and effort using Oracle Enterprise Manager.



Stay Connected:
Twitter |
Facebook | YouTube | Linkedin | Newsletter
Download the Oracle Enterprise Manager 12c Mobile app

Thursday Jan 30, 2014

Oracle Enterprise Manager Helps Manage Systems for Gaia Mission

The Italian National Institute of Astrophysics (INAF) has selected Oracle to store, analyze and manage scientific data generated from the European Space Agency's Gaia mission. The mission sets out to provide in-depth 3-D mapping of the Milky Way galaxy over the course of the next 5 years. An estimated 1 petabyte of astronomical data (equivalent to 1 million gigabytes) will be collected and stored in Oracle Database with Oracle Enterprise Manager entrusted to manage the system.

The goal of the Gaia mission will give researchers a better understanding into how the Milky Way was formed and how it has evolved over time. According to Roberto Morbidelli, Scientific Operation Manager at INAF, "Our activity within the Gaia mission will provide a huge volume of information, a very precious heritage of astronomical data that will have to be stored for the whole 21st century and beyond. Oracle has demonstrated in other research contexts that it would be the ideal technological partner to manage scientific projects of this kind of size. Thus we are sure that it will be a successful choice for INAF too. Oracle has been selected for its technology’s reliability, scalability, availability and the appropriate technological evolution planned in the next years; also key was the competence showed by Oracle experts in the development of features useful to our research.”

Oracle Enterprise Manager will be deployed to help manage the multiple Oracle Database instances and Oracle Real Application Clusters. Oracle Enterprise Manager will be used to ensure reliable access to Gaia mission data, allowing for numerous third-party applications and systems that control and verify the correct functioning of satellites and astronomical instruments.

“We are proud to offer our technology to the Gaia mission, an international research project that is of both major importance and high ambition,” said Xavier Verhaeghe, Vice President, Technology & Big Data Oracle EMEA. “INAF’s choice is another confirmation of Oracle’s ability to easily manage the extreme challenges involved in processing petabytes of Big Data."

Follow the Gaia Mission on Facebook.
Read the press release.


Stay Connected:
Twitter |
Facebook | YouTube | Linkedin | Newsletter
Download the Oracle Enterprise Manager 12c Mobile app

Tuesday Sep 17, 2013

Oracle Enterprise Manager 12c Upgrade sessions at Oracle OpenWorld 2013

This year @ Oracle OpenWorld 2013 we have customers Wells Fargo and Colorcon sharing their success stories and real-life lessons about upgrading to Oracle Enterprise Manager 12.1.0.x. then come join us for the below session: 

https://oracleus.activeevents.com/2013/connect/sessionDetail.ww?SESSION_ID=9588&tclass

Stay Connected:

Twitter |  Face book |  You Tube |  Linked in |  Google+ Newsletter

Thursday Aug 22, 2013

Reduce Oracle Enterprise Manager 12c Patch Set Upgrade Downtime

As Product Manager for Oracle Enterprise Manager, one question that is often being asked to me is how much is the upgrade downtime and how it can be reduced? 

One easy way to reduce the downtime while doing patch set upgrades is to perform Software only upgrade and then shutdown the existing OMS for the upgrade. This approach will not completely eliminate the downtime but reduce it to a great extent. 

When I mention patch set upgrade, we cover following upgrade paths:

a) 12.1.0.1 (with Bundle Patches 1) to 12.1.0.2/ 12.1.0.3

b) 12.1.0.2 to 12.1.0.3

Following table compares the steps required for regular installation (OUI) and software only installation.


 As you may notices from the steps listed above, regular OUI upgrade requires stopping OMS before invoking runInstaller and keeping it down until the upgrade is complete. On the other hand Software only upgrade first copies the bits and sets up the environment before stopping OMS, thus reducing the upgrade downtime.

Next comes Agent upgrade. While we recommend Agent Upgrade Console (AUC) to upgrade agents from 12.1.0.1 (with bundle patch1) /12.0.1.02 to 12.0.1.3, sometimes it’s not clear what happens during the Agent upgrade and when is the actual downtime . So here are high level steps describing the complete process: 


The actual downtime while doing the agent upgrade is on step9 where we shut down your old agent. When the agent is in blackout from step 1 to 8 it still collect’s all the monitoring data so there is no loss. 

More Information: It is recommended to go through the below checklist notes before starting your upgrade 

MOS note 1568143.1 - EM 12c R3: Checklist for Upgrading Enterprise Manager Cloud Control from Version 12.1.0.x to 12.1.0.3

MOS Note  1569883.1 EM 12c R3: Checklist for Upgrading Management Agents Version 12.1.0.x to 12.1.0.3

Collateral :

 EM 12.1.0.3 Install and Upgrade collateral page(PPT,Recorded demo,Whitepapers) on OTN:http://www.oracle.com/technetwork/oem/install-upgrade/index.html

Understanding Enterprise Manager 12.1.0.3 Upgrade and Agent Upgrades
http://www.oracle.com/technetwork/oem/install-upgrade/em-12103-upgrade-1967205.pdf

Stay Connected:

Twitter |  Face book |  You Tube |  Linked in |  Google+ Newsletter


Friday Aug 02, 2013

Managing Oracle Database 12c

Oracle recently announced new management capabilities for Oracle Database 12c, providing customers with even more enhancements to improve productivity and manageability. The new Oracle Enterprise Manager 12c features are supported out-of-the-box with Oracle Database 12c. So whether you want to take advantage of the new Data Redaction capabilities at the security layer, or whether you want to take a look at some of the heat map capabilities in our Information Lifecycle Management or leverage the new performance management features, such as, Database Operations Monitoring or Enhanced Real-Time ADDM, you can use Oracle Enterprise Manager 12c to manage them all.

These new capabilities can be integrated with your standard monitoring and management that you already have in your environment without having to undertake any additional tools or any additional training. Simply install or upgrade to Oracle Enterprise Manager 12c and Oracle Database 12c and together these two products will let you plug into the Cloud.

Here is a quick summary of all the new Oracle Enterprise Manager 12c capabilities for Oracle Database 12c:

  • Complete lifecycle management of multitenant databases: Support for the entire lifecycle operations of multitenant databases that comprise migration, creation, cloning, patching and tracking for compliance
  • Consolidated database replay: Allows customers to test and plan their consolidation using Oracle’s multitenant container and pluggable database technology
  • At-source data masking: Allows customers to maximize compliance and security by masking data in-flight as it is being copied from production
  • Enhanced diagnostics: Improvements to Automatic Database Diagnostic Monitor (ADDM) for real-time and proactive problem detection, especially designed for catching short, transient performance issues
  • Real-time business operations monitoring: Monitors composite business operations such as; batch jobs and ETL operations, providing real-time reports on all SQLs and PL/SQLs executed inside the job
  • Performance hub: Newly redesigned performance home page that provides administrators with a single, at-a-glance view of all performance data and advisors
  • New Oracle Enterprise Manager Database Express 12c: An out-of-the-box, lightweight, easy-to-use web-based management solution for managing individual databases
  • Schema as a Service: This ultimate consolidation of databases lets administrators host multiple application schemas within a single database and offer database as a service to hundreds of application users without creating database sprawl
  • Snap Clone: Instant database cloning allows administrators to create fully functional copies of databases using the copy-on-write capabilities of the underlying storage layer

To learn more about all the latest capabilities, be sure to register for our upcoming webcast: Managing Oracle Database 12c with Oracle Enterprise Manager 12c.

Stay Connected:
Twitter |
Facebook | YouTube | Linkedin | Newsletter
Download the Oracle Enterprise Manager Cloud Control12c Mobile app

Tuesday Mar 12, 2013

WEBCAST: Delivering Database as a Service with Oracle Enterprise Manager 12c


Thursday March 14
10:00 a.m. PST / 1:00 p.m. EST

Join us for a live Webcast to find out about the recently released Oracle Enterprise Manager 12c plug-ins that deliver new capabilities and support for managing database cloud services with schema as a service for extreme database consolidation and quick efficient database cloning through Snap Clone or RMAN Backups. These new capabilities provide an optimum utilization of development and database resources giving customers more flexibility and control during application development, leading to a faster time-to-market for delivering IT services.

Register Now!

Stay Connected:
Twitter |
Facebook | YouTube | Linkedin | Newsletter
Download the Oracle Enterprise Manager Cloud Control12c Mobile app

Friday Mar 08, 2013

Schema as a Service for Extreme Consolidation

As we deal with Database as a Service use cases, we often find that consumers do not need dedicated databases of their own. Developers of a home-grown application, for example, might be satisfied with a logical slice of the database. This logical slice, leads us to the concept of Schema as a Service—a new capability offered in the latest release of Oracle Enterprise Manager 12c Release 2 Plug-in Update 1.

Schema as a service is the ultimate and extreme in consolidating multiple schemas in a shared database model. Cloud users can request one or more schemas, with or without seed data, from Oracle Enterprise Manager 12c’s out-of-the-box self service portal. It offers excellent manageability, not only for its fast efficient provisioning, but because administrators only need to manage a small number of databases.


Schema as a Service: Consolidate Multiple Schemas in a Shared Database Cloud Services Model

However, consolidation comes at the expense of isolation, because the operating system and database are not isolated among the database consumers. While enabling Schema as a Service, it’s important to isolate the workloads as much as possible to make sure that one user doesn't run away with all the database resources. Administrators can guarantee this does not happen by using Oracle Enterprise Manager 12c’s CPU monitoring capabilities built in to Oracle Database Resource Manager to maintain service levels.

For security, the more consolidated you get, the more concerns administrators have about data isolation and security. Using Oracle Data Vault can help resolve these issues. It is integrated with Oracle Enterprise Manager 12c, and administrators can use Oracle Data Vault to enable fine grain control based on roles and privileges within the database cloud service.

For reporting purposes, metering and chargeback capabilities can be implemented to help IT organizations gain in-depth visibility into resource consumption and expenses incurred with each schema as a service deployment. This is useful for regulatory compliance requirements as well.

Schema as a Service at a Glance:

  • Consolidate multiple application schemas in a shared database deployment model
  • Each application user (i.e. developers or testers) can provision one or more database schema(s) with a dedicated database cloud service
  • Automated placement can be based on workload characteristics and specifications
  • Service levels are guaranteed through Oracle Database Resource Manager
  • Service governance is done through quotas, retirement policies and chargeback plans
  • Integrated with Oracle Data Vault for security isolation and control
  • De-provision schemas when needs change

Benefits:

  • Save resources through ultimate consolidation of multiple database applications
  • Boost administrator productivity and increase efficiency with automated provisioning
  • Deploy schema as a service implementations consistently using self-service profiles and templates
  • Metering and chargeback helps keep track of resource consumption and usage for accountability and reporting
  • Minimize administrative overhead and compliance challenges by preventing database sprawl

How To:
There are several steps involved when setting up and deploying database schema as a service in Oracle Enterprise Manager’s self service portal. Here is a quick summary of what’s involved. For more details be sure to review the resources below.

1. Setting up Platform as a Service Zones

  • Before deploying your schema as a service, you first need to create a Platform as a Service (PaaS) infrastructure using Oracle Enterprise Manager 12c’s self-service portal. A PaaS Zone comprises multiple hosts, i.e. servers with Oracle Enterprise Manager 12c agent installed.
  • Use the portal to create a PaaS zone and organize it by function type (i.e. based on geography, line of business (sales, development) or application lifecycle. (i.e. dev, test, QA, production)
  • Next expose the PaaS zone to the self-service cloud users in the portal. For example, developers can now have the option to select a development PaaS zone or testers can select a QA zone.
  • Visibility of each zone can be restricted based on the self-service user's credentials.

2. Setting up Database Pools

  • Database pools are a collects of databases used to host schema as a service.
  • To create a new database pool, you can use a portion of resources that are available to the zone. Keep in mind that all members of the database pool need to be the same target type. For example, a single database instance or database cluster; platform, or same database version. This ensures provisioning consistency during deployment.
  • Next configure placement constraints and policies for the database pool. For placing databases within the pool and controlling how resources are utilization, you need to first create a placement constraint and set its policies. This provides protection for the database members within the pool for resource consumption. For example, a production database pool might enforce more conservative constraints whereas a development pool might allow liberal limits.
  • You can set a constraint for each database in the pool by services or by workload associated with the service request based on CPU and memory. You can also enable Oracle Database Resource Manager for the database pool to control your CPU usage and the underlying service levels.

3. Request Settings

  • During this part of the schema as a service set up, future reservations, archive retention and duration of request can all be enabled.

4. Quotas

  • Controlling quotas and setting limits for users based on role level can be assigned in this step of the process. Oracle Enterprise Manager supports quota based on CPU, memory and number of database services.

5. Profiles and Service Templates

  • A service template is standardized definition that is offered to self-service users to create a database or schemas within the deployment. A service template defines the workload characteristics and schema details that can be generated with or without seed data.
  • To create a service template with seed data, you need to create a profile. A profile is an entity that captures source database information for provisioning purposes. Once you create your service template it becomes part of a collection which makes up the service catalog. This catalog is then exposed to cloud users in the self-service portal.
  • Next, you can either export the seed data from the source database or export the schema definitions without the data. Once you decide, a Data Pump Export job will be created.
  • You can now map your newly created profile and service templates to the required zone(s) and database pools.

6. Chargeback

  • The final step in deploying schema as a service is to configure resource metering and chargeback.
  • Setting up metering and chargeback can easily be done in order to track resource usage within the schema as a service implementation.
  • For more information on how to set up chargeback we recommend reading this white paper.

LEARN MORE:

Product Info:
  • Oracle Cloud Management
  • Zero to Cloud Resource Center
  • Demos:
  • Oracle Cloud Management
  • Setting up Database Clouds for Schema as a Service
  • Whitepapers:
  • Delivering Database as a Service using Oracle Enterprise Manager 12c
  • Best Practices for Database Consolidation in Private Clouds
  • Oracle Enterprise Manager 12c: Metering and Chargeback
  • Cloud Management for Oracle Database

  • Stay Connected:
    Twitter |
    Facebook | YouTube | Linkedin | Newsletter
    Download the Oracle Enterprise Manager Cloud Control12c Mobile app
    About

    Latest information and perspectives on Oracle Enterprise Manager.

    Related Blogs




    Search

    Archives
    « April 2014
    SunMonTueWedThuFriSat
      
    3
    5
    6
    7
    9
    10
    11
    12
    13
    14
    15
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
       
           
    Today