How to create ASM Disk group in Oracle 19C Database

By -

 In this post will see types of disk groups and how to create disk group, altering & delating disk group 

Types of Disk groups

 

Normal: Uses two-way mirroring. A normal redundancy disk group requires a minimum of two disk devices (or two failure groups).

 

External: Choosing not to use ASM mirroring of files

 

High: Uses three-way mirroring of Oracle ASM metadata and user data. A high redundancy disk group requires a minimum of three disk devices (or three failure groups). The effective disk space in a high redundancy disk group is one-third the sum of the disk space in all of its devices. A high redundancy disk group can tolerate two failures.

 

SYNTAX:-

 

CREATE DISKGROUP <DISKGROUP_NAME> REDUNDANCY DISK<'OSDISK_LOCATION'> NAME <FAILGROUP_NAME>;

 

What is mirroring & stripping?

 

Mirroring: Redundant copies of the data over multiple disks. 

 

Stripping: Spreading the data over multiple disks.


EXTERNAL REDUNDANCY  - No mirroring

 

Create the ASM DISK group

 

Find the disk group patch using below command

 

SQL> select group_number,name,failgroup,path from v$asm_disk;



SQL> CREATE DISKGROUP DATA_1 EXTERNAL REDUNDANCY DISK '/dev/oracleasm/disks/ASM_DISK5' NAME DISK_1;

 

Diskgroup created.

SQL>



Data_1 disk group created


Normal Redundancy:-

 

Uses two-way mirroring. A normal redundancy disk group requires a minimum of two disk devices (or two failure groups).

 

 

SQL> CREATE DISKGROUP DGROUPA NORMAL REDUNDANCY FAILGROUP CONTROLLER1 DISK '/dev/oracleasm/disks/ASM_DIS10' FAILGROUP CONTROLLER2 DISK '/dev/oracleasm/disks/ASM_DISK9';

 

Diskgroup created.


High Redundancy

 

Uses three-way mirroring of Oracle ASM metadata and user data. A high redundancy disk group requires a minimum of three disk devices (or three failure groups).

 

SQL> CREATE DISKGROUP DGROUPB HIGH REDUNDANCY FAILGROUP CONTROLLER1 DISK '/dev/oracleasm/disks/ASM_DISK8' FAILGROUP CONTROLLER2 DISK '/dev/oracleasm/disks/ASM_DISK6' FAILGROUP CONTROLLER3 DISK'/dev/oracleasm/disks/ASM_DISK4';

 

Diskgroup created.



Altering the DISK group:

 

Whenever we are adding the disk group based up on the redundancy we need to add the disks

 

SQL> ALTER DISKGROUP DGROUPA ADD DISK '/dev/oracleasm/disks/ASM_DISK11','/dev/oracleasm/disks/ASM_DISK7';

 

Diskgroup altered.



DROP Disk GROUP

 

DROP DISKGROUP <Diskgroup_name> INCLUDING CONTENTS;

Alter DISKGROPUP <DISKGROUP_NAME> DROP DISK <DISK_NAME>;

 

 

SQL> Alter diskgroup DGROUPA drop disk DGROUPA_0002;

 

Diskgroup altered.

 

SQL> Alter diskgroup DGROUPA drop disk DGROUPA_0003;

 

Diskgroup altered.

 

SQL> drop diskgroup DGROUPA;

 

Diskgroup dropped.

 

 

Reference:-

https://docs.oracle.com/en/database/oracle/oracle-database/19/ostmg/create-diskgroups.html#GUID-D8A4F1E1-D5F2-4372-8BF8-2A6CB9724930


Comments

Post a Comment

Popular posts from this blog

How to troubleshoot long running concurrent request in R12.2

By -
Normally we are getting concurrent program running longer and concurrent request not picking jobs, etc. those are very frequent issue we expected from development team. Collect below basis level of information to development team 1 Oracle seeded program/Custom program? 2 How much time it used earlier? 3 Is there any recent code change done in concurrent program? 4 Is this program fetching higher data compare to last run? 5 Does this job running any specific time/ It can be run any time? 6 Does this job fetching data using DB link? 7 Does the problem happen on both the test and production instance? Once asked above questions to development team in meanwhile we need to start basic sanity check in our environment. 1 Verify the status of the concurrent program select REQUEST_ID,phase_code,status_code,ORACLE_SESSION_ID from apps.fnd_concurrent_requests where request_id=’1234567’; 2 Find which concurrent manger ran a specific concurrent request select b.USER_CONCURR
Read more

How to run Gather Schema Statistics in R12.2

By -
Image
What is Gather Schema Statistics? Gather Schema Statistics program generates statistics that quantify the data distribution and storage characteristics of tables, columns, indexes, and partitions. The cost-based optimization (CBO)  uses these statistics to calculate the selectivity of prediction and to estimate the cost of each execution plan. Why Run the Gather Schema Statistics? When Data is update, insert, delete in table of user end Like (Technical User ,Finance User ,Ect) It become necessary to run the Gather Schema Statistics It’s recommended to Run GSS in Weekly Once or twice. How to run Gather Schema Statistics? Login application with sysadmin user Submit Request Window Navigate to: Concurrent > Requests Enter the parameters This can be run for specific schemas by specifying the schema name or enter ‘ALL’ to gather statistics for every schema in the database Submit the Gather Schema Statistics program Parameters: Schem
Read more

How to compile forms in R12.2

By -
STEP 1--> Login to app server STEP 2--> Go to  directory $AU_TOP/forms?US STEP 3--> Move to ".fmb" file STEP 4--> Execute the below command to generate ".fmx" frmcmp_batch userid=apps/<apps_pwd> module=<form_name>.fmb output_file=<form_name>.fmx module_type=form batch=no compile_all=special (EX):-   frmcmp_batch userid=apps/apps module=JAINTAXT.fmb output_file=$JA_TOP/forms/US/JAINTAXT.fmx module_type=form batch=no compile_all= special (O/p):   Created form file /oracle/CLONE/apps/fs2/EBSapps/appl/ja/12.0.0/forms/US/ JAINTAXT.fmx Refer: R12: How to Compile a Form in Release 12 (Doc ID 1085928.1)
Read more