Extract ASM disk info


If you are asked to provide an extract of SAN allocation, then the following query can be used to provide the breakdown

ASM Disk Info Query
$ sqlplus / as sysdba

set pages 200 lines 250 --colsep ,


col DiskPath format a50
col diskname format a20
col diskgroup_name format a20


break on Diskgroup_name skip 2
compute sum label 'Group_Size-GB' of total_gb on Diskgroup_name
compute sum label 'Group_Size-GB' of Used_GB on Diskgroup_name
compute sum label 'Group_Size-GB' of Free_GB on Diskgroup_name
compute Avg label 'Free_percent%' of free_percent on Diskgroup_name
select a.name Diskgroup_name,
       b.name diskname,
       b.path DiskPath,
       round((b.total_mb/1024),2) Total_GB,
       round(((b.total_mb-b.free_mb)/1024),2) Used_GB,
       round((b.free_mb/1024),2) Free_GB,
       100 - round((((b.total_mb - b.free_mb)*100)/b.total_mb),2) free_percent
  from v$asm_diskgroup a,
       v$asm_disk b
where a.group_number=b.group_number
   order by 1,
   decode(a.name, 'DATA',to_number(substr(b.name,5,2)),
                  'FLASH',to_number(substr(b.name,6,2)),
                  'MGMT',to_number(substr(b.name,6,2)),
                  'FAST',to_number(substr(b.name,5,2))
         );

Sample Output

DISKGROUP_NAME       DISKNAME  DISKPATH            TOTAL_GB    USED_GB    FREE_GB FREE_PERCENT
-------------------- --------- ----------------- ---------- ---------- ---------- ------------
DATA                 DATA1     /dev/emcpowerb        136.16     121.71      14.45        10.61
                     DATA2     /dev/emcpowerc        136.16      121.7      14.45        10.62
                     DATA3     /dev/emcpowerd        136.16     121.71      14.45        10.61
********************                             ---------- ---------- ---------- ------------
Free_percent%                                                                       10.6133333
Group_Size-GB                                        408.48     365.12      43.35


FAST                 FAST1     /dev/emcpowere        136.16     126.33       9.83         7.22
********************                             ---------- ---------- ---------- ------------
Free_percent%                                                                             7.22
Group_Size-GB                                        136.16     126.33       9.83


MGMT                 MGMT_0000 /dev/emcpowera         17.02        .21      16.81        98.77
                     MGMT_0001 /dev/emcpowerf         17.02        .18      16.84        98.95
********************                             ---------- ---------- ---------- ------------
Free_percent%                                                                            98.86
Group_Size-GB                                        34.04        .39      33.65

Popular posts from this blog

Recover Standby database from ORA-00332: archived log is too small

When a standby database crashes and upon instance recovery gets stuck with error ORA-00332: archived log is too small - may be incompletely archived, then following set of actions must be carried out to restore the service. 1. Check that the instance is in MOUNTED. (select status from v$instance) 2. If not mounted, then start the database in mounted mode SQL> startup mount; 3. Search the alert log to identify the archive log that is corrupt,  Sample lines from the alert log Errors in file /u01/app/oracle/diag/rdbms/fxfgsby/FXFGSBY1/trace/FXFGSBY1_ora_19463.trc: ORA-00332: archived log is too small - may be incompletely archived ORA-00334: archived log: '+FLASH/fxfgsby/archivelog/2013_08_19/thread_1_seq_173831.5998.823855747' Shutting down recovery slaves due to error 332 4. In the above example, the corrupt log file belongs to Thread#=1 and Sequence#=173831 5. Log on to the Primary database cluster and take a copy of the file from ASM onto the local file system. Not...
Read more

Check Active Dataguard Replication Status

In order to check if ADG is up-to-date, one has to tail the alert log on both the Primary and Physical Standby databases, followed by a manual check to look for the log status of (in-transit) against each of the threads. While this method is perfect it can be bit tedious to perform. You can now do the same using one of the attached SQL from the Primary database. Deployment and usage steps - Open a vi editor on the Primary database. - Copy of the below SQL into the editor - Complete the  database link creation command based on the database    you are checking. - Save the text file as check_adg_status.sql - execute the sql file as sys user. e.g. sqlplus -s  / as sysdba @check_adg_status.sql  Note : These commands cannot be run from the Physical standby as the query relies on using a temporary database link that cannot be created on a read-only database. Troubleshooting 1. Some database clusters may report the following error when invoked   ...
Read more

Top CPU consuming oracle sessions

Use the shell script from  here  to obtain the details of the Oracle sessions using high CPU.  Usage: Log in as oracle user and navigate to the folder where the script has been copied into. Do not forget to grant execute permissions to the script prior to invoking it. $ ./top_oracle_sessions.sh [cpu_threshold]  e.g.1  $ ./top_oracle_sessions.sh 90       This will gather information if overall CPU usage is above 90% e.g.1  $ ./top_oracle_sessions.sh        This will gather information if overall CPU usage is above 50%. This is the default setting. Notes: Use the attached script to obtain the details of the Oracle sessions using high CPU. The script works by follows Takes 2 snapshots using Linux "top" command with a interval of 2 seconds between snaps Uses the data from the second snapshot to determine if the overall CPU usage is above a set threshold. The threshold is a conf...
Read more