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

Post a Comment

Popular posts from this blog

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 dumpfile=content12051
3 comments
Read more

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
9 comments
Read more

SQL query to find the cause or reason for more archive log generation

Finding reason or cause for heavy or more archive log generation in a particular time period As i said in the previous post we are going to see SQL queries to find the cause or reason for more archive log generation in a problematic window... Sometimes customer would ask the sql query which generated more archive logs sometimes before or days before (not for current archive logs generation which is described in the previous post). In such scenarios, follow the steps below. Step 1: ====== First you must know the timing when more number of archive logs generated in the databases. for that you can use the below query. Below sql query gives how many number of archive logs generated for each and every hour... col day for a12 set lines 1000 set pages 999 col "00" for a3 col "01" for a3 col "02" for a3 col "03" for a3 col "04" for a3 col "05" for a3 col "06" for a3 col "07" for
1 comment
Read more