Thursday Nov 28, 2013

Database Cloning in Minutes using Oracle Enterprise Manager 12c Snap Clone

Date: Tuesday, December 3 , 2013
Time: 7:00 a.m. PST | 10:00 p.m. EST

Oracle Enterprise 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:

  • Leverage storage copy-on-write technologies for fast provisioning
  • Integrate cloning with other Oracle Enterprise Manager 12c Lifecycle Management features, such as data masking and sub-setting
  • “Time travel” across multiple database snapshots to restore and access past data
  • 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 Nov 13, 2013

Webcast: Delivering Pluggable Database as a Service

Date: Thursday, November 21, 2013
Time: 10:00 a.m. PST | 1:00 p.m. EST

Save 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:

  • Accelerate provisioning of database clouds through self-service
  • Facilitate consolidation with unique automation capabilities
  • Lower IT costs by managing many databases as one

Register Now!


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

Tuesday Nov 12, 2013

Automate RAC Cluster Upgrades using EM12c

One of the most arduous processes  in DB maintenance is upgrading Databases across major versions, especially for complex RAC Clusters.
With the release of Database Plug-in  (12.1.0.5.0), EM12c Rel 3 (12.1.0.3.0)  now supports automated upgrading of RAC Clusters in addition to Standalone Databases.

This automation includes:

  • Upgrade of the complete Cluster across the nodes. ( Example: 11.1.0.7 CRS, ASM, RAC DB  ->   11.2.0.4 or 12.1.0.1 GI, RAC DB) 
  • Best practices in tune with your operations, where you can automate upgrade in steps:
    Step 1: Upgrade the Clusterware to Grid Infrastructure (Allowing you to wait, test and then move to DBs).
    Step 2: Upgrade RAC DBs either separately or in group (Mass upgrade of RAC DB's in the cluster).
  • Standard pre-requisite checks like Cluster Verification Utility (CVU) and RAC checks
  • Division of Upgrade process into Non-downtime activities (like laying down the new Oracle Homes (OH), running checks) to Downtime Activities (like Upgrading Clusterware to GI, Upgrading RAC) there by lowering the downtime required.
  • Ability to configure Back up and Restore options as a part of this upgrade process. You can choose to :
    a. Take Backup via this process (either Guaranteed Restore Point (GRP) or RMAN)
    b. Set the procedure to pause just before the upgrade step to allow you to take a custom backup
    c. Ignore backup completely, if there are external mechanisms already in place. 

    Mass Upgrade of RAC using EM12c


High Level Steps:

  1. Select the Procedure "Upgrade Database" from Database Provisioning Home page.
  2. Choose the Target Type for upgrade and the Destination version
  3. Pick and choose the Cluster, it picks up the complete topology since the clusterware/GI isn't upgraded already
  4. Select the Gold Image of the destination version for deploying both the GI and RAC OHs
  5. Specify new OH patch, credentials, choose the Restore and Backup options, if required provide additional pre and post scripts
  6. Set the Break points in the procedure execution to isolate Downtime activities
  7. Submit and track the procedure's execution status. 

The animation below captures the steps in the wizard.  For step by step process and to understand the support matrix check this documentation link.

Explore the functionality!!

In the next blog, will talk about automating rolling Upgrades of Databases in Physical Standby Data Guard environment using Transient Logical Standby.

Monday Nov 11, 2013

Implementing Service Level Agreements in Enterprise Manager 12c for Oracle Packaged Applications

Contributed by Eunjoo Lee, Product Manager, Oracle Enterprise Manager.

Service Level Management, or SLM, is a key tool in the proactive management of any Oracle Packaged Application (e.g., E-Business Suite, Siebel, PeopleSoft, JD Edwards E1, Fusion Apps, etc.). The benefits of SLM are that administrators can utilize representative Application transactions, which are constantly and automatically running behind the scenes, to verify that all of the key application and technology components of an Application are available and performing to expectations.

A single transaction can verify the availability and performance of the underlying Application Tech Stack in a much more efficient manner than by monitoring the same underlying targets individually.

In this article, we’ll be demonstrating SLM using Siebel Applications, but the same tools and processes apply to any of the Package Applications mentioned above. In this demonstration, we will log into the Siebel Application, navigate to the Contacts View, update a contact phone record, and then log-out.

This transaction exposes availability and performance metrics of multiple Siebel Servers, multiple Components and Component Groups, and the Siebel Database - in a single unified manner. We can then monitor and manage these transactions like any other target in EM 12c, including placing pro-active alerts on them if the transaction is either unavailable or is not performing to required levels. The first step in the SLM process is recording the Siebel transaction. The following screenwatch demonstrates how to record Siebel transaction using an EM tool called “OpenScript”. A completed recording is called a “Synthetic Transaction”.

The second step in the SLM process is uploading the Synthetic Transaction into EM 12c, and creating Generic Service Tests. We can create a Generic Service Test to execute our synthetic transactions at regular intervals to evaluate the performance of various business flows. As these transactions are running periodically, it is possible to monitor the performance of the Siebel Application by evaluating the performance of the synthetic transactions. The process of creating a Generic Service Test is detailed in the next screenwatch. EM 12c provides a guided workflow for all of the key creation steps, including configuring the Service Test, uploading of the Synthetic Test, determining the frequency of the Service Test, establishing beacons, and selecting performance and usage metrics, just to name a few.

The third and final step in the SLM process is the creation of Service Level Agreements (SLA). Service Level Agreements allow Administrators to utilize the previously created Service Tests to specify expected service levels for Application availability, performance, and usage. SLAs can be created for different time periods and for different Service Tests. This last screenwatch demonstrates the process of creating an SLA, as well as highlights the Dashboards and Reports that Administrators can use to monitor Service Test results.

Hopefully, this article provides you with a good start point for creating Service Level Agreements for your E-Business Suite, Siebel, PeopleSoft, JD Edwards E1, or Fusion Applications. Enterprise Manager Cloud Control 12c, with the Application Management Suites, represents a quick and easy way to implement Service Level Management capabilities at customer sites.

Stay Connected:

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

Monday Nov 04, 2013

Announcing: Oracle Enterprise Manager 12c Delivers Advanced Self-Service Automation for Oracle Database 12c Multitenant

New Self-Service Driven Provisioning of Pluggable Databases

Today Oracle announced new capabilities that support managing the full lifecycle of pluggable database as a service in Oracle Enterprise Manager 12c Release 3 (12.1.0.3). 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.

This 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.

Benefits

  • Self-service provisioning allows rapid access to pluggable database as a service for hosting or certifying applications on Oracle Database 12c
  • Self-service 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
  • Single 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
  • Resource guarantee via database resource manager (and IORM on Oracle Exadata) that enables deployment of mixed workloads in a shared environment
  • Quota, role based access, and policy based management that enforces governance and reduces administrative overhead
  • Chargeback or showback which improves metering and accountability for services consumed by each pluggable database
  • Comprehensive REST APIs that support integration with ticketing or change management systems, and or with other self-service portals
  • Minimal administrative and maintenance overhead through self-managing automation that allows for intelligent placement of pluggable databases

To understand how pluggable database as a service works, watch this quick demo:


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

Saturday Nov 02, 2013

Sending notification after an event has remained open for a specified period

Enterprise Manager (EM) 12c allows you to create an incident rule to send a notification and/or create an incident after an event has been open for a specified period. Such an incident rule will help prevent premature alerts on issues that may correct themselves within a certain amount of time.

For example, there are some agents in an unstable network area, and often there are communication failures between the agents and the OMS lasting three, four minutes at a time. In this scenario, you may only want to receive alerts after an agent in that area has been in the Agent Unreachable status for at least five minutes.

Note: Many non-target availability metrics allow users to specify the “number of occurrences” or the number of consecutive times metric values reach thresholds before a notification is sent. It is best to use the feature for such metrics.


This article provides a step-by-step guide for creating an incident rule set to cater for the above scenario, that is, to create an incident and send a notification after the Agent Unreachable event has remained open for a five-minute duration.


Steps to create the incident rule

1.     Log on to the console and navigate to Setup -> Incidents -> Incident Rules.

Note: A non-super user requires the Create Enterprise Rule Set privilege, which is a resource privilege, to create an incident rule.


The Incident Rules - All Enterprise Rules page displays.


2.     Click Create Rule Set …

The Create Rule Set page displays.


3.     Enter a name for the rule set (e.g. Rule set for agents in flaky network areas), optionally enter a description, and leave everything else at default values, and click + Add.

The Search and Select: Targets page pops up.


Note:  While you can create a rule set for individual targets, it is a best practice to use a group for this purpose.



4.     Select an appropriate group, e.g. the AgentsInFlakyNework group. The Select button becomes enabled, click the button.

The Create Rule Set page displays.


5.     Leave everything at default values, and click the Rules tab.

The Create Rule Set page displays.


6.     Click Create…

The Select Type of Rule to Create page pops up.


7.     Leave the Incoming events and updates to events option selected, and click Continue.

The Create New Rule : Select Events page displays.


8.     Select Target Availability from the Type drop-down list.

The page shows more options for Target Availability.


9.     Select the Specific events of type Target Availability option, and click + Add.

The Select Target Availability events page pops up.


10.   Select Agent from the Target Type dropdown list.

The page expands.


11.   Click the Agent unreachable checkbox, and click OK.


Note: If you want to also receive a notification when the event is cleared, click the Agent unreachable end checkbox as well before clicking OK.


The Create New Rule : Select Events page displays.


12.   Click Next.

The Create New Rule : Add Actions page displays.


13.   Click + Add.

The Add Actions page displays.


14.   Do the following:

a.     Select the Only execute the actions if specified conditions match option (You don’t want the action to trigger always).

The following options appear in the Conditions for Actions section.

b.     Select the Event has been open for specified duration option.

The Conditions for actions section expands.

c.     Change the values of Event has been open for to 5 Minutes as shown below.

d.     In the Create Incident or Update Incident section, click the Create Incident checkbox as following:

e.     In the Notifications section, enter an appropriate EM user or email address in the E-mail To field.

f.     Click Continue (in the top right hand corner).

The Create New Rule : Add Actions page displays.


15.   Click Next.

The Create New Rule : Specify name and Description page displays.


16.   Enter a rule name, and click Next.

The Create New Rule : Review page appears.


17.   Click Continue, and proceed to save the rule set.

The incident rule set creation completes.

After one of the agents in the group specified in the rule set is stopped for over 5 minutes, EM will send a mail notification and create an incident as shown in the following screenshot.



In conclusion, you have seen the steps to create an example incident rule set that only creates an incident and triggers a notification after an event has been open for a specified period. Such an incident rule can help prevent unnecessary incidents and alert notifications leaving EM administrators time to more important tasks.

- Loc Nhan

About

Latest information and perspectives on Oracle Enterprise Manager.

Related Blogs




Search

Archives
« November 2013 »
SunMonTueWedThuFriSat
     
1
3
5
6
7
8
9
10
14
15
16
17
18
19
20
21
22
23
24
25
26
27
29
30
       
Today