EMC CLARiiON: Oracle Database 10g/11g/11gR2 with Storage Replication Consistency


This white paper is intended of database and system administrators interested in implementing backup and remote disaster protection plan on Linux and Windows Plataform for Oracle databases using the consistenty features of EMC CLARiiON SnapView nad MirrorView/S. The reader should be familiar with Oracle Database software and ASM and EMC CLARiion SnapView and MirrorView replication  technologies.

Click link below…




Performance benefits of IBM Storwize V7000 with Easy Tier for Oracle 11g workload

This paper demonstrates the performance benefits that IBM® Easy Tier™ provides by seamlessly migrating hot extents from hard disk drives (HDDs) to a higher performing solid-state drives within theIBM Storwize V7000 solution.

This might be either to internal solid-state drives in the IBM Storwize V7000or to external storage systems that are virtualized by IBM Storwize V7000.

The other load generator tool that has been used here is Oracle Vdbench. The objective of Vdbench is togenerate a wide variety of controlled storage I/O workloads, allowing control over workload parameterssuch as I/O rate, logical unit number (LUN) or file sizes, transfer sizes, thread count, volume count,volume skew, read/write ratios, read and write cache hit percentages, and random or sequentialworkloads.

The other load generator used to arrive at the configuration guidelines is the Oracle I/O Calibration ToolORION) calibration tool.

This tool generates I/O using the same I/O software stack used by the Oracle server software without having to install the server software and create a database. It can simulatevarious workload types at different load levels to arrive at performance metrics for input/output operationsper second (IOPS), and latency (response time). It can also simulate the effect of striping performed byAutomatic Storage management (ASM).

The intention of this paper is not to demonstrate the maximum possible I/O benchmark or performancenumber for the IBM Storwize V7000. Those benchmark and performance numbers are likely to be shownin the Storage Performance Council SPC-1 and SPC-2 results posted by IBM on the SPC website. Thispaper demonstrates how to configure Easy Tier, and explains how Easy Tier might benefit theperformance for an Oracle database workload by optimizing the utilization of solid-state drives.

See link below…

EasyTier for Oracle


Oracle Automatic Storage Management (ASM) on the IBM SAN Volume Controller (SVC)

This paper discusses some guidelines for administering space usage for Oracle Automatic Storage Management (ASM) on the IBM® System Storage™ SAN Volume Controller (SVC). The back-end storage controller used with SVC is the IBM System Storage DS8000®.

The discussion includes scenarios which show the tasks necessary for space administration in a checklist format. The scenarios presented assume that space administration is occurring during periods of high storage I/O activity. Therefore, a freely available Oracle load generator, Swingbench, is used to generate a heavy I/O workload during the exercises.

The subjects covered include:

• A brief overview of the hardware and software technology stack used for the scenarios.This includes the IBM SVC, the IBM System Storage DS8000, the IBM System Storage SAN32B-3 Fibre Channel switch (also known as the IBM Brocade 2005-B5K or Brocade 5000), Oracle 11g ASM, the Red Hat Enterprise Linux 5.3 and IBM AIX 6.1 operating systems, and IBM TotalStorage® Productivity Center (TPC) 3.3.2.

• A detailed description of the usage of the Swingbench Oracle load generator, including how to configure Swingbench to generate as much storage I/O as possible.

• Basic space administration tasks for the IBM SAN Volume Controller (SVC). • Basic space administration tasks for Oracle Automatic Storage Management (ASM).

• Typical space addition scenarios for Oracle ASM on SVC. Two scenarios will be discussed, adding an ASM disk to an existing ASM diskgroup and expanding existing ASM disks in a diskgroup.

• Typical space reduction scenarios for Oracle ASM on SVC. Two scenarios are discussed, removing an ASM disk from an existing ASM diskgroup and shrinking existing ASM disks in a diskgroup.

• A scenario where an MDisk is added to an SVC MDisk Group containing the database. The VDisk extents on that MDisk Group are then rebalanced across all of the MDisks now contained in the MDisk Group.

• A scenario where all of the VDisks which contain the database, including the OCR and Vote disks, are non-disruptively migrated to a different MDisk Group via the “svctask migratevdisk …” command. This could be used to migrate the database to different back-end storage controller.

• A scenario where all of the VDisks which contain the database, including the OCR and Vote disks, are non-disruptively migrated to a different MDisk Group via VDisk mirroring. The VDisks are mirrored and after the mirror is synchronized the original copies of the VDisks are deleted. Again, this could be used to migrate the database to a different back-end storage controller.

• Some basic SVC CLI (Command Line Interface) and Oracle SQL*Plus scripts that can be used for SVC and ASM space administration and monitoring.

See link below





Deploying Oracle RAC 11g with ASM on IBM AIX 6.1 using IBM XIV Storage System

This white paper describes in detail the step-by-step configuration of the IBM® XIV® with Oracle Database11g, Oracle Real Application Cluster (RAC), and Oracle Automatic Storage Management (ASM) on the IBMAIX® 6.1 operating system.

The test exercise demonstrates that it is easy to configure IBM’s XIV storagesystem in this environment by using the guidelines that are laid out in this document.

The IBM XIV disk storage array offers expandable data open storage and data-protective systems withconsistent performance to correspond with specific business requirements.

The XIV storage system has arevolutionary high-end storage architecture designed to eliminate the complexity of administration andmanagement of tiered storage and information lifecycle management.

XIV provides system virtualization thatgreatly simplifies IT operations and optimizes performance through automatic distribution of data acrosssystem resources, avoiding hot spots without manual tuning.

Oracle Database 11g and Oracle Clusterware technologies offer several features that work in single instance database and Oracle RAC database environments.

Oracle Automatic Storage Management (ASM)technology is a feature that is designed to distribute information uniformly across all storage disk groups(configured for ASM).

The AIX operating system’s multipath driver (MPIO) works with the XIV disk-storage system in a multipathI/O environment that runs on servers with the ppc-64 architecture, including the IBM System p® platform. If apath fails, MPIO reroutes the I/O through the remaining paths.

Click link below

Deploying Oracle RAC 11g with ASM on IBM AIX 6.1 Using IBM XIV Storage System




Step by Step Installing Oracle 11g R1 on AIX 5.3

This document is written to provide help installing Oracle11g Real Application Clusters (11.1) release 1 withOracle Automatic Storage Management on IBM System pand i servers with AIX.

We will describe step by step the architecture Oracle CRS (Cluster Ready Service) on raw disks and database on ASM(Automatic Storage Management).

See link Below



Cloning an Oracle Database to the Same Server Using FlashCopy and VolumeCopy on DS3400, DS4000, and DS5000

Maximizing hardware return on investment is an important business concern. To conserve hardware resources, many IT environments run multiple databases on a single server. With this proliferation of databases also comes the proliferation of database clones. Database clones are very useful for testing, developing, or keeping a point-intime image for evaluation purposes. However, too many database clones take up a lot of server space.

When there is a shortage of server hardware, and when the source server has enough resources to run another database, the clone can run on the same server as the source database. For example, if needed, you could clone a development database back onto the development server.

Cloning a database onto the same server is more complicated than cloning the database onto a different server. To isolate the clone from its source database on the same server, you have to know which files to edit and how to edit them. Otherwise, any mistake that you might make when you create the clone might overwrite the source database and corrupt it. Not surprisingly, Oracle Database administrators are often reluctant to try to create clones on the same server. Even though doubling up would conserve hardware resources, sometimes the risk is not worth taking.

This document explains how to isolate a cloned database from its source. This document explains how to set up the cloned database using different storage locations from the source database. Initially, all of the pointers in the cloned database point to the original locations for the source database. You have to change the locations before you can use the cloned database. This document describes how to edit all of the references to the file systems so that it is safe to use the cloned database.

This document also describes a solution that simplifies cloning. Specifically, this document focuses on expediting the important task of cloning an Oracle Database to the same server. The solution combines Oracle Database products with IBM® storage subsystems and the premium features, FlashCopy ® and VolumeCopy, which come with both DS Storage Manager and IBM DS Storage Manager 10. This method of cloning a database requires less effort than using an Export/Import function or backing up and restoring the database using Oracle RMAN.


The intended reader for this document is an Oracle Database administrator with experience in the following areas:

• Oracle Database and its related components

• Cloning an Oracle Database

• Storage, including an understanding

See link below

Cloning Oracle DB to same server using DS5000 DS4000 DS3400


Best Practices for Running an Oracle Database on an IBM Mid-Range Storage Subsystem

Owning state-of-the-art storage subsystems is not enough to excel in today’s competitive business climate. Even with the best storage subsystem, the continuous demands upon the IT environment can create challenges:

• Unused capacity on expensive equipment becomes a financial waste.

• Continuous hardware and software sprawl create an ever-changing environment that constantly must be re-tuned to adjust to new conditions.

• New equipment is hot-added when possible, often resulting in a convoluted configuration that makes tuning for high performance complex and difficult to manage.

This document describes the optimum performance settings for IBM® System Storage ™ DS5000®  storage subsystems and IBM System Storage DS4800 storage subsystems with the Oracle® Database application. This document identifies parameters for optimizing a high-performance storage subsystem.

For each parameter, this document explains how to monitor, evaluate, adjust, and make sure that the adjustment was appropriate and positive. The process of keeping the parameters tuned involves the following tasks:

• Identify the relevant parameters.

• Take a baseline to determine the benchmark value for each relevant parameter.

• Continuously monitor each parameter on an ongoing basis. Only continuous monitoring can isolate the triggers that impact performance. Also, continue monitoring after any adjustment so that the effectiveness of the adjustment can be evaluated.

• Adjust parameters while the system remains in production.

• Watch how adjustments in one parameter are affecting other parameters.

See link below

Best Practices for Running an Oracle Database on DS4800 DS5000