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

ASM_Space_Administration_on_SVC_v2

Enjoy

 

 

Advertisements

---