ODA: Can you resize ASM diskgroups on Oracle Database Appliance?

Asset ID:	1-71-1514604.1
Update Date:	2017-05-19
Keywords:

Solution Type Technical Instruction Sure

Solution 1514604.1 : ODA: Can you resize ASM diskgroups on Oracle Database Appliance?

Applies to:

Oracle Database Appliance Software - Version 2.1.0.1 to 12.1.2.9 [Release 2.1 to 12.1]
Oracle Database Appliance - Version All Versions and later
Information in this document applies to any platform.
ODA, Resize, ASM, ACFS

Goal

A common question with customers running on Oracle Data Appliance (ODA HA) is whether it is possible to change space allocation of an existing system.

For example, move space out of the +RECO diskgroup and allocate the space to the +DATA diskgroup.
Another question is: Can we make and size our own diskgroups?

Are there instructions for this?

COMMENT: ODA [HA] for High Availability diskgroup sizes for ASM are set during the initial deployment and _not_ alterable after the deployment including 12.x versions of the ODA.
                This note does NOT apply to the new ODA Lite series including ODA X6-2S X6-2M and X6-2L
   For information regarding 12.1 and higher ODA and ODAVP versions please refer to the current ODA Documentation at --  docs.oracle.com

- e.g.   http://docs.oracle.com/cd/E22693_01/index.htm

Solution

There are no general instructions for resizing ASM diskgroups on ODA* because ASM is not user definable as seen in other non-ODA based configurations:

In order to 'resize' the disk group's Redundancy or backup storage to an existing ASM configuration you will need to redeploy.

ASM on the ODA has been pre-tested and configured to include stability, ease of administration and performance for this known, and fixed physical configuration.
The ODA ASM configuration is based on three defined Diskgroups: DATA ; RECO ; and REDO (and starting with the X5-2 FLASH).

The only method to alter the ASM storage choices is during the deployment.

The most common method to set-up storage for the ODA is to use the Oracle Database Appliance Configurator which can be downloaded from the following link:

http://www.oracle.com/technetwork/server-storage/engineered-systems/database-appliance/overview/index.html

The instructions are provided in the following ODA documentation: Using Oracle Appliance Manager Configurator

Select 'Custom Configuration' and not 'Typical' to create AND SAVE a new configuration file.

How to see different ASM storage choices

You also have the option of loading and existing configuration file, then applying changes if the original was also custom type.
You then feed the new configuration file to the new deployment:

NOTE: Make sure you always choose the correct backup option as well as redundancy option: Using the custom configurator installation 'external backup' allocates more space to the+DATA diskgroup.

X5-2 use the Custom Configuration

For actual allocated ASM sizes see Appendix A in the most current documentation:

Disk + group capacities by HW Type

Using an Existing Configuration File to Configure Oracle Database Appliance

For cleanup before the new deployment, refer to 'Deinstalling Oracle Software and Reinitializing Storage'

NOTE:

A redeployment wipes out your data, so you MUST take backups of your databases and other data, and restore them after deployment.
Using a second ODA in a DataGuard (DG) configuration is the preferred method for continuous operations using the ODA.

New for X5-2

X5-2 uses ACFS on top of the ASM

There is a required ACCELERATOR Disk group to enhance performance for these 8T shared disks.
The default location for the accelerator disk group is on REDO ( SSDs )
DURING DEPLOYMENT there is also an option to locate this diskgroup to the FLASH diskgroup when using High Redundancy (3x) Data and Reco ASM diskgroups.
- The ACFS accelerator volume on FLASH allows more space for REDO for more database intensive configurations

Choose the CUSTOM Configuration Type to access Redundancy, Backup Location and Accelerator Diskgroup locations

Three options for changing storage DURING DEPLOYMENT ONLY

2x ASM redundancy use REDO for Accel

HighCanUseFlash

For more general information regarding ASM choices and questions using the ODA please refer to

ODA (Oracle Database Appliance) and Bare Metal ASM storage configuration choices for 2.1 through 2.10+ (Doc ID 1519879.1)

For information on ODA and ACFS which sits on top of ASM please review docs.oracle.com

http://docs.oracle.com/cd/E75549_01/doc.121/e74838/GUID-F99D3337-E913-405D-BE3F-85C31103A26A.htm#CMTAR218

"...The Oracle ACFS file systems are automatically created when you create a shared repository, or when you create a database on Oracle Database Appliance.

However, the file systems do not initially consume all of the storage in the appliance which preserves space for additional repositories, or in some cases, database files stored directly in Oracle ASM.
In Oracle Database Appliance software releases 12.1.2.2 and earlier, the Oracle ACFS file systems do not automatically extend if they run low on space, even if storage space is still available in the shared storage pool.
You can check for available storage space in your file systems by running the operating system command df -h as shown in the following example.

..."

ALSO SIMILAR

----------------

Can we resize /u01 on the ODA?

a) With the Virtualized software, /u01 lives in /OVS/Repositories/…, which means it is physically on the shared disk shelf.
So, it is a virtual disk and you have room for expansion.

b) The /u01 in BM case is on top of logical volume and is resizable and straightforward to do.

[root@oda1 ~]# mount | grep u01

/dev/mapper/VolGroupSys-LogVolU01 on /u01 type ext3 (rw)

[root@oda1 ~]# lvdisplay /dev/mapper/VolGroupSys-LogVolU01

--- Logical volume ---
LV Name /dev/VolGroupSys/LogVolU01
VG Name VolGroupSys
LV UUID 34rsEb-86hO-2kt5-1tZ9-39Qo-Etch-9eQL0c
LV Write Access read/write
LV Status                available
# open                   1
LV Size 100.00 GB
Current LE 3200
Segments 1
Allocation               inherit
Read ahead sectors auto
- currently set to 256
Block device 252:1

You can check the volume group VolGroupSys and see the free size in the volume group and resize the LogVolU01 volume to that size. And then extend the filesystem on top of it.

[root@oda1 ~]# vgdisplay

--- Volume group ---
VG Name               VolGroupSys
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 5
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 4
Open LV 4
Max PV 0
Cur PV 1
Act PV 1
VG Size 465.25 GB
PE Size 32.00 MB
Total PE 14888
*Alloc PE / Size 6848 / 214.00 GB
*Free PE / Size 8040 / 251.25 GB
VG UUID                  KVckxf-zDlL-L6Wo-qxWL-Ukia-cRTH-Lcurs1

Regards,
Sandeep

* In resizing step of u01, please mention that " Free PE / Size " is not in any operation of ODA.
Some users may confuse if it is used in patching or any maintenance activity.

Vivek

References

<NOTE:1417713.2> - Information Center: Oracle Database Appliance
<NOTE:1519879.1> - ODA (Oracle Database Appliance) and ASM 2.1 up to 2.10 Storage Options for V1, X3-2 and X4-2 Hardware

Attachments

This solution has no attachment