Skip to main content

Steps to add ASM disk to existing ASM diskgroup

Steps to add disk to disk group

Please follow the below steps once disk presented and partitioned by OS team.

      1)      Create the disk using ASMLIB

For example
# /usr/sbin/oracleasm createdisk PRODDATA08 /dev/xvdq1
# (this command needs to be executed as root user)

      2)      Since this is a RAC installation, the disks would only be stamped by one node. The other node would just scan for the disks.

       For example
# /usr/sbin/oracleasm scandisks
# (this command needs to be executed as root user)

You can use the next steps to validate whether the candidate disk(s) is/are in good shape and can be accessed from each node (without harm the existing production diskgroups) before adding, as follow:

      3)      As Oracle or Grid OS user, run the next commands on each node

       For example
$> id 
$> /usr/sbin/oracleasm listdisks 
$> /usr/sbin/oracleasm querydisk <each disk from previous output>

      4)      Confirm the disks are visible (I/O) at OS level (as oracle or grid OS user) from each node

       For example
 $> id 
$> ls -l  <disk name>
$> dd if=/dev/oracleasm/disks/PRODDATA08 of=/dev/null count=100 bs=8192

       5)      Verify that kfed can read on the candidate disk(s) at OS level (as oracle or grid OS user) from each node:

       For example
kfed read /dev/oracleasm/disks/PRODDATA08 
Note: If the disk is not a FORMER disk, then kfed on new disks will return: 
 kfbh.type: 0 ; 0x002: KFBTYP_INVALID and that is expected.

       6)      Now connect to the ASM instance as sysasm and add the disk to existing diskgroup

       For example
SQL> ALTER DISKGROUP PRODDATA ADD DISK '/dev/oracleasm/disks/PRODDATA08';


Note: ASMCA UTILITY can also be used for adding, dropping, dismount ASM disk/disk groups

Comments

Popular posts from this blog

Pinning execution plan for a sql_id using 'SQL Profile' to consistently reproduce a good plan

Deal all, Below post content is not my own. It is taken from MOSC document but the example shown below is taken from our environment. I got to know the below topic when we had experienced the bad SQL query performance in one of our production environment during daily batch running time. Hence we had implemented the same mentioned in the title "Pinning execution plan for a sql_id using 'SQL Profile' to consistently reproduce a good plan". Introduction The "cost-based optimizer (CBO or just optimizer) is the part of database software that determines the most efficient means of accessing the specified data (or at least what it "calculates" as the most efficient). The optimizer determines which execution plan is most efficient by considering several sources of information, including query conditions, available access paths, statistics gathered for the system, and hints. Some changes in those conditions may affect the calculations of the plan...

Export and import multiple schema using expdp/impdp (Data Pump utility)

Use the below sql query to export and import multiple schema: expdp schemas=schema1,schema2,schema3 directory=DATA_PUMP_DIR dumpfile=schemas120514bkp.dmp exclude=statistics logfile=expdpschemas120514.log impdp schemas=schema1,schema2,schema3 directory=DATA_PUMP_DIR dumpfile=schemas120514bkp.dmp logfile=impdpschemas120514.log sql query to export and import a schema: expdp schemas=schema directory=DATA_PUMP_DIR dumpfile=schema120514bkp.dmp exclude=statistics logfile=expdpschema120514.log impdp schemas=schema directory=DATA_PUMP_DIR dumpfile=schema120514bkp.dmp logfile=expdpschema120514.log Parameter STATISTICS=NONE can either be used in export or import. No need to use the parameter in both. To export meta data only to get ddl of the schemas: expdp schemas=schema1,schema2,schema3 directory=TEST_DIR dumpfile=content.dat content=METADATA_ONLY exclude=statistics To get the DDL in a text file: impdp directory=TEST_DIR sqlfile=sql.dat logfile=sql.log dumpfil...

Cloud Control EM13c - Loader Throughput (rows per second) for Loader_D crossed the critical threshold and Total Loader Runtime in the Last Hour (seconds) for Loader_D crossed the critical threshold

Hello Guys, Here is an another post related to Cloud Control EM13c - Real-time Scenario. Suddenly We were receiving the following warning and critical alerts from EM13c Cloud Control during the time slot between 12 AM and 04:00 AM daily. 1)  Message= Loader Throughput (rows per second) for Loader_D crossed the critical threshold (xx). Current value: xx.xx 2)  Message= Total Loader Runtime in the Last Hour (seconds) for Loader_D crossed the critical threshold (x,xxx). Current value: xxxx.xx 3)  ORA-error stack (3,136) and ORA-error stack (609) were also logged in alert log 4)  Message= Incident (BEA-310003 [LowMemory]) detected in $OMS_HOME/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/adr/diag/ofm/GCDomain/EMGC_OMS1/alert/log.xml at time/line number: When we analyzed the AWR reports of EM PDB repository database, we found there were few PL/SQL statements given below causing this issue with wait event  SQL*Net Break/reset To Client...