If you are using Fast Recovery Area (FRA) for the archive
destination and the destination is set to USE_DB_RECOVERY_FILE_DEST,
you may notice that the Archive Area % Used metric does not trigger
anymore. Instead you will see the
Recovery Area % Used metric trigger when it hits a Warning threshold of 85%
full, and Critical of 97% full. As this metric is controlled by the server side database thresholds
it cannot be modified by Enterprise Manager (see MOS Note 428473.1
for more information). Thresholds of 85/97 are not sufficient for
some of the larger, busier databases. This may not give you enough time
to kickoff a backup and clear enough
logs before the archiver hangs. If you
need different thresholds, you can easily accomplish this by creating a
Extension (ME) and setting thresholds to your desired values. This blog
will walk through an example of creating an ME to monitor archive on
FRA destinations, for more information on ME's and how they can be used,
refer to the Oracle Enterprise Manager Cloud Control Administrator's Guide.
One of the most critical events to monitor on an Oracle Database
is your archive area. If the archive
area fills up, your database will halt until it can continue to archive the
redo logs. If your archive destination
is set to a file system, then the Archive Area % Used metric is often the best
way to go. This metric allows you to
monitor a particular file system for the percentage space that has been
used. However, there are a couple of things
to be aware of for this critical metric.
Cluster Database vs.
You will notice in EM 12c, the Archive Area metric exists on
both the Cluster Database and the Database Instance targets. The majority of Cluster Databases (RAC) are
built against database best practices which indicate that the Archive
destination should be shared read/write between all instances. The purpose for this is that in case of
recovery, any instance can perform the recovery and has all necessary archive
logs to do so. Monitoring this
destination for a Cluster Database at the instance level caused duplicate
alerts and notifications, as both instances would hit the Warning/Critical
threshold for Archive Area % Used within
minutes of each other. To eliminate duplicate
notifications, the Archive Area % Used metric for Cluster Databases was
introduced. This allows the archive
destination to be monitored at a database level, much like tablespaces are
monitored in a RAC database.
In the Database Instance (RAC Instance) target, you will notice
the Archive Area % Used metric collection schedule is set to Disabled.
If you have a RAC database and you do not share archive
destinations between instances, you will want to Disable the Cluster Database
metric, and enable the Database Instance metric to ensure that each destination
is monitored individually.
Database Testing for Improved Agility and Cost Savings
Wednesday, February 26, 2014
10:00 AM PST | 1:00 PM EST
Join us in a webcast to learn how Oracle Real Application Testing—an
Oracle Database 12c, Enterprise Edition option and Oracle Enterprise Manager
12c—work together to provide an easy-to-use solution for making
changes to your mission-critical database. Learn from Oracle experts about
the new Oracle Real Application Testing capability, SQL Performance Analyzer
(SPA) Quick Check. It lets DBAs run quick validations on production databases
for any system change.
Discover how SPA Quick
Check helps to:
Safely test and
deploy system changes using real workloads
scenarios for better resource management
Improve the quality
of service for business agility and uptime
effort and risks for database changes
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.
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.”
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.
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."
Tuesday, December 3 , 2013
Time: 7:00 a.m. PST | 10:00 p.m. EST
Manager 12c Snap Clone allows administrators to create fully functional
copies of databases using the copy-on-write capabilities of the underlying
storage layer. Users can request databases from Oracle Enterprise Manager
12c's self-service portal and have them provisioned within minutes instead
of hours while keeping storage needs to a minimum. Part of Oracle Enterprise
Manager 12c Cloud Management Pack for Oracle Databases, Snap Clone can
fundamentally improve the efficiency and agility of administrators and
QA engineers while saving storage costs and other capital expenses.
Join us for this webcast
to learn how Oracle Enterprise Manager 12c Snap Clone can help:
copy-on-write technologies for fast provisioning
with other Oracle Enterprise Manager 12c Lifecycle Management features,
such as data masking and sub-setting
across multiple database snapshots to restore and access past data
overhead from integrated lifecycle management
Thursday, November 21, 2013
Time: 10:00 a.m. PST | 1:00 p.m. EST
Time and Costs, Reduce Complexity
Database as a service
(DBaaS) offers a variety of benefits to help companies improve operations
and move faster to the cloud. Using Oracle Multitenant—a new option
for Oracle Database 12c featuring pluggable databases—and Oracle
Enterprise Manager 12c, companies can make the most of those benefits.
Join us for the webcast
and learn how Oracle technology can help:
of database clouds through self-service
with unique automation capabilities
Self-Service Driven Provisioning of Pluggable Databases
announced new capabilities that support managing the full lifecycle
of pluggable database as a service in Oracle Enterprise Manager 12c
Release 3 (126.96.36.199). This latest release builds on the existing capabilities
to provide advanced automation for deploying database as a service using
Oracle Database 12c Multitenant option. It takes it one step
further by offering pluggable database as a service through Oracle Enterprise
Manager 12c self-service portal providing customers with fast
provisioning of database cloud services with minimal time and effort.
is a significant addition to Oracle Enterprise Manager 12c’s
existing portfolio of cloud services that includes infrastructure as a
service, database as a service, testing as a service, and Java platform as a service. The solution
provides a self-service mechanism to provision pluggable databases allowing
users to request and access database(s) on-demand. The self-service operations
are also enabled through REST APIs allowing customers to integrate with
third-party automation systems or their custom enterprise portals.
provisioning allows rapid access to pluggable database as a service
for hosting or certifying applications on Oracle Database 12c
driven migration to pluggable database as a service in order to migrate
a pre-Oracle Database 12c database to a pluggable database
as a service model and test the consolidation strategy
service catalog for all approved pluggable database as a service configurations
which helps customers achieve standardization while catering to all
applications and users in the enterprise
guarantee via database resource manager (and IORM on Oracle Exadata)
that enables deployment of mixed workloads in a shared environment
role based access, and policy based management that enforces governance
and reduces administrative overhead
or showback which improves metering and accountability for services
consumed by each pluggable database
REST APIs that support integration with ticketing or change management
systems, and or with other self-service portals
administrative and maintenance overhead through self-managing automation
that allows for intelligent placement of pluggable databases
how pluggable database as a service works, watch this quick demo:
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) 188.8.131.52 (with Bundle Patches 1) to 184.108.40.206/ 220.127.116.11
b) 18.104.22.168 to 22.214.171.124
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 126.96.36.199 (with bundle patch1) /12.0.1.02 to 188.8.131.52, 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 184.108.40.206
MOS Note 1569883.1 EM 12c R3: Checklist for Upgrading Management Agents Version 12.1.0.x to 220.127.116.11
EM 18.104.22.168 Install and Upgrade collateral page(PPT,Recorded demo,Whitepapers) on OTN:http://www.oracle.com/technetwork/oem/install-upgrade/index.html
Understanding Enterprise Manager 22.214.171.124 Upgrade and Agent Upgrades
miss this opportunity to learn first-hand how Oracle Database 12c
and Oracle Enterprise Manager 12c bring together the next evolution
in self-manageability—so you can plug into the Cloud faster using
the power of Oracle Database 12c.
Join us for this live
webcast to discover new groundbreaking management capabilities for:
diagnostics and application tuning
Managing many pluggable
databases as one
database cloud services
Only Oracle Enterprise
Manager 12c offers customers maximum performance, enhanced automation,
and total control for Oracle Database 12c.
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
Here is a quick summary
of all the new Oracle Enterprise Manager 12c capabilities for Oracle Database
lifecycle management of multitenant databases: Support
for the entire lifecycle operations of multitenant databases that
comprise migration, creation, cloning, patching and tracking for compliance
data masking: Allows customers to maximize compliance and security
data in-flight as it is being copied from production
diagnostics: Improvements to Automatic
Database Diagnostic Monitor (ADDM) for real-time and proactive problem
detection, especially designed for catching short, transient performance
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
hub: Newly redesigned performance
home page that provides administrators with a single, at-a-glance
view of all performance data and advisors
Enterprise Manager Database Express 12c: An out-of-the-box,
lightweight, easy-to-use web-based
management solution for managing individual databases
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
database cloning allows administrators to create fully functional
copies of databases using the copy-on-write capabilities of the underlying
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.
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
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
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.
a Service at a Glance:
application schemas in a shared database deployment model
user (i.e. developers or testers) can provision one or more database
schema(s) with a dedicated database cloud service
can be based on workload characteristics and specifications
are guaranteed through Oracle Database Resource Manager
is done through quotas, retirement policies and chargeback plans
Oracle Data Vault for security isolation and control
when needs change
through ultimate consolidation of multiple database applications
productivity and increase efficiency with automated provisioning
Deploy schema as
a service implementations consistently using self-service profiles and
Metering and chargeback
helps keep track of resource consumption and usage for accountability
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
up Platform as a Service Zones
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.
each zone can be restricted based on the self-service user's credentials.
up 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.
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.
During this part
of the schema as a service set up, future reservations, archive retention
and duration of request can all be enabled.
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.
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.
The final step
in deploying schema as a service is to configure resource metering and
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