Last night I was working through some of the ASM Global Dynamic Views.
I was wondering, why both GV$ASM_DISKGROUP_STAT and GV$ASM_DISKGROUP are having same columns and showing the same data.
I got a nice explanation from www.orafaq.com. (Link: http://www.orafaq.com/wiki/ASM_FAQ)
GV$ASM_DISKGROUP_STAT fetches data from cache while
GV$ASM_DISKGROUP fetches data from disk headers.
The former view (%_stat) operates faster than the later.
Moreover, they suggested to change the references of GV$ASM_DISKGROUP to GV$ASM_DISKGROUP_STAT in $ORACLE_HOME/bin/asmcmdcore, if someone feels that, asmcmd command line utility is slow.
There are 4 references of GV$ASM_DISKGROUP in "asmcmdcore" file.
(These findings are applicable to oracle 10.2.0.3 EE. Readers kindly check the documentation of their Db version)
I was wondering, why both GV$ASM_DISKGROUP_STAT and GV$ASM_DISKGROUP are having same columns and showing the same data.
I got a nice explanation from www.orafaq.com. (Link: http://www.orafaq.com/wiki/ASM_FAQ)
GV$ASM_DISKGROUP_STAT fetches data from cache while
GV$ASM_DISKGROUP fetches data from disk headers.
The former view (%_stat) operates faster than the later.
Moreover, they suggested to change the references of GV$ASM_DISKGROUP to GV$ASM_DISKGROUP_STAT in $ORACLE_HOME/bin/asmcmdcore, if someone feels that, asmcmd command line utility is slow.
There are 4 references of GV$ASM_DISKGROUP in "asmcmdcore" file.
(These findings are applicable to oracle 10.2.0.3 EE. Readers kindly check the documentation of their Db version)
No comments:
Post a Comment
Kindly make your valuable and progressive comments here.
Junks will be deleted without notice :-)