ASM disk group and multiple databases

Hi,
I want to create a second database on my RAC cluster. Can the ASM diskgroups I have defined for use with the first database , service the second database or do I have to create another set of ASM diskgroups for the second dataabase?
Thanks,
Anne

ASM does not have any data files. ASM will store data files required for the RDBMS instance only.
After you have installed the Oracle binaries, (best practice is to have two Oracle homes one for ASM and another for RDBMS), you can create the ASM instances using DBCA and during this process or later can create ASM diskgroups.
( e,g disk1G, disk2G,disk3G,disk4G) using the above four you can create ASM DISK GROUPS..

Similar Messages

Share an ASM disk group among multiple nodes

According to Oracle documentation:
*“To share an ASM disk group among multiple nodes, you must install Oracle Cluster ware on all of the nodes, regardless of whether you install Oracle RAC on the nodes”.*
And if I understand it right to share the same ASM storage group from multiple nodes from separate RACs or multiple non-RAC nodes ASM instances in those nodes need to communicate to synchronize ASM related metadata using same technique like cache fusions.
My question is how this ASM communication take place among different ASM instances located in different RACs and standalone servers. Do we have to have some kind of Interconnect settings among the nodes?

Hi,
ASM and database instances require shared access to the disks in a disk group. ASM instances manage the metadata of the disk group and provide file layout information to the database instances.
ASM instances can be clustered using Oracle Clusterware; there is one ASM instance for each cluster node. If there are several database instances for different databases on the same node, then the database instances share the same single ASM instance on that node.
If the ASM instance on a node fails, then all of the database instances on that node also fail. Unlike a file system failure, an ASM instance failure does not require restarting the operating system. In an Oracle RAC environment, the ASM and database instances on the surviving nodes automatically recover from an ASM instance failure on a node.
see this link
http://download.oracle.com/docs/cd/B28359_01/server.111/b31107/asmcon.htm :)

Can 1 ASM Disk group serve multiple RAC DBs?

DB version: 11gR2
Platform : Sun OS 5.10
Number of Nodes : 2
We currently have a 2 node RAC DB called PMDB1 running with a Disk group called DG1_DATA of 1 Tera Byte.
We would like to add another Database in this cluster.
Can this DB use the same Disk Group (DG1_DATA) which PMDB1 use?

Hi Haiti
Can this DB use the same Disk Group (DG1_DATA) which PMDB1 use?Yes. No problem.
One ASM instance in RAC can be associated with several DBs' instances. Right?Right
Regards,
Levi Pereira

Difference between ASM Disk Group, ADVM Volume and ACFS File system

Q1. What is the difference between an ASM Disk Group and an ADVM Volume ?
To my mind, an ASM Disk Group is effectively a logical volume for Database files ( including FRA files ).
11gR2 seems to have introduced the concepts of ADVM volumes and ACFS File Systems.
An 11gR2 ASM Disk Group can contain :
ASM Disks
ADVM volumes
ACFS file systems
Q2. ADVM volumes appear to be dynamic volumes.
However is this therefore not effectively layering a logical volume ( the ADVM volume ) beneath an ASM Disk Group ( conceptually a logical volume as well ) ?
Worse still if you have left ASM Disk Group Redundancy to the hardware RAID / SAN level ( as Oracle recommend ), you could effectively have 3 layers of logical disk ? ( ASM on top of ADVM on top of RAID/SAN ) ?
Q3. if it is 2 layers of logical disk ( i.e. ASM on top of ADVM ), what makes this better than 2 layers using a 3rd party volume manager ( eg ASM on top of 3rd party LVM ) - something Oracle encourages against ?
Q4. ACFS File systems, seem to be clustered file systems for non database files including ORACLE_HOMEs, application exe's etc ( but NOT GRID_HOME, OS root, OCR's or Voting disks )
Can you create / modify ACFS file systems using ASM.
The oracle toplogy diagram for ASM in the 11gR2 ASM Admin guide, shows ACFS as part of ASM. I am not sure from this if ACFS is part of ASM or ASM sits on top of ACFS ?
Q5. Connected to Q4. there seems to be a number of different ways, ACFS file systems can be created ? Which of the below are valid methods ?
through ASM ?
through native OS file system creation ?
through OEM ?
through acfsutil ?
my head is exploding
Any help and clarification greatly appreciated
Jim

Q1 - ADVM volume is a type of special file created in the ASM DG. Once created, it creates a block device on the OS itself that can be used just like any other block device. http://docs.oracle.com/cd/E16655_01/server.121/e17612/asmfilesystem.htm#OSTMG30000
Q2 - the asm disk group is a disk group, not really a logical volume. It combines attributes of both when used for database purposes, as the database and certain other applications know how to talk "ASM" protocol. However, you won't find any general purpose applications that can do so. In addition, some customers prefer to deal directly with file systems and volume devices, which ADVM is made to do. In your way of thinking, you could have 3 layers of logical disk, but each of them provides different attributes and characteristics. This is not a bad thing though, as each has a slightly different focus - os file system\device, database specific, and storage centric.
Q3 - ADVM is specifically developed to extend the characteristics of ASM for use by general OS applications. It understands the database performance characteristics and is tuned to work well in that situation. Because it is developed in house, it takes advantage of the ASM design model. Additionally, rather than having to contact multiple vendors for support, your support is limited to calling Oracle, a one-stop shop.
Q4 - You can create and modify ACFS file systems using command line tools and ASMCA. Creating and modifying logical volumes happens through SQL(ASM), asmcmd, and ASMCA. EM can also be used for both items. ACFS sits on top of ADVM, which is a file in an ASM disk group. ACFS is aware of the characteristics of ASM\ADVM volumes, and tunes it's IO to make best use of those characteristics.
Q5 - several ways:
1) Connect to ASM with SQL, use 'alter diskgroup add volume' as Mihael points out. This creates an ADVM volume. Then, format the volume using 'mkfs' (*nix) or acfsformat (windows).
2) Use ASMCA - A gui to create a volume and format a file system. Probably the easiest if your head is exploding.
3) Use 'asmcmd' to create a volume, and 'mkfs' to format the ACFS file system.
Here is information on ASMCA, with examples:
http://docs.oracle.com/cd/E16655_01/server.121/e17612/asmca_acfs.htm#OSTMG94348
Information on command line tools, with examples:
Basic Steps to Manage Oracle ACFS Systems

Need for multiple ASM disk groups on a SAN with RAID5??

Hello all,
I've successfully installed clusterware, and ASM on a 5 node system. I'm trying to use asmca (11Gr2 on RHEL5)....to configure the disk groups.
I have a SAN, which actually was previously used for a 10G ASM RAC setup...so, reusing the candidate volumes that ASM has found.
I had noticed on the previous incarnation....that several disk groups had been created, for example:
ASMCMD> ls
DATADG/
INDEXDG/
LOGDG1/
LOGDG2/
LOGDG3/
LOGDG4/
RECOVERYDG/
Now....this is all on a SAN....which basically has two pools of drives set up each in a RAID5 configuration. Pool 1 contains ASM volumes named ASM1 - ASM32. Each of these logical volumes is about 65 GB.
Pool #2...has ASM33 - ASM48 volumes....each of which is about 16GB in size.
I used ASM33 from pool#2...by itself to contain my cluster voting disk and OCR.
My question is....with this type setup...would doing so many disk groups as listed above really do any good for performance? I was thinking with all of this on a SAN, which logical volumes on top of a couple sets of RAID5 disks...the divisions on the disk group level with external redundancy would do anything?
I was thinking of starting with about half of the ASM1-ASM31 'disks'...to create one large DATADG disk group, which would house all of the database instances data, indexes....etc. I'd keep the remaining large candidate disks as needed for later growth.
I was going to start with the pool of the smaller disks (except the 1 already dedicated to cluster needs) to basically serve as a decently sized RECOVERYDG...to house logs, flashback area...etc. It appears this pool is separate from pool #1...so, possibly some speed benefits there.
But really...is there any need to separate the diskgroups, based on a SAN with two pools of RAID5 logical volumes?
If so, can someone give me some ideas why...links on this info...etc.
Thank you in advance,
cayenne

The best practice is to use 2 disk groups, one for data and the other for the flash/fast recovery area. There really is no need to have a disk group for each type of file, in fact the more disks in a disk group (to a point I've seen) the better for performance and space management. However, there are times when multiple disk groups are appropriate (not saying this is one of them only FYI), such as backup/recovery and life cycle management. Typically you will still get benefit from double stripping, i.e. having a SAN with RAID groups presenting multiple LUNs to ASM, and then having ASM use those LUNs in disk groups. I saw this in my own testing. Start off with a minimum of 4 LUNs per disk group, and add in pairs as this will provide optimal performance (at least it did in my testing). You should also have a set of standard LUN sizes to present to ASM so things are consistent across your enterprise, the sizing is typically done based on your database size. For example:
300GB LUN: database > 10TB
150GB LUN: database 1TB to 10 TB
50GB LUN: database < 1TB
As databases grow beyond the threshold the larger LUNs are swapped in and the previous ones are swapped out. With thin provisioning it is a little different since you only need to resize the ASM LUNs. I'd also recommend having at least 2 of each standard sized LUNs ready to go in case you need space in an emergency. Even with capacity management you never know when something just consumes space too quickly.
ASM is all about space savings, performance, and management :-).
Hope this helps.

How reInstall Gride Infrastructure and Use old ASM disk groups

<pre>Hello to all
I installed Grig Infrastructure 11gR2 on a standalone server (OS is Linux)
and I configured ASM and my database created on ASM
Conceive that my OS disk corrupted and OS doesn't start and the Gride Home is on that disk,
and I have to install OS again
My ASM disks are safe , Now how can I install Grig Infrastructure again somehow that it can use previous ASM disks
and disk groups and I don't oblige to create my database again ?
In the step 2 of installing Gride Infrastructure it has four options
<pre>
1.Install and configure Oracle Grid Infrastructure for a Cluster
2.Configure Oracle Grid Infrastructure for a Standalone Server
3.Upgrade Oracle Gride Infrastructure or Oracle Automatice Storage Management
4.Install Oracle Gride Infrastructure Software Only
</pre>
If I select the option 2 it wants to create a disk group again
I guess that I need to select option 4 and then do some configuration but I don't know what I must configure
Do you know answer of my question , if yes please explain it's stages
Thank you so much
</pre>

Hi,
no you are not obliged to recreate your database again. However there is a small flaw in the installation procedure, which does not make it 100% easy...
When you installed the Oracle Restart (Standalone GI), your ASM diskgroup will contain the SPFILE of the ASM instance. And this is exactly the small flaw you will be encountering. So you have 2 options for "recovery":
1.) Do a software only install (4), and run roothas.pl. This however will not create any ASM entries. You would have to add it manually (using srvctl) and you can specify the ASM Spfile with the srvctl command. Problem here is however to have to know where your ASM spfile has been. If you have a backup of your OLR and a backup of the GPNP profile, this might be easier to find out.
2.) Do a new installation (2) and configure a new diskgroup (with a "spare" disk or small lun and a new name), that Oracle restart creates ASM instance and the new ASMSpfile for you.
Then you can simply mount the diskgroup containing your database additionally. You then shoudl however move your new ASMSpfile to the new diskgroup (or simply exchange it with the existing one). In this case it is easier to find out where it was - however you will need a spare (though small) LUN for the new spfile (temporarily, until you exchange it).
In either case after you have your ASM instance back (and access to your old diskgroup), you have to reregister your database and services - if you do not have an OLR backup.
Again => It is doable and you can simply mount the ASM diskgroup containing your database. However I suggest you try this one time to know what really needs to be done in this case.
Regards
Sebastian

Standby Database ASM Disk Groups

Hi Guys
I wonder if anyone can tell me - does a standby database have to have an identical configuration for its ASM Disk Groups?
My production database has two disk groups, one for data and the other for temp. Can I get away with a single diskgroup in my standby database or would I need two of the same name as the production database?
Cheers
Simon

Hi Saml
I have been busy googling at the same time as discussing this and it would appear that it will use the db_file_name_convert:
http://asanga-pradeep.blogspot.com.au/2012/07/11gr2-standalone-data-guard-with-asm.html
The link above shows the output of someones RMAN session where the OMF names are changed automatically. Problem is that some people are recommending that the parameter not be used, so now I am really confused!
I think I will try the parameter, if it doesnt work or the duplicate fails I will drop the temp table space in production and then do the duplicate, then recreate the temp tablespace. I can do that because there will be no one on the system on Sunday when I do it.
Thanks again for your help - I will let you know how it goes.
Ragards
Simon

RE: Creation of two oracle database in Single ASM Disk group

IS it possible to create two oracle database in Single ASM Disk group. if it is possible how?.
Giri

All you have to do is to create a tablespace at the most minimumlevel and your db would become a client of the disk group. Other than that, you can migrate your db tothe disk group and it would be then start using the same disk group shared by another database for its use also.
HTH
Aman....

Recover OCR and VOTE disk after complete corruption of ASM disk groups.

Hi Gurus,
I am simulating a recovery situation to perform recover of OCR and Vote files after complete corruption of ASM related disks and diskgroups. I have setup my environment as follows:\
Environment: RAC
OS: OEL 5.5 32-bit
GI Version: 11.2.0.2.0
ASM Disk groups: +OCR, +DATA
OCR, Vote Files location: +OCR
ASM Redundancy: External
ASM Disks: /dev/asm-disk1, /dev/asm-disk2
/dev/asm-disk1 - mapped on +OCR
/dev/asm-disk2 - mapped on +DATA
With the above configuration in place I have manually corrupted +OCR, +DATA diskgroups with dd command. I used this command to completely corrupt +OCR disk group.
dd if=/dev/zero of=/dev/asm-disk1. I have manual backups as well as automatic backups of OCR and Vote disk. I am not using ASMLib.
I followed this link:
http://docs.oracle.com/cd/E11882_01/rac.112/e17264/adminoc.htm#TDPRC237
When I tried to recover OCR file, I could not do so as there is no such diskgroup which ASM can restore the OCR, Voting disk to. I could not Re-create OCR and DATA diskgroups as I cannot connect to ASM instance. If you have a solution or workaround for my situation please describe it. That will be greatly appreciated.
Thanks and Regards,
Suresh.

Please go through the following document which have the detailed steps to restore the OCR
How to restore ASM based OCR after complete loss of the CRS diskgroup on Linux/Unix systems [ID 1062983.1]

EM Alert: Warning:+ASM Disk Group requires rebalance

Environment:
O.S Version : HP-UX B.11.31 U ia64
Oracle DB Version : 11.2.0.3.0 , Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
Database files are on : ASM Disk Group
It is about the ASM Diskgroup low disk space alert by Oracle Enterprise Manager.
Message=Disk Group DG_FLASH_01 requires rebalance because at least one disk is low on space.
Metric=Disk Minimum Free (%) without Rebalance
Metric value=18.961548
Disk Group Name=DG_FLASH_01
Severity=Warning
Target Name=+ASM_dbsrver.siva.com
Target type=Automatic Storage Management
There is only 1 LUN assigned to this diskgroup +DG_FLASH_01_.
We have a Oracle Enterprise Manager Grid Control Job MN_DBSRVR_DEL_ARCHIVELOGS runs every 12 hours by 1 AM and again at 1PM daily. It cleans-up the archivelogs older than 3 days old. The FLASH diskgroup is continuously being written with new files for both archivelogs and flashback logs.
If there was multiple disks and a vast difference between the files on the different LUNs then a rebalance would be good to run.
How to address such recurring alert of " *Disk Group DG_FLASH_01 requires rebalance because at least one disk is low on space*. " with _only one LUN on the +ASM Diskgroup_?

As I stated earlier there is only one disk on this diskgroup
DISK_NUMBER      OS_MB   TOTAL_MB    FREE_MB NAME                           PATH
          0      65536      65536      12995 DG_FLASH_01_0000        /devasm/gc/ora_asm_gc_b03_a14_d10_08_36
          0      65536      65536      43064 DG_DATA_01_0000         /devasm/gc/ora_asm_gc_b03_a13_d12_08_35So disk REBALANCE not required
Edited by: Sivaprasad S on Feb 14, 2013 11:46 PM

DBCA did not see the ASM disk group in NODE 2 but see in NODE 1

Are there anyone who encountered creating a database using DBCA with ASM as file system?
Our issue before is in both nodes the DBCA did not see the ASM disk group.
But after setting the TNS_ADMIN in both nodes and running the DBCA as administrator in Node 1, the DBCA able to see now the ASM disk group. Unfortunately, in Node 2 it didn't work out?
So we didn't know why is it from Node 2, the DBCA still didn't see the ASM disk group?Since it is both the same.
Any ideas? Please advise.
For you information, we are using Windows 64-bit, Oracle 11g R2
Thank you in advance for those who will respond.
Edited by: 822505 on Dec 20, 2010 7:47 PM

822505 wrote:
Are there anyone who encountered creating a database using DBCA with ASM as file system?
Our issue before is in both nodes the DBCA did not see the ASM disk group.
But after setting the TNS_ADMIN in both nodes and running the DBCA as administrator in Node 1, the DBCA able to see now the ASM disk group. Unfortunately, in Node 2 it didn't work out?
So we didn't know why is it from Node 2, the DBCA still didn't see the ASM disk group?Since it is both the same.
Any ideas? Please advise.
For you information, we are using Windows 64-bit, Oracle 11g R2
Thank you in advance for those who will respond.
Are the disks given to the ASM are visible from Node2?
Aman....

Oracle ASM disk group

Hi,
Having a multiple Oracle ASM disk group is more beneficial for Oracle database? if no why? if yes why?
Any metalink note if have.
thanks

Any metalink note do you refer?What is your database version?
Please see these docs.
11g ASM New Feature [ID 429098.1]
ASM 11g New Features - How ASM Disk Resync Works. [ID 466326.1]
Thanks,
Hussein

Oracleasm listdisks is not listing all disk groups and returning "strange special characters" and disks groups are dismounting unexpected

Hi everybody,
I have a 3 node Oracle Cluster with verstion 11.2.0.3.0 installed using ASM/ACFS/ADVM.
Red Hat 5.7 - Kernel 2.6.18-371.12.1.el5 64bits
OracleASM version:
     oracleasm-support-2.1.8-1.el5
     oracleasm-2.6.18-371.12.1.el5-2.0.5-1.el5
     oracleasmlib-2.0.4-1.el5
On may, 2014 we had a physical failure in our storage system and all our disk partitions were completely lost.
The Oracle Grid Infrastructure and Oracle RDBMS haven't needed to be reinstalled because they were healthy.
The Oracle Cluster Registry (OCR) was lost (it was composed by three ASM disk groups in a redundant structure) and after recreation of the OCR disk groups I recover the Oracle Registry information from backup.
All cluster information were recovered (listener, SCAN, VIP, databases and services)
Databases could not be started because all ASM disk groups have been lost and oracle ASM instance (asmcmd -p) was showing all disk groups, but they were all "empty" - the physical partition related with them were recreated.
All the "old" disk groups were dropped, and the "new" disk groups were recreated and all the backups from the databases were restored.
After all services were up, and the environment seems to be OK, I check the healthiness of it, by executing the oracle cluster post-installation tool and others verify tools (crsctl and srvctl), well all returning messages saying that the environment was completely OK and no errors were found or generated (including in many log files I have inspected)
After 2 weeks from the completely recover of the environment, without any error/failure message been received from it, the disk groups started to dismount unexpectedly, from whatever node and not only one specific disk group stops, but any one of them, any time.
I opened a SR in Metalink (Oracle Support) and they conduct me to upgrade RedHat kernel version and OracleASM version.
Simultaneously I opened a Case Solution in RedHat to help me identify the better way to do the upgrade in advantage of the Oracle specifications.
From:
rpm -qa | grep kernel
kernel-devel-2.6.18-274.el5
kernel-headers-2.6.18-274.el5
kernel-2.6.18-274.el5
rpm -qa | grep oracleasm
oracleasm-support-2.1.8-1.el5
oracleasmlib-2.0.4-1.el5
oracleasm-2.6.18-274.el5-2.0.5-1.el5
To:
rpm -qa | grep kernel
kernel-devel-2.6.18-371.12.1.el5
kernel-2.6.18-371.12.1.el5
kernel-headers-2.6.18-371.12.1.el5
rpm -qa | grep oracleasm
oracleasm-support-2.1.8-1.el5
oracleasm-2.6.18-371.12.1.el5-2.0.5-1.el5
oracleasmlib-2.0.4-1.el5
Well, after this upgrade less times the disk groups dismounted, but they continue dismounting from whatever node, any disk group, any time.
So, I opened another SR in Metalink (3-10143566371 still open) and they are conducting me again to upgrade the RedHat kernel version and OracleASM version.
Information about OracleASM:
# oracleasm listdisks
ACFS
FRA
OCR01
OCR02
OCR03
$ asmcmd -p
ASMCMD [+] > ls -l
State    Type    Rebal Name
MOUNTED EXTERN N      ACFS/
MOUNTED EXTERN N      ARCH/
MOUNTED EXTERN N      DEV/
MOUNTED EXTERN N      DIR_LOG/
MOUNTED EXTERN N      JAVA_ARCHIVE/
MOUNTED EXTERN N      MSAF/
MOUNTED NORMAL N      OCR/
MOUNTED EXTERN N      PRD_DATA/
MOUNTED EXTERN N      PRD_REDO1/
MOUNTED EXTERN N      PRD_REDO2/
MOUNTED EXTERN N      PRD_REDO3/
MOUNTED EXTERN N      PRD_REDO4/
MOUNTED EXTERN N      RASTR/
MOUNTED EXTERN N      STAGE/
This is what happens when execute "oracleasm scandisks":
# oracleasm scandisks
Reloading disk partitions: done
Cleaning any stale ASM disks...
Scanning system for ASM disks...
Instantiating disk "ùìÿÿÿÿÿÿÿÿÿÿÿìóæþÿ¥Ï¨®Ð¢"
Unable to instantiate disk "ùìÿÿÿÿÿÿÿÿÿÿÿìóæþÿ¥Ï¨®Ð¢"
Instantiating disk "ü´ñõ
                        ñõúìsö"
Unable to instantiate disk "ü´ñõ
                                ñõúìsö"
~±Ã1~u·}cÿ-Ûg disk "
¾s
~±Ã1~u·}cÿ-Ûinstantiate disk "
¾s
Instantiating disk "à·Öªß³Ö½Þ®hìëÖßßÞÖÛÜØÖÕ"
Unable to instantiate disk "à·Öªß³Ö½Þ®hìëÖßßÞÖÛÜØÖÕ"
Instantiating disk "êËbkî,c
~,XZ±´b¹u²´biÅr"
Unable to instantiate disk "êËbkî,c
~,XZ±´b¹u²´biÅr"
Instantiating disk "
PuTTYPuTTYUnable to instantiate disk "
kÍ3|úùõ/øÊInstantiating disk "u
i)ïìL"
kÍ3|úùõ/øÊe to instantiate disk "u
My question is: "This will really solve the problem?"
Another: "Oracle really understood what is happening and they can help me to solve this problem?"
Final: "Can anyone please help me this problem?"

Hi,
my two cent.
Wait for the SR feedback.
But for the future I advice you to do an ASM Metadata backup to be able to restore this data if you lost
configurations or complete disks and so on.
asmcmd md_backup -b <Pfad>/Filename
and also an ocrconfig backup via crontab.
ocrconfig -local -manualbackup
regards

ASM Disk Group RAID Levels

This is the scenario that I am currently working on. Just need some input on whether it is feasible or not.
We have a 2 node RAC running Oracle 10.2.0.3 on AIX 5L. Database size is ~2TB. The database mostly performs OLTP but also stores some historical data.
There are two main applications using the database - one performs high reads with some small updates & inserts, while the other is very write intensive but does some reads as well.
Currently there are three disk groups one for the tablespaces (dg_data), another for system/sysaux/undo tablespaces (dg_system) and another for archived logs & redo log copies (dg_flash) - all using external redundancy. ASM best practises recommend no more than 2 disk groups. It also recommends disk groups with disks of similar characteristics including raid levels. However, the dg_data disk group has both RAID 5 and RAID 1+0 disks which house tablespaces for both applications. Seeing that the applications have different requirements (heavy reads vs heavy writes) does it make sense to create a separate disk group with 2 different RAID levels or would using RAID 5 in dg_data satisfy both requirements?

I am attempting to generate some statistics on the ASM Disks I/O activity before implementing the disk group separation in order have some metrics for comparison purposes. Enterprise Manager Grid Control displays the performance of disk groups and individual disks by showing the Disk Group I/O Cumulative Statistics. When comparing the results with the asmiostat output I am unable to correlate the results. I know that the asmiostat queries the v$asm_disk_stat view. Where does EM GC pull it's information from?
For example, I run the following query on the ASM instance:
SQL> select group_number,disk_number,total_mb,free_mb,name,path,reads,writes,read_time,write_time,bytes_read,bytes_written
2 from v$asm_disk_stat
3 where group_number=
4 (select group_number from v$asm_diskgroup
5* where name = 'DG_FLASH')
GROUP_NUMBER DISK_NUMBER TOTAL_MB FREE_MB NAME PATH READS WRITES READ_TIME WRITE_TIME BYTES_READ BYTES_WRITTEN
1 0 8671 8432 DG_FLASH_0000 /dev/asm2 14379476 10338479 149205.75 19633.64 290,136,450,560.00 7.2165E+10
1 1 8671 8431 DG_FLASH_0001 /dev/asm3 11470508 10278698 184597.5 19313.54 249,769,027,584.00 9.2911E+10
1 2 8671 8432 DG_FLASH_0002 /dev/asm4 17274529 8743188 178547.56 38342.52 339,439,240,192.00 6.7165E+10
The output from the same period on Grid Control is below
MEMBER DISKS AVG RESPTIME AVG THROUGHPUT TOT I/O TOT RDS TOT WRTS RDERRS WRTERRS
DG_FLASH_0000 5.58 2.58 33179503 21949607 11,229,896 0 0
DG_FLASH_0001 8.26 1.83 25752100 13131695 12,620,405 0 0
DG_FLASH_0002 8.11 1.86 28269693 18798823 9,470,870 0 0
The statistics in the query are lower than those in the EM GC report. I also tried querying the fixed views (x$) but the results were even more confusing.
What is the best method for comparing and gathering statistics on ASM activity?

How to move or migrate whole directories between ASM disk groups?

Hello everyone!
I'm playing around with Oracle ASM and Oracle Database (11g R1), I'm a student. This is just for testing purposes.
Computer specifications are:
Processor: Intel Pentium 4 HT 3.00 Ghz.
RAM Memory: 2 GB.
Hard Disk: 250 GB
O.S.: Windows XP Professional Edition SP 2.
I installed Oracle ASM, I created an ASM disk group (+FRA), I installed Oracle Database and I created a testing database. The database is working properly over the ASM disk group. Days ago, I got help about the initialization parameters DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_1, DB_CREATE_ONLINE_LOG_DEST_2 and DB_RECOVERY_FILE_DEST, based on their function, I created another 3 ASM disk groups (+FILES, LOG1, LOG2). Currently, the four initialization parameters are pointing to its corresponding ASM disk group. As you can deduce, at the installation moment of the Oracle Database I used the ASM disk group "+FRA" and inside it were created the directories: CONTROLFILE, DATAFILE, ONLINELOG, PARAMETERFILE, TEMPFILE and the SPFile.
My point is I wanna move or migrate the directories DATAFILE, PARAMETERFILE, TEMPFILE and the SPFile to "+FILES", ONLINELOG and CONTROLFILE to "+LOG1" and "+LOG2", this way, the ASM disk group "+FRA" will contain the Flash Recovery Area only. What is the procedure to do this?
Thanks in advance!

user1987306 wrote:
Hello everyone!
My point is I wanna move or migrate the directories DATAFILE, PARAMETERFILE, TEMPFILE and the SPFile to "+FILES", ONLINELOG and CONTROLFILE to "+LOG1" and "+LOG2", this way, the ASM disk group "+FRA" will contain the Flash Recovery Area only. What is the procedure to do this?
Thanks in advance!
Hi,
There are couple of approaches you can use, here is some of them
- To move datafile, start the database in mount state
RMAN > copy datafile '+FRA/xxx' to '+FILES1';
SQL > alter database rename file '+FRA/xxx' to '+FILES1/xxx';
- To move tempfile
SQL > alter tablespace TEMP add tempfile '+FILES1' SIZE 10M;
SQL > alter database tempfile '+FRA/xxx' drop;
- To move onlinelog
SQL > alter database add logfile member '+LOG1' to group 1;
SQL > alter database add logfile member '+LOG2' to group 1;
SQL > alter database drop logfile member '+FRA/xxx';
- To move controlfile
SQL > restore controlfile to '+FILES1' from '+FRA/xxx';
update the spfile to reflect new location of controlfile
Cheers

ASM disk group and multiple databases

Similar Messages

Maybe you are looking for