Skip to main content

Recommended ASM Parameters Settings


<<Back to Oracle ASM Main Page

Recommended Settings for Oracle ASM Initialization Parameters

In this post I will explain only some important parameters which you need to consider while configuring ASM Instance
• ASM_DISKGROUPS
• ASM_DISKSTRING
• ASM_POWER_LIMIT
• ASM_PREFERRED_READ_FAILURE_GROUPS
• DIAGNOSTIC_DEST
• INSTANCE_TYPE
• PROCESSES

ASM_DISKGROUPS
This Parameter specifies a list of names of disk groups to be mounted by an Automatic Storage Management instance at instance startup or when an ALTER DISKGROUP ALL MOUNT statement is issued. There is no default value. Automatic Storage Management (ASM) automatically adds a disk group to this parameter when the disk group is successfully created or mounted, and automatically removes a disk group from this parameter when the disk group is dropped or dismounted.
Note: For Oracle Database 12c Release 1 or later, Oracle ASM configurations support up to 511 disk groups. Oracle ASM configurations with Oracle Database releases before
12c Release 1 can only support up to 63 disk groups.

SQL>  show parameter diskgroup;
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
asm_diskgroups                       string      DG_TEST_FRA, DG_TEST_REDO, DG_
                                                 TEST_DATA, DG_TEST
SQL> select GROUP_NUMBER,NAME,STATE from v$asm_diskgroup;
GROUP_NUMBER NAME                           STATE
------------ ------------------------------ -----------
           1 DG_TEST_DATA                   MOUNTED
           2 DG_TEST_FRA                    MOUNTED
           3 DG_TEST_REDO                   MOUNTED
           4 DG_TEST                        MOUNTED
SQL>  alter diskgroup DG_TEST dismount;
Diskgroup altered.
SQL> show parameter diskgroup;
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
asm_diskgroups                       string      DG_TEST_FRA, DG_TEST_REDO, DG_
                                                 TEST_DATA <= DismountedDG has been removed from the list
SQL> select GROUP_NUMBER,NAME,STATE from v$asm_diskgroup;
GROUP_NUMBER NAME                           STATE
------------ ------------------------------ -----------
           0 DG_TEST                        DISMOUNTED
           1 DG_TEST_DATA                   MOUNTED
           2 DG_TEST_FRA                    MOUNTED
           3 DG_TEST_REDO                   MOUNTED
NOTE: If you are not using SPFILE you have to manually adjust the parameter in pfile and restart the ASM instance to bring the parameter in effect. It is strongly recommended to use SPFILE
ASM_DISKSTRING
This specifies an operating system-dependent value used by Automatic Storage Management to limit the set of disks considered for discovery.
The default value is null string which means ASM  discovery finds all disks in an operating system-specific location to which the Automatic Storage Management instance has read/write access.
SQL> show parameter string
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
asm_diskstring                       string      AFD:* <= Indicates AFD (ASM Filter Driver is used)
ASM_POWER_LIMIT
This parameter specifies maximum number of processes for disk rebalancing. The higher the limit, the faster rebalancing will complete but might result in higher I/O overhead and hence degrading the overall performance
Default value is 1. Value 0 disables the rebalancing. The maximum allowed value for this parameter is 1024 if ASN compatibility for the DG is set =>11.2.0.2 else the value is 11
Specifying the value using POWER clause in ALTER DISKGROUP.... operation always takes precedence and used to perform rebalancing for that particular operation
ASM_PREFERRED_READ_FAILURE_GROUPS
This is an interesting parameter and very useful in case of Extended RAC. Let me explain how
If you dont configure  ASM_PREFERRED_READ_FAILURE_GROUPS parameter ASM used to read only Primary copy of extents. In case of extended RAC cluster for example
Node1 is running in SITEA
Node2 is running in SITEB

In this kind of configuration data is striped across the sites and reading the data from remote location ( ie Node1 has to read the data from SITEB for all primary extents located in SITEB and Node2 has to read it from SITEA for all primary extents located in SITEA) will cause network overhead as well as latency impacting overall performance, although a copy of the same data is available locally as secondary extent, This is so because oracle tend to read the data from primary extent by default.
To solve this issue oracle introduced the parameter ASM_PREFERRED_READ_FAILURE_GROUP starting from 11g. If ASM_PREFERRED_READ_FAILURE_GROUP parameter is set DB Instance prefers to read the data from local site only. The ASM_PREFERRED_READ_FAILURE_GROUPS parameter setting is instance specific.
How to Setup ASM Preferred Mirror Read:
SQL> alter system set asm_preferred_read_failure_groups='ams_diskgroup_name.asm_failure_group_name';
NOTE:- Please do ensure to investigate the pros/cons while using Flex ASM the behavior might be different
DIAGNOSTIC_DEST
The DIAGNOSTIC_DEST initialization parameter specifies the directory where diagnostics
for an instance are located.
The default value for an Oracle ASM instance is the $ORACLE_BASE directory for the
Oracle Grid Infrastructure installation.
INSTANCE_TYPE
The INSTANCE_TYPE initialization parameter specifies whether the instance is a database
instance, an Oracle Automatic Storage Management (Oracle ASM) instance, or an
Oracle ASM Proxy instance.
The following is an example of the INSTANCE_TYPE parameter in the initialization file:
INSTANCE_TYPE = ASM
In addition to values asm and rdbms, INSTANCE_TYPE can be set to asmproxy in an Oracle
Flex ASM configuration.
PROCESSES
The PROCESSES initialization parameter affects Oracle ASM, but the default value is
usually suitable.
However, if multiple database instances are connected to an Oracle ASM instance,
then you can use the following formulas, where n is the number of database instances
connecting to the Oracle ASM instance.
In a non-Exadata environment, the recommended settings are:
• For n < 10, PROCESSES = 50*n + 50
• For n >= 10, PROCESSES = 10*n + 450
In an Oracle Exadata environment, the recommended setting is PROCESSES = MAX(450 +
10*n, 1024)

Comments

Popular posts from this blog

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the server to be powered on, run the

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco

ORA-16905: The member was not enabled yet

<<Back to Oracle DataGuard Main Page ORA-16905 Physical Standby Database is disabled DGMGRL> show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database (disabled)       ORA-16905: The member was not enabled yet. Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 58 seconds ago) DGMGRL> DGMGRL> enable database 'ORCL1PS'; Enabled. DGMGRL>  show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 38 seconds ago)

How to Switch Log File from All Instances in RAC

<<Back to Oracle RAC Main Page Switch The Log File of All Instances in Oracle RAC. In many cases you need to switch the logfile of the database. You can switch logfile using alter system switch logfile command but if you want to switch the logfile from all the instances you need to execute the command on all the instances individually and therefore you must login on all the instances. You can avoid this and switch logfile of all instances by just running the below command from any of the instance in RAC database SQL> ALTER SYSTEM SWITCH ALL LOGFILE;   System altered.

ORA-65104: operation not allowed on an inactive pluggable database alter pluggable database open

<<Back to DB Administration Main Page ORA-65104: operation not allowed on an inactive pluggable database SQL> alter pluggable database TEST_CLON open; alter pluggable database TEST_CLON open * ERROR at line 1: ORA-65104: operation not allowed on an inactive pluggable database Cause The pluggable database status was UNUSABLE. It was still being created or there was an error during the create operation. A PDB can only be opened if it is successfully created and its status is marked as NEW in cdb_pdbs.status column SQL> select PDB_NAME,STATUS from cdb_pdbs; PDB_NAME             STATUS -------------------- --------------------------- PDB$SEED             NORMAL TEST_CLON            UNUSABLE Solution:  Drop the PDB and create it again. Related Posts How to Clone Oracle PDB (Pluggable Database) with in the Same Container

ORA-46630: keystore cannot be created at the specified location

<<Back to DB Administration Main Page ORA-46630: keystore cannot be created at the specified location CDB011> ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "xxxxxxx"; ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "EncTest123" * ERROR at line 1: ORA-46630: keystore cannot be created at the specified location Cause  Creating a keystore at a location where there is already a keystore exists Solution To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location. Note: Oracle does not recommend deleting keystore file (ewallet.p12) that belongs to a database. If you have multiple keystores, you can choose to merge them rather than deleting either of them.

Starting RMAN and connecting to Database

  <<Back to Oracle Backup & Recovery Main Page Starting RMAN and connecting to Database Starting RMAN and connecting to Database To start RMAN you need to set the environment and type rman and press enter. You can connect to database either using connect command or using command line option. using command line option localhost:$ export ORACLE_HOME=/ora_app/product/18c/dbd2 localhost:$ export PATH=$ORACLE_HOME/bin:$PATH localhost:$ export ORACLE_SID=ORCL1P localhost:$ rman target / Recovery Manager: Release 18.0.0.0.0 - Production on Sun Apr 4 08:11:01 2021 Version 18.11.0.0.0 Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved. connected to target database: ORCL1P (DBID=4215484517) RMAN> using connect option localhost:$ rman RMAN> connect target sys@ORCL1P  target database Password:******** connected to target database: ORCL1P (DBID=4215484517) NOTE: To use connect command you need to ensure that  you have proper TNS sentry for database (ORCL

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02             EXPORT               FULL       EXECUTING OR You can also find the job name for export/import in logfile in beginning itself. Step2>Attach to the Job and check status One you get the Export/Import Job Name attach the job and check its status. You can attach or det

ORA-15040: diskgroup is incomplete

<<Back to Oracle ASM Main Page ORA-15040: diskgroup is incomplete SQL> startup ORA-00099: warning: no parameter file specified for ASM instance ASM instance started Total System Global Area 1140850688 bytes Fixed Size                  8629704 bytes Variable Size            1107055160 bytes ASM Cache                  25165824 bytes ORA-15110: no diskgroups mounted Reason: The reason of this error is simply the ASM is not able to find the some or all the disks. Solution: Investigate and make all the disks available to ASM to mount the disk group. Make sure the disks has proper permissions. If you are using AFD check following services are online oracleacfs oracleadvm oracleoks  oracleafd   Source of Problem : Issue started after restart of the server After restarting the server when I tried to start the ASM instance its started throwing error.  ORA-15110: no diskgroups mounted Investigation in my Case Step1> ASM Logfile Scanning  Looked i