Wednesday Apr 16, 2014

RMAN Backups using Cloud Control

Friends, a technical article was recently published on the Oracle Technical Network:

Back Up a Thousand Databases Using Enterprise Manager Cloud Control 12c

This detailed technical article explains the set up and scheduling of full and incremental RMAN Database backups for  thousands of databases using Enterprise Manager 12c, and how this is done more easily and efficiently than the older, more time-consuming, manual method of performing Unix shell scripting, RMAN scripting, and CRON jobs for each database to be backed up.

And with the Database Group Backup feature new to Enterprise Manager 12c, it can be even faster to set up RMAN backups for multiple databases - even if there are thousands - that are part of an Enterprise Manager Database Group (one kind of target group).


The article also highlights the advantages of using Pluggable Databases (PDBs) in Oracle Database 12c and backing them up using RMAN. RMAN cannot backup individual schemas, and it has always been difficult to perform point-in-time-recovery (PITR) at an individual schema level, since schemas can easily be distributed across multiple tablespaces. The advantage in using PDBs in a Container Database is that you can easily set up RMAN backups at the Container Database level, and yet perform PITR at the PDB level. This is a clear technical advantage of the Multi-tenant architecture of Oracle Database 12c.

The set up and scheduling of RMAN database backups forms a part of the Base Database Management features of Enterprise Manager that enables numerous customers to get familiar with the day-to-day use of Enterprise Manager 12c. The full list of Base Database Management features can be found in the Enterprise Manager Licensing Information guide here.

In fact I had personally introduced Enterprise Manager to one of India’s largest financial services organizations in India in 2007 for the purpose of their RMAN backups, they started using it for the first time, and today we are proud to say that they are an Enterprise Manager reference customer who have presented in OOW for the last 2 years. The following slide is from their recent OOW presentation.


One thing I forgot to include in the article (and yes, it is a long article) was on reporting of the RMAN backups. A few readers asked me that question after the article’s publication, both inside and outside Oracle.

I told them that if they were using an RMAN catalog, the catalog would have this information and could easily be queried. If they were not using a catalog, then this backup information would be stored in the control file, and they would have to query each database’s control file (using V$ views) to get the backup report. BI Publisher, installed as an add-on to Enterprise Manager, could be used for this purpose. However note that if BI Publisher is used to query information from a source other than the Enterprise Manager repository database, a license is payable for each database it accesses.

Read the full article at “Back Up a Thousand Databases Using Enterprise Manager Cloud Control 12c”, and enjoy the world of Oracle Enterprise Manager.

Regards,

Porus Homi Havewala (OCM 11g/10g).

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


Tuesday Apr 08, 2014

Consolidated Database Replay: Playing Nice Together

Here is a great article from resident Oracle ACE, Arup Nanda, who details insight into predicting the impact of consolidating separate database workloads into one. The article outlines a typical consolidation scenario and explains how Oracle Real Application Testing's Consolidated Database Replay capabilities can help measure the impact of the workload consolidation. A must read for those considering a consolidation project in the near future. Read the article.


Database work load patterns of two applications.


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

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

Friday Mar 28, 2014

Oracle Database 2 Day + Performance Tuning Guide

Great Resource for Learning Oracle Database 12c and Oracle Enterprise Manager 12c

The guide includes coverage of Oracle Diagnostics Pack and Oracle Tuning Pack features such as Automatic Database Diagnostic Monitor (ADDM), Active Session History (ASH) Analytics, SQL Tuning Advisor, Real-time SQL Monitoring and more. Download the PDF or HTML verision.

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

Tuesday Mar 18, 2014

Oracle OpenWorld 2014 Call for Proposals is now open!

It's that time of year again...the Oracle OpenWorld 2014 Call for Proposals is now open!

Information about the OpenWorld 2014 Call for Proposals is available at the following URL:

http://www.oracle.com/openworld/call-for-papers/index.html

We are told the Call for Proposals will remain open from March 18th until April 15th, 2014.   

We've got a tough act to follow this year for OpenWorld 2014, because last year at OpenWorld 2013, we shattered all previous records for customer and partner participation in Oracle Enterprise Manager activities.  We were thrilled to showcase such a diverse set of customer case studies, best practices and expert advice across a wide variety of Oracle Enterprise Manager disciplines.  A few of last year's highlights are captured in earlier editions of this blog, but there were many, many more:

We take the opportunity to showcase our customers and partners very seriously, and encourage both experienced and new presenters to participate.  We promise to review all submissions carefully.  

Please take this opportunity to make OpenWorld 2014 an even better event for you and for Oracle Enterprise Manager by submitting your proposal before April 15.

Thanks in advance for your creativity and enthusiasm.  We look forward to reading your proposals.

 

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.

Thursday Feb 27, 2014

Fast Recovery Area for Archive Destination


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 Metric 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

[Read More]

Tuesday Feb 25, 2014

Focus on Oracle Applications Management at Collaborate14

There is a lot of focus on advanced management tools in Enterprise Manager Cloud Control 12c (EMCC) for Oracle Applications at Collaborate14!

For the purposes of this article, "Oracle Applications" refers to Fusion Applications, E-Business Suite, PeopleSoft, Siebel, and J.D. Edwards EnterpriseOne. The cornerstone of Oracle’s strategy for managing their Applications is Oracle Enterprise Manager Cloud Control and the Application Management Suites (AMS). AMS allows customers to achieve a high level of application performance, introspection, and availability, while reducing the costs associated with managing these Applications. There are a number of sessions that showcase these products at Collaborate14, including:

There is a lot of focus on advanced management tools in Enterprise Manager Cloud Control 12c (EMCC) for Oracle Applications at Collaborate14!

For the purposes of this article, "Oracle Applications" refers to Fusion Applications, E-Business Suite, PeopleSoft, Siebel, and J.D. Edwards EnterpriseOne. The cornerstone of Oracle’s strategy for managing their Applications is Oracle Enterprise Manager Cloud Control and the Application Management Suites (AMS). AMS allows customers to achieve a high level of application performance, introspection, and availability, while reducing the costs associated with managing these Applications.

Below is a listing of the Apps Management sessions. To get the detailed abstracts, go to the Collaborate14 Session Scheduler and provide the Session ID in the search box.  A complete listing of all Enterprise Manager activities at Collaborate14 is located here.

Title Date & Time Room Session ID
Workshop: Simplify, Automate, and Enhance Management of E-Business Suite (EBS) Applications

Monday, April 7

1:00 PM - 4:00 PM

Level 1

Sands 101

15526
Oracle Presentation: Oracle E-Business Suite Plug-In for Enterprise Manager – Features and Roadmap

Thursday, April 11

4:15 PM - 5:15 PM

Level 1

Sands 309

15260
Customer Presentation: PeopleSoft Application and System Monitoring Basics

Wednesday, April 9

4:30 PM - 5:30 PM

Level 4

Marcello 4405

101140
Oracle Presentation: Migrating From Applications Unlimited (E-Business Suite, PeopleSoft, Siebel) to Fusion Applications

Thursday, April 10

8:30 AM - 9:30 AM

Level 1

Casanova 605

15254
SIG Meeting: OAUG Enterprise Manager Informational Session/SIG Formation

Thursday, April 10

3:00 PM - 4:00 PM

Level 1

Marco Polo 703

15368

Note that Monday's Workshop environments for the hands-on portion are provided by Apps Associates, an Oracle Enterprise Manager 12c "Specialized" partner. These environments are provisioned using an Amazon Web Services (AWS) platform. More about Apps Associates is at www.appsassociates.com and info about their AWS Test Drive Labs is at www.appsassociates.com/awslabs

Finally, one sure place that you can always get the latest information is at our Kiosk #7 “Total Control for Oracle Applications” located in the Applications area of the Oracle Demogrounds. Be sure to stop by the kiosk to speak with our Application management experts.  A complete listing of all Enterprise Manager activities at Collaborate14 is available here.

We look forward to seeing you in Las Vegas!

Tuesday Feb 18, 2014

Monitoring Archive Area % Used on Cluster Databases


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. Database Instance

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.


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