Erez Alsheich - GridControl

<Insert Picture Here>

Erez@valinor.co.il

RAC, ASM and Linux Forum, October 12, 2010

Erez Alsheich C.E.O

Managing Your RAC with

OEM – Grid Control

Erez@valinor.co.il

• Leading database service provider

• Merged with on July 2010

• All major databases

• Gold Partners

• OEM – Grid Control expertise and leadership

• Currently looking for talented DBAs: jobs@valinor.co.il

- Introduction

Erez@valinor.co.il

Some of our (300+) Customers

Erez@valinor.co.il

About OEM – Grid Control

Agenda

RAC Administration

RAC Monitoring

RAC Performance Diagnostics & Tuning

RAC Configuration Management

Erez@valinor.co.il

About OEM – Grid Control

Erez@valinor.co.il

OEM & RAC

• Entire stack: cluster, hosts, database,

database instances,, ASM instances,

listeners

• All aspects: Administration,

Monitoring,

Performance diagnostics

Performance tuning

Configuration management

Erez@valinor.co.il

RAC Administration

Erez@valinor.co.il

Cluster Administration

Erez@valinor.co.il

Manage Resources

Erez@valinor.co.il

Resource Information

Erez@valinor.co.il

Resource Advanced Settings

Erez@valinor.co.il

Manage Resource Types

Erez@valinor.co.il

Cluster - Interconnects

Erez@valinor.co.il

Topology & Status

Erez@valinor.co.il

Dashboards – Cluster Database

Erez@valinor.co.il

Dashboards – Host

Erez@valinor.co.il

Dashboards – ASM

Erez@valinor.co.il

RAC Monitoring

Erez@valinor.co.il

Monitoring Highlights

• OOTB metrics for all target types

• OOTB thresholds and sample frequencies

• Over-Time graphs for each metric!!

• Automatic Corrective Actions

• User Defined Monitoring metrics

• Built-in Email notification

• SNMP traps to Manager-of-Managers (MoM)

• Built-in connectivity with leading MoM solutions

Erez@valinor.co.il

Database OOTB Metrics

Erez@valinor.co.il

Host OOTB Metrics

Erez@valinor.co.il

Cluster OOTB Metrics

Erez@valinor.co.il

ASM OOTB Metrics

Erez@valinor.co.il

Metric Data over Time

- Diagnostics

- Trend Analysis

- Capacity

Planning

- Comparison

Erez@valinor.co.il

RAC Performance

Diagnostics & Tuning

Erez@valinor.co.il

Host Performance Dashboard

Erez@valinor.co.il

ASM Performance Dashboard

Erez@valinor.co.il

Database Performance Dashboard

Erez@valinor.co.il

ADDM – Automatic Diagnostics

Erez@valinor.co.il

Automatic Tuning Advisor

Erez@valinor.co.il

RAC Configuration Management

Erez@valinor.co.il

View Configuration:

HW,SW,Patches,Params

Erez@valinor.co.il

Compare Configurations

Erez@valinor.co.il

Comparison Results - Summary

Erez@valinor.co.il

Comparison Results - HW

Erez@valinor.co.il

Comparison Report - OS

Erez@valinor.co.il

Change Tracking

Erez@valinor.co.il

Thanks

<Insert Picture Here>

Erez@valinor.co.il

RAC, ASM and Linux Forum, October 12, 2010

Avi Apelbaum DBA & System engineer

Real Life Experience with

RAC 11GR2

Erez@valinor.co.il

Upgrading 10g cluster to 11gR2 grid

Agenda

Moving ASM to extended RAC

Questions

Erez@valinor.co.il

Upgrading 10g cluster to 11gR2 GI

• Technique 1 :

Creating a new cluster.

Erez@valinor.co.il

Technique 1 : Creating a new cluster

Step 1 : If your db is 10.2.0.1 or below so first

upgrade it to 10.2.0.4

Step 2 : Taking (of course) a full backup of the db

(rman or storage snapshot).

The following steps are if you are using

the same machine:

Step 3 : Backup spfile (if not in asm)/init.ora

Step 4 : Take notes of the current services

(prefered nodes,TAF policies,etc…)

Erez@valinor.co.il

Step 5 : Uninstall rdbms software (both ASM and

DB if separated) and cluster software.

Step 6 : Uninstall clusterware and cleanup the

machine (use metalink:239998.1)

Step 7 : Install 11gR2 Grid Infrastructure

Step 8 : Install 10.2.0.1 rdbms software and

upgrade it to 10.2.0.4 (or the version of

your DB).

Technique 1 : Creating a new cluster

Erez@valinor.co.il

Step 9 : Copy the backed up spfile/init.ora to it‟s new

place.

Step 10 : Add the DB to the new cluster by using

“srvctl add database” and add then add

instances by using “srvctl add instance”

Step 11 : Add services by using srvctl add service.

Technique 1 : Creating a new cluster

Erez@valinor.co.il

If you choose to do it on a new machine

you have 3 possibilities:

• After shutdown the DB, unmap LUNs from old

machines and map them to the new machine

(has to be same OS).

If using linux run the command oracleasm

scandisks as root user and then oracleasm

listdisks. In other case you can use the following

command “kfod disks=all dscvgroup=TRUE”

Technique 1 : Creating a new cluster

Erez@valinor.co.il

• Export the data and then import it into a newly

created database.

• Using Transportable database to move it to a new

machine. In this case the DB can me moved

between platforms (look at oracle documentation

for limitations).

Technique 1 : Creating a new cluster

Erez@valinor.co.il

Upgrading 10g cluster to 11gR2 GI

• Technique 2 :

Upgrading the existing cluster.

Erez@valinor.co.il

This technique is well documented in oracle but I‟ve

choose to build a new one for the following

reasons/issues:

• When beginning the upgrade we had only 1 votedisk.

After running rootUpgrade.sh on the first node this

node changed/upgraded the only votedisk available

and the second node upgrade (of course) failed.

Technique 2 :

Upgrading the existing cluster

Erez@valinor.co.il

Technique 2 :

Upgrading the existing cluster

• After a second retry, which succeeded, at the final

step we‟ve made a restart to the cluster but it failed to

start because for some unknown reason the

interconnect and public interface configuration were

changed in such a way the cluster was not able to

start anymore and it was unable to get to a state were

the reconfiguration was possible (using oifcfg ).

Erez@valinor.co.il

Upgrading 10g cluster to 11gR2 GI

• Using ASM for Extended RAC.

Erez@valinor.co.il

Moving ASM to Extended RAC

Extended ASM is actually a diskgroup in normal or high redundancy in

which each Failure Group is on a separate storage machines

in different locations.

Erez@valinor.co.il

I used the following main steps to migrate our 11gR2 asm

to extended RAC:

• Step 1 : Map new volumes from both storage

machines to all the cluster nodes. The same number

and size of volume should be use in both storages.

• Step 2 :Create a new Diskgroup/s with normal

redundancy when each failgroup is on a different

storage.

Moving ASM to Extended RAC

Erez@valinor.co.il

• Step 2a: Create a normal redundancy diskgroup with

at least 3 disks for the votedisks and OCR.

• Step 3 Move votedisks to new DG (“crsctl replace

votedisk +<NEW DG NAME>”)

• Step 4 Move ocr disks (ocrconfig)

• Step 5 Move controlfiles to new DG‟s

Moving ASM to Extended RAC

Erez@valinor.co.il

• Step 6 When DB is in mount state copy datafiles to

new DG by using the command: “backup as copy

database format +<NEW DATA DG”

• Step 7 After succsessfully competion of the copy

perform the following to update control file with the

copied datafiles :”switch database to copy” and then

“alter database open”

Moving ASM to extended RAC

Erez@valinor.co.il

• Step 8 : Create a new temp TBS or add a new file to

the current one and then delete the old file from that

temp TBS(alter database tempfile „path to file‟ drop;)

• DONE.

Moving ASM to extended RAC

Erez@valinor.co.il

Q&A

Upgrading 10g cluster to 11gR2 GI

Erez@valinor.co.il

contact@valinor.co.il

Upgrading 10g cluster to 11gR2 GI