Monday Jun 23, 2014

Patch automation of Data Guard Databases takes a leap with EM12cR4


Patching has always been one of the many joys (or dreads) of Oracle DBAs. 
The effort compounds as the Database sprawl grows and the architecture complexity increases.  Additionally,  there is an increasing pressure to patch the systems with minimal or zero downtime. EM12c's Database patch automation functionality provides  an end-to-end management starting with proactive patch recommendations (like quarterly PSUs and CPUs), complete pre-flight checker to ensure predictable patching during maintenance window and  automation for patching the comprehensive list of products under the Oracle Database family.  ( EM12c Patch Automation overview

Patching has always been one of the many joys (or dreads) of Oracle DBAs. The effort compounds as the Database sprawl grows and the architecture complexity increases. Additionally, there is an increasing pressure to patch the systems with minimal or zero downtime. 

EM12c's Database patch automation functionality provides an end-to-end management starting with proactive patch recommendations (like quarterly PSUs and CPUs), complete pre-flight checker to ensure predictable patching during maintenance window and  automation for patching the comprehensive list of products under the Oracle Database family.  ( EM12c Patch Automation overview)

With the introduction of "Out of Place" patching in EM12c, the automation feature got a complete overhaul. Over the past 3 years I have seen customers moving to this mode to achieve their automation goals.  ( What is Out of Place?)

Patching Data guard environments (read as Primary and its corresponding Standby Databases) has always been a challenging task for the DBAs. 
In addition to handling the differences in steps needed for the configuration, the very nature of its distributed environment and incorporating any additional custom tasks makes it more demanding. Till now in EM we only supported automation in disparate steps and in “In Place” mode.

Starting 12.1.0.4 (EM12c R4), the support is enhanced to be more tighter, can be done in 'Out of Place' mode, and has new supplemental features to manage the process along with its additional tasks.

In this post we will take a closer look of the data guard stand by patching feature and then dive into a use case, you could try out in your environment.

[Read More]

Creating a Network Aggregated Link with Ops Center (12R2)

Contributed by Juergen Fleischer and Mahesh Sharma.

In this short blog we will use Ops Center to create Link Aggregation. This will allow us to combine multiple network connections in parallel to increase the throughput and provide redundancy.

If you recall from the ""Ops Center 12.2: Creating a CDOM - Detaching Unused PCIe Buses - Adding PCIe Buses", we created the CDOM with just one network connection (net0, ixbge2), this was from pci_0 which is the onboard bus. Pci_0 also had device ixgbe3 attached which we did not configure during provisioning.

In the “"Ops Center 12.2: Creating a CDOM - Detaching Unused PCIe Buses - Adding PCIe Buses" blog we also attached another PCIe bus (pci_1) to the Control Domain, which gave us another two network devices (ixbge0 and ixbge2) as seen below.

So to summarize we have the following devices:

Link PCIe Bus Physical Device
net0 pci_0 (on board) ixgbe2
net1 pci_0 (on board) xgbe3
net4 pci_1 xgbe0
net5 pci_1 xgbe1

The idea here is that net1, net4 and net5 will be connected to our Production network on the CDOM. As mentioned above we would like to combine the Nets to provide some redundancy and better throughput.

So, let us create the aggregated link with Ops Center.

From: Navigation -> Assets , select the CDOM OS Asset as shown below:

From the tabs in the middle panel select "Networks" then "Link Aggregations". Click on green plus sign “Create Link Aggregations”

From the next screen, specify an aggregation name and move the nets from “Available Network Interfaces” to “Link Aggregation Members”, as shown below:

The next screen allows you to configure the Links:

The last step is to review the Summary and click Finish.

Let’s confirm these changes have taken place by command line and from the Ops Center BUI.

From the command line, log on to the Control Domain and run the following:

We can see we have an aggregated link called aggr0, which consisting of net 1, 4 and 5.

This can also be seen from the BUI.

Hope this helps!






About

Latest information and perspectives on Oracle Enterprise Manager.

Related Blogs




Search

Archives
« June 2014 »
SunMonTueWedThuFriSat
1
2
5
7
8
11
12
14
15
21
22
25
28
29
30
     
       
Today